https://dovecot.org/releases/2.2/dovecot-2.2.29.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.29.tar.gz.sig
- passdb/userdb dict: Don't double-expand %variables in keys. If dict was used as the authentication passdb, using specially crafted %variables in the username could be used to cause DoS (CVE-2017-2669)
- When Dovecot encounters an internal error, it logs the real error and usually logs another line saying what function failed. Previously the second log line's error message was a rather uninformative "Internal error occurred. Refer to server log for more information." Now the real error message is duplicated in this second log line.
- lmtp: If a delivery has multiple recipients, run autoexpunging only for the last recipient. This avoids a problem where a long autoexpunge run causes LMTP client to timeout between the DATA replies, resulting in duplicate mail deliveries.
- config: Don't stop the process due to idling. Otherwise the configuration is reloaded when the process restarts.
- mail_log plugin: Differentiate autoexpunges from regular expunges
- imapc: Use LOGOUT to cleanly disconnect from server.
- lib-http: Internal status codes (>9000) are no longer visible in logs
- director: Log vhost count changes and HOST-UP/DOWN
- quota: Add plugin { quota_max_mail_size } setting to limit the maximum individual mail size that can be saved.
- imapc: Add imapc_features=delay-login. If set, connecting to the remote IMAP server isn't done until it's necessary.
- imapc: Add imapc_connection_retry_count and imapc_connection_retry_interval settings.
- imap, pop3, indexer-worker: Add (deinit) to process title before autoexpunging runs.
- Added %{encrypt} and %{decrypt} variables
- imap/pop3 proxy: Log proxy state in errors as human-readable string.
- imap/pop3-login: All forward_* extra fields returned by passdb are sent to the next hop when proxying using ID/XCLIENT commands. On the receiving side these fields are imported and sent to auth process where they're accessible via %{passdb:forward_*}. This is done only if the sending IP address matches login_trusted_networks.
- imap-login: If imap_id_retain=yes, send the IMAP ID string to auth process. %{client_id} expands to it in auth process. The ID string is also sent to the next hop when proxying.
- passdb imap: Use ssl_client_ca_* settings for CA validation.
- fts-tika: Fixed crash when parsing attachment without Content-Disposition header. Broken by 2.2.28.
- trash plugin was broken in 2.2.28
- auth: When passdb/userdb lookups were done via auth-workers, too much data was added to auth cache. This could have resulted in wrong replies when using multiple passdbs/userdbs.
- auth: passdb { skip & mechanisms } were ignored for the first passdb
- oauth2: Various fixes, including fixes to crashes
- dsync: Large Sieve scripts (or other large metadata) weren't always synced.
- Index rebuild (e.g. doveadm force-resync) set all mails as \Recent
- imap-hibernate: %{userdb:*} wasn't expanded in mail_log_prefix
- doveadm: Exit codes weren't preserved when proxying commands via doveadm-server. Almost all errors used exit code 75 (tempfail).
- ACLs weren't applied to not-yet-existing autocreated mailboxes.
- Fixed a potential crash when parsing a broken message header.
- cassandra: Fallback consistency settings weren't working correctly.
- doveadm director status <user>: "Initial config" was always empty
- imapc: Various reconnection fixes.
It's failing tests on CentOS 6, it looks like it's expecting the IMAP server to be running when it isn't, perhaps this test should soft-fail?
Making check in lib-imap-client
make[2]: Entering directory
`/builddir/build/BUILD/dovecot-2.2.29/src/lib-imap-client'
for bin in test-imapc-client; do
if ! ./$bin; then exit 1; fi;
done
Warning: imapc(127.0.0.1:0): connect(127.0.0.1, 0) failed: Connection
refused - reconnecting (delay 10 ms)
Error: imapc(127.0.0.1:0): connect(127.0.0.1, 0) failed: Connection
refused - disconnecting
test: random seed #1 was 1492054294
imapc connect failed ................................................. : ok
Warning: imapc(127.0.0.1:42704): connect(127.0.0.1, 42704) timed out
after 0 seconds - reconnecting (delay 0 ms)
Error: imapc(127.0.0.1:42704): connect(127.0.0.1, 42704) timed out after
0 seconds - disconnecting
imapc banner hangs ................................................... : ok
Warning: imapc(127.0.0.1:36762): Authentication timed out after 0
seconds - reconnecting (delay 0 ms)
Error: imapc(127.0.0.1:36762): Authentication failed: Disconnected from
server
imapc login hangs .................................................... : ok
test-imapc-client.c:358: Assert failed: test_imapc_cmd_last_reply_pop()
== IMAPC_COMMAND_STATE_OK
imapc reconnect ...................................................... :
FAILED
imapc reconnect resend commands ...................................... : ok
imapc reconnect resend commands failed ............................... : ok
imapc reconnect mailbox .............................................. : ok
1 / 7 tests failed
Peter
On 11 Apr 2017, at 0.39, Peter peter@pajamian.dhs.org wrote:
It's failing tests on CentOS 6, it looks like it's expecting the IMAP server to be running when it isn't, perhaps this test should soft-fail?
The test is itself running both the client and the server. Most of those errors are expected. Does it work if you run it a couple of times?
On 11 Apr 2017, at 9.54, Timo Sirainen tss@iki.fi wrote:
On 11 Apr 2017, at 0.39, Peter peter@pajamian.dhs.org wrote:
It's failing tests on CentOS 6, it looks like it's expecting the IMAP server to be running when it isn't, perhaps this test should soft-fail?
The test is itself running both the client and the server. Most of those errors are expected. Does it work if you run it a couple of times?
No, I hadn't cherry-picked one change and due to some other reasons didn't notice this unit test failing :(
Fixed by https://github.com/dovecot/core/commit/3a1c64363a64cdfe9153eb6292d8923f38955... https://github.com/dovecot/core/commit/3a1c64363a64cdfe9153eb6292d8923f38955...
On 11/04/17 19:04, Timo Sirainen wrote:
No, I hadn't cherry-picked one change and due to some other reasons didn't notice this unit test failing :(
Fixed by https://github.com/dovecot/core/commit/3a1c64363a64cdfe9153eb6292d8923f38955...
Thanks, I applied that patch and it builds and tests run fine now for both CentOS 6 and 7.
Peter
On 11 April 2017 at 10:04, Timo Sirainen tss@iki.fi wrote:
On 11 Apr 2017, at 9.54, Timo Sirainen tss@iki.fi wrote:
On 11 Apr 2017, at 0.39, Peter peter@pajamian.dhs.org wrote:
It's failing tests on CentOS 6, it looks like it's expecting the IMAP server to be running when it isn't, perhaps this test should soft-fail?
The test is itself running both the client and the server. Most of those
errors are expected. Does it work if you run it a couple of times?
No, I hadn't cherry-picked one change and due to some other reasons didn't notice this unit test failing :(
Fixed by https://github.com/dovecot/core/commit/ 3a1c64363a64cdfe9153eb6292d8923f38955d82 <https://github.com/dovecot/ core/commit/3a1c64363a64cdfe9153eb6292d8923f38955d82>
For those of us not having any issues so far, do we need to apply this patch or just wait for 2.2.30?
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft."
On 11.04.2017 12:13, Odhiambo Washington wrote:
On 11 April 2017 at 10:04, Timo Sirainen tss@iki.fi wrote:
On 11 Apr 2017, at 9.54, Timo Sirainen tss@iki.fi wrote:
On 11 Apr 2017, at 0.39, Peter peter@pajamian.dhs.org wrote:
It's failing tests on CentOS 6, it looks like it's expecting the IMAP server to be running when it isn't, perhaps this test should soft-fail? The test is itself running both the client and the server. Most of those errors are expected. Does it work if you run it a couple of times?
No, I hadn't cherry-picked one change and due to some other reasons didn't notice this unit test failing :(
Fixed by https://github.com/dovecot/core/commit/ 3a1c64363a64cdfe9153eb6292d8923f38955d82 <https://github.com/dovecot/ core/commit/3a1c64363a64cdfe9153eb6292d8923f38955d82>
For those of us not having any issues so far, do we need to apply this patch or just wait for 2.2.30?
This is just unit test issue, the test was wrong.
Aki
participants (4)
-
Aki Tuomi
-
Odhiambo Washington
-
Peter
-
Timo Sirainen