Loren Wilton wrote:
Ah. There were some changes in 3.1 dealing with alarm interrupts that triggered this. Current thinking is that this is a fairly benign pyzor bug. There is apparently a pyzor patch or two that makes it go away.
FWIW, Pyzor has always done this, SA just didn't log it before. Patches: http://antispam.imp.ch/08-opensource.html?lng=0 Discussion: http://bugzilla.spamassassin.org/show_bug.cgi?id=4580 Daryl
