On Tue, Oct 22, 2019 at 06:46:52PM +0200, darthd...@gmail.com wrote:
a crash is a bug irrespective of a server being funny.
please add -Dn to the command line and send me the log.
Here's the log for running mbsync with -Dn
https://gist.githubusercontent.com/darthdeus/7589662a40809a17d11652970a927b71/raw/ff94b8b3d455c011ef12d5e9cc41be36f172d631/mbsync.log
...
* 523 FETCH (UID 964 FLAGS (\Seen))
* 524 FETCH (UID 965 FLAGS (\Seen))
...
>>> 36 UID FETCH 964 (BODY.PEEK[])
* 523 FETCH (UID 964 BODY[] {4753}
)
36 OK FETCH completed (took 183 ms)
last good command.
>>> 37 UID FETCH 965 (BODY.PEEK[])
* 965 FETCH (BODY[] {4386}
)
ugh, the server is going totally haywire - it sends the uid instead of
the sequence number and omits the uid field. as a message with that
sequence number exists (uid 1599), it's plausible that it simply
overlooks the "uid" and executes a regular "fetch" instead of "uid
fetch".
try PipelineDepth 1 to see whether it just happens to have a problem
with (too much) parallelism.
whatever you find, that's something the email provider should be
informed about.
also, mbsync clearly shouldn't assert here - this isn't an internal
error, but bogus input which should be handled properly. putting it on
the todo.
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
