[18363] in North American Network Operators' Group
Re: SPAM, RE: Internic and there lame response
daemon@ATHENA.MIT.EDU (Anthony Sticha)
Mon Jul 13 10:32:23 1998
From: "Anthony Sticha" <ASticha@in.com.au>
To: "Andrea Di Lecce" <slinky@rogerswave.ca>,
"Dean Robb" <pceasy@norfolk.infi.net>
Cc: <nanog@merit.edu>, <RS-TALK@LISTS.INTERNIC.NET>
Date: Mon, 13 Jul 1998 06:00:44 +1000
X-MDaemon-Deliver-To: nanog@merit.edu
OK so what to do if their upstream does nothing? Like PBI
>>There are many other ways to track a spammer.
>>
>>- Do nslookup on the IP that originated the spam (sometimes this takes a
>>bit of detective work to find what IP actually originated the spam).
>>- Traceroute to the originating IP. Email the ISP that is directly
upstream.
>
>*I* know these techniques. Joe User who's irritated at his spam likely
>does not.
>
>>- Look in the Whois information for contact emails and nameservers - if
>>these are for the upstream ISP, or some ISP other than the spammer, report
>>it to them.
>
>But there's the rub. A great deal of the information (including
>delegations) in domain registrations by net.abusers is complete
>fabrication. InterNIC refuses to deal with it, even when it's pointed out
>to them.
>
>>- If they are advertising a web page, track the web page host, and their
>>upstream, and report it to them.
>
>All the time :>
>>
>>>What do spammers and nails have in common? They're both intended for
>>>hammering.
>>
>>Amen.
>
>Witnesses available at www.witness.com...:)
>
>
>What do spammers and nails have in common? They're both intended for
>hammering.
>
>Dean Robb
>PC-Easy
>On-site computer services
>(757) 495-EASY [3279]
>
>
>
