Hello all,
I am running postfix, with policyd as the front end, and spampd, a
perl daemon, as the postfix content-filter shim to spamassassin.
It works well.
I have a client that would like to have all spam dumped into a
folder rather than reject any mail at all. I've recommended against
this for several reasons, as I think they will have too much junk to
sort through and will lose mail. But, that is what they think they
want.
A problem these days is spamassassin overload; I simply cannot
afford to send all incoming mail through spamassassin to determine
if it is spam. There is too much of it, and it is getting worse; no
surprises in that to anyone here I'm sure.
I have in mind to add a per destination domain feature to policyd to
allow mail from sources that would normally be rejected to be
accepted and tagged with a unique X- header. The mail would then
pass to spampd, which scans the headers before giving the mail to
spamassassin. If the particular X- header is seen, the mail would
be delivered as spam without going through spamassassin.
As I see it this would keep the spamassassin load down and give them
all the suspected mail. Any thoughts on this system, in particular
any downsides I've missed? Is there anything available that already
does this sort of thing? Thanks...
-- Michael
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
policyd-users mailing list
policyd-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/policyd-users
