Bug 222132 - emacs Mail-mode inserts bogus headers
Summary: emacs Mail-mode inserts bogus headers
Keywords:
Status: CLOSED DUPLICATE of bug 213813
Alias: None
Product: Fedora
Classification: Fedora
Component: emacs
Version: 6
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Chip Coldwell
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-01-10 16:45 UTC by Art Werschulz
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-01-10 17:01:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
A description of various experiments I ran to isolate the problem. (2.39 KB, text/plain)
2007-01-10 16:45 UTC, Art Werschulz
no flags Details

Description Art Werschulz 2007-01-10 16:45:41 UTC
Description of problem:
emacs Mail-mode adds the following extra headers:
(*) a blank line
(*) a repeated From: header
(*) a repeated To: header

Version-Release number of selected component (if applicable):
emacs-21.4-17

How reproducible:
Simply compose a msg using RMAIL-mode, and read it using whatever MUA you like.

Steps to Reproduce:
1. Compose a msg in emacs running under FC6.
2. Read it using some MUA (I use emacs RMAIL mode), and notice the blank line
and the extra headers.
  
Actual results:
The aforementioned extra three lines.

Expected results:
To *not* get these three lines.

Additional info:
I am attaching a full description, explaining some experiments.
BTW, this is similar to bug 195736; however, that bug is for Fedora Legacy RHL9,
whereas this bug is for FC6.

Comment 1 Art Werschulz 2007-01-10 16:45:41 UTC
Created attachment 145267 [details]
A description of various experiments I ran to isolate the problem.

Comment 2 Art Werschulz 2007-01-10 16:47:43 UTC
One additional remark: This is high-severity, since it breaks recognition of
MIME attachments (such as those attached via the "etach" package).

Comment 3 Chip Coldwell 2007-01-10 17:01:48 UTC

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


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