similar to: core not dumped

Connecting to dovecot with ssl3 causes imap-login to die: $ openssl s_client -connect localhost:993 -ssl3 CONNECTED(00000003) 4277630796:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:s3_pkt.c:1461:SSL alert number 40 4277630796:error:1409E0E5:SSL routines:ssl3_write_bytes:ssl handshake failure:s3_pkt.c:645: --- no peer certificate available --- No client certificate

I have built and installed Pigeonhole 0.4.4 with Dovecot 2.2.15. For users with no sieve at all I am getting an error on delivery. Delivery is from exim via lmtp. Syslog: Oct 28 11:03:50 mailhost dovecot: [ID 583609 mail.crit] lmtp(18915): Fatal: master: service(lmtp): child 18915 killed with signal 11 (core not dumped - set service lmtp { drop_priv_before_exec=yes }) There is no global

On 19/03/2015 13:35, Markus Sch?nhaber wrote: >> dumped". If I put "abort()" in the code at the point it is reporting >> then a core file is written, so there is no OS reason why a core can not >> be written. It appears to be dovecot's choice to control the child. In >> an attempt to obtain a core file I have: >> >> service imap-login {

On 20 Mar 2015, at 13:59, James <lista at xdrv.co.uk> wrote: > > Connecting to dovecot with ssl3 causes imap-login to die: > > Mar 20 11:30:35 MAILHOST dovecot: [ID 583609 mail.crit] imap-login: Fatal: master: service(imap-login): child 21918 killed with signal 11 (core dumped) [last ip=127.0.0.1] I can't reproduce it. I tried it with the same ssl_* settings you had. Can

Am 19.03.2015 um 14:07 schrieb James: > There is some underlying problem with imap-login but in order to debug > it I'd like to see a core file. On error dovecot reports "core not > dumped". If I put "abort()" in the code at the point it is reporting > then a core file is written, so there is no OS reason why a core can not > be written. It appears to

Hi, at the moment I see only packages named *2.2.26* on xi.dovecot.fi. Can we expect packages for v2.2.27 to appear there? -- Regards mks

On 01.09.2016 14:20, Piper Andreas wrote: > Hello Timo, > > with the newly build CSW-package the crashes still occur, today already > twice within two hours. The log shows always the same: > > Sep 1 11:50:13 surz113 dovecot: [ID 583609 mail.crit] imap(user): > Panic: file imap-client.c: line 837 (client_check_command_hangs): > assertion failed: (client->io != NULL) >

All, Just move our mail servers over to a new mail server running postfix 2.11.1 and dovecot 2.2.13 and getting the subject line errors in my /var/adm/files. People are complaining of loosing their connections to the mail server. I've been able to google this error but haven't found fix for this yet. NOt sure where to put the drop-priv option in the config files either. Any

Aki Tuomi, Fri, 02 Mar 2018 20:06:35 +0200: > the problem is default > ?protocols = imap pop3? Ah, OK. I wasn't aware that the default had changed. It seems to be protocols = imap pop3 lmtp now. > packaging should use > protocols = > protocols = $protocols imap Yep, explicitly setting protocols = before !include_try /usr/share/dovecot/protocols.d/*.protocol helps. IMO

Hi everyone! I?m using dovecot 2.3.5. submission-login is crashing many times in a day: Here is a sample error message: dovecot: submission-login: Fatal: master: service(submission-login): child 34247 killed with signal 11 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set service submission-login { drop_priv_before_exec=yes }) After I added drop_priv_before_exec, I got

On 20/03/2015 18:24, Timo Sirainen wrote: >> Connecting to dovecot with ssl3 causes imap-login to die: >> >> Mar 20 11:30:35 MAILHOST dovecot: [ID 583609 mail.crit] imap-login: Fatal: master: service(imap-login): child 21918 killed with signal 11 (core dumped) [last ip=127.0.0.1] > > I can't reproduce it. I tried it with the same ssl_* settings you had. Can you get a

Hi, looking at the source archive of pigeonhole 0.4.20 <https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.20.tar.gz> I noticed that the contained ChangeLog mentions v0.4.20.rc1 as first entry and pigeonhole-version.h defines git revision 7cd71ba as version where I'd expect 4a55e6c. This is probably no big deal. But since Makefile.in and install-sh also differ (see

Stephan Bosch, Mon, 25 Apr 2016 15:16:55 +0200: > Oops. Turned off package composer for maintenance, but didn't turn it > back on. > > It is building now..... Is there something to turn on to build packages in /debian/pool/wheezy-auto/dovecot-2.2 ? Or don't you provide packages for wheezy anymore? > Op 25-4-2016 om 14:47 schreef Harald Leithner: >> Hi, >>

Hello, Dovecot 2.2.25 OS: Solaris 11 (SunOS 5.11 11.3 i86pc i386 i86pc) Virtualization: VMware Filesystem: ZFS active users: ~4000 About once a day Dovecot crashes with "Panic: file imap-client.c: line 837 (client_check_command_hangs): assertion failed: (client->io != NULL)" The log shows in each case: Aug 29 12:59:00 surz113 dovecot: [ID 583609 mail.crit] imap(username): Panic:

EL8: Since the new update of firefox (rebased), I get a lot of coredumps while playing videos. Anyone experiencing the same? Aug 30 16:44:05 work.localdomain systemd-coredump[27017]: Process 21016 (firefox) of user 1006 dumped core. Stack trace of thread 21016: #0

Hi! We are pleased to release Pigeonhole release v0.4.24.2 Tarball is available at https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.24.2.tar.gz https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.24.2.tar.gz.sig Changes ------- * CVE-2019-11500: ManageSieve protocol parser does not properly handle NUL byte ? when scanning data in quoted strings, leading

When exim runs deliver -m and tries to write to a directory that does not exist is causes a crash which stops the exim MTA. Dec 9 23:20:38 mailhost exim: [ID 197553 mail.info] 2010-12-09 23:20:38 1PQpmu-0007O9-OD <= dovecot-bounces+user=domain.co.uk at dovecot.org H=dovecot.org [62.236.108.70] P=esmtp S=2714 id=1291936811.2991.135.camel at kurkku.sapo.corppt.com Dec 9 23:20:38 localhost

Hello, given a Debian 9 system with Dovecot 2.2.34 installed from self-built packages made from the official tarball combined with Stephan Bosch's debian files (upgraded multiple times from packages made in a similar way). Today, I updated this system to 2.3.0.1 from the official repository at repo.dovecot.org. After the update, dovecot wouldn't start because of: > dovecot: master:

I'm running the following: # 2.3.4 (0ecbaf23d): /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 11.2-RELEASE-p4 amd64 # FS: ZFS auth_mechanisms = plain login auth_username_format = %Ln listen = * mail_location = maildir:~/Maildir namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe

Hi Jake, thanks for fixing this. I have installed now the newly built package on my production system and will report, if any more core dumps occur. Regards, Andreas Am 31.08.2016 um 20:19 schrieb Jake Goerzen: > Hi Andreas & Timo, > > > I've found out what is causing the incorrect hash in the built > packages. Our build system use here at OpenCSW has internal git