http://www.exim.org/bugzilla/show_bug.cgi?id=392
Summary: Option not to panic when spamd/clamd is down
Product: Exim
Version: 4.63
Platform: All
OS/Version: All
Status: NEW
Severity: wishlist
Priority: low
Component: Content Scanning
AssignedTo: tom@duncanthrax.net
ReportedBy: ph10@hermes.cam.ac.uk
QAContact: exim-dev@exim.org
This came up on the mailing list:
Date: Wed, 09 Aug 2006 14:46:37 +0200
From: Marc Haber <mh+exim-users@zugschlus.de>
To: exim users <exim-users@exim.org>
Subject: Re: [exim] restarting spamd makes spam slip through?
On Tue, 08 Aug 2006 18:21:15 +0200, Andreas Pettersson
<andpet@telia.com> wrote:
>I run Exim 4.63 and SpamAssassin (from acl) on FreeBSD.
>Sometimes when I need to restart spamd I find that a few spam mails slip
>through, even though spamd is unavailable for less than a second. To
>prevent this from happening I tried to stop exim first, wait a few
>seconds, and then restart spamd, but the problem still occurs sometimes.
>
>I get three of these in paniclog:
>spam acl condition: warning - spamd connection to 127.0.0.1, port 783
>failed: Connection refused
>spam acl condition: all spamd servers failed
Same thing happens when clamav is reloading its virus databases after
an upgrade. No big deal, but annoying, since the panic log gets these
messages and log checking mechanisms are going to fire.
I'd like exim to behave a little more tolerant here.Date: Wed, 09 Aug 2006
22:22:52 +0200
From: Jakob Hirsch <jh@plonk.de>
Reply-To: exim-users@exim.org
To: Marc Haber <mh+exim-users@zugschlus.de>
Cc: exim users <exim-users@exim.org>
Subject: Re: [exim] restarting spamd makes spam slip through?
Quoting Marc Haber:
> Same thing happens when clamav is reloading its virus databases after
> an upgrade. No big deal, but annoying, since the panic log gets these
> messages and log checking mechanisms are going to fire.
>
> I'd like exim to behave a little more tolerant here.
It probably should, but clamav could also be more nice here. A clamav
client cannot know that clamd will be back in a sec. Exim could retry
after some seconds (how many seconds and how often?). That will delay
all mail when clamd is really down, but that shouldn't be a problem for
smtp.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
--
## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
Summary: Option not to panic when spamd/clamd is down
Product: Exim
Version: 4.63
Platform: All
OS/Version: All
Status: NEW
Severity: wishlist
Priority: low
Component: Content Scanning
AssignedTo: tom@duncanthrax.net
ReportedBy: ph10@hermes.cam.ac.uk
QAContact: exim-dev@exim.org
This came up on the mailing list:
Date: Wed, 09 Aug 2006 14:46:37 +0200
From: Marc Haber <mh+exim-users@zugschlus.de>
To: exim users <exim-users@exim.org>
Subject: Re: [exim] restarting spamd makes spam slip through?
On Tue, 08 Aug 2006 18:21:15 +0200, Andreas Pettersson
<andpet@telia.com> wrote:
>I run Exim 4.63 and SpamAssassin (from acl) on FreeBSD.
>Sometimes when I need to restart spamd I find that a few spam mails slip
>through, even though spamd is unavailable for less than a second. To
>prevent this from happening I tried to stop exim first, wait a few
>seconds, and then restart spamd, but the problem still occurs sometimes.
>
>I get three of these in paniclog:
>spam acl condition: warning - spamd connection to 127.0.0.1, port 783
>failed: Connection refused
>spam acl condition: all spamd servers failed
Same thing happens when clamav is reloading its virus databases after
an upgrade. No big deal, but annoying, since the panic log gets these
messages and log checking mechanisms are going to fire.
I'd like exim to behave a little more tolerant here.Date: Wed, 09 Aug 2006
22:22:52 +0200
From: Jakob Hirsch <jh@plonk.de>
Reply-To: exim-users@exim.org
To: Marc Haber <mh+exim-users@zugschlus.de>
Cc: exim users <exim-users@exim.org>
Subject: Re: [exim] restarting spamd makes spam slip through?
Quoting Marc Haber:
> Same thing happens when clamav is reloading its virus databases after
> an upgrade. No big deal, but annoying, since the panic log gets these
> messages and log checking mechanisms are going to fire.
>
> I'd like exim to behave a little more tolerant here.
It probably should, but clamav could also be more nice here. A clamav
client cannot know that clamd will be back in a sec. Exim could retry
after some seconds (how many seconds and how often?). That will delay
all mail when clamd is really down, but that shouldn't be a problem for
smtp.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
--
## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##