On Wed, May 26, 2010 at 01:14:08PM -0400, Joshua Pettett wrote:
> On Wednesday 26 May 2010, Victor Duchovni wrote:
> > On Wed, May 26, 2010 at 12:42:17PM -0400, Joshua Pettett wrote:
> > > I have a policy server that needs to be able to make policy decisions
> > > after a before-queue content filter. The problem is that the client IP
> > > address reported by the second smtpd instance to the policy server is
> > > that of the proxy (i.e. localhost), rather than of the sending server.
> > > Would it make sense to add the values provided by XFORWARD to the list of
> > > attributes passed to the policy server? For example:
> >
> > Why is the policy service behind the content filter?
>
> Because I'm performing client-reputation-based greylisting/rejecting that
> takes into account SpamAssassin score.
Embed SA into amavisd-new or similar, and then you don't need a separate
policy service.
--
Viktor.
