-
-
Notifications
You must be signed in to change notification settings - Fork 807
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
The IMAP server replied to the 'FETCH' command with a 'BAD' response: Error in IMAP command FETCH: Invalid messageset (0.000 + 0.041 + 0.040 secs). #572
Comments
Hello Below is the log I have cleared the mail data as it is that of a customer What could be the problem? |
That command should have worked, but your IMAP server seems finicky. It might not like a single message UID in the FETCH request. I've just committed a fix to make it encode as |
FWIW, normally you don't Fetch() for a single message, you normally do it for a batch of messages to be more efficient. I probably won't get a chance to make a new nuget release for a week or so, so this fix won't show up for a little while yet. |
I had to revert my fix for this due to the fact that it breaks expected behavior. Syntax as defined by rfc3501:
So the fact that MailKit is encoding the FETCH command as:
is perfectly valid syntax that your IMAP server is not properly handling. |
That said, this will work for you in the next release: var uid = new UniqueId (78270);
var uids = new UniqueIdRange (uid, uid);
var str = uids.ToString (); // this will now be "78270:78270" |
Thanks Jeffrey
I do all the tests and update you on the results...
Bye
Il giorno sab 28 ott 2017 alle 19:30 Jeffrey Stedfast <
notifications@github.com> ha scritto:
… That said, this will work for you in the next release:
var uid = new UniqueId (78270);var uids = new UniqueIdRange (uid, uid);var str = uids.ToString (); // this will now be "78270:78270"
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#572 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AfZmbDwgSaZKXZtfKgGRtxEC76JgTKrYks5sw2TQgaJpZM4P-3o1>
.
|
To help me debug your issue, please explain:
If you got an exception, please include the exception Message and StackTrace.
Please also INCLUDE A PROTOCOL LOG (scrubbed of any authentication data), especially
if you got an exception such as
Syntax error in XYZ. Unexpected token: ...
.If you do not include the protocol log, you will make me VERY UNHAPPY.
Without a protocol log, I CANNOT fix the issue. I will simply close the bug report.
To get a protocol log, follow one of the following code snippets:
Note: if the protocol log contains sensitive information, feel free to email it to me at
jestedfa@microsoft.com instead of including it in the GitHub issue.
The text was updated successfully, but these errors were encountered: