Andy Jezierski <[EMAIL PROTECTED]> wrote on 09/13/2004 10:13:01 AM:
> I've got a question as to whether you think this is a milter error or a
> spamd error. I'm thinking milter.
>
> I'm running milter-spamc 0.24 along with sendmail 8.13 on one box, which
is
> calling spamd 3.0rc3 (haven't had a chance to go to rc4 yet) running on
> another box. Everything works just fine, except, when I run an sa-learn
on
> the box running spamd.
>
[snip]
I got a reply from the milter author saying this is a problem with
spamd....
> Sep 13 09:36:31 viper milter-spamc[40625]: 34482 i8DEYOCH096305: timeout
> before input from SPAMD server
> Sep 13 09:36:31 viper milter-spamc[40625]: 34482 i8DEYOCH096305: SPAMD
> status line failure
> Sep 13 09:36:44 viper milter-spamc[40625]: 34486 i8DEYake096312: timeout
> before input from SPAMD server
> Sep 13 09:36:44 viper milter-spamc[40625]: 34486 i8DEYake096312: SPAMD
> status line failure
This is the problem with spamd, its not truely threaded and gets hung up
when ever more than one process (spamd, sa-learn, spamassassin) access
the token/database files.
The second set up errors from sendmail could be avoided by increasing
the sendmail-milter timeout in the INPUT_MAIL_FILTER line, but this is
not guaranteed solve overall problems with SA.
Essentially, the problem lies with SA perl bloat and lack of decent
threading.
You could try increasing the milter-spamd timeout, but if you do this
you must increase the sendmail-milter timeout to account for this.
Should I open a bugzilla on this or is there no way around the problem for
now?
Andy
