spamass-milt-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bad protocol


From: Dan Nelson
Subject: Re: bad protocol
Date: Tue, 29 Apr 2003 09:32:33 -0500
User-agent: Mutt/1.5.4i

In the last episode (Apr 29), VERLAINE, Olivier said:
> From: Dan Nelson [mailto:address@hidden
>>In the last episode (Apr 29), VERLAINE, Olivier said:
>>> In the log, I have spamd: bad protocol: header error.  Do you know
>>> hot to correct this ?? My spamassassin version is 2.44.
>> 
>> Could you paste in the exact error?  That's a spamc/spamd
>> communication error, and it should read "bad protocol: header error:
>> XXX", where XXX is a header or error message.  It might happen if
>> your spamc and spamd are different versions.
>
> here is the message
> 
> Apr 29 01:34:25 mx spamd[18805]: Still running as root: user not specified, 
> not found, or set to root.  Fall back to nobody. 
> Apr 29 01:34:25 mx spamd[18805]: processing message (unknown) for root:99, 
> expecting 5348 bytes. 
> Apr 29 01:34:25 mx spamd[18805]: bad protocol: header error: (Content-length 
> mismatch: 5348 vs. 5342) 

This is probably because of a Perl 5.8 bug that broke backwards
compatibility - see
http://www.hughes-family.org/bugzilla/show_bug.cgi?id=1243 . That bug
is marked fixed, and my spamassassin version 2.53 does not seem to
check this header, so upgrading might fix this problem:

Apr 29 09:12:48 <2.6> dan spamd[43850]: processing message 
<200304291416.h3TEG9K address@hidden> for root:26.

Notice it doesn't say "expecting xxxx bytes" like yours does

-- 
        Dan Nelson
        address@hidden




reply via email to

[Prev in Thread] Current Thread [Next in Thread]