Reindl Harald wrote: > Am 14.03.2013 17:07, schrieb Kris Deugau: >> Sieve can't call outside programs (eg SpamAssassin) by design. IMO the >> inability to call any external filtering programs (even from a >> restricted whitelist) makes overall mail filtering significantly harder
By "harder" I mean that you end up going to a great deal of trouble to properly deal with a message that user A really, really wants in their Inbox, and which user B never ever EVER wants to see at all. > usually sieve comes AFTER SpamAssassin because it is a broken > setup using a pre queue filter because it results in become > a backscatter and you are usually not permitted by law > accept a message with "250 OK" and drop it silent Laws vary by region. So far as my personal mail handling goes, I also want to divert eg mailing lists like this one to a mail folder *before* calling an expensive content filter on a message that isn't spam. Wearing my ISP mail admin hat, we don't use procmail, but the mail flow would be entirely compatible; there are several stages of filtering and each one can short-circuit the process and deliver the message (either to the Inbox or the Spam folder), instead of having to run *everything* through an expensive SpamAssassin scan. -kgd
