-
Notifications
You must be signed in to change notification settings - Fork 1
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
Proton Mail (Bridge) sends quoted strings with not allowed bytes #38
Comments
I precise that the error occurs only from Proton Bridge (v3.6.1 tested). The malformed message displays correctly in their web interface. |
CF https://datatracker.ietf.org/doc/html/rfc5738 They take it for granted and activated by default? How they handle UTF 8 in mailbox names ? |
In fact, Proton Bridge sends invalid bytes even when the message is correctly encoded. With
Looks like. I precise that I do not send any
I created a folder named
|
Looks like they also return invalid bytes in |
Looks like Proton Bridge does not support the |
May be related: ProtonMail/proton-bridge#451 ProtonMail/proton-bridge#478 |
The message is malformed I would say. But: IMAP is weird.
... can be interpreted as ... Status {
tag: ...
code: Some(Other("Error offset=5")),
// The next ":" is broken
text: "unknown command `enable`"
} ... or (with a lot goodwill) as ... Status {
tag: ...
code: None,
text: "[Error offset=5]: unknown command `enable`",
} See #31. I think the |
Given the following malformed message:
When fetching the envelope associated to this message from Proton Bridge, it returns a
FETCH
containing envelope address with not allowed bytes inside quoted strings, which leads toimap_next
errorReceived malformed message
.I did the same test with Gmail, Outlook, Posteo and even 163, they all encode correctly the sender. Proton Bridge seems to send back envelope addresses as they are in the original message.
CC @duesee
The text was updated successfully, but these errors were encountered: