| Summary: | Particular combination of UTF8 characters results in corrupt subject in Yahoo mail | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Claws Mail (GTK 2) | Reporter: | George <removed-gdpr> | ||||
| Component: | Plugins | Assignee: | users | ||||
| Status: | RESOLVED INVALID | ||||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | 3.16.0 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Attachments: |
|
||||||
They both display fine in claws-mail, they just different character encoding. There is no bug here. There is a bug because it results in incompatibility and because it is happening only with particular set of characters. If the subject is simply "Абв" it does not happen. I don't know what standard Yahoo uses for encoding the subject and what CM uses but it would be good to check why this is happening (perhaps provide an option for being compatible). Yahoo is quite popular (for good or bad). (In reply to comment #2) > There is a bug because it results in incompatibility and because it is > happening only with particular set of characters. If the subject is simply > "Абв" it does not happen. > > I don't know what standard Yahoo uses for encoding the subject and what CM > uses but it would be good to check why this is happening (perhaps provide an > option for being compatible). Yahoo is quite popular (for good or bad). Yes, and it's yahoo's bug. In one the subject was encoded using quoted-printable and the other is base64. |
Created attachment 1861 [details] screenshots + message sources STR: 1. Using a Yahoo IMAP account open to compose a new message in CM 2. Type in subject: Абв 123 ( - где 12345-6) + жзи 3. Save in Drafts (or send) 4. Go to Yahoo web mail 5. Repeat 1-3 creating another message EXPECTED The 2 messages should have the same subject exactly as typed ACTUAL The message created in CM shows in Yahoo with subject Абвгдежзи and looking at the source of both messages reveals that there it is different too. Yet in CM's message list the two subjects look identical NOTE: Tested with a Gmail account too - no issue there.