On 2024-10-08 13:13, Jan Eden wrote: > On 2024-10-08 09:40, Jan Eden via isync-devel wrote:
> > Hi,
> >
> > I synchronize a mail account with very few (large) mailboxes on two
> > machines using isync/mbsync. Each mailbox contains messages from a
> > single year, with 'Archive' being used for the current year.
> >
> > After the initial sync on the second machine (with isync 1.4.4), I ended
> > up with ~ 6800 messages instead of ~ 8400 messages in Archive, while the
> > older mailboxes (> 10,000 messages each) were synchronized entirely.
> >
> > Although each sync completes without errors and takes 'Archive' into
> > account (according to the output in debug mode), the 'Archive' mailbox
> > seems to be detached from the far side, and if I manually copy messages
> > to 'Archive' on the second machine, they are not propagated to the
> > server.
> >
> > The Inbox is synchronized properly.
> >
> > Is there anything I can do to debug?
>
> I misinterpreted the issue, which occurs on the *first* machine. This is
> what happens in debug mode:
>
> (1 in progress) F: >>> 21 APPEND "Archive" (\Answered \Seen) "16-Aug-2024
> 16:05:10 +0200" {51748+}
> F: >>>>> (51748 bytes omitted)
> (2 in progress) F: >>> 22 APPEND "Archive" (\Seen) "16-Aug-2024 15:12:15
> +0200" {8573+}
> F: >>>>> (8573 bytes omitted)
> (3 in progress) F: >>> 23 APPEND "Archive" (\Answered \Seen) "16-Aug-2024
> 16:49:37 +0200" {19318+}
> F: >>>>> (19318 bytes omitted)
> (4 in progress) F: >>> 24 APPEND "Archive" (\Seen) "16-Aug-2024 16:06:59
> +0200" {33803+}
> F: >>>>> (33803 bytes omitted)
> (5 in progress) F: >>> 25 APPEND "Archive" (\Seen) "16-Aug-2024 17:04:37
> +0200" {40036+}
> F: >>>>> (40036 bytes omitted)
> F: BAD Command Error. 10
> F: Callback enter bad store
> F: Enter cancel_store
> F: [ 34] Callback enter store_msg, sts=4
>
> When deleting the message with the timestamp 16-Aug-2024 17:04:37 and a
> second one received immediately afterwards, this happens:
>
> (1 in progress) F: >>> 21 APPEND "Archive" (\Answered \Seen) "16-Aug-2024
> 16:05:10 +0200" {51748+}
> F: >>>>> (51748 bytes omitted)
> (2 in progress) F: >>> 22 APPEND "Archive" (\Seen) "16-Aug-2024 15:12:15
> +0200" {8573+}
> F: >>>>> (8573 bytes omitted)
> (3 in progress) F: >>> 23 APPEND "Archive" (\Answered \Seen) "16-Aug-2024
> 16:49:37 +0200" {19318+}
> F: >>>>> (19318 bytes omitted)
> (4 in progress) F: >>> 24 APPEND "Archive" (\Seen) "16-Aug-2024 16:06:59
> +0200" {33803+}
> F: >>>>> (33803 bytes omitted)
> (5 in progress) F: >>> 25 APPEND "Archive" (\Answered \Seen) "16-Aug-2024
> 15:26:31 +0200" {30991+}
> F: >>>>> (30991 bytes omitted)
Sorry, incomplete extract from the log:
(1 in progress) F: >>> 21 APPEND "Archive" (\Answered \Seen) "16-Aug-2024
16:05:10 +0200" {51748+}
F: >>>>> (51748 bytes omitted)
(2 in progress) F: >>> 22 APPEND "Archive" (\Seen) "16-Aug-2024 15:12:15 +0200"
{8573+}
F: >>>>> (8573 bytes omitted)
(3 in progress) F: >>> 23 APPEND "Archive" (\Answered \Seen) "16-Aug-2024
16:49:37 +0200" {19318+}
F: >>>>> (19318 bytes omitted)
(4 in progress) F: >>> 24 APPEND "Archive" (\Seen) "16-Aug-2024 16:06:59 +0200"
{33803+}
F: >>>>> (33803 bytes omitted)
(5 in progress) F: >>> 25 APPEND "Archive" (\Answered \Seen) "16-Aug-2024
15:26:31 +0200" {30991+}
F: >>>>> (30991 bytes omitted)
F: BAD Command Error. 10
F: Callback enter bad store
F: Enter cancel_store
F: [ 34] Callback enter store_msg, sts=4
>
> Is there any way to link the error (which manifests as `IMAP error:
> unexpected tag BAD` during regular operation) to a specific message, or
> to some other known issue with the (Exchange) server?
>
> - Jan
signature.asc
Description: PGP signature
_______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
