https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6421
Summary: Spamd (3.2.5) seems to cut all messages over 163770
(+/- 2) bytes
Product: Spamassassin
Version: 3.2.5
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Libraries
AssignedTo: [email protected]
ReportedBy: [email protected]
I'm using spamassassin in two Debian lenny computers, one a virtual openvz
server and the other a physical one. I have spamc installed in the first and
spamassassin in the second. The first one receives mail through postfix, and
then uses spamc to forward it, through an SSL connection, to the second one and
check it.Both spamc and spamassassin have been installed using the Debian
package system (so they are version 3.2.5) and are kept updated.
I've found that some spam messages were not even being checked. When
investigating this, I discovered that for those messages spamc were reporting
errors like this:
Apr 22 15:33:41 correu spamc[23878]: failed sanity check, 240674 bytes claimed,
163771 bytes seen
Apr 22 15:34:50 correu spamc[24028]: failed sanity check, 189634 bytes claimed,
163770 bytes seen
Apr 22 15:37:09 correu spamc[24135]: failed sanity check, 240674 bytes claimed,
163771 bytes seen
Apr 22 15:37:13 correu spamc[24136]: failed sanity check, 312445 bytes claimed,
163770 bytes seen
Apr 22 15:37:26 correu spamc[24148]: failed sanity check, 240674 bytes claimed,
163771 bytes seen
Apr 22 15:38:40 correu spamc[24199]: failed sanity check, 240674 bytes claimed,
163771 bytes seen
Apr 22 15:40:35 correu spamc[24293]: failed sanity check, 311545 bytes claimed,
163770 bytes seen
Apr 22 15:41:31 correu spamc[24345]: failed sanity check, 240674 bytes claimed,
163771 bytes seen
Apr 22 15:43:02 correu spamc[24436]: failed sanity check, 240674 bytes claimed,
163771 bytes seen
Apr 22 15:48:15 correu spamc[24677]: failed sanity check, 240674 bytes claimed,
163771 bytes seen
then discarded the returned message and instead gave back the original one to
postfix.
I modified and compiled a version of spamc to not register a failure when this
error happened and tried it manually, to see what was spamc receiving. I found
that it really got back the message from spamd cut at the length it reported. I
checked the logs in the spamd machine, and there were not errors, but there was
an entry identifying as spam the message I had just tried (which was).
Moreover, using the option -R with those messages, I always get the correct
spam status.
I modified your provided sample-spam.txt and sample-nonspam.txt to be longer
than 170 KB and got the same behaviour with both of them: the data returned by
spamd was always cut around 163770 bytes (and yet the spam status was correctly
identified with the -R option). I tried spamassassin manually in the spamd
machine for those files and I obtained, locally, the full correct record.I
tried modifying the MTU length for the ethernet interface of the spamd
computer, but it made no difference. I googled for this error and I found some
similar cases; it seems in one case it was solved by setting LANG=C but in my
case that changed nothing. There was another case which seemed to involve using
spamassassin in a cygwin environment, which aparently could be worked around
adding a sleep instruction somewhere in the spamd code, but it was an old
version (not 3.2.5) and was not very clear on where to put this modification,
so I have not been able to try that.
It may be I had inadvertently misconfigured something, but as far as I can
tell, I'm using standard options everywhere (except, maybe, for the SSL
connection) and other network connections (ssh, scp) between both computers are
working flawlessly.
I would be grateful for any help in that problem. Thanks in advance!
Josep Guerrero
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
