Closed Bug 30048 Opened 25 years ago Closed 25 years ago

The replied message should have the To: field from the original header

Categories

(MailNews Core :: Backend, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: fenella, Assigned: rhp)

Details

Linux (2000-03-02-09 M15) win32 (2000-03-02-09 M15) Mac (2000-03-02-09 M15) Summary: Please refer to bug 20726 for details of this bug. The header in the replied message (Reply from user 2 to user3) contains the original header (from user 1 to user 2): From Nova: Subject: Nova from user 1 fenella to user 2 qatest38 Date: Wed, 01 Mar 2000 17:33:33 -0800 From: fenella@netscape.com (Fenella Gor) To: qatest38@netscape.com 5.0 contains one line less: Subject: From user 1 fenella to user 2 qatest38 From: fenella@netscape.com (Fenella Gor) Date: Wed, 01 Mar 2000 17:33:33 -0800 The To: line is missing in 5.0. This occurs in all 3 platforms.
This is me. - rhp
Status: NEW → ASSIGNED
Target Milestone: M15
Mine.
Assignee: phil → rhp
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
Ok, I think I have this fixed in my tree. It will be ready to go when the tree opens for M15. - rhp
Summary: The replied message should have the To: field from the original header → [FIXED] The replied message should have the To: field from the original header
Just checked in my fix for this issue. - rhp
Summary: [FIXED] The replied message should have the To: field from the original header → The replied message should have the To: field from the original header
Grr...if you change the summary, comment and resolution all at once...resolution doesn't stick. :-( - rhp
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Linux (2000-04-11-09 M15) Win32 (2000-04-12-06 M15) Mac (2000-04-11-08 M15) The To: problem is fixed. However, in the replied message, addition information were added which does not happen on Nova.
Status: RESOLVED → VERIFIED
Bug 35649 is used to track the problem for content information.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.