You can send SIGINT to OfflineIMAP using (~/.offlineimap/pid) to kill it. SIGUSR1 will force an immediate resync of all accounts. This will be ignored for all accounts for which a resync is already in progress.
Can someone please explain how to send a signal to a file?
- In that file is stored PID (process ID) of the current running offlineimap process. You can use this number as an argument to kill command, to send signals. Like this:
kill -s SIGUSR1 `cat ~/.offlineimap/pid`
- You can see more details here, Nixie 13:50, 7 February 2011 (EST)
Before (re)adding more warnings about offlineimaps alleged lack of stability and the potential to cataclysmically delete all your mail, please provide some examples of where this has actually happenend. I have been using it exclusively for the last 3 years on at least 3 machines and have experienced no issues. I can't find a single forum thread describing any such massive failures and the repeated attempts to include warnings on this page is starting to look like scaremongering.
I can second Jason's view. I have been using offlineimap for well over ten years and have never experienced any kind of data loss in that time.
The whole part about killing OfflineIMAP in case of freeze should probably be removed, since offlineimap-oneshot.service includes:
I think the note about imapfw replacing OfflineIMAP is misleading. I just found myself searching for an Arch package and considering to not set up the allegedly soon to be replaced OfflineIMAP at all. imapfw has been public for over 4 years now and is still labeled "WORK IN PROGRESS and EXPERIMENTAL". The latest commit is over 2 years old. OfflineIMAP on the other hand still has active development. Grmat (talk) 13:58, 20 December 2019 (UTC)