At 18:04 2002-09-13 -0700, Hack Hawk wrote:
[snip]
------ Here's the details -------------
Return-Path: <marmitek(_at_)mail(_dot_)com>
Received: from 200.38.225.6 ([217.167.180.65])
by denali.nightsource.com (8.11.0/8.11.0) with SMTP id g8DAgho31277
for <pmhh(_at_)hackhawk(_dot_)net>; Fri, 13 Sep 2002 03:42:44 -0700
[snip - argh!]
Note that if you were using the recently discussed filter "IP1 != IP2",
this would have been caught quite handily.
Further, the IP (the actual one, in brackets) is listed in bl.spamcop.net
and relays.osirusoft.com (no doubt others as well, but I just checked it
against some of the blacklists I use, and this spam would clearly have been
rejected at the SMTP stage if it were sent to me).
If more people USED procmail and other tools instead of using this list to
moan about their individual spam woes, they might not get nearly so much spam.
Oh, jeez, ANOTHER post of the spam too...
216.72.57.66 is listed in bl.spamcop.net.
Look, everybody gets spam - heck, the PROCMAIL LIST itself sometimes is
spammed - the LIST itself delivering the spammers message. Adapt your
filters or learn to live with it. Start checking into DNSBLs - they're
generally very effective and will also reduce the amount of YOUR network
bandwidth which spammers consume.
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail