Closed Bug 10294 Opened 21 years ago Closed 21 years ago

XML parsing error occurs when addressee name contains non-ascii

Categories

(MailNews Core :: Internationalization, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED WONTFIX

People

(Reporter: marina, Assigned: nhottanscp)

Details

Steps to reproduce:
-open New Mail composition window;
-fill out "To" using in the email address non-ascii chars:
 To:íqátést1<iqatest1@netscape.com>;
-fill out Subject field;
-sent message;
-get message and notice:
// XML parsing error and no header in the subject
*****observed with 1999-07-21-11-M9 Windows build***
Status: NEW → ASSIGNED
Target Milestone: M10
Adding mscott@netscape.com to cc as he has a similar bug 8405.
I think IQA should provide a collection of this kind of examples (not included
in the smoke test) available in a zip file.
Set mile stone to M10.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → WONTFIX
I can see MIME decoded non-ascii addressee name with my local build (pulled
8/10). Below is the data I used for the test.

From - Tue Aug 10 15:29:44 1999
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Return-Path: <naoki2@polyglot.mcom.com>
Received: from polyglot.mcom.com ([208.12.37.168]) by polyglot.mcom.com
          (Netscape Messaging Server 3.5)  with ESMTP id AAA4814;
          Tue, 10 Aug 1999 15:26:35 -0700
Message-ID: <37B0A6C1.5E8BF3AE@polyglot.mcom.com>
Date: Tue, 10 Aug 1999 15:25:05 -0700
From: =?iso-8859-1?Q?N=E1oki?= Hotta <naoki2@polyglot.mcom.com>
X-Mailer: Mozilla 4.5 [en]C-NSCP  (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: naoki2@netscape.com, naoki2@polyglot.mcom.com
Subject: test sent by =?iso-8859-1?Q?n=E1oki?=
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
test sent by n&aacute;oki</html>
Blocks: 12633
No longer blocks: 12633
QA Contact: momoi → marina
Status: RESOLVED → VERIFIED
verified as such.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.