Hi daniel, > > I don't see much point in tagging spam and then delivering > > it anyway. The spammers still got their message through. > > So what if it's in a special little folder all its own? > > The problem with this approach is that SpamAssassin is a heuristic > system. I have had a number of false positives on this list, for > example, over the last week. > > With your system, not only would I not know about this, I > would probably > have lost my subscription when the number of bounced messages got too > high...
That's why I do both: spam with a rating > 17 gets bounced at the smtp level; anything else gets a header "X-Spam-level: ****** (6.1)" (number and ***s obviously depending on SA hits) and an "X-Spam-Warning" header if > configured SA spam level (default 5). That way, each user can filter based on the X-spam-level header for individual treshhold or use x-spam-warning for preconfigured one. Also, to verify that 17 is a reasonable level to bounce, I use mimedefangs action_quarantine_entire_message with corresponding admin notification, so I get to see sender, recipient and headers (including SA report) for each bounced message; so far I haven't had false positives at bounce level, and quite a lot of spam never makes it to the users mailboxes at all. I much prefer using an smtp bounce for high probability spam - it sent directly by a massmailer, smtp errors might get the email address removed, and in case a legitimate message should be caught at least the sender gets a clean error message back and can take apropriate action. Bye, Martin _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
