Hello, On Mon, Jul 12, 2021 at 03:41:27PM +0200, Michal Suchánek wrote: > Hello, > > after mirroring my mail with mbsync I see this: > > C: 1/1 B: 8/8 F: +0/0 *0/0 #0/0 N: +0/0 *0/0 #0/0 > C: 1/1 B: 8/8 F: +0/0 *0/0 #0/0 N: +0/0 *0/0 #0/0 > C: 1/1 B: 8/8 F: +0/0 *0/0 #0/0 N: +0/0 *0/0 #0/0 > C: 0/1 B: 0/8 F: +0/0 *0/0 #0/0 N: +0/0 *0/0 #0/0 > Warning from IMAP server: Mailbox is locked, will abort in 89 seconds > Warning from IMAP server: Mailbox is locked, will abort in 58 seconds > Warning from IMAP server: Mailbox is locked, will abort in 28 seconds > C: 1/1 B: 8/8 F: +0/0 *77/77 #0/0 N: +1/1 *0/0 #0/0 > C: 0/1 B: 0/8 F: +0/0 *0/0 #0/0 N: +0/18 *0/0 #0/0 > IMAP error: unable to parse BODY[] > C: 1/1 B: 1/8 F: +0/0 *0/0 #0/0 N: +0/18 *0/0 #0/0 > C: 0/1 B: 0/8 F: +0/0 *0/0 #0/0 N: +0/0 *0/0 #0/0 > Warning from IMAP server: Mailbox is locked, will abort in 99 seconds > Warning from IMAP server: Mailbox is locked, will abort in 67 seconds > Warning from IMAP server: Mailbox is locked, will abort in 36 seconds > Warning: lost track of 18 pulled message(s) > C: 0/1 B: 0/8 F: +0/0 *0/0 #0/0 N: +0/682095 *0/0 #0/0 > Warning from IMAP server: Mailbox is locked, will abort in 92 seconds > > which suggests that IMAP error causes mbsync to throw away all state and > re-mirror all messages. Sure enough, after mirroring finished I have all > mail twice.
After investigating some more I concluded that the problem is in the mail server. There are two servers, and when connection error happens it can be because the server went down and the other took over. For some mailboxes the state is consistent across servers, for some it is not. I have very large debug logs now from multiple attempts at mirroring the mailbox but I don't think they are really interesting. Thanks for mbsync and for your continued support of this great software Michal _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
