Hi,
On Fri, Oct 28, 2022 at 02:23:48PM +0200, Oswald Buddenhagen wrote:
> > Problem is, the message doesn't go away when you re-run mbsync.
> >
> that's worrisome.
> re-run with -D.
I'm not sure how much context you need. I'm hesitant to post the whole log as
it contains things about my mailboxes in it.
The relevant bit seems to be:
```
...
Oct 28 15:20:31 -> log: & 110994 0 (TUID lost)
Oct 28 15:20:31 pair(111024,0) TUID TxgMA2qxXYAr
Oct 28 15:20:31 -> log: & 111024 0 (TUID lost)
Oct 28 15:20:31 pair(111040,0) TUID dwlaHQNJcRsT
Oct 28 15:20:31 -> log: & 111040 0 (TUID lost)
Oct 28 15:20:31 pair(111048,0) TUID g0eDFBImd3uK
Oct 28 15:20:31 -> log: & 111048 0 (TUID lost)
Oct 28 15:20:31 pair(111051,0) TUID LM96m56YJLw1
Oct 28 15:20:31 -> log: & 111051 0 (TUID lost)
Oct 28 15:20:31 pair(111053,0) TUID nE3Fxc1C+UVi
Oct 28 15:20:31 -> log: & 111053 0 (TUID lost)
Oct 28 15:20:31 pair(111065,0) TUID IUiq9bleIf+E
Oct 28 15:20:31 -> log: & 111065 0 (TUID lost)
Oct 28 15:20:31 pair(111070,0) TUID sW6CsXoqj/2b
Oct 28 15:20:31 -> log: & 111070 0 (TUID lost)
Oct 28 15:20:31 pair(111075,0) TUID P8TdPwBLGUir
Oct 28 15:20:31 -> log: & 111075 0 (TUID lost)
Oct 28 15:20:31 pair(111081,0) TUID Zo1MVI71Vxhk
Oct 28 15:20:31 -> log: & 111081 0 (TUID lost)
Oct 28 15:20:31 Warning: lost track of 112 pulled message(s)
Oct 28 15:20:31 matching messages on near side against sync records
Oct 28 15:20:31 N: [ 8] Callback leave load_box
Oct 28 15:20:31 N: [ 8] Leave load_box
Oct 28 15:20:31 F: [ 5] Callback leave open_box
Oct 28 15:20:34 F: * 1 FETCH (UID 63843 FLAGS (\Seen))
Oct 28 15:20:34 F: * 2 FETCH (UID 63844 FLAGS (\Seen))
Oct 28 15:20:34 F: * 3 FETCH (UID 63846 FLAGS (\Seen))
...
```
> > Changing the pipeline depth from 4 to 1, it becomes:
> > ```
> > far side: 41156 messages, 0 recent
> > Warning: lost track of 1 pushed message(s)
> > Synchronizing...
> > > > > 8 APPEND "INBOX" (\Seen) {29056725}
> > + go ahead
> > Socket error on imap.gmail.com (64.233.184.108:993): timeout.
> > ```
> >
> that's weird - this was supposed to be fixed since v1.3.2.
> running
> mbsync -DN gmail 2>&1 | ts
>
> should reveal roughly what is going wrong (`ts` is in `moreutils` on debian;
> i suppose *bsd has something similar).
```
...
Oct 28 15:17:08
MTE5NTI0NiAwMDAwMCBuIAowMDIxMTk1Nzk4IDAwMDAwIG4gCjAwMjExOTYxNjIgMDAwMDAg
Oct 28 15:17:08
biAKdHJhaWxlcgo8PCAvU2l6ZSAzMTYgL1Jvb3QgMTkyIDAgUiAvSW5mbyAzMTUgMCBSIC9J
Oct 28 15:17:08
RCBbIDwwM2RhNGFhMDQ3YmU4NWNkOTgzZDE1ODg3OGJmNDY4ZT4KPDAzZGE0YWEwNDdiZTg1
Oct 28 15:17:08
Y2Q5ODNkMTU4ODc4YmY0NjhlPiBdID4+CnN0YXJ0eHJlZgoyMTE5NjM5NAolJUVPRgo=
Oct 28 15:17:08
Oct 28 15:17:08 --ybR7w8Lo12h+exFG--
Oct 28 15:17:08 >>>>>>>>>
Oct 28 15:17:09 (1 in progress) >>> 10 UID FETCH 110231 (BODY.PEEK[])
Oct 28 15:17:36 (2 in progress) >>> 11 UID FETCH 110283 (BODY.PEEK[])
Oct 28 15:17:36 (3 in progress) >>> 12 UID FETCH 110284 (BODY.PEEK[])
Oct 28 15:17:56 Socket error on imap.gmail.com (74.125.140.109:993): timeout.
```
Any ideas?
--
Best Regards
Edd Barrett
https://www.theunixzoo.co.uk
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
