http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig
- director: "doveadm director move" to same host now refreshes user's timeout. This allows keeping user constantly in the same backend by just periodically moving the user there.
- When new mailbox is created, use initially INBOX's dovecot.index.cache caching decisions.
- Expunging mails writes GUID to dovecot.index.log now only if the GUID is quickly available from index/cache.
- pop3c: Increase timeout for PASS command to 5 minutes.
- Mail access errors are no longer ignored when searching or sorting. With IMAP the untagged SEARCH/SORT reply is still sent the same as before, but NO reply is returned instead of OK.
- Make dovecot.list.index's filename configurable. This is needed when there are multiple namespaces pointing to the same mail root (e.g. lazy_expunge namespace for mdbox).
- Add size.virtual to dovecot.index when folder vsizes are accessed (e.g. quota=count). This is mainly a workaround to avoid slow quota recalculation performance when message sizes get lost from dovecot.index.cache due to corruption or some other reason.
- auth: Support OAUTHBEARER and XOAUTH2 mechanisms. Also support them in lib-dsasl for client side.
- auth: Support filtering by SASL mechanism: passdb { mechanisms }
- Shrink the mail processes' memory usage by not storing settings duplicated unnecessarily many times.
- imap: Add imap_fetch_failure setting to control what happens when FETCH fails for some mails (see example-config).
- imap: Include info about last command in disconnection log line.
- imap: Created new SEARCH=X-MIMEPART extension. It's currently not advertised by default, since it's not fully implemented.
- fts-solr: Add support for basic authentication.
- Cassandra: Support automatically retrying failed queries if execution_retry_interval and execution_retry_times are set.
- doveadm: Added "mailbox path" command.
- mail_log plugin: If plugin { mail_log_cached_only=yes }, log the wanted fields only if it doesn't require opening the email.
- mail_vsize_bg_after_count setting added (see example-config).
- mail_sort_max_read_count setting added (see example-config).
- pop3c: Added pop3c_features=no-pipelining setting to prevent using PIPELINING extension even though it's advertised.
- Index files: day_first_uid wasn't updated correctly since v2.2.26. This caused dovecot.index.cache to be non-optimal.
- imap: SEARCH/SORT may have assert-crashed in client_check_command_hangs
- imap: FETCH X-MAILBOX may have assert-crashed in virtual mailboxes.
- imap: Running time in tagged command reply was often wrongly 0.
- search: Using NOT n:* or NOT UID n:* wasn't handled correctly
- director: doveadm director kick was broken
- director: Fix crash when using director_flush_socket
- director: Fix some bugs when moving users between backends
- imapc: Various error handling fixes and improvements
- master: doveadm process status output had a lot of duplicates.
- autoexpunge: If mailbox's rename timestamp is newer than mail's save-timestamp, use it instead. This is useful when autoexpunging e.g. Trash/* and an entire mailbox is deleted by renaming it under Trash to prevent it from being autoexpunged too early.
- autoexpunge: Multiple processes may have been trying to expunge the same mails simultaneously. This was problematic especially with lazy_expunge plugin.
- auth: %{passdb:*} was empty in auth-worker processes
- auth-policy: hashed_password was always sent empty.
- dict-sql: Merge multiple UPDATEs to a single statement if possible.
- fts-solr: Escape {} chars when sending queries
- fts: fts_autoindex_exclude = \Special-use caused crashes
- doveadm-server: Fix leaks and other problems when process is reused for multiple requests (service_count != 1)
- sdbox: Fix assert-crash on mailbox create race
- lda/lmtp: deliver_log_format values weren't entirely correct if Sieve was used. especially %{storage_id} was broken.
- lmtp_user_concurrency_limit didn't work if userdb changed username
On 2017-02-24 14:34, Timo Sirainen wrote:
http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig
Are there any plans to do a bugfix-release, that includes the few issues seen in the mailing-list, or do you consider 2.2.28 safe to upgrade to?
Thanks
Tom
On 6 Mar 2017, at 9.17, Tom Sommer mail@tomsommer.dk wrote:
On 2017-02-24 14:34, Timo Sirainen wrote:
http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig
Are there any plans to do a bugfix-release, that includes the few issues seen in the mailing-list, or do you consider 2.2.28 safe to upgrade to?
I don't see anything critical. A couple of bugs that might or might not affect you. We'll have 2.2.29 soon enough, so no plans for other releases before that.
On 03/06/2017 11:30 PM, Timo Sirainen wrote:
On 6 Mar 2017, at 9.17, Tom Sommer mail@tomsommer.dk wrote:
On 2017-02-24 14:34, Timo Sirainen wrote:
http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig Are there any plans to do a bugfix-release, that includes the few issues seen in the mailing-list, or do you consider 2.2.28 safe to upgrade to?
I don't see anything critical. A couple of bugs that might or might not affect you. We'll have 2.2.29 soon enough, so no plans for other releases before that. Truncating passwords with dict protocol* seems quite critical to me. :-O Or is it just me, who's affected by that?
*: http://dovecot.org/list/dovecot/2017-February/107265.html
On 07.03.2017 10:52, Nagy, Attila wrote:
On 03/06/2017 11:30 PM, Timo Sirainen wrote:
On 6 Mar 2017, at 9.17, Tom Sommer mail@tomsommer.dk wrote:
On 2017-02-24 14:34, Timo Sirainen wrote:
http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig Are there any plans to do a bugfix-release, that includes the few issues seen in the mailing-list, or do you consider 2.2.28 safe to upgrade to?
I don't see anything critical. A couple of bugs that might or might not affect you. We'll have 2.2.29 soon enough, so no plans for other releases before that. Truncating passwords with dict protocol* seems quite critical to me. :-O Or is it just me, who's affected by that?
*: http://dovecot.org/list/dovecot/2017-February/107265.html
Hi!
The password is not actually truncated, it's actually subjected to var_expand, which is silly. We are working on a patch for this and let y'all know when it's ready. The only truncation happens with % as last character.
Aki
On 07.03.2017 11:08, Aki Tuomi wrote:
On 07.03.2017 10:52, Nagy, Attila wrote:
On 03/06/2017 11:30 PM, Timo Sirainen wrote:
On 6 Mar 2017, at 9.17, Tom Sommer mail@tomsommer.dk wrote:
On 2017-02-24 14:34, Timo Sirainen wrote:
http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig Are there any plans to do a bugfix-release, that includes the few issues seen in the mailing-list, or do you consider 2.2.28 safe to upgrade to? I don't see anything critical. A couple of bugs that might or might not affect you. We'll have 2.2.29 soon enough, so no plans for other releases before that. Truncating passwords with dict protocol* seems quite critical to me. :-O Or is it just me, who's affected by that?
*: http://dovecot.org/list/dovecot/2017-February/107265.html Hi!
The password is not actually truncated, it's actually subjected to var_expand, which is silly. We are working on a patch for this and let y'all know when it's ready. The only truncation happens with % as last character.
Aki
Also, this only happens if you configure the lookup key to be password, that is: key passdb { key = %w format = json }
So, passwords are not truncated in general, only in this particular use case.
Aki
On 3/6/17 2:30 PM, Timo Sirainen wrote:
I don't see anything critical. A couple of bugs that might or might not affect you. We'll have 2.2.29 soon enough, so no plans for other releases before that.
As a comment: When trying to choose which version of Dovecot to use in production, I've found it difficult that minor point releases add new features and make other changes, as well as purely fixing bugs.
It's a challenge to find a Dovecot version that fixes known issues without introducing other (possibly problematic) changes. As a result, I end up using what seems to be a mostly stable version, plus "extra patches I grabbed from reading the mailing list".
I'm grateful for all the effort put into the code, but for me, at least, it would be easier to work with if new features and changes were only in new versions like 2.3, with 2.2.x only fixing bugs. (And when 2.3 is stable, new features would be in 2.4, with 2.3.x just fixing bugs, and so on.) This is the model used in Postfix development, for example, and I find it easier to work with in terms of finding a known stable version.
But again, this could be just me, and I apologize if this has already been suggested and found inappropriate. As I said, I definitely appreciate that the code is constantly being improved.
-- Robert L Mathews, Tiger Technologies, http://www.tigertech.net/
participants (6)
-
Aki Tuomi
-
Gedalya
-
Nagy, Attila
-
Robert L Mathews
-
Timo Sirainen
-
Tom Sommer