Bug 44198 - formail 3.14 corrupts lines that look like headers
Summary: formail 3.14 corrupts lines that look like headers
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: procmail
Version: 6.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact: David Lawrence
URL:
Whiteboard:
: 44200 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-06-12 01:46 UTC by peterw
Modified: 2007-04-18 16:33 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-06-12 14:18:06 UTC
Embargoed:


Attachments (Terms of Use)

Description peterw 2001-06-12 01:46:23 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.19-6.2.1 i686; en-US; rv:0.9.1)
Gecko/20010607

Description of problem:
The formail binary from procmail 3.14-2 tries to "clean up" message headers
that contain whitespace between the header name and the colon, e.g.
"Subject : test" becomes "Subject: test". But it does this for all lines,
even within the body of a message. It should only do this sort of thing to
message headers.

Data corruption of course is rather evil. PGP-signed messages may be
rendered unverifiable. Source code or other important data sent via email
may be rendered unusable or even dangerous.

How reproducible:
Always

Steps to Reproduce:
1. printf 'Subject: test\nTo: test\nFrom: test\n\nhere is text\nNotaheader
: this is a body line\n' | formail -f

	

Actual Results:  "Notaheader : this is a body line" is changed to
"Notaheader: this is a body line" (the space between "Notaheader" and the
colon is removed).


Expected Results:  formail should echo exactly what printf gave it, as the
Subject/To/From headers are correct, and the "Notaheader" line is in the
message body.

Additional info:

The HISTORY file at www.procmail.org suggests that this problem was
introduced in procmail 3.14 and fixed in procmail 3.15. I have tested the
formail binary from the official procmail 3.15.1 distribution, and it does
seem to handle these messages properly.

Comment 1 Trond Eivind Glomsrxd 2001-06-12 14:18:02 UTC
*** Bug 44200 has been marked as a duplicate of this bug. ***

Comment 2 Trond Eivind Glomsrxd 2001-06-12 14:30:53 UTC
procmail-3.15.1-1 which is currently in Rawhide should fix this problem.


Note You need to log in before you can comment on or make changes to this bug.