-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect RFC 1522/2047 encoding of quoted text #44
Comments
I don't understand, what is the desired action / change in DFeed here? The Unicode characters are correctly encoded and decoded in DFeed as far as I can tell. |
If you mean that you see This encoding style is used ONLY in headers. If it is encountered in the message body, it is treated like any other sequence of characters. |
BTW I see no relation to the message's subject here. The subject of the message you linked is "Re: Rant after trying Rust a bit". |
Sorry, I thought it was somehow caused by DFeed inserting the original sender into the reply without unescaping it. But you're right, Walter's using a different user agent which seems to have problems. Or, as someone else has since pointed out, Ola's newsreader wrongly uses quotes and encoded atoms at the same time. Sorry for the noise. |
The original message was sent from DFeed, so headers come from DFeed? The original diagnosis was that the escaped name is incorrectly quoted, which causes Thunderbird to choke on it. From: "Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?= According to RFC 2047 [1]: "An 'encoded-word' MUST NOT appear within a 'quoted-string'." (top of page 7), so this should be written as: From: Ola Fosheim =?UTF-8?B?R3LDuHN0YWQ=?=
|
I am away from D stuff so haven't read the entire thread. Can you propose a pull request? The relevant code is in ae.net.ietf.message, |
As I understand, it's called like this: |
- headers["From"] = format(`"%s" <%s>`, author, authorEmail);
+ headers["From"] = format(`%s <%s>`, author, authorEmail); Something like this. |
Let's try it: Hopefully this will not cause issues. |
Example:
http://forum.dlang.org/post/movlj4$29cb$1@digitalmars.com
The text was updated successfully, but these errors were encountered: