On Sun, 22 Jun 1997, T.C. Thomas wrote:
On Sun, 22 Jun 1997, Tim wrote:
This is a good example here of how not properly making sure UCE you are
bouncing is being bounced to a list (read: A bad thing).
[SNIP!]
Basically, *please* don't bounce mailing list spam back to the mailing
list.
This is a bug in SpamBouncer. It apparently grabbed the mailing list
address along with the rest. I have taken SpamBouncer offline, and welcome
all suggestions regarding modifications that would remedy the situation.
I do a two-level filtering at my ISP.
First is checking if the messages is to a mailing list. If the message is
to a mailing list, then it gets a header such as
X-MailingList: procmail
after that I do checking for Spam -- I have modified the SpamBouncer you
are using to insert headers like this:
X-Spam: passed
(if the message did not contain any header info that flagged it as spam)
or
X-Spam: Cyberpromo
if the message matched, and the word tells me what recipe it matched.
Doing this, I can determine what spam gets auto-replied and what does not.
:0
* !^X-Spam: passed
{
:0
* !^X-MailingList
SpamToMailingList
recipe to file or bounce, or both
}
At the moment I am not bouncing any messages, as I am still beta testing
the spam check recipes. However, this method should prevent any messages
going to any mailing lists which I have presorted.
TjL
--
TjL <luomat(_at_)peak(_dot_)org> / http://www.peak.org/~luomat/next/
NeXT bookmarks: http://www.peak.org/~luomat/next/bookmarks.html
*** Starting July 2nd I will be taking Hebrew. Email and Usenet
response time will be noticeably slower. ***