| 1 |
Cyrus IMAP 2.4.3 Release Notes |
| 2 |
****************************** |
| 3 |
|
| 4 |
Changes to the Cyrus IMAP Server since 2.4.2 |
| 5 |
|
| 6 |
* Many fixes to replication edge case handling |
| 7 |
|
| 8 |
* Added missing flags to reconstruct |
| 9 |
|
| 10 |
* Replicate DELETED.user folders in sync_client -u (matches XFER |
| 11 |
behaviour now) |
| 12 |
|
| 13 |
* Make sync_client only connect after forking in rolling mode. Fixes |
| 14 |
two things - ssl crashes due to shared resource conflicts, and also |
| 15 |
means master will start up even if the replica is not contactable |
| 16 |
|
| 17 |
* Fixed crash on cyr_expire and ipurge annotation based expiry |
| 18 |
|
| 19 |
* Many XFER fixes for compatibility across versions: |
| 20 |
|
| 21 |
* allowing XFER in from delayed_expunge mailboxes |
| 22 |
|
| 23 |
* allowing XFER back all the way to Cyrus 2.2.12. This was |
| 24 |
accomplished by adding logic that can generate backwards-compatible |
| 25 |
older version indexes, and version detection from the imapd banner. |
| 26 |
|
| 27 |
* correctly fixing seen information for sub-mailboxes on XFER in |
| 28 |
|
| 29 |
* Multi-target replication. Strictly this is a new feature - there was |
| 30 |
a broken implementation in 2.4.0, which is how this snuck in to the |
| 31 |
bugfix release. It's not super-well documented yet, but it works by |
| 32 |
creating a separate log file for each destination "channel", and |
| 33 |
then running one sync_client process per channel, so replication can |
| 34 |
fall behind on one without affecting replication to the other. |
| 35 |
|
| 36 |
* Fixed some crashes and errors which occured when upgrading and |
| 37 |
opening corrupted mailboxes |
| 38 |
|
| 39 |
* Modified AFS ptloader configure options to allow building on more |
| 40 |
modern systems |
| 41 |
|
| 42 |
Cyrus IMAP 2.4 Releases |