SA Bugzilla – Bug 5347
Spamassassin is erasing the message header of HAM and sending a blank subject, from and to
Last modified: 2007-02-22 05:57:44 UTC
Spammassassin is inserting blank from, and subject message headers, after parsing the original message. -----Original Message----- From: Sent: None Subject: Received: from hathayogalesson.com ([200.55.53.228]) by mdpllc.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 20 Feb 2007 20:28:06 -0600 Message-ID: <01c7553e$6ae82300$0500a8c0@pc1d581a92b772> Reply-To: "Titty Duvall" <terezi@hathayogalesson.com> From: "Titty Duvall" <terezi@hathayogalesson.com> Content-Class: urn:content-classes:message To: "Saku Stem" <ews@mdpllc.com> Importance: normal Priority: normal Subject: *****SPAM***** for celandin Date: Tue, 20 Feb 2007 23:28:17 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.607 Return-Path: <terezi@hathayogalesson.com> X-OriginalArrivalTime: 21 Feb 2007 02:28:06.0815 (UTC) FILETIME=[EBB59AF0:01C7555F] X-Spam-Prev-Subject: for celandin Hi, VIArrGRA $3. 35 VALrrIUM $1. 25 CIArrLIS $3. 75 XArrNAX SOrrMA FOR LESS! http://www.kedrx-com Replace "-" with "." in the above link to make it working. But she wasnt entirely right about that. As the girl crossed the Hall,
please attach a copy of the message *as an attachment* of application/octet-stream type.
(In reply to comment #1) > please attach a copy of the message *as an attachment* of > application/octet-stream type. Don't have the means, as the attorney who is getting these sent it to me inline, and lacks the expertise to send it as an attachment. It put the empty headers on both spam and ham messages. Just found out, that attachments are not making it through spamassassin, as I tried to send the message to myself, as an attachment, and SA killed the attached file. What do I have set wrong. Running 3.1.8 with exchange 2003 and chris williams exchange sink.
How are you calling SpamAssassin? SA-milter? Older versions of it are known to have this problem.
I think he said it was with an Exchange sink. this kind of bug is generally caused by the calling code using the wrong line-ending characters. If you can reproduce it with the "spamassassin" command line tool, then it may be an SA bug; otherwise I suspect it's a bug in the sink.
Was old files, left from 3.1.3 when the previous IT guy upgraded. I have taken over that task, and re-installed clean. All is well now.