similar to: Dovecot release v2.3.7

On 12 Jul 2019, at 21.05, Michael Grimm via dovecot <dovecot at dovecot.org> wrote: > > Aki Tuomi via dovecot <dovecot at dovecot.org> wrote: > >> We are pleased to release Dovecot release v2.3.7. > > My upgrade from 2.3.6 to 2.3.7 broke replication (FreeBSD 12.0-STABLE r349799): > > | dovecot[76032]: master: Dovecot v2.3.7 (494d20bdc) starting up for

A user reported this to me, and I'm seeing it too: Hi all :) After mail/dovecot upgrade to v2.3.7 it seems something went wrong with stat-writer... IMAP and POP3 logs: Jul 12 19:45:34 mail dovecot: imap-login: Error: file_ostream.net_set_tcp_nodelay((conn:unix:/var/run/dovecot/stats-writer), TRUE) failed: Invalid argument Jul 12 19:45:34 mail dovecot: imap-login: Error:

LMTP is broken on director: Jul 13 13:42:41 lmtp(34824): Panic: file smtp-params.c: line 685 (smtp_params_mail_add_body_to_event): assertion failed: ((caps & SMTP_CAPABILITY_8BITMIME) != 0) Jul 13 13:42:41 lmtp(34824): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xdf06a) [0x7f561203806a] -> /usr/lib64/dovecot/libdovecot.so.0(+0xdf0b1) [0x7f56120380b1] ->

Michael Grimm via dovecot <dovecot at dovecot.org> wrote: > > Timo Sirainen via dovecot <dovecot at dovecot.org> wrote: >> This likely fixes it anyway: >> >> diff --git a/src/lib/ostream-file.c b/src/lib/ostream-file.c > I do not compile from source, I'm using FreeBSD's ports. Thus I tried to put this patch at the desired location to become used

On 13 Jul 2019, at 18.39, Michael Grimm via dovecot <dovecot at dovecot.org> wrote: > > Now replication is working from my point of view, besides occational error messages like: > > | imap-login: Error: file_ostream.net_set_tcp_nodelay(, TRUE) failed: Connection reset by peer Here's the final fix for it:

On 2019-07-13 13:44, Tom Sommer via dovecot wrote: > LMTP is broken on director: > > Jul 13 13:42:41 lmtp(34824): Panic: file smtp-params.c: line 685 > (smtp_params_mail_add_body_to_event): assertion failed: ((caps & > SMTP_CAPABILITY_8BITMIME) != 0) > Jul 13 13:42:41 lmtp(34824): Error: Raw backtrace: > /usr/lib64/dovecot/libdovecot.so.0(+0xdf06a) [0x7f561203806a] ->

Version 2.3.7 appears to break director ring sync. After upgrading, our logs are full of these kinds of messages: Jul 14 04:09:20 yyy dovecot: director: Error: director: User xxx host lookup failed: Timeout because ring not synced - queued for 30 secs (Ring not synced for 1410 secs, hash=271838221) Jul 14 04:09:20 yyy dovecot: director: Error: director: User xxx host lookup failed: Timeout

Aki Tuomi via dovecot <dovecot at dovecot.org> wrote: > We are pleased to release Dovecot release v2.3.7. My upgrade from 2.3.6 to 2.3.7 broke replication (FreeBSD 12.0-STABLE r349799): | dovecot[76032]: master: Dovecot v2.3.7 (494d20bdc) starting up for imap, lmtp, sieve | dovecot[76035]: replicator: Error: file_ostream.net_set_tcp_nodelay((conn:unix:/var/run/dovecot/stats-writer),

Timo Sirainen via dovecot <dovecot at dovecot.org> wrote: > > On 12 Jul 2019, at 21.05, Michael Grimm via dovecot <dovecot at dovecot.org> wrote: >> My upgrade from 2.3.6 to 2.3.7 broke replication (FreeBSD 12.0-STABLE r349799): > > I don't think these cause any actual breakage? It doesn't break completely, but it leaves replication shaken: 1) replication

