Debian Codegraph @

doc/html/_sources/imap/download/release-notes/3.0/x/3.0.11.rst.txt

raw
1 :tocdepth: 3
2
3 ===============================
4 Cyrus IMAP 3.0.11 Release Notes
5 ===============================
6
7 .. IMPORTANT::
8
9 This is a bug-fix release in the stable 3.0 series.
10
11 Refer to the Cyrus IMAP 3.0.0 Release Notes for important information
12 about the 3.0 series, including upgrading instructions.
13
14 Download via HTTPS:
15
16 * https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.0.11/cyrus-imapd-3.0.11.tar.gz
17 * https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.0.11/cyrus-imapd-3.0.11.tar.gz.sig
18
19
20 .. _relnotes-3.0.11-changes:
21
22 Changes Since 3.0.10
23 ====================
24
25 Release changes
26 ---------------
27
28 We're trialing using the Github Releases feature. If you have trouble downloading
29 this release, please report this to the mailing lists. Thanks!
30
31 Data-loss bug fix (:issue:`2839`)
32 ---------------------------------
33
34 This bug affects upgrades to all Cyrus IMAP 3.0.x releases prior to 3.0.11,
35 where mailboxes have existed from 2.3 and earlier.
36
37 Specifically, mailboxes that either:
38
39 * still have an index version less than 8, or
40 * previously had an index version less than 8, but were upgraded to a newer
41 index version by Cyrus IMAP 2.4 or 2.5, or
42 * previously had an index version less than 8, but were upgraded to a newer
43 index version by some earlier Cyrus IMAP 2.3.x versions (unknown which)
44
45 may contain message records with an uninitialised modseq of 0.
46
47 Some later versions of 2.3.x (unknown which) would rewrite modseqs of 0 to 1
48 while upgrading indexes. If one of these versions was used to upgrade the
49 index, then there will no longer be message records with a modseq of 0.
50
51 This behaviour was removed during pre-2.4 refactors, so Cyrus IMAP 2.4 and
52 2.5 do not replace modseq of 0 when upgrading indexes.
53
54 A new API introduced in Cyrus IMAP 3.0.0 resulted in index records with a
55 modseq of 0 being completely ignored (therefore invisible to users, and
56 apparently "missing"). This includes the `reconstruct` utility, which means
57 that attempting to fix the "missing messages" by running `reconstruct` will
58 ignore (and maybe remove) the existing index records, and then "rediscover"
59 the message files on disk and add new records for them (without the index-only
60 data from the old record, like seen state and other flags).
61
62 Cyrus IMAP 3.0.11 no longer ignores these records.
63
64 Bug fixes
65 ---------
66
67 * Fixed :issue:`2777`: `rm` and `rsync` binary locations are now detected during
68 configure, rather than just hardcoded as `/bin/rm` and `/usr/bin/rsync`
69 * Many documentation enhancements (thanks Дилян Палаузов, Christoph Moench-Tegeder,
70 Xavier Guimard)
71 * Fixed :issue:`2795`: failing unit test on PPC (32-bit, Big Endian)
72 * Fixed :issue:`2817`: build failure with ICU 64
73 * Fixed: removed old limit of 20 delayed-delete subfolders
74 (`mailing list discussion <https://lists.andrew.cmu.edu/pipermail/info-cyrus/2019-July/040948.html>`_)
75 * Fixed :issue:`2831`: httpd version info footer formats LibXML version correctly
76 (thanks Дилян Палаузов)
77 * Fixed :issue:`2832`: httpd no longer crashes on timezone propfind for
78 nonexistent mailbox (thanks Дилян Палаузов)