This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/anti-abuse-wg@ripe.net/
[anti-abuse-wg] Abuse Reporting Issues
- Previous message (by thread): [anti-abuse-wg] Abuse Reporting Issues
- Next message (by thread): [anti-abuse-wg] Abuse Reporting Issues
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Arnold
wiegert at telus.net
Thu Mar 14 10:20:35 CET 2013
On 3/12/2013 6:03 PM, Leo Vegoda wrote: > Hi, > > Arnold wrote: > > [...] > >> First I look up the originating IP address in the source code of the >> SPAM message, >> plug it into a WhoIs look up via the IANA ipv4-address-space.xml files. > Why would you do this instead of using the whois service at whois.iana.org or http://www.iana.org/whois? The whois service will always return the most specific answer in an IANA registry. > > Regards, > > Leo Because that way it is all contained within my SPAM reporter program. Assuming that IANA updated their DB files at reasonable intervals - my program checks to see if it has the latest file and if not it downloads the latest one - so it should end up being much easier - no cut-n-paste. Only if I can't find it within the latest IANA data do I consult other sources and in several years worth of using this, most of the time IANA does the job for me. Arnold -- Fight Spam - report it with wxSR 0.5 - ready for Vista & Win7 http://www.columbinehoney.net/wxSR.shtml
- Previous message (by thread): [anti-abuse-wg] Abuse Reporting Issues
- Next message (by thread): [anti-abuse-wg] Abuse Reporting Issues
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]