Michael Brunnbauer writes:
Hello Sam, On Thu, Feb 07, 2019 at 06:40:13AM -0500, Sam Varshavchik wrote: > 0xa0 is ISO-8859-1, not even UTF-8. In UTF-8, the non-breaking space is > multibyte sequence 0xc2 0xa0. Ah yes - it's not interpretable as UTF-8. So even POP3/IMAP-Clients that support RFC 6855 would get that error message with the mail from Paypal?
No, they'll get the message, but it'll be up to them to figure out what to do with it. This is where RFC 6855 sets the bar: if mail contains non-ASCII headers it is presumed to be UTF-8 and IMAP clients that didn't indicate that they understand UTF-8 will get the cold shoulder.
It would be nice to have two different error messages - one for the client fail and one for the sender fail - so I don't have to do detective work each time. I'm also not sure which clients besides mutt cannot handle message/global. Being unable to read the original message would make the thing much worse for my customers. Sarcasm aside - I like software that screams when things go wrong. But in a broken ecosystem with paying customers, I also need the option to be liberal.
The raw message can always be downloaded. Any MIME client worth it's salt will have an option to download unknown content that it doesn't recognize. If a particular client doesn't offer an option to do so, it's broken.
On MS-Windows, there is an extension that associated files with E-mail messages. Either .eml, or maybe .msg. Downloading the message and saving it as such should make the resulting file openable with the system default E- mail client.
pgplcO9qpIpiE.pgp
Description: PGP signature
_______________________________________________ Courier-imap mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
