Why can't you just use the built-in Greylist Opt-in / Opt-out? Then all that user's mail will pass Greylisting and head into SpamAssassin, where it'll be tagged and dumped accordingly.

##
# Greylist Opt-in / Opt-out
########################################

  Certain accounts / spamtraps / users do not want greylisting.
  Opt-in/out can be enabled in policyd.conf

  _priority is an indication of which entry has the highest preference.

So for example, if you want only ONE user to be subjected to greylisting
  for the domain mweb.co.za:

  1 == Opt-in
  0 == Opt-out

INSERT INTO policy (_rcpt,_optin,_priority) VALUES ('@mweb.co.za', 0, 10);
  ^^ above mweb.co.za is by default opted out.

INSERT INTO policy (_rcpt,_optin,_priority) VALUES ('[EMAIL PROTECTED]', 1, 50); ^^ above [EMAIL PROTECTED] has a higher priority therefore will override the
     first rule

This allows for mixed and matched configurations. So another example, if you want everyone for the domain to be subjected to greylisting EXCEPT
  for [EMAIL PROTECTED]:

INSERT INTO policy (_rcpt,_optin,_priority) VALUES ('@mweb.co.za', 1, 10);
  ^^ above mweb.co.za is by default opted in.

INSERT INTO policy (_rcpt,_optin,_priority) VALUES ('[EMAIL PROTECTED]', 0, 50); ^^ above [EMAIL PROTECTED] has a higher priority therefore will override the
     first rule (and thus be opted out)

-Rob

On Feb 28, 2007, at 1:36 AM, Michael Brennen wrote:

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

--
Robert A. Pickering Jr.              SixDoes IT Solutions

"I just the other day got, an internet was sent by my staff at 10 o'clock in the morning on Friday and I just got it yesterday. Why? Because it got tangled up with all these things going on the internet commercially." -- Sen. Ted Stevens (R-Alaska)


-------------------------------------------------------------------------
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

Reply via email to