127228 - Mailnews doesn't set the Content-Transfer-Encoding correctly when subject: field contains 8bit characters

Status: RESOLVED INVALID

(MailNews Core :: MIME, defect)

Description

[harrij]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.8+) Gecko/20020221
BuildID:    2002022103

Mailnews doesn't set the Content-Transfer-Encoding field correctly when Subject
field contains 8bit characters. 

If the Subject-field contains 8bit characters but the message body does not
Mailnews sets Content-Transfer-Encoding: 7bit instead of
Content-Transfer-Encoding: 8bit.


Reproducible: Always
Steps to Reproduce:
1. compose new message
2. edit Subject to contain 8bit characters eg. Ä, Ö, Ü etc.
3. make sure the message body does not contain any 8bit characters
4. send


Actual Results:  Mailnews sets Content-Transfer-Encoding to 7bit

Expected Results:  Content-Transfer-Encoding should be 8bit

Comment 1

[Toylet]

yes. I got the same problem.I was reading chinese message in a local newsgroup.
When I compose a new message to the newsgroup, it followed the EMAIL's encoding 
settings (Western), rather than the setting of the newsgroup (Big5).

But if I replied (rather than create new), the character encoding followed the 
newsgroup's property. It's a minor bug.

Comment 2

[dominik]

I use Mozilla1.0 RC3 with GNU/Linux and got the same problem:
I set all my character encodings to Unicode UTF8, but left the checkbox "apply
character coding to all mails (ignore MIME Headers)" unchecked. If i recieve a
mail eg with character coding = iso-8859-1 i can read all Umlauts like ä
correctly in the mailbody, but NOT (!!!) in the mail header, where i only get a
? for every character after the first Umlaut.

Comment 3

[Jari Boman]

Same problem, mozilla1.1 Windows; WinNT4.0; en-US;
I can't send mail with Content-Transfer-Encoding: 8bit. format. 
System Crash (dr. watson) access violation (allways if try use дц letters 
subject or message body).
Only way is get mail with Content-Transfer-Encoding: 8bit and use replay. Then 
it is possible to send message with letters дц (äö) without crashing.

Comment 4

[Jean-Francois Ducarroz]

cc'ing Naoki

Comment 5

[nhottanscp]

>Expected Results:  Content-Transfer-Encoding should be 8bit
The expected result is that the transfer encoding should be 7bit if the body
only contains 7bit characters. 8 bit characters in the header is encoded by
RFC2047 format independent from transfer encoding. See example below.


Subject: =?ISO-8859-1?Q?=E1a_?=
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <title></title>
</head>
<body>
&aacute;a&nbsp;
</body>
</html>