Outlook365 Sync Issues

I haven't seen this error before, but it appears that office365 is throttling your connection. It's not a standard response. It's just a human readable string and there's no way for MailMate to reliably parse it.

According to the message then waiting a few minutes should allow MailMate to continue, but since MailMate would continue synchronizing the account then I'm guess the error would soon return.

How large is the account in terms of number of messages and/or total message size?

I'm afraid there's nothing I can do other than suggest that you take the account offline some time before letting it continue to synchronize. (Alternatively, I could perhaps try detecting the human readable string and put MailMate into a special throttle-state -- which already exists to handle similar behavior from Gmail.)

I've been trailing MailMate and have bumped into the same issue - also using Office 365. Once while initially syncing my mail, and now when trying to clear my deleted messages folder. I have 250k emails across my entire account, and 60k deleted messages.

@Bryan: You need to enable “watching” the ticket to get my replies.

Ok, that is a pretty big account and that makes it more likely to trigger throttling when initially synching the account. I don't see though why clearing deleted messages would trigger it. This makes me think that there might be some kind of busy looping involved. Try this:

1. Take the account offline a few hours to make sure it's no longer throttled.
   
2. Open the “Activity Viewer” (⌥⌘0).
   
3. Take the account online and let it start working on deleting those emails.
   
4. If/when you get the error, use “Help ▸ Send Server Logs” to send me the logs.

Thanks in advance! (And thanks for trying out MailMate.)

@Benny

Unfortunately I wasn't able to replicate again after my first reply. I'd managed to delete about 40k when I replied and the the last 20k were deleted without incident afterwards. I even deleted my MailMate preferences and let it download my whole mailbox over again (now at 221k emails) and it didn't trigger again. I'm afraid the only other evidence I have is a screenshot of the error dialog (attached).