Re: Per user SPF and Anti Virus checks

5 msg	postfix/ldap - can one special_result_attribute...
2 msg	mailing list goes to bulk / spam folder
9 msg	SMTP Auth on multiple instances
4 msg	Auto-response, but not vacation
4 msg	bypassing reject_rbl_client for certain recipie...
12 msg	rewritten log

Per user SPF and Anti Virus checks
\ Paul G. Allen (31 Mar 2008)
. \ mouss (31 Mar 2008)
. . \ Ronald MacDonald (31 Mar 2008)
. \ Ronald MacDonald (31 Mar 2008)
. . \ mouss (31 Mar 2008)
. . . \ Paul G. Allen (31 Mar 2008)
. . . . \ Scott Kitterman (31 Mar 2008)
. . . . . \ Paul G. Allen (1 Apr 2008)
. . . . \ mouss (1 Apr 2008)
. . . . . \ Paul G. Allen (8 Apr 2008)
. . . . . . \ mouss (8 Apr 2008)

9 msg	Instance on policies
2 msg	Removing internal mailers from headers
7 msg	Open Relay issue
1 msg	Messages not picked up from active queue
3 msg	Semantics question about myorigin
22 msg	mime, header_checks question
3 msg	problem using greylist and gmail
9 msg	451 4.3.0 Error: queue file write error and vir...
5 msg	Network_biopair_interop errors
1 msg	what means error msg in auth.log (failed to map...
5 msg	problem upgrading from 2.4.5 to 2.5.1
5 msg	failover
13 msg	smtp_fallback_relay

Subject:	Re: Per user SPF and Anti Virus checks
Group:	Postfix-users
From:	Scott Kitterman
Date:	31 Mar 2008

On Monday 31 March 2008 19:31:18 Paul G. Allen wrote:
> mouss wrote:
> > Ronald MacDonald wrote:
> >> On 31/03/2008, Paul G. Allen <paul.allen> wrote:
> >>> [snip]
> >>>
> >>> What affect will it have on performance with hundreds of e-mail
> >>> accounts?
> >
> > I think he is concerned about amavisd-new. amavisd-new uses spamassassin
> > for spam filtering.
>
> Yes I am as the AVG documentation states that there may be performance
> issues when using it. We are expanding our customer base every week and
> the load will only increase.
>
> > Multiple instances may be worth the effort. they allow using whatever
> > filter he wants, and make it easy to use multiple machines for filtering
> > (each machine would filter mail for a set of users) when needed.
>
> In the future this may be (well, hopefully we get to a large enough
> customer base where we need multiple servers :) ) necessary in the
> future. Currently AVG and policyd-spf are running on the Postfix server.

There are several SPF policy servers. If you are using my Python policy
server, it supports using restriction classes in combination with the policy
server to support different actions based on SPF result and per user. I
don't know that it's a sufficiently scalable approach for your needs, but it
might be worth a look. There's a per user README included with the package
that at least roughs out the concept:

http://www.openspf.org/Software#python-postfix-policyd-spf

Scott K