3 ms·
I've never had it screw up any of my email. Thankfully, no matter what the errors ended up being, it really gracefully handled leaving IMAP/Maildir in a stable,
by pyre 16y ago
I've never had it screw up any of my email. Thankfully, no matter what the errors ended up being, it really gracefully handled leaving IMAP/Maildir in a stable, non-corrupted state. The major pain comes from keeping it going.
If it dies on a "Can't call X on NoneType object" exception, then just running it again is fine (though it's really annoying that 'production-level' consistently code dies with these types of exceptions). But protecting against offlineimap freezing when the laptop suspended in the middle of a sync (or because it hit some infinite-loop that wants to eat 99% of my CPU) is another thing altogether. It's hard to write a simple shell script to protect against those things, and I don't think that I should need to create some convoluted system of parallel processes that monitor each other just to keep offlineimap running.