similar to: Fatal: master: service(imap): child n killed with signal 11 (core dumped) - in mail_cache_header_fields_read

We're seeing a core dump for a user connecting from IPHONE. The user mail are in NFS mount. # dovecot --version 2.2.12 # doveconf -n # 2.2.12: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.4 auth_cache_negative_ttl = 0 auth_cache_size = 20 M auth_verbose = yes default_client_limit = 4000 default_process_limit = 1000 default_vsz_limit = 2 G director_mail_servers =

This is log from dovecot 2.1.17 (I had to downgrade from 2.2.10 because lot of problems) on CentOS 6.5: 2014-01-14T18:36:03+01:00 server/a.b.c.d dovecot: lmtp(5927): Fatal: master: service(lmtp): child 5927 killed with signal 11 (core dumped) # uname -a Linux server 2.6.32-431.1.2.0.1.el6.x86_64 #1 SMP Fri Dec 13 13:06:13 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux (gdb) bt full #0

We uograded our dovecot from version 2.1.10 -> 2.10.12, but within the first hour of use, dovecot-lda would segfault during delivery. This left a lock file lying around causing the user's mail readers to hang; much hilarity ensues. All further deliveries to the same user will result in a crash. The only thing that fixes this condition is to blow away the user's INBOX cache index.

http://dovecot.org/releases/2.2/rc/dovecot-2.2.13.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.13.rc1.tar.gz.sig There have been a ton of smaller and some larger changes since v2.2.12, so I thought I'd first make a RC release and the final v2.2.13 tomorrow. Please try it out! BTW. I've read most of the mails again in Dovecot mailing list, but there are still a few reported

http://dovecot.org/releases/2.2/rc/dovecot-2.2.13.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.13.rc1.tar.gz.sig There have been a ton of smaller and some larger changes since v2.2.12, so I thought I'd first make a RC release and the final v2.2.13 tomorrow. Please try it out! BTW. I've read most of the mails again in Dovecot mailing list, but there are still a few reported

I'm seeing a few warnings emitted when building for x86. They're pretty obvious, but if you want the configure options etc, I can provide those. In Dovecot 2.1.2 (I also see some of these in 2.1.1): 1) src/lib-index/mail-cache-fields.c (comparison between two last_used fields) mail-cache-fields.c: In function 'mail_cache_header_fields_read': mail-cache-fields.c:406: warning:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 13 Feb 2014, Francesco Fiore wrote: > Is there any news for this problem? read the other threads about the issue and find the patch in the 2.2.11 thread. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUvyfF3D1/YhP6VMHAQIeDQf7BTMO9RzoL21mS06n56j1nRT2HbSYNsXx

Hello all, Recently, I was setting up SpamAssassin and procmail on my system (used to run Courier, and was converted using Courier convert scripts). I was setting up a rule in PINE to filter all previously marked SPAM messages into a folder, when I suddenly got disconnected from the IMAP server. I attempted to reconnect, but any attempts to access my INBOX would disconnect me. I looked in

I'm using release 2.2.12, during a copy operation i get segfault on imap process. I have full bt of the issue: (gdb) bt #0 0x00007fcc521029cd in mail_cache_header_fields_read (cache=0x15c7210) at mail-cache-fields.c:369 #1 0x00007fcc52100664 in mail_cache_open_and_verify (cache=0x15c7210) at mail-cache.c:497 #2 0x00007fcc5210244d in mail_cache_register_get_list (cache=0x15c7210,

Dovecot 1.1.2 crashes reliably for me now on a Mac OS X machine. Here's some info: --- Telnet session --- $ telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Dovecot ready. a login user1 password a OK Logged in. b select inbox * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen

Hi, I obtain continuosly segmentation fault of processes pop3 and imap, with version 2.2.10. This is the error for the pop3 process (but for imap is is the same): 2014-02-10 11:06:22 pop3(xxxxxxx at yyyyyyyy.zz): Fatal: master: service(pop3): child 23804 killed with signal 11 (core dumped) This is the kernel log: Feb 10 11:06:22 pecpop5 kernel: pop3[23804]: segfault at 7fa42a3f4070 ip

Here is the log over a 12 hour period: pid 91923 (pop3), uid 25039: exited on signal 6 pid 98265 (pop3), uid 25039: exited on signal 6 pid 95547 (pop3), uid 25039: exited on signal 6 pid 235 (pop3), uid 25039: exited on signal 6 pid 239 (pop3), uid 25039: exited on signal 6 pid 318 (pop3), uid 25039: exited on signal 6 pid 386 (pop3), uid 25039: exited on signal 6 pid 415 (pop3), uid 25039: