You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by "Shaun T. Erickson" <st...@smxy.org> on 2004/03/28 08:41:40 UTC
Site-wide SA vs Per-user SA
I want to be able to use SA (from within amavisd-new, as a postfix
before-queue content filter) to block the worst of the spam from even
getting onto my system, say, everything above some preset level.
But of the mail that makes it onto the system, I'd really like my users
to be able to set their own spam-thresholds, and to be able to use
[white/black]lists on the mail that actually makes it to their mailbox.
Is there any way to accomplish this? I guees I'm looking for the best of
both worlds ...
-ste
Re: Site-wide SA vs Per-user SA
Posted by Tom Emerson <os...@pacbell.net>.
On Saturday 27 March 2004 10:41 pm, Shaun T. Erickson wrote:
> I want to be able to use SA (from within amavisd-new, as a postfix
> before-queue content filter) to block the worst of the spam from even
> getting onto my system, say, everything above some preset level.
>
> But of the mail that makes it onto the system, I'd really like my users
> to be able to set their own spam-thresholds, and to be able to use
> [white/black]lists on the mail that actually makes it to their mailbox.
>
> Is there any way to accomplish this? I guees I'm looking for the best of
> both worlds ...
Actually, I think this would be mostly automatic. Since SA will have been run
against the message, the SA headers will be in the message when it gets "to
the user". (meaning they can apply their own rules based on the SA headers.)
All you have to decide is what your highest "false positive" will likely be
-- 7 points, 10, 15, or whatever -- then set your prefilter to block/discard
anything that is higher than this threshold.
--
Top o' the Blog: Google Nirvana gone bye-bye?
http://osnut.homelinux.net/mtblog/ya_index.html