Re: Working with gmail

[Oswald B. <osw...@gm...>]

On Thu, Nov 06, 2025 at 02:43:55AM +0200, Gesh wrote:
>> Error: channel gesh-iobox: near side box [Gmail]/Sent Mail cannot be 
>> opened.
>Investigating suggests I need to escape the name of the near-side box by writing
>it as
>> Channel gesh-iobox-sent
>> Far :gesh-remote:"[Gmail]/Sent Mail"
>> Near :gesh-local:"\\[Gmail\\]/Sent Mail"
>>
huh ... where did you get that from?

>A tangential bug I had here is that for some reason, syncing messages 
>meant that a bunch of them had their delivery times reset *on the 
>server end*,
>
i suppose this would happen if the messages are moved between boxes 
client-side (and thus re-delivered to gmail's unified inbox).

>> CopyArrivalDate yes
>and hope it fixes things
>
i guess it might.

>An alternative concept would be to patch mbsync so it stores/updates 
>IMAP extension attributes. Eg for Gmail[1], a configuration such as
>> IMAPAccount ...
>> StoreAttr X-GM-MSGID X-GM-THRID X-GM-LABELS
>> UpdateAttr X-GM-LABELS
>
i think it's a bit "optimistic" that one could just name random 
attributes and expect them to be handled usefully without isync knowing 
their semantics.
anyway, there is a long-standing todo item to support imap keywords.

>Finally finally, I'm not sure I 100% understand the guidance re 
>trashing/expunging and its interaction with Gmail --

>do I understand correctly that the default behaviour is for the Gmail 
>server to automatically delete email once it's vanished from all 
>labels,
>
dunno. i don't actively use gmail, and haven't looked at the settings 
for a few years.

>preventing batch processing,
>
no idea what you mean here.

>and that the recommended behavior instead is to set it to move messages 
>to Trash once their final copy is expunged?
>
gmail may have a setting to trash on expunge. using that would be a good 
choice, indeed.

ps: i overlooked your message in the moderation queue. it's best to 
subscribe ...