TB should support RFC-6856 for proper UTF-8 support in POP3
Categories
(MailNews Core :: Networking: POP, enhancement)
Tracking
(Not tracked)
People
(Reporter: Ralf-mozilla.org, Unassigned)
References
Details
Steps to reproduce:
Upgrade Courier POP3 server to a version (1.0.6-1) that suddenly sends warnings about a client that doesn't properly support RFC-6856.
Actual results:
One of my users complained that they are receiving "strange" emails via POP3 that all contain the following warning:
Subject: Cannot display Unicode content
From: Mail Delivery Subsystem <postmaster>
This E-mail message was determined to be Unicode-formatted
but your E-mail reader does not support Unicode E-mail.
Please use an E-mail reader that supports POP3 with UTF-8
(see https://tools.ietf.org/html/rfc6856.html).
This can also happen when the sender's E-mail program does not
correctly format the sent message.
The original message is included as a separate attachment
so that it can be downloaded manually.
Expected results:
Message should have been retrieved properly from POP3 server with no warnings, preserving all UTF-8 encoded characters.
Reporter | ||
Comment 1•2 years ago
•
|
||
The TB team have already dealt with the respective problem for IMAP: Bug 1571672
Updated•2 years ago
|
Comment 3•1 year ago
|
||
As https://bugzilla.mozilla.org/show_bug.cgi?id=1860540 has been closed:
If the server delivers unescaped iso-8859-* messages, Thunderbird will display these as ascii text, showing strange symbols for the missing special characters.
The Maildir storage system stores each mail as a single file, preserving the original encoding, and courier-pop will deliver these as they are. The file utility will show ascii, utf8 or iso-8859-(1,12,15) as encoding for the individual email files, if used on the server. The unicode error messages will only be generated for unescaped utf8 encoded email.
Description
•