On Fri, Nov 22, 2002 at 09:22:51AM -0600, Chris Garrigues wrote:
>> From: Ronald Wiplinger <[EMAIL PROTECTED]>
>> 2. I use system wide SpamAssassin, which flags already recognized Spam,
>> and reduce so my willingness to read the e-mail.
>
>Here's what I do:
>
>I have Spam Assassin running on my firewall under qmail-scanner so all mail
>has the X-Spam-Status header before it gets to my mail server.
Up until recently I had been using spamassassin in addition to TMDA.
Spamassassin was first in the procmailrc. Everything that got by it went
to TMDA. I have now switched to using TMDA exclusively. Spamassassin was
getting too many false positives (i.e. spamassassin said an email was spam
but it wasn't). What's most worrisome was that of the false positives,
a large percentage of them were due to spamassassin thinking that TMDA
generated email addresses looked like spam addresses.
Email to some of my dated addresses and keyword addresses got marked
as spam, as well as a couple of harvested sender addresses. But most
disturbing was the fact that some of my friends confirmation responses
got marked by spamassassin as SPAM because of the confirm address in
the header and in the body.
Now, the email to the harvested sender addresses actually *was* spam.
So, to a certain extent spamassassin was doing its job. However, I would
have preferred spamassassin to have let TMDA do it's job, also. And I
was really disappointed that SA was calling confirmation responses spam.
Now, of course, I could have added a rule to spamassassin to recognize
TMDA address and lower the spam threshold. Possibly something like:
header TMDA_CONFIRM To =~ /-confirm-/
describe TMDA_CONFIRM To a TMDA confirm address
score TMDA_CONFIRM -4.00
header TMDA_DATED To =~ /-dated-/
describe TMDA_DATED To a TMDA dated address
score TMDA_DATED -4.00
header TMDA_SENDER To =~ /-sender-/
describe TMDA_SENDER To a TMDA dated address
score TMDA_SENDER -4.00
header TMDA_KEYWORD To =~ /-keyword-/
describe TMDA_KEYWORD To a TMDA dated address
score TMDA_KEYWORD -4.00
But, of course, I just grabbed the -4 score out of thin air. I don't
know if that's a good enough score to ensure that SA doesn't falsly
id TMDA addresses as spam. I could make the thrshold -400, I suppose.
But at that point what would spamassassin be doing for me that TMDA isn't?
It seemed to me it was time to get rid of the guess work and just let
TMDA do it's job.
So I got rid of spamassassin. Haven't had any more spam show up in my
mailbox, but my pending queue is bigger.
$.02.
- Mark
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
