You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2005/07/14 08:35:00 UTC

[Bug 4138] spamd hanging on infinite loop

http://bugzilla.spamassassin.org/show_bug.cgi?id=4138





------- Additional Comments From Bob@Menschel.net  2005-07-13 23:34 -------
Michael, "This really looks like a corrupt bayes_seen db file.  Did you already
rm the old files and start from scratch?" Per the original report, "Erasing them
fixes the problem. Setting the old files back reintroduces the problem. A
sa-learn --backup and a --restore also seems to fix the problem." 

Henk, after you've deleted the Bayes files, does the problem come back, or is it
gone for good?  

If it comes back, then if it is caused by Bayes corruption, there's a problem
that's /causing/ the corruption that should be looked into, if possible. 

Even so, why would /this/ message aggravate the corruption and cause a
spamd/spamc hang, but not most others? 

Henk, you included the debug output from spamd, which ends with the header
tokenize. I don't know spamd well enough to know whether there should then be
body tokenize lines.  It might be that tokenize is failing on the body. Perhaps
on those long lines of encoded equal signs? 

You attached a "spamassassin -D --lint", but not a "spamassassin -D <message"
output.  Can you do that latter, so we can compare the two debug outputs as they
actually attempt to process the message, the same message, against the same
problematic bayes files? 



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.