[MlMt] "throttled" source ?

[Benny Kjær Nielsen]

On 1 Jul 2016, at 8:15, Max Rydahl Andersen wrote:

> Yeah, I figured so much but I haven't really done anything differently 
> and I've been using this setup for over a year now.
>
> Today the source is no longer throttled so not an urgent issue at this 
> point but damn it would be useful if Google would
> provide a way to know how close one is to the limit. Right now it 
> seems to be a random ;/
>
> Anyway, seems to be an issue between Google and me, not mailmate 
> specifically.

I'm afraid I suspect MailMate is to blame since I've had some similar 
reports in the most recent months. The “throttled” state is quite 
new. This was mainly introduced to improve the behavior of MailMate 
during the initial synchronization of large account(s). When MailMate is 
in this state then it stops synchronizing with the exception of the 
INBOX. When the account is no longer throttled then MailMate resumes 
synchronization (which can quickly lead to the throttled state again, 
but there's not much I can do about that).

So, I fear that you get into the throttled state because MailMate has 
been busy looping with the server. It could be related to the issue very 
recently reported by 
[Bill](https://freron.lighthouseapp.com/projects/58672/tickets/1491-the-definition-of-insanity#ticket-1491-2), 
but I'm not sure about that. I suspect there is a separate issue only 
related to Gmail (because of the handling of IMAP keywords and Gmail 
labels).

I'm not really interested in when MailMate gets into the throttled state 
since that's just a symptom. I'm more interested in suspicious 
persistent spinners for specific mailboxes. In that case, use “Help 
▸ Send Server Logs” and I'll look for any issues.

-- 
Benny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freron.com/pipermail/mailmate/attachments/20160701/f0cdaad5/attachment.html>