NEWS 3.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127
  1. [1.1.0]
  2. Support for hierarchical mailboxes in Patterns.
  3. Full support for IMAP pipelining (streaming, parallelization) added.
  4. This is considerably faster especially with high-latency networks.
  5. Faster and hopefully more reliable support for IMAP servers without the
  6. UIDPLUS extension (e.g., M$ Exchange).
  7. More automatic handling of SSL certificates.
  8. Data safety in case of system crashes is improved.
  9. [1.0.0]
  10. Essentially a rewrite. Synchronization state storage concept, configuration
  11. and command line changed entirely.
  12. But you needn't to worry about the upgrade, as a fully automated migration
  13. path is provided, even for users of isync 0.7 and below.
  14. Still, you should re-read the manual to be able to take full advantage of the
  15. new features:
  16. The supported mailbox types can be freely paired.
  17. A possible application of this is using a local IMAP server to access
  18. mailboxes that are not natively supported yet.
  19. Message deletions (expunges) are now propagated both ways, so there is no need
  20. for using mutt with maildir_trash any more.
  21. Additional trash options added.
  22. `OneToOne' replaced by something more flexible.
  23. Partial support for IMAP pipelining (streaming, parallelization) added.
  24. Makes flag change propagation much faster - this affects every message that
  25. becomes Seen/Read.
  26. [0.9]
  27. Added Tunnel directive to allow the user to specify a shell command to run
  28. to set up an IMAP connection in place of a TCP socket (eg., to run over
  29. an SSH session).
  30. Added PREAUTH support (useful mostly in conjunction with Tunnel).
  31. Messages marked deleted are not uploaded when we are going to expunge.
  32. Locally generated messages are not re-fetched after uploading even if the
  33. UIDPLUS extension is not supported by the server.
  34. Added `OneToOne' configuration option: ignore any Mailbox specifications
  35. and instead pick up all mailboxes from the local MailDir and remote Folder
  36. and map them 1:1 onto each other according to their names.
  37. -C now creates both local and remote boxes; -L and -R create only local/remote.
  38. --quiet is now really quiet.
  39. [0.8]
  40. !!! IMPORTANT !!!
  41. In order to fix the problem where messages copied from one mailbox to
  42. another were not uploaded to the new mailbox, the way Isync stores the UID
  43. for each message needed to be changed. As a result, you _MUST_ delete all
  44. the messages in the local maildir box before using this version. Otherwise
  45. it will upload every message to the server thinking its a new mail.
  46. [0.7]
  47. Added `MaxMessages' configuration option to allow tracking of only the most
  48. recently added message in the local mailbox.
  49. Added --create (-C) command line option to force creation of the local
  50. maildir-style mailbox if it doesn't already exist.
  51. [0.6]
  52. Added `Delete' configuration option to correspond to the -d command line
  53. option.
  54. Added -a (--all) command line option to synchronize all mailboxes.
  55. [0.5]
  56. Updated SSL support.
  57. Added CRAM authentication support.
  58. Added MailDir configuration option to specify the default location of local
  59. mailboxes when relative paths are used.
  60. Added support for uploading local messages to the IMAP server.
  61. Added CopyDeletedTo configuration option to cause isync to move deleted
  62. messages to a particular mailbox on the server when they are expunged.
  63. [0.4]
  64. Added MaxSize configuration option to limit downloading of new messages from
  65. the server to less than some threshold.
  66. More robust --fast option works without using \Recent flags, so the previous
  67. problem with multiple accesses killing these flags is no longer a problem.
  68. RFC2060 obsoleted RFC822.PEEK, use BODY.PEEK[] instead which does the same
  69. job.
  70. Don't need to request UID in a FETCH when doing UID FETCH (RFC2060 states
  71. that its automatically returned).
  72. [0.3]
  73. Fixed to clean up temp maildir files when the fetch of a new message failed.
  74. Fixed to not assume order of the flags returned by "UID FETCH"
  75. Added support for building RPMs.
  76. [0.2]
  77. SSL support added.
  78. [0.1]
  79. Initial release.