Bug 3575 - SA 3.0pre1 causes broken header
Summary: SA 3.0pre1 causes broken header
Status: RESOLVED WORKSFORME
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: All All
: P5 minor
Target Milestone: 3.0.1
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-06 23:54 UTC by Dan Kohn
Modified: 2004-10-10 00:32 UTC (History)
1 user (show)


Attachment Type Modified Status Actions Submitter/CLA Status
Original message that results in broken headers text/plain None Dan Kohn [HasCLA]
Message after processing by SA 3.0pre1 text/plain None Dan Kohn [HasCLA]
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Kohn 2004-07-06 23:54:18 UTC 
This is an odd bug, but it's completely repeatable, so I decided to report.  A 
daily blog update I subscribe to always breaks the headers in the same way 
under SA 3.0pre1, but didn't under 2.63.  The odd thing is that the SA 
processed message looks fine to me when I view it on the server, but shows up 
broken in Exchange/Outlook.  Specifically, when it gets forwarded to Outlook, 
the body of the message shows:

Content-Type: text/plain; charset=iso-8859-1

X-Spam-Checker-Version: SpamAssassin 3.0.0-pre1 (2004-06-19) on emlis.pair.com
X-Spam-Level: 
X-Spam-Status: No, score=0.2 required=5.0 tests=AWL,BAYES_50,
	FORGED_YAHOO_RCVD,HTTP_WITH_EMAIL_IN_URL autolearn=no 
	version=3.0.0-pre1
Return-Path: root@www.webflyer.com
X-OriginalArrivalTime: 06 Jul 2004 06:48:18.0671 (UTC) FILETIME=
[3889C7F0:01C46325]


Here are the entries from Jul 5, 2004 for View From the Wing - 
(http://www.webflyer.com/blog/)

[rest elided]

The header of the message (viewable in Outlook under View: Options) is:

Microsoft Mail Internet Headers Version 2.0
Received: from emlis.pair.com ([209.68.2.61]) by exchange2003.ad.skymv.com 
with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 5 Jul 2004 23:48:18 -0700
Received: (qmail 39932 invoked by uid 3368); 6 Jul 2004 06:32:26 -0000
Delivered-To: dankohn-dankohn:com-dan@dankohn.com
X-Envelope-To: dan@dankohn.com
Received: (qmail 39909 invoked from network); 6 Jul 2004 06:32:20 -0000
Received: from www.webflyer.com (64.78.185.89)
  by emlis.pair.com with SMTP; 6 Jul 2004 06:32:20 -0000
Received: (qmail 13493 invoked by uid 0); 6 Jul 2004 06:31:10 -0000
Date: 6 Jul 2004 06:31:10 -0000
Message-ID: <20040706063110.13492.qmail@www.webflyer.com>
To: dan@dankohn.com
Subject: View From the Wing - Entries for Jul 5, 2004
From: gleff@yahoo.com <gleff@yahoo.com>
Reply-To: gleff@yahoo.com <gleff@yahoo.com>
MIME-Version: 1.0 


That is, it appears that an extra return is getting inserted after the Mime-
Version header that is mistakenly causing the rest of the headers to be 
treated as the body.  I've attached the original message and the SA-processed 
message before forwarding, and I can't see any problems with either.  However, 
the same header flaw gets repeated every day on this blog update, but with no 
other mail.

I thought I'd post in case the cause of the problem is more obvious to others.
Comment 1 Dan Kohn 2004-07-06 23:55:11 UTC 
Created attachment 2095 [details]
Original message that results in broken headers
Comment 2 Dan Kohn 2004-07-06 23:55:44 UTC 
Created attachment 2096 [details]
Message after processing by SA 3.0pre1
Comment 3 Dan Kohn 2004-07-07 00:07:10 UTC 
BTW, I should have made clear that I'm calling SpamAssassin from procmail and 
forwarding to my Outlook/Exchange account using the script described at 
http://wiki.apache.org/spamassassin/ProcmailToForwardMail
Comment 4 Daniel Quinlan 2004-07-07 08:55:45 UTC 
Subject: Re:  SA 3.0pre1 causes broken header

The message headers appear to be fine and it works for me.  It looks
like a bug somewhere else, maybe whitespace is being changed somewhere
(your rewritten version has some spaces at the beginning of the
continuation line for X-Spam-Checker-Version where I have a tab instead).

You might try putting the original on a Unix POP3 server in mbox format
and see if your MUA is able to display that right.
Comment 5 Malte S. Stretz 2004-07-07 13:55:56 UTC 
I've seen random bugs like this for more than a year. For maybe one out of 
10.000 mails I encounter it but was never able to reproduce it.
Comment 6 Daniel Quinlan 2004-08-27 17:35:54 UTC 
bugs for 3.0.1 milestone
Comment 7 Theo Van Dinter 2004-09-27 19:16:49 UTC 
has there been anything else with this?  does 3.0.0 final have the same issue?

I can't reproduce the issue either, so I'm tempted to close wfm.
Comment 8 Theo Van Dinter 2004-10-10 08:32:21 UTC 
closing as wfm.  dan, if the problem occurs with the released versions of 3.0.x,
we can reopen and investigate, etc.