Closed
Bug 20767
Opened 26 years ago
Closed 26 years ago
Reply to Plain Text msg result in incorrect Content-Transfer-Encoding
Categories
(MailNews Core :: MIME, defect, P3)
MailNews Core
MIME
Tracking
(Not tracked)
VERIFIED
FIXED
M14
People
(Reporter: pmock, Assigned: rhp)
Details
Build Date & Platform Bug Found:
Win32 commercial seamonkey build 1999-12-02-11-m12 installed on P166 Win98
Linux commercial seamonkey build 1999-12-02-12-m12 installed on P200 Redhat 6.1
MacOS commercial seamonkey build 1999-12-02-12-m12 installed on G3 MacOS 8.6
Overview Description:
If you reply to a plain text message that was sent from 5.0 using a plain text
editor, the message is sent with the wrong Content-Transfer-Encoding. It states
it 8 bit instead of 7 bit.
This problem occurs only if I reply to a plain text message that was sent from
5.0. Plain text message sent from 4.7 win32, does not appear to exhibit this
problem.
Steps to Reproduce:
0) Edit your prefs.js file and change the user pref to false for
user_pref("mail.identity.id1.compose_html", false);
1) Launch Seamonkey
2) Start Messenger
3) Start a new plain text message
4) Send the message to yourself, add a title, and couple of sentence of text
Be sure not to use any extended characters.
5) Send and receive the mail message
6) Reply to the plain text message
7) Use Communicator 4.7 to view the message page source.
The Content-Transfer-Encoding is 8 bit instead of 7 bit.
Actual Results:
The page source says the message is Content-Transfer-Encoding: 8bit
Expected Results:
If there are no extended characters in the mail message, it should be 7 bit.
Additional Builds and Platforms Tested On:
Additional Information:
Note: I did double check that my original mail message was 7 bits and had
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
---sample reply---
Return-Path: <qatest35@netscape.com>
Received: from tintin.mcom.com ([205.217.233.42]) by
dredd.mcom.com (Netscape Messaging Server 4.1 Aug 9 1999
18:28:31) with ESMTP id FM6V1200.AU6 for <pmock@dredd.mcom.com>;
Fri, 3 Dec 1999 15:39:02 -0800
Received: from netscape.com ([208.12.40.46]) by tintin.mcom.com
(Netscape Messaging Server 4.1) with ESMTP id FM6V1200.3NG; Fri,
3 Dec 1999 15:39:02 -0800
Message-ID: <3848549B.7050807@netscape.com>
Date: Fri, 03 Dec 1999 15:39:07 -0800
From: qatest35@netscape.com (qa test35)
User-Agent: Mozilla 5.0 [en-US] (Windows_98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: qa test35 <qatest35@netscape.com>, pmock@netscape.com
Subject: Re: Another simple test
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Replying to this message
qa test35 wrote:
> test message
>
> again again
>
| Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M14
Updated•26 years ago
|
Target Milestone: M14 → M16
Comment 1•26 years ago
|
||
Doesn't seem like there are any user-visible problems with this, so pushing past
B1. Feel free to move it back if I'm mistaken.
| Assignee | ||
Comment 2•26 years ago
|
||
Good catch Peter! It makes my life so much easier (not to mention a better
product) when you guys dig these issues.
I have a fix in my tree and will check in if the tree opens today.
- rhp
Summary: Reply to Plain Text msg result in incorrect Content-Transfer-Encoding → [FIXED] Reply to Plain Text msg result in incorrect Content-Transfer-Encoding
Target Milestone: M16 → M14
| Assignee | ||
Comment 3•26 years ago
|
||
Checked this fix in.
- rhp
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Summary: [FIXED] Reply to Plain Text msg result in incorrect Content-Transfer-Encoding → Reply to Plain Text msg result in incorrect Content-Transfer-Encoding
Linux (2000-03-09-13 M15)
Win32 (2000-03-09-09 M15)
Mac (2000-03-09-09 M15)
Replying to plain text shows: "Content-Transfer-Encoding: 7bit" on all 3
platforms now.
Status: RESOLVED → VERIFIED
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•