-
Notifications
You must be signed in to change notification settings - Fork 288
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
v2: in capability-data: imapwire: expected atom, got \"\\r\"" #571
Comments
Seems similar to #540 I'm worried about calling |
Thank you very much, I will using |
This is a server bug: they are not strictly following the RFC's grammar. |
Hey @uuthink, can you say which server generated the CAPABILITY response with the trailing space? |
* a compliant response should be like: * CAPABILITY IMAP4<SP><SP>IMAP4rev1<CRLF> * this commit compatible with the following response: * CAPABILITY IMAP4<SP><SP>IMAP4rev1<SP><CRLF> related: emersion#571
a compliant response should be like: * CAPABILITY IMAP4<SP>IMAP4rev1<CRLF> this commit compatible with the following response: * CAPABILITY IMAP4<SP><SP>IMAP4rev1<SP><CRLF> related: emersion#571
For reference, cc @duesee imap.exmail.qq.com sends:
smtp-n.global-mail.cn sends:
|
Fixed in #596 |
Sometimes while fetching a mail with UIDFetch I get the following error:
Here are the logs
I noticed that there is a space before the ending newline character
I try to modify the SP method to solve this problem. The modification is as follows. Is it correct?
The text was updated successfully, but these errors were encountered: