Closed
Bug 267702
Opened 20 years ago
Closed 17 years ago
Return receipt garbles non-ASCII characters in subject and message body
Categories
(SeaMonkey :: MailNews: Backend, defect)
SeaMonkey
MailNews: Backend
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 335534
People
(Reporter: info, Assigned: jshin1987)
References
(Blocks 1 open bug)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041007 Galeon/1.3.17 (Debian package 1.3.17-2) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.7.3) Gecko/20041007 Debian/1.7.3-5 The german version of the MDN Message uses 8 bit (ISO-8859-1) characters, but doesn't encode them (even in the Subject line). The Content-Transfer-Encoding of the text part is 7bit, even if there are 8bit characters in it. Reproducible: Always Steps to Reproduce: Generate a return receipt using a mozilla with german localization Actual Results: Subject: Empfangsbestätigung (angezeigt) - Test To: XXXX References: <418A3761.2080209@ix.de> MIME-Version: 1.0 Content-Type: multipart/report; report-type=disposition-notification; boundary="------------mdn010304000009080901010109" --------------mdn010304000009080901010109 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Dies ist eine Empfangsbestätigung für die Mail, die Sie an XXX geschickt haben. Expected Results: Subject: =?ISO-8859-1?Q?Empfangsbest=E4tigung?= (angezeigt) - Test To: XXXX References: <418A3761.2080209@ix.de> MIME-Version: 1.0 Content-Type: multipart/report; report-type=disposition-notification; boundary="------------mdn010304000009080901010109" --------------mdn010304000009080901010109 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Dies ist eine Empfangsbestätigung für die Mail, die Sie an XXX geschickt haben.
Reporter | ||
Comment 1•20 years ago
|
||
The encoding is a little bit misleading, in the original return receipt ISO-8859-1 is used. This has become UTF-8 during the bug report somehow. So the expected result ist ISO-8859 iff Content-Type: text/plain; charset=ISO-8859-1, which works. The Problem is the 'Content-Transfer-Encoding: 7bit' and the 8bit header.
Updated•20 years ago
|
Product: Browser → Seamonkey
Assignee | ||
Comment 2•19 years ago
|
||
taking this for now. it's also reported by a Korean user. it may turn out to be trivial or may have some deeper issues.
Assignee: bienvenu → jshin1987
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Return receipt uses 8bit characters in localized version → Return receipt garbles non-ASCII characters in subject and message body
Assignee | ||
Comment 3•19 years ago
|
||
http://lxr.mozilla.org/seamonkey/source/mailnews/extensions/mdn/src/nsMsgMdnGenerator.cpp#568 It seems like it's rather easy to fix this.
Comment 4•18 years ago
|
||
I think this is a little more complicated than just replacing NS_LossyConvertUTF16toASCII(). See comments in bug 139615, which this is probably a dupe of.
Comment 5•18 years ago
|
||
I think this is a little more complicated than just replacing NS_LossyConvertUTF16toASCII(). See comments in bug 139615, which this is probably a dupe of.
Depends on: 139615
Comment 6•18 years ago
|
||
Indeed, this happens in TB 1.5.0.5 (20060719), German localisation, too. Amavisd-new doesn't like it and quarantines such messages; that's how I noticed. The return receipt headers also do not contain an X-Mailer line. Does that conform to the RFCs? BTW, the probably related Bug 139615 has been opened in April 2002.
Comment 7•17 years ago
|
||
jshin, you're back "in business" (here) again?
OS: Linux → All
Hardware: PC → All
Comment 8•17 years ago
|
||
locale resources are usually UTF-8, so mailnews should detect use of non-ASCII in header/body and correctly send them as UTF-8-encoded fields (either via MIME-encoding or 8bit+charset, depending on if it's header or body)
Status: NEW → ASSIGNED
OS: All → Linux
Hardware: All → PC
Updated•17 years ago
|
OS: Linux → All
Hardware: PC → All
Comment 9•17 years ago
|
||
Is anyone actively working on this issue?
Comment 10•17 years ago
|
||
yeah, I thought I fixed this. Is it still broken?
Comment 11•17 years ago
|
||
marking dup - if this bug isn't totally a dup, please re-open and explain...
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Comment 12•17 years ago
|
||
When I tested today, this bug is still not fixed. TB 1.5 However, like 2~3months ago, TB 2 beta worked fine.
Comment 13•17 years ago
|
||
No one ever said it was fixed in 1.5 - it should be fixed in 2.0, which came out a while ago.
Component: MailNews: Return Receipts → MailNews: Backend
QA Contact: grylchan → offline
You need to log in
before you can comment on or make changes to this bug.
Description
•