lobo/isync
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
e2d3b4d55b
isync/NEWS

184 lines
5.3 KiB
Plaintext
Raw Normal View History

delete the compat wrapper it was deprecated in 1.2. until 1.4 gets released, enough time will have passed for sure.
2017-10-01 13:21:05 +00:00
[1.4.0]
The 'isync' compatibility wrapper was removed.
add support for (disabling) TLS v1.3 this is actually potentially counterproductive, as people who have set SSLVersions and fail to adjust it will _lose_ tls 1.3 support. however, without the option being there, people (incorrectly) believe that tls 1.3 is not supported.
2019-11-26 15:05:46 +00:00
Added support for disabling TLS v1.3 - adjust SSLVersions if you set it.
remove support for SSLv3 it's insecure and default builds of openssl don't include it any more.
2019-11-26 15:18:58 +00:00
Removed support for obsolete/insecure SSL v3.
add support for (disabling) TLS v1.3 this is actually potentially counterproductive, as people who have set SSLVersions and fail to adjust it will _lose_ tls 1.3 support. however, without the option being there, people (incorrectly) believe that tls 1.3 is not supported.
2019-11-26 15:05:46 +00:00
implement Forwarded flag maildir supports a 'P' flag which denotes the fact that a message has been 'passed' on (forwarded, bounced). notmuch syncs this to the 'passed' tag. Per https://tools.ietf.org/html/rfc5788, IMAP has a user-defined flag (keyword) '$Forwarded' that is supported by many servers and clients these days. (Technically, one should check for '$Forwarded' in the server response.) Restructure mbsync's flag parser to accept keywords (flags starting with '$') but still bail out on unknown system flags (flags starting with '\'). Support '$Forwarded' as a first keyword since it maps to maildir's 'P' and needs to be sorted in between the system flags. Signed-off-by: Michael J Gruber <github@grubix.eu>
2018-06-21 14:52:01 +00:00
The IMAP '$Forwarded' / Maildir 'P' (passed) flag is supported now.
Add support for specifying cipher string used for ssl connection Some distributions (e.g. Fedora) added support for system wide crypto policies. This is supported in most common crypto libraries including OpenSSL. Applications can override this policy using their own cipher string. This commit adds support for specifying the cipher string in the mbsync configuration. For example, to exclude Diffie-Hellman, the user can specify CipherString "DEFAULT:!DH" in the IMAP Account's configuration.
2019-11-09 18:47:55 +00:00
Support for configuring a TLS cipher string was added.
Add option to use IMAP LSUB instead of LIST Based on patch by Cedric Ware <cedric.ware__bml@normalesup.org>
2019-11-26 14:49:19 +00:00
IMAP mailbox subscriptions are supported now.
add socket timeout handling
2015-04-06 14:49:33 +00:00
[1.3.0]
Network timeout handling has been added.
make NEWS more accurate
2017-08-12 09:51:27 +00:00
Support for proper Maildir++ and a Maildir sub-folder naming style
without extra dots have been added.
support verbatim and real Maildir++ subfolder naming styles the legacy style is a poorly executed attempt at Maildir++, so introduce the latter for the sake of completeness. but most users will probably just want to use subfolders without any additional dots.
2015-05-01 17:16:23 +00:00
add support for sending a TLS client certificate
2015-08-08 17:45:53 +00:00
Support for TLS client certificates was added.
implement Message-Id based UIDVALIDITY recovery
2016-12-18 19:50:20 +00:00
Support for recovering from baseless UID validity changes was added.
rename get-cert => mbsync-get-cert to avoid undue namespace pollution. inspired by debian.
2017-10-01 08:44:09 +00:00
The get-cert script was renamed to mbsync-get-cert.
deprecate the compat wrapper after a decade, it's about time to phase it out.
2014-07-12 11:50:12 +00:00
[1.2.0]
The 'isync' compatibility wrapper is now deprecated.
don't refuse to strip Path just because it's INBOX/ no ambiguity can result from this, so there is no reason to treat sub-folders of INBOX differently from any other namespace.
2015-03-23 19:16:47 +00:00
An IMAP Path/NAMESPACE rooted in INBOX won't be handled specially any more.
This means that some Patterns may need adjustment.
revamp console output options - the old meaning of -V[V] was moved to -D{n|N}, as these are really debugging options. - don't print the info messages by default; this can be re-enabled with the -V switch, and is implied by most debug options (it was really kind of stupid that verbose/debug operation disabled these). - the sync algo/state debugging can be separately enabled with -Ds now.
2015-03-23 07:42:51 +00:00
The default output is a lot less verbose now.
The meanings of the -V and -D options changed significantly.
re-design SSL/TLS configuration the combinations of the various options made quite a mess. additionally, 'RequireSSL no' is inherently insecure - "use SSL if available" is plain stupid. the old options are still accepted, but will elicit a warning.
2014-07-12 18:35:55 +00:00
The SSL/TLS configuration has been re-designed.
SSL is now explicitly enabled or disabled - "use SSL if available" is gone.
Notice: Tunnels are assumed to be secure and thus default to no SSL.
add SASL support patch initially by Jack Stone <jwjstone@fastmail.fm>, cleaned up by Jan Synacek <jsynacek@redhat.com>, ... and then almost completely rewritten by me. ^^
2014-07-27 16:41:22 +00:00
Support for SASL (flexible authentication) has been added.
rework authentication mechanism configuration RequireCRAM (another fairly stupid "use if available" option) is now deprecated. instead, the AuthMech option can be used to give a precise list of acceptable authentication mechanisms (which is currently "a bit" short). in particular, this allows *not* using CRAM-MD5 even if it's available.
2014-07-12 19:02:25 +00:00
introduce FieldDelimiter and InfoDelimiter options ... for windows fs compatibility. the maildir-specific InfoDelimiter inherits the global FieldDelimiter (which affects SyncState), based on the assumption that if the sync state is on a windows FS, the mailboxes certainly will be as well, while the inverse is not necessarily true (when running on unix, anyway). REFMAIL: <CA+m_8J1ynqAjHRJagvKt9sb31yz047Q7NH-ODRmHOKyfru8vtA@mail.gmail.com>
2014-10-25 15:30:57 +00:00
Support for Windows file systems has been added.
added support for IMAP DEFLATE initial patch by Jesse Weaver <pianohacker@gmail.com>, but mostly rewritten by me.
2014-12-13 11:09:15 +00:00
Support for compressed data transfer has been added.
add support for propagating folder deletions
2014-12-29 01:08:48 +00:00
Folder deletions can be propagated now.
pre-release doc updates
2012-08-26 13:17:38 +00:00
[1.1.0]
Support for hierarchical mailboxes in Patterns.
Full support for IMAP pipelining (streaming, parallelization) added.
This is considerably faster especially with high-latency networks.
Faster and hopefully more reliable support for IMAP servers without the
UIDPLUS extension (e.g., M$ Exchange).
More automatic handling of SSL certificates.
pre-release doc updates
2013-12-08 21:29:15 +00:00
IPv6 support.
IMAP password query can be scripted.
Message arrival dates can be propagated.
Data safety in case of system crashes was improved.
MaxMessages was made vastly more useful.
add option to control amount of fsync()ing
2012-09-15 13:15:22 +00:00
The Big Rewrite. too many change to list them all. as opposed to earlier threats, BerkDB was not entirely dropped; i suppose the isync 0.7 -> 0.8 change had a reason, so i added an alternative UID storage scheme. note that BDB 4.0 is not sufficient, as the db->open function changed in an incompatible way ... i updated the debian packaging except for a changelog entry. note that i removed the upgrade blurb, as upstream now has a smooth upgrade path down to at least isync 0.4.
2004-03-27 16:07:20 +00:00
[1.0.0]
Essentially a rewrite. Synchronization state storage concept, configuration
and command line changed entirely.
But you needn't to worry about the upgrade, as a fully automated migration
path is provided, even for users of isync 0.7 and below.
Still, you should re-read the manual to be able to take full advantage of the
new features:
The supported mailbox types can be freely paired.
A possible application of this is using a local IMAP server to access
mailboxes that are not natively supported yet.
Message deletions (expunges) are now propagated both ways, so there is no need
for using mutt with maildir_trash any more.
Additional trash options added.
`OneToOne' replaced by something more flexible.
Partial support for IMAP pipelining (streaming, parallelization) added.
Makes flag change propagation much faster - this affects every message that
becomes Seen/Read.
- took over maintenance - moved to sourceforge - reorganized cvs structure
2002-12-28 03:05:43 +00:00
[0.9]
update
2003-05-06 02:16:05 +00:00
Added Tunnel directive to allow the user to specify a shell command to run
to set up an IMAP connection in place of a TCP socket (eg., to run over
an SSH session).
Added PREAUTH support (useful mostly in conjunction with Tunnel).
Messages marked deleted are not uploaded when we are going to expunge.
Locally generated messages are not re-fetched after uploading even if the
UIDPLUS extension is not supported by the server.
Added `OneToOne' configuration option: ignore any Mailbox specifications
and instead pick up all mailboxes from the local MailDir and remote Folder
and map them 1:1 onto each other according to their names.
-C now creates both local and remote boxes; -L and -R create only local/remote.
--quiet is now really quiet.
- took over maintenance - moved to sourceforge - reorganized cvs structure
2002-12-28 03:05:43 +00:00
updated year in copyright notice the uid for each message in the maildir is now stored in a dbm database rather than the filename. this change was necessary because isync became confused if you copied a message to another folder, in which case the uid was invalid. as a result of the above change, isync now acquires a mutex on the mailbox to protect the dbm database from concurrent access. main() was reworked to continue gracefully when an error is encountered, and to always call maildir_close() so that the lock can be disabled, and the database closed.
2002-01-16 19:47:28 +00:00
[0.8]
remove tilde backup files for distclean fixed indentation added full name to AUTHORS reformated NEWS blurb for 0.8
2002-01-16 22:23:26 +00:00
!!! IMPORTANT !!!
In order to fix the problem where messages copied from one mailbox to
another were not uploaded to the new mailbox, the way Isync stores the UID
for each message needed to be changed. As a result, you _MUST_ delete all
the messages in the local maildir box before using this version. Otherwise
it will upload every message to the server thinking its a new mail.
updated year in copyright notice the uid for each message in the maildir is now stored in a dbm database rather than the filename. this change was necessary because isync became confused if you copied a message to another folder, in which case the uid was invalid. as a result of the above change, isync now acquires a mutex on the mailbox to protect the dbm database from concurrent access. main() was reworked to continue gracefully when an error is encountered, and to always call maildir_close() so that the lock can be disabled, and the database closed.
2002-01-16 19:47:28 +00:00
Added MaxMessages patch from Eivind Eklund <eivind@FreeBSD.org>. config_defaults() can just use memcpy() instead of assigning each struct member individually. config_defaults() can be declared static
2001-11-15 23:59:27 +00:00
[0.7]
Added `MaxMessages' configuration option to allow tracking of only the most
recently added message in the local mailbox.
added --create/-C command line option to force creation of the local maildir-style mailbox if nonexistent debug.h was not included in isync_SOURCES in Makefile.am
2001-11-20 18:06:09 +00:00
Added --create (-C) command line option to force creation of the local
maildir-style mailbox if it doesn't already exist.
added `Delete' configuration option to force -d option sync_mailbox() didn't consider MaxSize == 0 to mean "unlimited". load_config() needs to print a newline in its error messages since next_arg() kills the newline of the line that was read out of the config file.
2001-10-03 05:42:22 +00:00
[0.6]
Added `Delete' configuration option to correspond to the -d command line
option.
post 0.6 commit
2001-10-31 06:06:06 +00:00
Added -a (--all) command line option to synchronize all mailboxes.
post 0.5-release commit
2001-06-13 17:13:30 +00:00
[0.5]
Updated SSL support.
Added CRAM authentication support.
Added MailDir configuration option to specify the default location of local
mailboxes when relative paths are used.
Added support for uploading local messages to the IMAP server.
Added CopyDeletedTo configuration option to cause isync to move deleted
messages to a particular mailbox on the server when they are expunged.
added MaxSize configuration variable fixed --fast to work robustly without relying on the \Recent flag in messages
2000-12-22 07:14:32 +00:00
[0.4]
Added MaxSize configuration option to limit downloading of new messages from
the server to less than some threshold.
More robust --fast option works without using \Recent flags, so the previous
problem with multiple accesses killing these flags is no longer a problem.
RFC2060 obsoleted RFC822.PEEK, use BODY.PEEK[] instead which does the same
job.
Don't need to request UID in a FETCH when doing UID FETCH (RFC2060 states
that its automatically returned).
updated NEWS for 0.3 release
2000-12-21 20:59:55 +00:00
[0.3]
Fixed to clean up temp maildir files when the fetch of a new message failed.
Fixed to not assume order of the flags returned by "UID FETCH"
Added support for building RPMs.
[0.2]
SSL support added.
initial import
2000-12-20 21:41:21 +00:00
[0.1]
Initial release.
Reference in New Issue Copy Permalink