Hi all! We are pleased to release v2.3.19 of Dovecot. The docker images have been upgraded to use bullseye as base image. https://dovecot.org/releases/2.3/dovecot-2.3.19.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.19.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Regards, Aki Tuomi Open-Xchange oy -- + Added

Hi all! We are pleased to release v2.3.19 of Dovecot. The docker images have been upgraded to use bullseye as base image. https://dovecot.org/releases/2.3/dovecot-2.3.19.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.19.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Regards, Aki Tuomi Open-Xchange oy -- + Added

On 2019-10-20 11:30, Timo Sirainen via dovecot wrote: >> On 18 Oct 2019, at 13.43, Tom Sommer via dovecot <dovecot at dovecot.org> >> wrote: >> >>> I am seeing a lot of errors since the upgrade, on multiple client >>> accounts: >>> Info: Connection closed: read(size=7902) failed: Connection reset by >>> peer (UID FETCH running for

Michael Grimm wrote: > But, replication still doesn't works as known from previous versions. > I will give it a try over night, but I am seeing ? > > | Queued 'full resync' requests 1 > > ? after 1 minute, already. The following modifications regarding my setup made replication work again (at least for the last 8 hours): #) Re-compiling dovecot with the patch

After upgrading to 2.3.7_1 I get those errors every now and then. Running FreeBSD 12-RELEASE. Any idea what they may be? Jul 13 08:07:11 pop3-login: Error: file_ostream.net_set_tcp_nodelay(, FALSE) failed: Connection reset by peer Jul 13 08:19:10 imap-login: Error: file_ostream.net_set_tcp_nodelay(, TRUE) failed: Connection reset by peer Jul 13 08:24:09 imap-login: Error:

Hi, One interesting thing in this release is the support for configuring OAUTH2 openid-configuration element. It would be nice if IMAP clients started supporting this feature to enable OAUTH2 for all IMAP servers, not just Gmail and a few others. This would allow all kinds of new authentication methods for IMAP and improve the authentication security in general.

Hi, One interesting thing in this release is the support for configuring OAUTH2 openid-configuration element. It would be nice if IMAP clients started supporting this feature to enable OAUTH2 for all IMAP servers, not just Gmail and a few others. This would allow all kinds of new authentication methods for IMAP and improve the authentication security in general.

Hi there! I compiled dovecot 2.3 from git. Because there is already a bug in virtual-plugin, and i hoped, it get fixed... but it doesn't. So this is the error-message from the log J?n 03 16:27:08 aldebaran dovecot[26460]: indexer-worker(jakob)<26476><qQ6g1+BhIJvAqAAO:sjYhMTH2TFpsZwAAk1Mx3g>: Panic: file unichar.c: line 160 (uni_ucs4_to_utf8_c): assertion failed:

Hello, Autoexpunge is not working when used with dotlock locking. It seems to been broken since version 2.2.28. When autoexpunge is enabled and mailbox locking is set to dotlock all imap, pop and lmtp connections crash with the same error "file file-lock.c: line 287: unreached". Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 SASL-IR

Hi, did you have time to investigate about 'Panic: file unichar.c' bug ? Because I have the same problem with a 2.3.0 installation without virtual plugin. Thanks, Marco On 2018-01-03 16:52, Aki Tuomi wrote: > This is not a bug in virtual plugin, but in some email which contains invalid unicode sequence somehow. Can you send me a core file? This should not have occured ofc but

Hi, As per my discussion with cmouse on irc, I'm currently just using dovecot for its auth mechanism, etc capabilities (alas, Exim does not support argon directly). Tis a fun little side project. :) I have the config pared down as far as I think is reasonable (see below) and all is working well except that dovecot is very silent. Errors hit the logs but I would appreciate seeing successful