From address isn't decoded if encoded data contains space

NEW
Unassigned

Status

15 years ago
2 years ago

People

(Reporter: bugzilla, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

211 bytes, message/rfc822
Details
(Reporter)

Description

15 years ago
If you have an mail with the following From header:
From: =?iso-8859-1?B?TmljaG9sYXMgT3ho+Go= ?= <blabla@bla.invalid>

the header isn't coded. Both Outlook and Outlook Express and the webmails I've
tested all decodes the From correct.
(Reporter)

Comment 1

15 years ago
Created attachment 159478 [details]
Mail testcase
Attachment #159478 - Attachment mime type: text/plain → message/rfc822
> From: =?iso-8859-1?B?TmljaG9sYXMgT3ho+Go= ?= <blabla@bla.invalid>

hmm... this space here looks suspicious... and indeed, if I remove it, it is
displayed correctly.
(Reporter)

Comment 3

15 years ago
I'm not sure where the decoding occors. I shouldn't be that hard to fix.
Summary: From address isn't decoded → From address isn't decoded if encoded data contains space

Comment 4

15 years ago
It shouldn't be that hard to generate a legal RFC2047 header, either.  What 
program generated the message from which the attachment was excerpted?

It's possible the space is being introduced by some program folding the header 
and then the header getting improperly unfolded (by an MS Exchange server?) with 
a space left in fold -- similar to the attachments at bug 87653 and bug 234547, 
where a space is introduced into the MIME boundary.

xref bug 227290
Product: MailNews → Core
sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody

Updated

11 years ago
QA Contact: mime
(Assignee)

Updated

11 years ago
Product: Core → MailNews Core

Comment 6

2 years ago
Still repro. Do we keep this open even though bug 87653 was closed as WONTFIX?

Thunderbird 52.0.1 (32-bit)
Windows 7 64-bit
You need to log in before you can comment on or make changes to this bug.