similar to: 3.0.14a: sig11/panic on redhat6x

Sometimes I'll get an email from a luser which will cause the POP3 daemon to sig11. The email "appears" to be legal. The sig11s only happen on specific emails, and once I remove the emails from the server, the rest can be downloaded. I gzipped the email, and its at http://theapt.org/bogusemail.gz. While this example is international spam, the sig11s happen with real emails too.

Hi, Here is the backtrace. -- Nico Que de tout inconnu le sage se m?fie. -+- Jean de La Fontaine (1621-1695), Le Renard, le Loup et le Cheval (Fables XII.17) -+- -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Dovecot-1.0-test57-backtrace URL:

I just upgraded my production box from 1.0-stable to 1.0.alpha1. I've noted some new errors in my dovecot logs: Aug 28 23:23:56 cliff dovecot: IMAP(rsferra): Corrupted index cache file /mail/mcad.edu/rsferra/Maildir/.Sent Items/dovecot.index.cache: indexid changed Aug 28 23:33:57 cliff dovecot: IMAP(acarr): Corrupted transaction log file /mail/mcad.edu/acarr/Maildir/.Deleted

On Mon, Jun 05, 2017 at 10:18:13AM +0300, Aki Tuomi wrote: > > > On 04.06.2017 22:35, Larry Rosenman wrote: > > On Fri, Jun 02, 2017 at 11:15:41AM -0500, Larry Rosenman wrote: > >> I'm seeing lots of: > > [snipped] > >> Jun 2 00:00:05 thebighonker exim[57437]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM

Hello. My smbd dies with SIG11. This occurs in 1.9.18p10 as well in 2.0.0beta2. I've read the Samba archive and found the article "Re: 1.9.17p4 - SIGNAL 11 error ??" from Luke and recompiled it with "-g -g". Here the results: After a "smbclient -L localhost" or any other tries to connect to the server the server dies an --- output of "gdb smbd core"

i recently helped a friend of mine migrate from imap-uw using mboxes to dovecot on top of Maildirs and came up against two issues. this is quite embarrassing as ive been claiming dovecot is Solid As A Rock(tm) and hasn't ever given me any issues. 1. if dovecot runs out of file descriptors it will loop forever trying to open new logging pipes. the code in question is at line 624 of

On 04.06.2017 22:35, Larry Rosenman wrote: > On Fri, Jun 02, 2017 at 11:15:41AM -0500, Larry Rosenman wrote: >> I'm seeing lots of: > [snipped] >> Jun 2 00:00:05 thebighonker exim[57437]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM >> IN) [52.40.16.7]:51339 I=[192.147.25.65]:465: 535 Incorrect authentication data

I don't know how this happened. I'm not sure if there is a coredump somewhere because I don't know what user, and I have nothing for 'root' or 'dovecot'. Any advice, or should I make all my coredumps go to a central writable directory so I have better chance of catching it if it happens again? Is it maybe from someone connecting to postfix and causing a SMTP-AUTH

This happened from one user near noon on the 17th and 19th (today) of this month. From the backtrace it looks like they were searching, but I won't know for sure unless I need to ask them. Is this possibly fixed already? I just haven't upgraded dovecot in a while due to lack of problems. The sig11 happened a few dozen times, a few seconds apart each day. I have one coredump from

Hello. When trying to sort a folder by thread (with pine4.61), I get a sig11. The mailstore is Maildir, indexes stored in /var/indexes/%u. The syslog on the server shows this: Nov 29 11:37:55 olan dovecot: IMAP(kowalski): Corrupted index cache file /var/indexes/kowalski/.INBOX/dovecot.index.cache: record points outside file Nov 29 11:37:56 olan dovecot: child 14344 (imap) killed with signal 11

On Fri, Jun 02, 2017 at 11:15:41AM -0500, Larry Rosenman wrote: > I'm seeing lots of: [snipped] > Jun 2 00:00:05 thebighonker exim[57437]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM > IN) [52.40.16.7]:51339 I=[192.147.25.65]:465: 535 Incorrect authentication data (set_id=web) > Jun 2 00:00:06 thebighonker exim[57439]: dovecot_login

Hi all, We recently moved our CVS repository from a 4.6-STABLE machine to a brand new 4.8 install, on another identical machine. The server runs cvs in 'pserver' mode, for remote access by various Windows/Solaris/Linux/FreeBSD clients. We pretty soon noticed that the cvs server process was occasionally crashing on sig11 (ie. a segfault). The only evidence for this was in the message

I'm seeing lots of: Jun 2 00:00:05 thebighonker exim[57437]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM IN) [52.40.16.7]:51339 I=[192.147.25.65]:465: 535 Incorrect authentication data (set_id=web) Jun 2 00:00:06 thebighonker exim[57439]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM IN)