https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6421
--- Comment #6 from Bjørn Mork <[email protected]> 2011-10-29 07:38:50 UTC --- Hello, I am seeing the exact same issue as the original reporter and am watching this bug for that reason. I just didn't think I had any more useful information to offer. A few of my most recent log messages: Oct 27 13:04:54 canardo spamc[7031]: failed sanity check, 701458 bytes claimed, 163770 bytes seen Oct 27 13:57:12 canardo spamc[9586]: failed sanity check, 4526382 bytes claimed, 163769 bytes seen Oct 27 20:14:26 canardo spamc[27097]: failed sanity check, 195214 bytes claimed, 163769 bytes seen Oct 28 09:15:23 canardo spamc[29946]: failed sanity check, 241547 bytes claimed, 163769 bytes seen Oct 28 10:17:39 canardo spamc[32734]: failed sanity check, 426548 bytes claimed, 163769 bytes seen Oct 28 10:27:31 canardo spamc[755]: failed sanity check, 521802 bytes claimed, 163769 bytes seen Oct 28 11:10:52 canardo spamc[2872]: failed sanity check, 279988 bytes claimed, 163770 bytes seen Oct 28 18:09:29 canardo spamc[23848]: failed sanity check, 1537235 bytes claimed, 163768 bytes seen As the original reporter, I am also using SSL between spamc and spamd, and my gut feeling tells me that this may be related to the problem. As the OR says: That is probably the only non-standard setting we use. My spamd command line is (with somewhat modified addresses) /usr/sbin/spamd --username=spamd --max-children 15 --helper-home-dir --allow-tell --nouser-config --sql-config -i -A 127.0.0.1,172.16.185.158,10.138.100.138 --ssl -d --pidfile=/var/run/spamd/spamd.pid Thanks, Bjørn -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
