http://bugzilla.spamassassin.org/show_bug.cgi?id=3506
------- Additional Comments From [EMAIL PROTECTED] 2004-07-27 03:26 -------
I don't reproduce the problem by setting the timeout in spamc -t to less that
the time that spamd takes to process a message, and I don't see how the behavior
that Dallas reports is possible.
The error message "spamd responded with bad string" only happens in one place
after this code
failureval =
_spamc_read_full_line(m, flags, ssl, sock, buf, &len, bufsiz);
if (failureval != EX_OK) {
goto failure;
}
For the error message to be reached, _spamc_read_full_line has to return EX_OK.
In _spamc_read_full_line, if a timeout causes bytesread to be <= 0 the way it
appears that it is supposed to, there is a goto failure which sets the return
code to something other than EX_OK. This won't happen if buf[len] happens to be
'\n' but that doesn't match the symptoms.
So I don't see how the code matches Dallas' debugging output or the reported
symptoms of the bug, and I can't reproduce the bug mysealf.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
