I'm getting an IMAP error fetching from Outlook Office 365.
IMAP error: bogus FETCH response
This results in all messages being lost in tracking, meaning they all
have to be refetched and I see the same error. Rinse and repeat.
Here's what I think is the relevant snippet from -D output:
S: [ 122929] Enter store_msg, flags=S, date=0, size=22738, to_trash=no
S: [ 122929] Callback enter store_msg, sts=0, uid=1237
-> new UID 1237 on slave
S: [ 122929] Callback leave store_msg
S: [ 122929] Leave store_msg
M: [ 1245] Callback leave fetch_msg
(49 in progress) M: >>> 1293 UID FETCH 337134 (BODY.PEEK[])^M
M: 1199 BAD Command Error. 12
IMAP error: unexpected tag 1199
M: Callback enter bad store
M: Enter cancel_store
M: [ 1246] Callback enter fetch_msg, flags=S, date=0, size=0
M: [ 1246] Callback leave fetch_msg
I do not see the "bogus FETCH response" message in the -D output.
I ran this again after deleting all the fetched messages and
got something slightly different:
S: [ 122503] Enter store_msg, flags=S, date=0, size=14023, to_trash=no
S: [ 122503] Callback enter store_msg, sts=0, uid=803
-> new UID 803 on slave
S: [ 122503] Callback leave store_msg
S: [ 122503] Leave store_msg
M: [ 811] Callback leave fetch_msg
(49 in progress) M: >>> 859 UID FETCH 336269 (BODY.PEEK[])^M
M: acy BAD Command Error. 12
IMAP error: unexpected tag acy
M: Callback enter bad store
M: Enter cancel_store
M: [ 812] Callback enter fetch_msg, flags=S, date=0, size=0
M: [ 812] Callback leave fetch_msg
Hrm...a differet bad command/tag value. This almost looks like
memory corruption within mbsync somewhere.
Any ideas on how to proceed?
-David
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
