MIME words (e.g.: =?UTF-8?Q?=30?=) entered by the user are not encapsulated in a MIME-compliant way
Categories
(MailNews Core :: MIME, defect)
Tracking
(Not tracked)
People
(Reporter: edu.a1978, Unassigned)
References
(Blocks 1 open bug, )
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.81 Safari/537.36
Steps to reproduce:
Compose message whose subject contains ascii text that are the characters that encodes some utf-8 string, for example an emoji like "=?utf-8?Q?=F0=9F=99=82?=" (without quotes).
Actual results:
The subject was sent as typed, so all e-mail reader display happy face emoji.
Expected results:
Subject should be encoded to show "=?utf-8?Q?=F0=9F=99=82?=". For example, it could have been sent as "=?us-ascii?Q?=3D=3Futf-8=3FQ=3F=3DF0=3D9F=3D99=3D82=3F=3D?=" or "=?us-ascii?B?PT91dGYtOD9RPz1GMD05Rj05OT04Mj89?=". Several webmail services have the same problem. Apple's mail client encodes it properly.
|
||
Comment 1•4 years ago
|
||
This bug has been reported before: Bug 756862.
However, it was probably closed by mistake. But since all involved seem to have left us, we can leave it alone.
|
|
||
Comment 2•4 years ago
|
||
RFC 2047 - 5. Use of encoded-words in message headers states (At the end of the chapter):
| [...] Use of 'encoded-word's to
| represent strings of purely ASCII characters is allowed, but
| discouraged. In rare cases it may be necessary to encode ordinary
| text that looks like an 'encoded-word'.
Description
•