> On Jan 24, 2016, at 11:29 AM, Martin Gregorie <[email protected]> wrote: > > On Mon, 2016-01-25 at 00:07 +0530, Sarang Shrivastava wrote: >> I am just a newbie who has started using SA. Someone on the mailing >> list suggested me to use -D option. So if this option is for >> debugging then how do we classify it ? >> > You don't classify it: that's SA's job. It only scores messages and > sets the Yes/No flag before adding the X-Spam-* headers to the message. > Nothing else. What you do with mail that SA has classified as spam is > the responsibility of your additional software and/or your users. > > Simplest case: configure SA to add [SPAM] as the first word in the > Subject header and let the users decide what to do with this mail. > > Next easiest: If your users' mail readers can detect spam and put it in > a spam folder, enable that feature for them once you've configured SA > to set whatever indicator the mail reader uses for spam identification. >
The best option I’ve found is to use sieve (filter) scripts (we have a default set we enable for all new users) that simply moves emails tagged as spam into a special folder for the user called SPAM. This allows them to have access to any false positives that may occur. Most common MDA/LDA’s have sieve script integration either by default or as a plugin module. For example Cyrus has timsieve server built it, and Dovecote has Pigeonhole, etc... > Beyond that: write a spam quarantine subsystem and install it in the > mail flow it where it can inspect messages that have been classified by > SA and quarantine or delete them. Of course, you'll also need some way > that your users can retrieve misclassified spam, and provide you with > feedback so you can correct misclassifications.... > > > Martin > >
