3 ms·
Huh. I've never had these problems (on a Macbook Pro); the only problem I have is that if you run it from a terminal window it fucks up the tty and you have to
by jfb 16y ago
Huh. I've never had these problems (on a Macbook Pro); the only problem I have is that if you run it from a terminal window it fucks up the tty and you have to close the session. But it goes great guns from cron and I've never had it lose or misplace a mail, reading from IMAP and writing to Maildir. I know, anecdotes aren't evidence; but I'm just happy I don't have to use the godawful fetchmail/procmail combo.
- pyre 16y agoI'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.