I'm using a combination of Ubuntu and Debian servers for scanning email with spamc/spamd. I'm running the following version: spamd -V SpamAssassin Server version 3.3.1 running on Perl 5.10.1 with SSL support (IO::Socket::SSL 1.33) with zlib support (Compress::Zlib 2.02)
I've been noticing a lot of messages in the logs like this since we started using SSL: Apr 10 08:02:11 mail spamc[5052]: failed sanity check, 293973 bytes claimed, 163770 bytes seen Apr 10 08:02:12 mail spamc[4882]: failed sanity check, 293178 bytes claimed, 163770 bytes seen Apr 10 08:02:32 mail spamc[6009]: failed sanity check, 294166 bytes claimed, 163770 bytes seen Apr 10 08:02:35 mail spamc[5917]: failed sanity check, 405520 bytes claimed, 163770 bytes seen Apr 10 08:02:36 mail spamc[6237]: failed sanity check, 295168 bytes claimed, 163771 bytes seen Apr 10 08:02:54 mail spamc[6358]: failed sanity check, 297001 bytes claimed, 163771 bytes seen I notice all of the messages are either 163770 or 163771 bytes seen. It seems to be a limitation of the SSL connection. I've found some bug reports that are talking about this issue having to do with syswrite, but they are from 2007 or so. I figured it would be fixed by now. Is there a setting or workaround for this issue or do I just need to stop using SSL? Trey Nolen
