Windows-1251-encoded subject containing CRLF fails to display correctly in message reader (malformed? tolerate anyway?)

UNCONFIRMED
Unassigned

Status

UNCONFIRMED
9 years ago
3 years ago

People

(Reporter: djordon, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: dupme)

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729)
Build Identifier: Thunderbird 2.x-3.x

Sometimes im received messages with incorrect subject.
For example:
Subject: =?windows-1251?B?W0lEIzIzNTc1XTogyOfs5e3l7ej/IOIg5+D/4urlLg==
    ?=
in HEX:
00000001A0: 3A 20 58 58 58 58 58 58 ¦ 58 58 0D 0A 53 75 62 6A  : XXXXXXXXd0Subj
00000001B0: 65 63 74 3A 20 3D 3F 77 ¦ 69 6E 64 6F 77 73 2D 31  ect: =?windows-1
00000001C0: 32 35 31 3F 42 3F 57 30 ¦ 6C 45 49 7A 49 7A 4E 54  251?B?W0lEIzIzNT
00000001D0: 63 31 58 54 6F 67 79 4F ¦ 66 73 35 65 33 6C 37 65  c1XTogyOfs5e3l7e
00000001E0: 6A 2F 49 4F 49 67 35 2B ¦ 44 2F 34 75 72 6C 4C 67  j/IOIg5+D/4urlLg
00000001F0: 3D 3D 0D 0A 20 20 20 20 ¦ 3F 3D 0D 0A 4D 49 4D 45  ==d0    ?=d0MIME



Reproducible: Always




The message source text:
X-Account-Key: account3
X-UIDL: 1158144725.36028
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
X-Mozilla-Keys:                                                                                 
Return-Path: XXXXXXXXXXXXX
<skiped>
X-Mailer: MarshallSoft SMTP/POP3 Email Engine Version 5.0.2 
X-OEM: Database Harbor Software                          
Date: Fri, 11 Dec 2009 9:22:26 +0300
To: XXXXXXX
From: XXXXXXXX
Subject: =?windows-1251?B?W0lEIzIzNTc1XTogyOfs5e3l7ej/IOIg5+D/4urlLg==
    ?=
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===SEE1094899118214453===MIX==="

--===SEE1094899118214453===MIX===
Content-Type: text/plain; charset=windows-1251
Content-Transfer-Encoding: quoted-printable
(Reporter)

Updated

9 years ago
Component: Folder and Message Lists → Message Reader UI
QA Contact: folders-message-lists → message-reader
Whiteboard: dupme
The issue is related to CRLF chars insert between "4urlLg==" and "?=" in subject line.
Could by a isp server issue?
(Reporter)

Comment 2

9 years ago
OE, MS Outlook display these letters correctly.
(Reporter)

Comment 3

9 years ago
OE, MS Outlook display these letters correctly.
(Reporter)

Comment 4

9 years ago
Whether this error will be corrected in the near future?
(In reply to djordon from comment #0)
> Sometimes im received messages with incorrect subject.
> For example:
> Subject: =?windows-1251?B?W0lEIzIzNTc1XTogyOfs5e3l7ej/IOIg5+D/4urlLg==
>     ?=

Can someone with the technical knowledge of RFC rules comment if we are supposed to tolerate CRLF in Subject lines (which causes the distorted subject)?

Reporter claims OE and OL tolerate them.
(In reply to djordon from comment #0)
> Sometimes im received messages with incorrect subject.
> For example:
> Subject: =?windows-1251?B?W0lEIzIzNTc1XTogyOfs5e3l7ej/IOIg5+D/4urlLg==
>     ?=

Can someone with the technical knowledge of RFC rules comment if we are supposed to tolerate CRLF in Subject lines (which causes the distorted subject)?

Reporter claims OE and OL tolerate them.
Summary: Subject failure display in the letter → Windows-1251-encoded subject containing CRLF fails to display correctly in message reader (malformed? tolerate anyway?)
Similar? Bug 64948, Bug 240924, Bug 506927 (which also reports other mail readers are more tolerant with malformed subjects)
TB itself *does* tolerate ASCII subjects (not encoded) with CRLF and wrapped with whitespace at beginning of second line:

Subject: Hello
   world

...will correctly display as "Subject: Hello world"
So according to http://tools.ietf.org/html/rfc5322#section-3.6.5 a subject is :

subject         =   "Subject:" unstructured CRLF

With unstructured being defined at http://tools.ietf.org/html/rfc5322#section-3.6.5
Some field bodies in this specification are defined simply as
   "unstructured" (which is specified in section 3.2.5 as any printable
   US-ASCII characters plus white space characters) with no further
   restrictions.  These are referred to as unstructured field bodies.
   Semantically, unstructured field bodies are simply to be treated as a
   single line of characters with no further processing (except for
   "folding" and "unfolding" as described in section 2.2.3).

So some CRLF are permitted in the subject for folding purposes.
You need to log in before you can comment on or make changes to this bug.