Bug 4289 - Incorrect application/ms-tnef parsing with \r\n
Summary: Incorrect application/ms-tnef parsing with \r\n
Status: RESOLVED DUPLICATE of bug 4363
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: 3.0.3
Hardware: PC Windows 2000
: P5 critical
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords: triage
: 4340 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-04-29 02:55 UTC by Nikolay V. Buslaev
Modified: 2005-06-08 20:47 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
File Before parsing application/octet-stream None Nikolay V. Buslaev [NoCLA]
File After parsing application/octet-stream None Nikolay V. Buslaev [NoCLA]
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 Nikolay V. Buslaev 2005-04-29 02:55:44 UTC 
After parse with spamassassin message in 8bit encofing containt ms-tnef 
attachment (winmail.dat)
All \r\n in binary body replaced to \n
and can't be readed with outlook
Comment 1 Bob Menschel 2005-05-03 23:22:35 UTC 
Nikolay, would it be possible for you to take a valid email that will
demonstrate this problem, feed it through spamassassin via 
> spamassassin <sample.in >sample.out
and attach both the "input" and "output" emails to this bug report, so we can
see what's happening and figure out why?  Thanks.
Comment 2 Nikolay V. Buslaev 2005-05-04 00:30:07 UTC 
Subject: Re:  Incorrect application/ms-tnef parsing with \r\n

Ok.

----- Original Message ----- 
From: <bugzilla-daemon@bugzilla.spamassassin.org>
To: <SiberianGhost@hotmail.com>
Sent: Wednesday, May 04, 2005 1:22 PM
Subject: [Bug 4289] Incorrect application/ms-tnef parsing with \r\n


> http://bugzilla.spamassassin.org/show_bug.cgi?id=4289
>
>
> Bob@Menschel.net changed:
>
>            What    |Removed                     |Added
> --------------------------------------------------------------------------
--
>            Keywords|                            |triage
>
>
>
>
> ------- Additional Comments From Bob@Menschel.net  2005-05-03
23:22 -------
> Nikolay, would it be possible for you to take a valid email that will
> demonstrate this problem, feed it through spamassassin via
> > spamassassin <sample.in >sample.out
> and attach both the "input" and "output" emails to this bug report, so we
can
> see what's happening and figure out why?  Thanks.
>
>
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
Comment 3 Nikolay V. Buslaev 2005-05-05 00:22:38 UTC 
Created attachment 2843 [details]
File Before parsing

Message content before spamassassin
Comment 4 Nikolay V. Buslaev 2005-05-05 00:23:49 UTC 
Created attachment 2844 [details]
File After parsing

Message after spamassassin
Comment 5 Nikolay V. Buslaev 2005-05-12 23:54:07 UTC 
How long time need for assigned staus of bug?
Comment 6 Kenneth Porter 2005-05-18 09:15:36 UTC 
*** Bug 4340 has been marked as a duplicate of this bug. ***
Comment 7 Nikolay V. Buslaev 2005-05-18 19:08:34 UTC 
So sorry
\r on offset 1821 in input file replaced to
\r\n on offset 1897 in output file replaced.
after parse with spamassassin
Comment 8 Nikolay V. Buslaev 2005-05-19 06:13:22 UTC 
I localized this "bug"
It's ActivePerl specific behavior on win32 platforms

to FIX this trouble - you mest correct spamassassin script
insert in first line this code
#----------
if ($^O =~ /^(windows|dos|os2|mswin)/i) {
  binmode(STDIN);
  binmode(STDOUT);
}
#----------
Comment 9 Malte S. Stretz 2005-06-09 04:47:24 UTC 
Now discussed in bug 4363. 

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