similar to: Sieve redirect is broken in 2.3.7.2 - signal 11

Hi Stephan, I managed to get GDB, I hope this one helps. If not I can send the config too, but exactly same config works with 2.3.6. 92b9d3412dc8:/$ gdb /usr/libexec/dovecot/dovecot-lda -f root at xxxxxxxx -d test at xxxxxxxxx GNU gdb (GDB) 8.0.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free

I think alpine does not have that https://pkgs.alpinelinux.org/packages?name=dovecot*&branch=v3.8&repo=main&arch=x86_64 https://git.alpinelinux.org/aports/tree/main/dovecot/APKBUILD?h=3.8-stable What else would help? strace? On 2019. 10. 06. 23:05, Stephan Bosch via dovecot wrote: > > > On 06/10/2019 23:03, Demonhost wrote: >> Hi Stephan, >> >> I managed

Hi Stephan, Here it is: Program received signal SIGSEGV, Segmentation fault. p_strdup (pool=pool at entry=0x55555579bc20, str=0x6d65642e6c69616d <error: Cannot access memory at address 0x6d65642e6c69616d>) at strfuncs.c:51 51????? strfuncs.c: No such file or directory. (gdb) bt full #0? p_strdup (pool=pool at entry=0x55555579bc20, str=0x6d65642e6c69616d <error: Cannot access memory at

That's a good thought. I'm building from the alpine repo and I indeed see pigeonhole is 0.5.5 https://git.alpinelinux.org/aports/tree/main/dovecot/APKBUILD?h=3.8-stable Let me build it with 0.5.7.2 Regards, ? Laszlo On 2019. 10. 07. 10:45, Stephan Bosch via dovecot wrote: > > > On 07/10/2019 10:17, Demonhost via dovecot wrote: >> Hi Stephan, >> >> Here it

Op 4-10-2019 om 12:10 schreef Demonhost via dovecot: > Hi, > > If we use sieve redirect under dovecot 2.3.7.2 we end up with > > Oct 04 03:30:31 dockerhost docker[12154]: 2019-10-04T03:30:31 > 53ac2ae27650 postfix: 0605F207B0F36: to=<xxxx at xxxx.xx>, > relay=127.0.0.1[127.0.0.1]:10024, delay=1.5, delays=0.36/0/0/1.1, > dsn=2.0.0, status=sent (250 2.0.0 from

On 06/10/2019 23:03, Demonhost wrote: > Hi Stephan, > > I managed to get GDB, I hope this one helps. If not I can send the > config too, but exactly same config works with 2.3.6. You don't have the debug symbols for Dovecot installed. Usually, your system will have a separate package for that. On Debian, it is called dovecot-dbg. > > 92b9d3412dc8:/$ gdb

On 06/10/2019 23:14, Demonhost wrote: > I think alpine does not have that > > https://pkgs.alpinelinux.org/packages?name=dovecot*&branch=v3.8&repo=main&arch=x86_64 > > > https://git.alpinelinux.org/aports/tree/main/dovecot/APKBUILD?h=3.8-stable > > > What else would help? strace? Do you have the opportunity to build Dovecot yourself, thereby including the

On 07/10/2019 10:17, Demonhost via dovecot wrote: > Hi Stephan, > > Here it is: > We still can't reproduce it here. First of all, did you update Pigeonhole along with Dovecot? This kind of weirdness can happen when Pigeonhole was compiled against a different version of Dovecot. You could compile Pigeonhole manually as well to make sure, which also gives you the opportunity to

I set up system copying all mails to a backup system. This used to work without a hitch - now in the last few days mails would pile up in the Postfix Queue, waiting to be delivered using the lmtp transport into dovecot. So dovecot was being slow, but why? After all, nothing changed. After reading some articles on stackoverflow I found a way of finding out which file gets the most IO: % sysdig

On 1 Oct 2019, at 16.45, Ralf Hildebrandt via dovecot <dovecot at dovecot.org> wrote: > > * Ralf Hildebrandt via dovecot <dovecot at dovecot.org>: > >> But why is that? Why would the index file be updated so often? > > BTW: This post is a followup to my "2.3.7 slower than 2.3.6?" post from back in July. Fixed by

* Ralf Hildebrandt via dovecot <dovecot at dovecot.org>: > * Timo Sirainen <timo at sirainen.com>: > > > > BTW: This post is a followup to my "2.3.7 slower than 2.3.6?" post from back in July. > > > > Fixed by https://github.com/dovecot/core/commit/5e9e09a041b318025fd52db2df25052b60d0fc98 and will be in the soon-to-be-released v2.3.8. > > I

Hi all, does the dovecot fixed version: 2.3.7.2, 2.2.36.4 (as the CVE-2019-11500 says) fix the LMTP error "Got unexpected reply" as well? The LMTP error "Got unexpected reply" is described here: https://dovecot.org/pipermail/dovecot/2018-August/112562.html https://dovecot.org/pipermail/dovecot/2018-August/112666.html Thanks in advance Regards, -- Gabriele Nencioni

Hi, i have a problem with libclucene-core.so.2.3.3.4. I See segfault error to messages log, when dovecot store mail to INBOX. set 12 13:41:21 box02.par-tec.it kernel: doveadm-server[20285]: segfault at 38 ip 00007f575b68fc42 sp 00007ffc0272e750 error 4 in libclucene-core.so.2.3.3.4[7f575b569000+188000] set 12 13:41:22 box02.par-tec.it kernel: doveadm-server[18871]: segfault at 38 ip

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

Hi List, after upgrading dovecot from version 2.2.33.2 to 2.3.7.2 I got a lot of error messages like the following if the process count of imap processes reaches nearly 1000 (~950 (there are a few pop-connections)). Sep 5 11:27:32 mailbox1 dovecot: imap-login: Internal login failure (pid=27728 id=116): user=<xxxx at xxxx.xx>, method=PLAIN, rip=x.x.x.x, lip=x.x.x.x,

Hello, i have update dovecot from version 2.2.15 to 2.3.7.2. I have a problem with mine java software because there is a different response when open connection to doveadm. I need open socket to doveadm for get imap quota of a mailbox. With version 2.2.15: # telnet 192.160.10.4 924 Trying 192.160.10.4... Connected to 192.160.10.4. Escape character is '^]'. - With version 2.3.7.2: #

On 1 Oct 2019, at 16.31, Ralf Hildebrandt via dovecot <dovecot at dovecot.org> wrote: > > I set up system copying all mails to a backup system. > > This used to work without a hitch - now in the last few days mails > would pile up in the Postfix Queue, waiting to be delivered using the > lmtp transport into dovecot. > > So dovecot was being slow, but why? After

Hi, some of our customers have discovered a replication issue after upgraded from 2.3.7.2 to 2.3.8. Running 2.3.8 several replication connections are hanging until defined timeout. So after some seconds there are $replication_max_conns hanging connections. Other replications are running fast and successful. Also running a doveadm sync tcp:... is working fine for all users. I can't see

* Ralf Hildebrandt via dovecot <dovecot at dovecot.org>: > But why is that? Why would the index file be updated so often? BTW: This post is a followup to my "2.3.7 slower than 2.3.6?" post from back in July.

* Timo Sirainen <timo at sirainen.com>: > > BTW: This post is a followup to my "2.3.7 slower than 2.3.6?" post from back in July. > > Fixed by https://github.com/dovecot/core/commit/5e9e09a041b318025fd52db2df25052b60d0fc98 and will be in the soon-to-be-released v2.3.8. I stopped 2.3.7, copied over the index files from the ramdisk into the physical "realm"