c4d7f0189c
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>
177 lines
5.1 KiB
Plaintext
177 lines
5.1 KiB
Plaintext
[1.4.0]
|
|
|
|
The 'isync' compatibility wrapper was removed.
|
|
|
|
The IMAP '$Forwarded' / Maildir 'P' (passed) flag is supported now.
|
|
|
|
[1.3.0]
|
|
|
|
Network timeout handling has been added.
|
|
|
|
Support for proper Maildir++ and a Maildir sub-folder naming style
|
|
without extra dots have been added.
|
|
|
|
Support for TLS client certificates was added.
|
|
|
|
Support for recovering from baseless UID validity changes was added.
|
|
|
|
The get-cert script was renamed to mbsync-get-cert.
|
|
|
|
[1.2.0]
|
|
|
|
The 'isync' compatibility wrapper is now deprecated.
|
|
|
|
An IMAP Path/NAMESPACE rooted in INBOX won't be handled specially any more.
|
|
This means that some Patterns may need adjustment.
|
|
|
|
The default output is a lot less verbose now.
|
|
The meanings of the -V and -D options changed significantly.
|
|
|
|
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.
|
|
|
|
Support for SASL (flexible authentication) has been added.
|
|
|
|
Support for Windows file systems has been added.
|
|
|
|
Support for compressed data transfer has been added.
|
|
|
|
Folder deletions can be propagated now.
|
|
|
|
[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.
|
|
|
|
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.
|
|
|
|
[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.
|
|
|
|
[0.9]
|
|
|
|
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.
|
|
|
|
[0.8]
|
|
|
|
!!! 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.
|
|
|
|
[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 it doesn't already exist.
|
|
|
|
[0.6]
|
|
|
|
Added `Delete' configuration option to correspond to the -d command line
|
|
option.
|
|
|
|
Added -a (--all) command line option to synchronize all mailboxes.
|
|
|
|
[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.
|
|
|
|
[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).
|
|
|
|
[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.
|
|
|
|
[0.1]
|
|
|
|
Initial release.
|