Author: Keith Brazington Date: To: exim-users@securitects.com CC: Exim-users Subject: Re: [Fwd: [exim] deferring when clamd/spamd is down]
On Tue, 22 Feb 2005 17:47:11 +0100, exim-users@???
<exim-users@???> wrote:
>
> To avoid this and have the mails deferred as long as one of the demons
> is down, I implemented the kind of tri-state logic that was given before
> on the list for sender verification (ok/bad/unknown). Since this is not
> the most beautiful solution in my eyes, I wonder whether there is
> another way to achieve the same goal. How do others on the list tackle
> this situation?
Using Unix sockets to connect to SpamAssassin gives me the required
defer if SpamAssassin stops running. Exim debug output shown below
processing "warn"
check spam = exim:true
trying server 127.0.0.1, port 783
LOG: MAIN PANIC
spam acl condition: warning - spamd connection to 127.0.0.1, port
783 failed: Connection refused
LOG: MAIN PANIC
spam acl condition: all spamd servers failed
warn: condition test deferred
As for the Virus check, that runs before SpamAssassin in a deny, so I
can't comment on that.
