offlineimap (7.1.2+dfsg1-1) unstable; urgency=low The status_backend configuration option has been removed, hence it is no longer possible to select the (legacy) plain text database. Anyone still using the old database will automatically migrate to the sqlite one. Note that, due to limitations in the code, the initial conversion may be extremely slow. As a workaround, consider running offlineimap with eatmydata while converting the database. -- Ilias Tsitsimpis Tue, 11 Jul 2017 18:00:33 +0300 offlineimap (7.0.6+dfsg1-1) unstable; urgency=medium With OfflineIMAP version v7.0.0, the sqlite database becomes the default. This change means that downgrading from v7.* to any previous release might be prone to errors. While the migration from the (legacy) plain text database to sqlite is seemingly handled, this is not the case the other way around. The plain text database may be deprecated and removed in the future. As part of work to support Python3, passwords are now expected in Unicode almost everywhere. However, some configuration options are not UTF-8 friendly, mostly because of library limitations (e.g., remotepass). Users with Unicode characters in the passwords are recommended to use a file or remotepasseval. Finally, If you have scripts using the PID file, be aware this file is no longer used because running multiple instances of the program is supported for years. -- Ilias Tsitsimpis Mon, 19 Sep 2016 15:33:05 +0300 offlineimap (6.7.0+dfsg1-1) unstable; urgency=low OfflineIMAP version 6.3.5 introduced a regression by changing the FMD5 part of a message's filename. This may cause a complete re-upload of all local emails, since OfflineIMAP believes that all the messages have been removed and adds them back. In case you are upgrading from a version older than 6.3.5, you may need to use the '--migrate-fmd5-using-nametrans' option in order to migrate the FMD5 hashes. For more information, see: http://www.offlineimap.org/configuration/2016/02/12/debian-upgrade-from-jessie-to-stretch.html -- Ilias Tsitsimpis Tue, 22 Mar 2016 10:11:06 +0200 offlineimap (6.6.0~rc3+dfsg1-1) unstable; urgency=medium OfflineIMAP has now SSL enabled by default to prevent sending private data in clear. The 'maxage' feature has also been removed for IMAP-to-IMAP sync since it was broken. Instead, a new option (named 'startdate') has been introduced, designed for IMAP/IMAP setups only. As for the Debian package, OfflineIMAP is now treated as a Python application (i.e., its modules are private) and uses the python-imaplib2 package instead of an embedded copy. -- Ilias Tsitsimpis Tue, 24 Nov 2015 13:59:19 +0200 offlineimap (6.5.4-1) unstable; urgency=low offlineimap.conf: * SSL certificate fingerprints are now actually verified. You may want to use provide correct fingerprints or use Debian SSL CA certifications for Remote repository validation with the following option: `sslcacertfile = /etc/ssl/certs/ca-certificates.crt` * createfolders (Default: True) enables creating folders in a repository, and can be set to False to disable the propagation of new folders to the new repository. See sample offlineimap.conf. * Notices added that '%' needs to be encoded as '%%' -- Dmitrijs Ledkovs Sun, 03 Jun 2012 23:55:15 +0100 offlineimap (6.5.3.1-2) unstable; urgency=low Reverse nametrans +++++++++++++++++ Starting with v6.4.0, OfflineImap supports the creation of folders on the remote repostory. This change means that people that only had a nametrans option on the remote repository (everyone) will need to have a nametrans setting on the local repository too that will reverse the name transformation. For further information, see documentation about this feature at: file:///usr/share/doc/offlineimap/html/nametrans.html#reverse-nametrans -- Dmitrijs Ledkovs Sun, 29 Apr 2012 18:13:18 +0100