On Tue, Feb 18, 2003 at 03:48:29PM -0700, al davis wrote: > A Spammer has the list. > > It took only one posting to this list to get spammed. > > Here's where it came from:
No, that's a random IP address followed by non-evidence. How do we know it really came from there? > > 4.40.163.14 > Server: 63.228.184.2 > Address: 63.228.184.2#53 > > Non-authoritative answer: > 14.163.40.4.in-addr.arpa name = > lsanca2-ar32-4-40-163-014.lsanca2.dsl-verizon.net. > > Authoritative answers can be found from: > 163.40.4.in-addr.arpa nameserver = dnsauth1.sys.gtei.net. > 163.40.4.in-addr.arpa nameserver = dnsauth2.sys.gtei.net. > 163.40.4.in-addr.arpa nameserver = dnsauth3.sys.gtei.net. > dnsauth1.sys.gtei.net internet address = 4.2.49.2 > dnsauth2.sys.gtei.net internet address = 4.2.49.3 > dnsauth3.sys.gtei.net internet address = 4.2.49.4 > > al@oliver:/home/al>ping 4.40.163.14 > PING 4.40.163.14 (4.40.163.14): 56 data bytes > 64 bytes from 4.40.163.14: icmp_seq=0 ttl=113 time=696.3 ms > 64 bytes from 4.40.163.14: icmp_seq=1 ttl=113 time=365.6 ms This all tells us nothing about the sammer. If you want to get proactive about spam, do something about it, like reporting it to the proper ISPs. Spamcop.net can get you started. It's considered extremely bad form to reply to spam, on or off list. -- .''`. Baloo <[EMAIL PROTECTED]> : :' : proud Debian admin and user `. `'` `- Debian - when you have better things to do than to fix a system
msg31652/pgp00000.pgp
Description: PGP signature
