Bradley Walker <[EMAIL PROTECTED]> wrote: > However within hours of making this upgrade customers started calling > me nonstop that their email "wasn't working". [snip] > 2006-01-10 23:05:23 1EwX9q-00060G-ML ** > <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] F=< > <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]> > R=spamcheck_director T=spamcheck: Child process of spamcheck transport > returned 2 from command: /usr/sbin/exim (preceded by transport filter > timeout while writing to pipe)
> My temporary solution has been to run Exim 4.60 but leave SA 3.1.0 > turned off until I can get a solution implimented. my temporary solution would be to put: timeout_defer ignore_status into the SA exim router. you should see what happens during that timeout. most probably it is SA spinning the CPU for few minutes. are you using bayes? i've had such problem when the token file got *really* big. debug might help, too. and these two lines are useful even as something more than a workaround, they insure that whenever SA timeouts/dies, a message is deferred instead of bounced. -- Stanisław Halik, http://tehran.lain.pl
pgpOp8i4XyvAt.pgp
Description: PGP signature
