Hi,
I have a Gmail sync that is currently failing with this `mbsync -V` debug
output:
Synchronizing...
>>> 27 APPEND "[Gmail]/All Mail" {153284}
+ go ahead
(1 in progress) >>> 28 APPEND "[Gmail]/All Mail" (\Seen) {6304}
* BYE Invalid character in literal
IMAP error: unexpected BYE response: Invalid character in literal
After printing this error, the rest of the sync proceeds and appears to
complete just fine, but at the end of the run `mbsync` exits with an error code
of 1. I don't have any insight into what parts of the sync effectively got
skipped as a result of this unexpected BYE.
Two problems:
(1) I have no way of distinguishing between a catastrophic, immediate failure
and one like this which appears to only affect part of the sync. I'm running
this thing once a minute, but with a backoff for repeated failures. As such,
this relatively minor error is slowing down the sync loop, and I'd really only
like to do that for hard errors like network failures and the like.
(2) It's not clear to me how to fix this error. I removed all local messages
from my maildir matching U=6304, and tried to delete the corresponding things
from the server using the Gmail web UI, but I'm still getting this error on
every sync attempt.
What do you think about teaching mbsync to use different exit codes to indicate
the severity of the error? Maybe 1 for catastrophic failures that cause an
immediate abort, and 2 for errors that don't derail the rest of the sync?
Additionally, any tips for how I could find out what this troubling message
with UID 6304 is and permanently eradicate it?
-Greg
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
