On Thu, May 30, 2002 at 04:09:01PM +0200, Tony L. Svanstrom wrote:
> No no no... not making it a rule with a negative score, but making SA ignore
> what looks like information another SA might have added.
That's a job for your procmail filter. How does SA know what another SA
put into the message? (it's all configurable you know)? The only thing
you're guaranteed about are the message headers (not including Subject
since it's configurable). ie: X-Spam-* ...
Personally, I do the following in my procmailrc:
:0fW
* ^X-Spam-Flag: YES
| formail -A "X-Reject: Previous Spamassassin match!"
:0E
{
INCLUDERC=$HOME/.procmail.d/spamassassin
INCLUDERC=$HOME/.procmail.d/spam
}
:0
* ^X-Reject
spam-work
So, if a message comes in and it's already marked as spam, I don't
bother running spamassassin again, I just add my X-Reject header and
let the last rule save it into a different folder. Spammers wouldn't
put a positive header in their mails, so this is safe.
If the incoming message isn't already marked as spam, I know that there's
not going to be any markup in the body and such, so I run SA over it.
A spammer can put in whatever they want in the header, SA will still
run over their message.
Anything else, like trying to look for SA-related phrases and such in
the header/body, just gives spammers an easy way out from being scanned.
In this case, you would probably want to keep a small cache of who you
sent an autoresponse to, and only send one every X days, ala vacation.
--
Randomly Generated Tagline:
"Hey, you're shaped like buddah, millions of people follow him!"
- The Drew Carey Show
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
