Bug 1233 - spamd reports spamc sending a bad content-length (bad protocol header error)
Summary: spamd reports spamc sending a bad content-length (bad protocol header error)
Status: RESOLVED DUPLICATE of bug 1243
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: 2.43
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-11-26 10:41 UTC by jerry asher
Modified: 2002-12-12 11:20 UTC (History)
0 users



Attachment Type Modified Status Actions Submitter/CLA Status
gzipped spam. Is gzipping spam sent as part of a bug unnecessary? application/octet-stream None jerry asher [NoCLA]

Note You need to log in before you can comment on or make changes to this bug.
Description jerry asher 2002-11-26 10:41:47 UTC
I was trying to determine why some obvious spam had no SA headers
attached to it.  Eventually I ran spamd and spamc as root as what 
I believe my mailer is doing (I am using the qmail/qmail-scanner
set up described at http://qmail-scanner.sourceforge.net/FAQ.php)

Running as root:
/usr/bin/spamd -L -x -a -D

Also running as root:
/usr/bin/spamc -d localhost < /tmp/spam.mail

I'll try to attach the spam.mail to this message.

What happens when I do this is that spamc returns 0/0, which
I gather means an error has occurred.

And spamd -D?  Eventually that spits out:

logmsg: connection from localhost.localdomain [127.0.0.1] at port 37033
logmsg: Still running as root: user not specified with -u, not found, or set to
root.  Fall back to nobody.
logmsg: checking message
<CAPRESUBNT2hhOjcdEc000015b4@capresubnt2.capresub.gov.co> for root:99, expecting
1589 bytes.
logmsg: bad protocol: header error: (Content-length mismatch: 1589 vs. 1580)
Comment 1 jerry asher 2002-11-26 10:44:22 UTC
Created attachment 461 [details]
gzipped spam.  Is gzipping spam sent as part of a bug unnecessary?
Comment 2 jerry asher 2002-11-26 10:46:19 UTC
I don't know what spamc is sending, nor what spamd is receiving, but the message
is apparently correct.  The spam is 1589 bytes and not 1580 bytes.
Comment 3 Duncan Findlay 2002-12-12 20:20:54 UTC

*** This bug has been marked as a duplicate of 1243 ***