[MlMt] Gmail message not moving to trash or changing read status

[Zvi Biener]

Thanks, Shoshanna. Fascinating. Where in MM did you see the 
‘throttled’ message? I don’t see it now, but I often don’t see 
what’s in front of my eyes! FWIW, I have not had any series 
up/download activity with gmail, so I don’t think they would have a 
reason to throttle me, but who knows…

On 26 Mar 2026, at 16:49, Shoshanna Green wrote:

> I'm seeing a similar problem with a start sometime in the last few 
> weeks; I don't use tags, but messages I delete in MailMate on my 
> desktop are often still in the inbox in Mail on my iOS devices and in 
> the Gmail web interface.
>
> The problem first started happening a month or two ago when I set up 
> MailMate on a new laptop. MailMate dutifully began downloading 
> alllllll my mail to its new installation, which was so much traffic (I 
> guess) that Gmail throttled the account; while throttled, deletions I 
> did on that laptop (and moves of messages from the inbox to folders) 
> weren't correctly carried out in the cloud or echoed to other MailMate 
> installations. MailMate on that laptop has long since finished 
> synching, and everything seemed fine for a while, but now MailMate 
> deletions on my desktop often have the same problem.
>
> I assumed that Gmail was throttling me again, for some unknown reason, 
> although I didn't ever catch the account actually showing "throttled" 
> -- until earlier today, when the "throttled" label did appear briefly 
> on my desktop MailMate installation.
>
> Zvi, any chance your account is also being throttled?
>
> If that's not the cause -- and again, I didn't actually see my account 
> marked "throttled" for most of the time that deletions have failed to 
> work, but I might have missed it -- I too would love to know what it 
> might be!
>
> On 26 Mar 2026, at 15:28, Zvi Biener wrote:
>
>> Hi All,
>> I wonder if anyone has run into the following behavior, or can think 
>> of why it is happening.
>>
>> Basically, it seems like MM is not moving Gmail inbox messages to the 
>> trash, and not changing their read status. I know that the MM/Gmail 
>> interaction is tweaked insofar as tags are concerned, but my setup 
>> has worked for years, but something changed in February.
>>
>> The flow is this: a message comes into the Inbox. It is matches 
>> certain criteria, it is deleted (using the “Delete”) action in 
>> the rules, and then a tag is added to it; say, “Marketing”. I am 
>> *not* subscribed to the “Marketing” folder in my gmail account 
>> from the MM side, since I want the tags to show *as tags* (for reason 
>> irrelevant here). The message remain unread, and I see it in a MM 
>> smart mailbox defined by the “Marketing” tag. (I’m not sure why 
>> it is deleted first and then tagged, as opposed to tagged and 
>> deleted; I set this up ages ago and remember having a reason, but I 
>> don’t remember what).
>>
>> This all looks perfectly fine from the MM side — the message’s 
>> source mailbox shows as Gmail/Trash and it is tagged properly. But 
>> the message is not actually moved to the Trash folder in Gmail, and, 
>> even after it is read in MM, remains as unread in Gmail. If I flag 
>> it, it does not become flagged in Gmail. However, if I flag it in 
>> Gmail, it becomes flagged in MM; but if I then unflag it, it does not 
>> unflag in Gmail.
>>
>> I don’t think this is related to an update in MM, since the 
>> timestamp on my MM app is from October, and the issue seems to have 
>> started in February. But I’m using the 6290 version.
>>
>> Any ideas?
>>
>> Thanks,
>> Zvi
>> _______________________________________________
>> mailmate mailing list
>> Unsubscribe: https://lists.freron.com/listinfo/mailmate
>
>
> Shoshanna Green (she/her)
> shoshannag at gmail.com
> _______________________________________________
> mailmate mailing list
> Unsubscribe: https://lists.freron.com/listinfo/mailmate
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freron.com/pipermail/mailmate/attachments/20260327/0c60a1e5/attachment-0001.htm>