Ilias Tsitsimpis <i.tsitsim...@gmail.com> (2017-04-10): > On Tue, Apr 04, 2017 at 07:10PM, Cyril Brulebois wrote: > > > This should be fixed in newer versions of OfflineIMAP. Could you please > > > give it a try? > > > > Well, trying out new versions is something I can do, but it really doesn't > > help with the fact that offlineimap in stable is responsible for data loss. > > You are right, that's why I didn't close this bug report. > > The patches that fix this bug should be: > > https://github.com/OfflineIMAP/offlineimap/commit/25513e90387 > https://github.com/OfflineIMAP/offlineimap/commit/8096f6cd5bf > > Unfortunately, backporting them is not trivial since they introduce > changes in the core logic of OfflineIMAP. > > Right now, I am considering uploading an updated version in stable, > where the docs will mention that this feature should not be used, and > there will also be a warning message in case it is used. Another option > would be to completely disable this feature in stable (since it is > broken and doesn't work as expected), but this may break older setups > (and I would like to avoid this). What do you think?
Yeah, I initially thought about updating the docs, but that doesn't help with longstanding ~/.offlineimaprc copied/edited from the example one. I think updated docs + warning when this setting is used would be a good compromise. This warning could get unnoticed though (because one might run offlineimap from a loop, cron, screen)… but I think it'd leave users a chance to avoid running into mail deletion. Would have worked for me at least. :D KiBi.
signature.asc
Description: Digital signature
