You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see that when fetching data from mailbox hosted on outlook.com, hotmail.com and etc (Microsoft Exchange Server Imap)
MailKit throws thousand of exceptions. I see a lot of these lines coming from microsoft servers
It seems that is common scenario for these popular servers and may be it is not good idea to throw exceptions for those. This will improve MailKit integration with Microsoft Exchange Imap.
The text was updated successfully, but these errors were encountered:
ekalchev
changed the title
ToMailboxAddress fails to often with Exceptions
ToMailboxAddress fails often with Exceptions when parsing response from Microsoft Exchange Server Imap
Oct 18, 2022
ekalchev
changed the title
ToMailboxAddress fails often with Exceptions when parsing response from Microsoft Exchange Server Imap
ToMailboxAddress fails too often with Exceptions when parsing response from Microsoft Exchange Server Imap
Oct 18, 2022
I see that when fetching data from mailbox hosted on outlook.com, hotmail.com and etc (Microsoft Exchange Server Imap)
MailKit throws thousand of exceptions. I see a lot of these lines coming from microsoft servers
S: * 2 FETCH (UID 3 FLAGS (\Seen) INTERNALDATE "27-Jan-2021 11:56:15 +0200" RFC822.SIZE 12006 ENVELOPE (NIL "Retrieval using the IMAP4 protocol failed for the following message: 3" (("Microsoft Exchange Server" NIL NIL ".MISSING-HOST-NAME.")) NIL NIL (("[email protected]" NIL "username" "testdomain.com")) NIL NIL NIL NIL) BODYSTRUCTURE ("text" "plain" ("charset" "us-ascii") NIL NIL "quoted-printable" 1 1 NIL NIL NIL NIL) BODY[HEADER.FIELDS (IMPORTANCE RECEIVED X-PRIORITY REFERENCES)] {2}
It seems that is common scenario for these popular servers and may be it is not good idea to throw exceptions for those. This will improve MailKit integration with Microsoft Exchange Imap.
The text was updated successfully, but these errors were encountered: