This is a discussion on Re: spamc timeouts continued with 3.2.2 - SpamAssassin ; --- Michał Jęczalik 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 ...
--- Michał Jęczalik
> 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
> > 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;
> > helps avoid client timeouts.), but a packet capture shows the following:
> > - spamc sends message to spamd
> > - spamd sends results back
> > [spamd performs Bayes expiration]
> > [spamc times out]
> > - spamd sends FIN to close TCP connection
> > So even though the results are sent back prior to Bayes expiration, spamc
> > still wait until the TCP connection is closed.
> > How can this get fixed?
> By disabling auto expire and doing it by cron.
> Michał Jęczalik, +48.603.64.62.97
> INFONAUTIC, +48.33.487.69.04
What happens if mail comes in while the cron-based expire is running? Will
spamc timeout then?
Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online.