similar to: Plugin ABI compat between v2.3.8 and v2.3.9

Hi! On 2020-06-16 12:37 -0000, Stuart Henderson wrote: > On 2020-06-15, Alexander Strasser <eclipse7 at gmx.net> wrote: > > I had some imap crashes (sig11) starting at the end of 2019 after > > an upgrade of dovecot. > > > > I found out, that I didn't have any problems using version v2.3.8, > > but any version v2.3.9 and higher would trigger the crashes.

On 2020-06-15, Alexander Strasser <eclipse7 at gmx.net> wrote: > I had some imap crashes (sig11) starting at the end of 2019 after > an upgrade of dovecot. > > I found out, that I didn't have any problems using version v2.3.8, > but any version v2.3.9 and higher would trigger the crashes. > > After investigating more deeply and creating a core dump, I saw > that

On 2020-06-16 20:32 +0200, Alexander Strasser wrote: > On 2020-06-16 12:37 -0000, Stuart Henderson wrote: > > On 2020-06-15, Alexander Strasser <eclipse7 at gmx.net> wrote: > > > I had some imap crashes (sig11) starting at the end of 2019 after > > > an upgrade of dovecot. > > > > > > I found out, that I didn't have any problems using version

Hi all! We are pleased to release v2.3.9 of Dovecot. Please find it from locations below --- Aki Tuomi Open-Xchange oy https://dovecot.org/releases/2.3/dovecot-2.3.9.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.9.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot --- * Changed several event field names for consistency and

Hi all! We are pleased to release v2.3.9 of Dovecot. Please find it from locations below --- Aki Tuomi Open-Xchange oy https://dovecot.org/releases/2.3/dovecot-2.3.9.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.9.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot --- * Changed several event field names for consistency and

I think there's a good chance that upgrading both will fix it. The bug already existed in old versions, it just wasn't normally triggered. Since v2.3.8 this situation is triggered on one dsync side, so the v2.3.9 fix needs to be on the other side. > On 5. Dec 2019, at 8.34, Piper Andreas via dovecot <dovecot at dovecot.org> wrote: > > Hello, > > upgrading to 2.3.9

> 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 0.242 + waiting input/output for 108.816 >> secs, 60 B in + 24780576+8192 B out,

On 22/10/2019 05:44, lty--- via dovecot wrote: > Dear all, > ? Dovecot upgraded from v2.2.36 to v2.3.8?There is no problem with the > configuration, but the lock directory seems to have an error. > > [root at spam dovecot]# /usr/libexec/dovecot/maildirlock /path/to/maildir 1 > Panic: BUG: No IOs or timeouts set. Not waiting for infinity. > 19276[root at spam dovecot]# Error:

Dear all, Dovecot upgraded from v2.2.36 to v2.3.8 There is no problem with the configuration, but the lock directory seems to have an error. [root at spam dovecot]# /usr/libexec/dovecot/maildirlock /path/to/maildir 1 Panic: BUG: No IOs or timeouts set. Not waiting for infinity. 19276[root at spam dovecot]# Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xe227a) [0x7f1cb567a27a]

On 2019-10-08 13:18, Aki Tuomi via dovecot wrote: > https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz > https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz.sig > Binary packages in https://repo.dovecot.org/ > - imap: SETMETADATA with literal value would delete the metadata value > instead of updating it. > - imap: When client issues FETCH PREVIEW (LAZY=FUZZY) command, the

> On 18/10/2019 14:25 Tom Sommer via dovecot <dovecot at dovecot.org> wrote: > > > On 2019-10-08 13:18, Aki Tuomi via dovecot wrote: > > https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz > > https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz.sig > > Binary packages in https://repo.dovecot.org/ > > > - imap: SETMETADATA with literal value

On 06 Dec 2019, at 16:28, Martynas Bendorius <martynas at martynas.it> wrote: > when zlib compression is enabled in dovecot, old emails remain untouched I?ve been considering doing this, or at least looking into how much space we?d save (answer so far, less than you might think), but I am hesitant to ?alter? the user?s mail stores without a bit more guidance. Has anyone found a good

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

On 08 Dec 2019, at 05:58, @lbutlr <kremels at kreme.com> wrote: > On 06 Dec 2019, at 16:28, Martynas Bendorius <martynas at martynas.it> wrote: >> when zlib compression is enabled in dovecot, old emails remain untouched > > I?ve been considering doing this, or at least looking into how much space we?d save (answer so far, less than you might think), but I am hesitant to

Hello, Aki created this patch a while ago: http://files1.directadmin.com/services/custombuild/patches/maildirlock-crash.patch It works perfectly to fix the issue :) Regarding dsync - I don't think it's a good replacement in all the cases, is it? We use maildirlock extensively for compression of email folders (when zlib compression is enabled in dovecot, old emails remain untouched). --

I've installed grep PRETTY /etc/os-release PRETTY_NAME="Fedora 32 (Server Edition)" dovecot --version 2.3.10.1 (a3d0e1171) openssl version OpenSSL 1.1.1g FIPS 21 Apr 2020 iiuc, Dovecot has apparently had support for setting TLS 1.3 ciphersuites since v2.3.9, per this commit lib-ssl-iostream: Support TLSv1.3 ciphersuites

Hi, i'm getting a coredump on a specific msg, i've attached the gdb. file on disk i noticed W=<vsize> is missing. 1571209735.M744550P1608.rwvirtual65,S=15886:2,S Best regards, mail.log Oct 18 14:41:39 rwvirtual10 dovecot: imap(johndoe at company.nl)<15868><qjTFpy6VPsMKAAok>: Error: Mailbox INBOX.Debug: UID=1041: read(/data/mail/

Hello Timo, upgrading both replicators did the job! Both replicators now run v2.3.9 and replication works fine, all sync-jobs which queued up during the upgrading have been processed successfully. Thanks for the reassurement and all your great work with dovecot, Andreas Am 05.12.19 um 13:15 schrieb Timo Sirainen via dovecot: > I think there's a good chance that upgrading both will

On 2019-10-18 13:25, Tom Sommer via dovecot 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 0.242 + waiting input/output for 108.816 > secs, 60 B in + 24780576+8192 B out, state=wait-output) > > Using NFS storage (not running with

Hi, I see a lot of crashes in my syslog lately. Specifically a sequence of errors exactly like this (only the timestamp differs). > Nov 10 21:29:53 khitomer dovecot: imap-login: Login: user=<user at hostname>, method=PLAIN, rip=XXXX, lip=YYYY, mpid=ZZZZ, TLS, session=<TTTT> > Nov 10 21:29:53 khitomer dovecot: imap(user at hostname): Panic: file mail-storage.c: line 2222