On Sun, 15 May 2022, at 7:49 PM, Oswald Buddenhagen wrote: > On Sun, May 15, 2022 at 12:30:20PM +0100, Sean Hammond wrote: >>Not segfaults, no. isync just exits with a non-zero exit status and >>without having synced all the mailboxes and messages. For example: >> [...] >> > ok, that's within expectations. such huge mailboxes always cause > trouble, because gmail has resource limits.
Good to know. It's a bit of a pain for automated backups that isync sometimes exits mid-way through syncing. I'd have to write a loop to keep running isync until it exits with 0 (assuming it never exits with 0 without finishing the whole sync). And then I'd worry that a loop like that would loop forever if a persistent error appeared. But I'm not sure what isync could do about it since it seems to be gmail's limits that are the problem. In practice it's fine: I put my gmail account at the bottom of my .mbsyncrc file so that `mbsync --all` syncs gmail last so if syncing gmail causes mbsync to exit early that won't have prevented any other accounts from syncing. If a gmail sync crashes part-way so be it: it'll probably get the rest of the messages the next time it runs since the errors seem to be intermittent, it's not like it's stuck on the same message or mailbox every time or anything like that. >>I also sometimes see "Warning: message 1314163 from far side has >>incomplete header; skipping" when syncing Gmail although this doesn't >>cause isync to stop. >> > master-next doesn't complain about this any more (you'll get an error > message or "blank" mail in your MUA instead). Great! _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
