Debian Codegraph @

doc/html/_sources/imap/download/release-notes/3.10/x/3.10.0.rst.txt

raw
1 :tocdepth: 3
2
3 =====================================
4 Cyrus IMAP 3.10.0 Release Notes
5 =====================================
6
7 Download from GitHub:
8
9 * https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.10.0/cyrus-imapd-3.10.0.tar.gz
10 * https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.10.0/cyrus-imapd-3.10.0.tar.gz.sig
11
12 .. _relnotes-3.10.0_changes:
13
14 Major changes since the 3.8 series
15 ==================================
16
17 * URLs found in HTML ``<a>``, ``<area>`` and ``<img>`` tags, as well as "alt"
18 text in ``<img>`` tags, are now indexed for search and snippets
19 * :cyrusman:`cyr_expire(8)` now supports non-day durations in the
20 archive/delete/expire annotations
21 * :cyrusman:`cyr_expire(8)` no longer supports fractional durations in command
22 line arguments. Installations that passed fractional durations such as
23 "1.5d" to any of the ``-E``, ``-X``, ``-D``, or ``-A`` arguments must adapt
24 these to only use integer durations such as "1d12h"
25 * :cyrusman:`cyr_expire(8)` now supports the 'noexpire_until' annotation to
26 disable cyr_expire per user
27 * JMAP calendar default alarms are now stored in a non-DAV mailbox annotation.
28 See :cyrus-3.10:`/imap/download/upgrade.html#default-alarms`
29 for upgrading instructions if you are
30 already using the experimental JMAP Calendars API
31 * Removes support for parsing and generating bytecode for the deprecated
32 denotify action and notify actions using the legacy (pre-:rfc:`5435`) syntax.
33 Existing bytecode containing these actions will still be executed. Scripts
34 that contain the deprecated denotify action should be rewritten to remove
35 them. Scripts that contain notify actions using the legacy syntax should be
36 rewritten to use the syntax in :rfc:`5435`
37 * Adds support for the "exp" and "nbf" JSON Web Token claims. Thanks Bruno
38 Thomas
39 * Adds support for IMAP Version 4rev2 (:rfc:`9051`)
40 * Adds support for IMAP NOTIFY (:rfc:`5465`). Only available if ``idled`` is
41 running
42 * Refresh interval for APNS subscriptions to DAV resources is now configurable.
43 See the ``aps_expiry`` :cyrusman:`imapd.conf(5)` option
44 * Upgrade IMAP Quota support to :rfc:`9208`. Sites running a Murder will be
45 unable to set ANNOTATION-STORAGE or MAILBOX quotas (formerly known as
46 X-ANNOTATION-STORAGE and X-NUM_FOLDERS) in a mixed-version environment until
47 frontends are upgraded. Upgraded frontends know how to negotiate with older
48 backends.
49 * Adds support for IMAP REPLACE (:rfc:`8508`)
50 * Adds support for IMAP UIDONLY extension (:draft:`draft-ietf-extra-imap-uidonly`)
51 * Adds experimental support for JMAP Contacts per upcoming IETF standards.
52 Requires the not-yet-released
53 `libicalvcard <https://github.com/libical/libical/pull/584>`_
54 * :cyrusman:`squatter(8)` now supports the "wait=y" :cyrusman:`cyrus.conf(5)`
55 option when started in rolling mode from the ``DAEMON`` section
56 * :cyrusman:`master(8)` now touches a ready file to indicate it is "ready for
57 work". See :cyrus-3.10:`/imap/download/upgrade.html#master-pid-and-master-ready-files`
58 * :cyrusman:`master(8)` now gets its pidfile name from the ``master_pid_file``
59 :cyrusman:`imapd.conf(5)` option. See :cyrus-3.10:`/imap/download/upgrade.html#master-pid-and-master-ready-files`
60 * Adds pcre2 support. Prefers pcre2 over pcre if both are available. See
61 :ref:`upgrade_pcre2_support`
62 * The ``proc`` :cyrusman:`cyr_info(8)` subcommand now also reports DAEMON and
63 EVENTS processes
64 * JMAP CalendarEventNotification objects are now automatically pruned.
65 The ``jmap_max_calendareventnotifs`` :cyrusman:`imapd.conf(5)` option can be
66 used to tune this behaviour
67 * Cyrus now requires libical >= 3.0.10 for HTTP support
68 * Sieve [current]date ``:zone`` parameter now accepts either a UTC offset or an
69 IANA time zone ID
70 * Adds an ``implicit_keep_target`` Sieve action to change the target mailbox
71 for an implicit keep
72 * :cyrusman:`squatter(8)` no longer holds a mailbox lock while extracting text
73 from attachments
74 * IMAP ``RENAME`` command no longer emits non-standard per-folder updates. Use
75 the new ``XRENAME`` command if you need this behaviour
76 * Outgoing SMTP connections now EHLO as `client_bind_name` or `servername`
77 rather than `localhost`
78 * Deprecates the experimental Cyrus Backups feature
79
80 .. _relnotes_3.10.0_storage_changes:
81
82 Storage changes
83 ===============
84
85 * None in 3.10. But if your upgrade is skipping over 3.6 and 3.8, please do
86 not miss :ref:`3.6.0 Storage changes <relnotes_3.6.0_storage_changes>`
87 and :ref:`3.8.0 Storage changes <relnotes_3.8.0_storage_changes>`
88
89 Updates to default configuration
90 ================================
91
92 The :cyrusman:`cyr_info(8)` `conf`, `conf-all` and `conf-default` subcommands
93 accept an `-s <version>` argument to highlight :cyrusman:`imapd.conf(5)`
94 options that are new or whose behaviour has changed since the specified
95 version. We recommend using this when evaluating a new Cyrus version to
96 check which configuration options you will need to examine and maybe set or
97 change during the process.
98
99 * The master pidfile name is now read from imapd.conf, and defaults
100 to ``{configdirectory}/master.pid``. If you have something that
101 looks for this file, you should either update it to look in the new
102 default location, or set ``master_pid_file`` in :cyrusman:`imapd.conf(5)`
103 to override the default. The ``-p`` option to :cyrusman:`master(8)`
104 can still be used to override it
105
106 Security fixes
107 ==============
108
109 * Fixed :cve:`CVE-2024-34055`:
110 Cyrus-IMAP through 3.8.2 and 3.10.0-beta2 allow authenticated attackers
111 to cause unbounded memory allocation by sending many LITERALs in a
112 single command.
113
114 The IMAP protocol allows for command arguments to be LITERALs of
115 negotiated length, and for these the server allocates memory to
116 receive the content before instructing the client to proceed. The
117 allocated memory is released when the whole command has been received
118 and processed.
119
120 The IMAP protocol has a number commands that specify an unlimited
121 number of arguments, for example SEARCH. Each of these arguments can
122 be a LITERAL, for which memory will be allocated and not released
123 until the entire command has been received and processed. This can run
124 a server out of memory, with varying consequences depending on the
125 server's OOM policy.
126
127 Discovered by Damian Poddebniak.
128
129 Two limits, with corresponding :cyrusman:`imapd.conf(5)` options, have
130 been added to address this:
131
132 * ``maxargssize`` (default: unlimited): limits the overall length of a
133 single IMAP command. Deployments should configure this to a size that
134 suits their system resources and client usage patterns
135 * ``maxliteral`` (default: 128K): limits the length of individual IMAP
136 LITERALs
137
138 Connections sending commands that would exceed these limits will see the
139 command fail, or the connection closed, depending on the specific context.
140 The error message will contain the ``[TOOBIG]`` response code.
141
142 These limits may be set small without affecting message uploads, as the
143 APPEND command's message literal is limited by ``maxmessagesize``, not by
144 these new options.
145
146 Significant bugfixes
147 ====================
148
149 * Fixed: squat db reindexes are no longer always incremental
150 * Fixed: squat db corruption from unintentional indexing of fields
151 intended to be skipped
152 * Fixed: squat db out of bounds access in incremental reindex docID map
153 * Fixed :issue:`4692`: squat db searches now handle unindexed messages
154 correctly again (thanks Gabriele Bulfon)
155 * Restored functionality of the sync_client ``-o``/``--connect-once`` option
156 * Fixed :issue:`4654`: copying/moving messages from split conversations is now
157 correct
158 * Fixed :issue:`4758`: fix renaming mailbox between users
159 * Fixed :issue:`4804`: mailbox_maxmessages limits now applied correctly
160 * Fixed :issue:`4932`: LITERAL+ broken in mupdate