Slow synchronization with Mailkit for yahoo, hotmail

[ekalchev]

We notice significant performance drop when using Mailkit IMAP, compared to Outlook or other email clients. I believe it is related to latency between issuing imap command and actual response from the server for some servers (yahoo, hotmail). For example yahoo imap - there is 1-3 sec delay between executing the command and getting back the response(tag FETCH 1 (BODY[])). We are trying to reduce amount of imap commands to speed up synchronization. Currently we use
GetStream method to download full messages and we execute this method for each message in the mail box. For mailbox with 200 emails that emit 200 imap fetch commands which stack up to 200-400sec delay only for getting response from the server(not accounting the actual data stream).

I can see commercial email clients like Outlook can achieve 10-20 times faster synchronization (when they are configured to download full messages (not only message summaries). I believe they download message bodies using batch like
tag FETCH 1:20 (BODY[])

Some performance figures for yahoo imap using console commands

tag FETCH 1 (BODY[]) - 6 sec to complete
tag FETCH 1:2 (BODY[]) - 7 sec to complete
tag FETCH 1:20 (BODY[]) - 11 sec to complete
tag FETCH 1:50 (BODY[]) - 25 sec to complete

It is clear it is much faster to download bodies on batch but I can't find a way to do this with Mailkit. I tripple checked the mailkit metods and can't find overload that allows me to do that. I would like to know how hard is to implement such overload myself or any advice how to speed up the synchronization with high latency servers?

[jstedfast]

What makes you think they are downloading full messages? You don't need to download all of the messages to show a message-list in an email client.

Use the Fetch() method to batch request the summary information.

[ekalchev]

We are implementing a mode where the user can choose to download full messages not only the summaries. Most of the email clients have this option. We already have synchronization that download message bodies on request (when the user try to open the actual message)

For outlook it is easy to see that the full message is downloaded by disconnecting from internet and check if you have access to the attachments and email text. Almost all email clients have this option.

[jstedfast]

They download using multiple connections, not just 1.

The problem with offering an API to batch download infinite full messages is, well, you don't have infinite memory and most users of my library do not understand this.

I've had complaints from users who download 1 message at a time, adding them to a List<MimeMessage> and complain that they eventually get an OutOfMemoryException.

I'm sure you can understand my hesitation with implementing this feature :)

[ekalchev]

Multiple connections was my first guess but I looked at the Outlook connections with TCPView and it was clear there was only one imap connection open. I believe i'll manage to add the functionality I need by myself.

[jstedfast]

it should be trivial to do. I modified the internal code to make this easier a few weeks ago.

[ekalchev]

This seems to be working https://github.com/ekalchev/MailKit/commit/af7cd360f95828bb82f1a94078d884e7d4ccdbf9
I'll be happy if you take a look. It is POC so the interface is bad but I need to know if I am on the right path and I am not missing something.

I am getting 20-50 times faster synchronization speed with yahoo when downloading full messages.

[jstedfast]

Yep, looks like your code is functionally correct.

I thought about this a bit last night and realized that returning an IList<MimeMessage> would be terrible because there'd be no way to know which message mapped to which UID and/or index which is pretty important for IMAP clients to be able to do (unless the "client" is just using IMAP like a POP3 server).

I also got to thinking that it may be a good idea, when requesting a list of messages by index, that you also provide the caller with the UID for each of those messages since the client will most likely want to cache these messages by the UID (useless to cache by index and somewhat racey if you use the index to do a UID lookup based on a previously cached IMessageSummary list if you aren't correctly listening to all events and/or if the API did return a list of messages rather than using a real-time callback approach).

[ekalchev]

Yeah returning IList is not a good idea. Additional to what you said that is also a lot of bytes allocated. However with streams it is different - if you don't return the streams but raise event when each stream is available the user can read the stream(save it to file or database) and dispose it. (or re-use the same memory with Microsoft.IO.RecyclableMemoryStream). This way you won't waste much memory for large number of messages and still have the flexibility fetching message parts with single FETCH command. Yeah you'll need to pair those stream with UID or index somehow.

I can give you another use case that cannot be done efficiently with Mailkit and it doesn't involve download of a full message.

See the message preview with red - that is part in most email clients. This preview is actually the first N characters of the TEXT body part of the message. So if I want to implement this with Mailkit I need to pull IMessageSummary on batch of 30 messages - that will be very efficient. However, to obtain the TEXT part of each message I don't have interface to pull those 30 TEXT parts as a single batch and I'll need to execute 30 commands FETCH index (BODY.PEEK[TEXT]). I need to wait those 30 fetches and with yahoo that is about ~40-60 sec. This way the experience of the user will be very slow synchronization even if I am not downloading the entire message. I understand the interface for such functionality is challenging but there are very common use cases which cannot be implemented efficiently with Mailkit . I hope in the future you can come up with something to cover this.

[jstedfast]

You probably don't want to use BODY.PEEK[TEXT] for that. I think what you actually want for that is to fetch the IMessageSummary.TextBody part's .TEXT part.

I've been trying to think of a way to do that and have been somewhat waiting for the IMAP working group to standardize a way to get this. There was talk a few years back about an IMAP extension for this but I have yet to see a draft/rfc for it.

Maybe it's time to give up waiting...

[jstedfast]

I've just committed a patch to add support for batch requesting message streams using a callback approach. I think that will satisfy your needs.

About the message text blurb: how many characters do you actually need? I was thinking about adding a MessageSummaryItem that I could use to mean "get the message text blurb".

It would be a less-awkward API than providing a GetStreams() method that takes a list of uids & BodyPart specifiers.

The problem is that it means I either need a new set of Fetch() methods that now also take a "blurbLength" argument or else I hard-code it to something (with the possibility of making it overridable if you subclass ImapClient or something?).

[jstedfast]

I was thinking of just requesting 1024 bytes, but that seems overkill. Maybe 256 bytes?