On Fri, Dec 12, 2008 at 12:34:57AM -0600, lee wrote:
> On Fri, Dec 12, 2008 at 12:26:10AM +1030, David Purton wrote:
>
> > acl_check_rcpt:
> > warn hosts = :
> > set acl_m0 = do-not-scan
> >
> > then in sa-exim.conf I have
> >
> > SAEximRunCond: ${if !eq {$acl_m0}{do-not-scan} {1}{0}}
> >
>
> Shouldn't that refer to the hosts exim is relaying mail for? The : in
> "warn hosts = :" makes for an empty host list, so what you're trying
> to do will not apply to any hosts.
I have an acl for that too - the above is an example that matches for
when exim is called via commandline by an MUA such as mutt.
> And if your acl_check_rcpt is acl_smtp_rcpt, that doesn't seem the
> right place to do it.
I gather it is if you are using sa-exim. There are some advantages that
I like that sa-exim provides over using exim's exiscan technique as you
are using. The reason for putting the acl in the rcpt is that some
variables are available at the time that spamassassin is called by the
sa-exim plugin - so you set acl_m0 at this point and test it later - at
least I *think* this is how it works.
I'm following the sa-exim readme:
http://marc.merlins.org/linux/exim/files/sa-exim-cvs/README
If I can't get it to work, then I might move to using exiscan, but I
like spamassassin's report_safe, which I understood was not available
using exiscan. Is this right?
cheers
dc
--
David Purton
dcpurton@marshwiggle.net
For the eyes of the LORD range throughout the earth to
strengthen those whose hearts are fully committed to him.
2 Chronicles 16:9a
Attachment:
signature.asc
Description: Digital signature