-
-
Notifications
You must be signed in to change notification settings - Fork 818
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
Unexpected token in IMAP response: [atom: 0] #428
Comments
Looks like the Courier-IMAP thinks that indexes start at 0 when in fact they start at 1 :( My guess is that newer versions of Courier IMAP have been fixed. I'll commit a fix to allow 0 for the index, I guess. You will probably have to ignore an Index of 0 in the MessageFlagsChanged event, though. |
When Courier-IMAP sends "* 0 FETCH ...", the Index value in the event args will be |
Thanks Cheers Mike Nelson // CEO (and Developer) // Beweb http://www.beweb.co.nz // 09 On 22 November 2016 at 02:03, Jeffrey Stedfast [email protected]
|
I released MailKit 1.10.1 with this fix to nuget.org |
@mike-nelson would you be willing to send me the first few lines of a log connecting to Courier IMAP? I mostly care about the greeting, but the CAPABILITIES would also be nice. Thanks! |
Hi, I got this error in this case from an IMAP server called Courier-IMAP (version from 2004) which is running in the wild (this is a user - not my server).
Trying to remove a flag from an email - seems to be OK but MailKit reports this as an error.
Unexpected token in IMAP response: [atom: 0]
I'm just going to catch that error on that line and call it OK, just thought you might like to know this case.
The text was updated successfully, but these errors were encountered: