On 2017-09-06, Oswald Buddenhagen wrote: > [take care to not drop the list]
Oops, I pressed the wrong reply key. > first, make sure that you sync only [All Mail] or specific labels, but > not both. I use Gmail like a regular IMAP server. I don't have labels. However i sync both the "INBOX" and "All Mail" folders. > also, make sure to disable gmail's auto-expunge. My Gmail IMAP settings are as follows: > When I mark a message in IMAP as deleted: > - [ ] Auto-Expunge on - Immediately update the server. (default) > - [X] Auto-Expunge off - Wait for the client to update the server. > > When a message is marked as deleted and expunged from the last visible IMAP > folder: > - [ ] Archive the message (default) > - [ ] Move the message to the Trash > - [X] Immediately delete the message forever > what seems more likely is that you did something wrong with notmuch. > it's supposed to alias the actual mails (which mbsync would sync) via > symlinks into virtual folders (mbsync should not even know that they > exist). The symlinks are only one way notmuch can output its search results for other clients. I'm not using that at all. Instead I use notmuch's Emacs client, which gets the search results directly from the notmuch's stdout. However I have another hypothesis. I'm syncing both the "INBOX and "All Mail" folders. Therefore all messages in "INBOX" are duplicates of "All Mail". A move of a message is synced as a separate delete of the old message and an insert of the new message. The order of these two actions might be undetermined. Now if the new message is uploaded to Gmail first it might detect it as a duplicate of the already existing message and just merge it. Then if the delete comes second it will delete the original message, but also the new message, since it has been merged as a duplicate. mbsync sees the new message being deleted by Gmail and dutifully syncs that back to my maildir and therefore ends up deleting the new message. But that doesn't explain why that happens with other IMAP servers as well. But I'm seeing the same issue with OfflineIMAP as well, so it's probably not mbsync's fault. I might have to adjust my script to work around Gmail's IMAP folders not being actual folders where each message can only be in one folder at a time. Not syncing the INBOX folder is not an option for me since my script's purpose is to sync the presence of the "inbox" tag with being in the INBOX folder. Does anyone have a similar setup? How are you handing these problems? ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
