On Jul 28, 2007, at 9:31 PM, Pedro LaWrench wrote:
What happens if mail comes in while the cron-based expire is
running? Will
spamc timeout then?
I stop most of the mail system (except for Postfix) at night while I
do the expire and backup the database. It finishes much faster and I
d
--- Micha³ Jêczalik <[EMAIL PROTECTED]> wrote:
> On Fri, 27 Jul 2007, Pedro LaWrench wrote:
>
> > I run spamc from SA 3.2.2 on one host, and spamd from SA 3.2.2 on another
> host.
> > 3.2 was supposed to fix timeouts (* bug 3466: do Bayes expiration, if
> > required, after results have been pass
On Fri, 27 Jul 2007, Pedro LaWrench wrote:
I run spamc from SA 3.2.2 on one host, and spamd from SA 3.2.2 on another host.
3.2 was supposed to fix timeouts (* bug 3466: do Bayes expiration, if
required, after results have been passed back to the client from spamd; this
helps avoid client timeout
I run spamc from SA 3.2.2 on one host, and spamd from SA 3.2.2 on another host.
3.2 was supposed to fix timeouts (* bug 3466: do Bayes expiration, if
required, after results have been passed back to the client from spamd; this
helps avoid client timeouts.), but a packet capture shows the following
Greetings Mike:
We've seen this happen when spamd dies or otherwise gets overloaded.
You may want to look at the "max children" option; you may have no value
(and therefore want to try it; we use 10 on busy mail servers and that
appears to work ok) or a high value (for which you may want to lower
I am running a global SpamAssassin 3.0.2 (spamd and spamc) via procmail
on a Solaris box (spamd and spamc running on the same server). During
periods of high load, I get the following messages in the syslog.
spamc[416]: [ID 702911 mail.error] connect(AF_INET) to spamd at
127.0.0.1 failed, retryin
