http://bugzilla.spamassassin.org/show_bug.cgi?id=3917
------- Additional Comments From [EMAIL PROTECTED] 2004-10-22 14:12 ------- It looks like spamd thinks everything is ok, but spamc is getting in error in the socket connection. 76 is, as you said, "remote error in protocol" which I see is defined as "The remote system returned something that was not possible during a protocol exchange". I could see how I could not reproduce it trying it once on my system. Here are some other things to try in order to narrow it down: Do you get the same results if you disable the network checks by running spamd with -L? How about running without Bayes? I'm thinking in terms of what happens if spamd is not doing anything that potemtially takes a long elapsed time. Another interesting extra piece of information would be to add timestamps to the spamd -D output. I guess you could do that by adding in the time to the warn "debug: " $msg line in sub dbg in SpamAssassin.pm. That would show if there are any long delays during the spamd processing in the cases that fail. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
