Ilias Tsitsimpis <i.tsitsim...@gmail.com> (2017-04-04):
> Control: fixed -1 6.6.0~rc3+dfsg1-1
> 
> Hi Cyril,
> 
> On Tue, Apr 04, 2017 at 01:28AM, Cyril Brulebois wrote:
> > Looking at the code, it seems “is that older than maxage?” is
> > implemented by looking at the timestamp in the filename for local
> > mails, which happens to be October 2016 for a mail received in 2015!
> 
> Your analysis is correct. Here is a blog post which explains in depth
> the above bug:
> 
>     http://www.offlineimap.org/devel/2015/04/14/why-we-changed-maxage.html

Yes I've read this.

> 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 may also be interested in the 'sync_deletes' feature, introduced in
> version 7.0.6+dfsg1-1. Copying from the docs:
> 
>     This option stands in the [Repository RemoteExample] section.
> 
>     Propagate deletions from remote to local. Messages deleted in this 
> repository
>     won't get deleted on the local repository if set to "no". Default is yes.

This looks like an ideal solution to my initial problem, thanks!


KiBi.

Attachment: signature.asc
Description: Digital signature

Reply via email to