similar to: Wrong credential caching

I'm getting "imap-login: Disconnected: Connection queue full:" messages like these: May 16 12:17:26 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=160.45.172.202, lip=141.42.4.250 May 16 12:17:26 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=141.42.165.160, lip=141.42.4.250, TLS May 16 12:18:23 postamt dovecot: imap-login: Disconnected:

I'm encountering lots of Oct 31 11:14:25 postamt dovecot: pipe() failed: Too many open files errors around midday ever since the latest upgrade to 1.0.7. The errors appear in pairs like this one: Oct 31 11:20:01 postamt dovecot: pipe() failed: Too many open files Oct 31 11:20:01 postamt dovecot: imap-login: Internal login failure: user=<username>, method=PLAIN, rip=193.175.174.239,

I'm getting these in my log: Jul 17 11:40:42 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 17 11:40:42 postamt dovecot: child 26581 (login) killed with signal 6 Jul 17 11:51:12 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 17 11:51:12 postamt dovecot: child

>From my log: Oct 6 00:10:36 postamt kernel: [2353838.557216] deliver[2799]: segfault at 48 ip b77dd649 sp bfcf3b48 error 6 in libdovecot-storage.so.0.0.0[b778e000+b8000] Oct 6 00:14:39 postamt kernel: [2354082.014722] deliver[6399]: segfault at 48 ip b7779649 sp bf9ca028 error 6 in libdovecot-storage.so.0.0.0[b772a000+b8000] Oct 6 00:28:12 postamt kernel: [2354894.551201] deliver[13972]:

a "masteruser" login fails: Oct 8 15:12:54 postamt dovecot: auth: Debug: auth(masteruser,141.42.206.38,master): Master user lookup for login: nonworkinguser Oct 8 15:12:54 postamt dovecot: auth: passdb(masteruser,141.42.206.38,master): Master user logging in as nonworkinguser Oct 8 15:12:54 postamt dovecot: auth: Debug: cache(nonworkinguser,141.42.206.38): expired Oct 8 15:12:54

Hi! Starting with 2.1.1 we suddely encounter quite a lot of these messages: Mar 2 11:09:28 postamt dovecot: imap(username): Error: Maildir filename has wrong S value, renamed the file from /home/a/i/username/Maildir/.A*Teens.Eink&AOQ-ufe, Spenden etc/cur/1323207735.M64829P19819.postamt.charite.de,S=5137:2,S to /home/a/i/username/Maildir/.A*Teens.Eink&AOQ-ufe, Spenden

One of our users seems to have strange problems with his mailbox: Oct 2 00:36:42 postamt dovecot: IMAP(rbxxxx): Corrupted transaction log file /home/r/b/rbxxxx/Maildir/.listen.CCL/dovecot.index.log: Append with UID 1096, but next_uid = 1097 Oct 2 00:36:42 postamt dovecot: IMAP(rbxxxx): Corrupted transaction log file /home/r/b/rbxxxx/Maildir/.listen.CCL/dovecot.index.log: Append with UID 1096,

QUERY: THREAD REFERENCES ISO-8859-1 ALL RESPONSE: [SERVERBUG] Internal error occurred. Refer to server log for more information. [2013-08-09 15:42:34] Aug 9 15:41:48 postamt dovecot: imap(username) tTbs7oPjfACNKs4m: Error: Threading lost Message ID Aug 9 15:42:34 postamt dovecot: imap(username) tTbs7oPjfACNKs4m: Error: Threading lost Message ID What does that mean? WHY has the Message-Id

Today I encountered this after upgrading: Feb 18 18:15:40 postamt dovecot: imap(lehnertr): Panic: LIST: Mailbox name not UTF-8: INBOX.Entw?rfe Feb 18 18:15:40 postamt dovecot: imap(lehnertr): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x4104a) [0xb75cc04a] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x410bb) [0xb75cc0bb] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0)

With 2.0.18 I was using a quota warning script like this: plugin { ... # Quota quota = maildir quota_rule = INBOX.Trash:storage=+2048M quota_warning = storage=99%% quota-warning 99 %u quota_warning2 = storage=95%% quota-warning 95 %u quota_warning3 = storage=90%% quota-warning 90 %u quota_warning4 = storage=85%% quota-warning 85 %u } # der schickt die Quota warnmails service

A user is logged in via imap from multiple devices. The log has this: Sep 21 11:46:32 postamt dovecot: imap(awxxxxer): delete: box=INBOX, uid=15347, msgid=<1341851741.4ffb085d2e2b7 at swift.generated>, size=15675 Sep 21 11:46:32 postamt dovecot: imap(awxxxxer): delete: box=INBOX, uid=15739, msgid=<b23b2e42f6ae9ba1602690be42b7b5c7.squirrel at webmail.charite.de>, size=18134 Sep 21

Found this today multiple times for the same user: Aug 16 16:59:38 postamt dovecot: IMAP(username): file strfuncs.c: line 165 (p_strndup): assertion failed: (max_chars != (size_t)-1) Aug 16 16:59:38 postamt dovecot: IMAP(username): Raw backtrace: imap [0x80c6d53] -> imap(i_fatal+0) [0x80c6795] -> imap(p_strndup+0x38) [0x80d8316] -> imap(t_strndup+0x22) [0x80d86d7] ->

dovecot version 1.0.0, compile from the sources. --------- snip -------- # /usr/local/etc/dovecot.conf listen: *:10143 ssl_listen: *:10943 ssl_cert_file: /etc/ssl/certs/postamt.pem ssl_key_file: /etc/ssl/private/postamt.key disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mail_location: maildir:~/Maildir mail_plugins:

>From my logs (dovecot-1.1.8) Jan 14 08:42:52 postamt dovecot: imap-login: *** glibc detected *** imap-login: malloc(): memory corruption: 0x0844e778 *** Jan 14 08:42:52 postamt dovecot: child 15380 (login) killed with signal 6 Jan 14 10:06:42 postamt dovecot: Panic: imap-login: file ioloop.c: line 71 (io_remove_full): assertion failed: (io->callback != NULL) Jan 14 10:06:42 postamt

Feb 23 20:40:36 postamt dovecot: IMAP(username): file message-parser.c: line 766 (message_parser_parse_next_block): assertion failed: (ctx->input->eof || ctx->input->closed || ctx->input->stream_errno != 0) Feb 23 20:40:36 postamt dovecot: IMAP(username): Raw backtrace: /usr/local/libexec/dovecot/imap [0x8009236d] -> /usr/local/libexec/dovecot/imap [0x80091ed8] ->

I'm getting a lot of entries like this in my log: Apr 16 10:10:18 postamt dovecot: auth(default): shadow(doxxxris,141.42.206.38): CRYPT(wrongpassword) != '$1$qSe71xxx$09MoMqNyll.wPLCdSaFuA0', try MD5-CRYPT scheme instead It seems that changing the password via SquirrelMail (poppasswd) breaks the authentication scheme somewhat. Users cannot log in anymore. -- Ralf Hildebrandt

>From my log today: May 22 07:38:48 postamt dovecot: imap-login: Disconnected (no auth attempts): rip=141.42.245.68, lip=141.42.4.250 May 22 07:39:29 postamt dovecot: imap-login: Disconnected (no auth attempts): rip=141.42.245.68, lip=141.42.4.250 May 22 07:39:50 postamt dovecot: imap-login: Disconnected (no auth attempts): rip=141.42.245.68, lip=141.42.4.250 May 22 07:39:50 postamt dovecot:

Feb 23 19:48:14 postamt deliver(username): copy: uid=1, box=Dovecot Delivery Mail, dest=INBOX, msgid=<47C06A3F.3040101 at charite.de>, size=423118 Feb 23 19:48:14 postamt deliver(username): msgid=<47C06A3F.3040101 at charite.de>: saved mail to INBOX Feb 23 19:48:14 postamt deliver(username): Transaction rolled back: Ignore last 1 changes What does that "Transaction rolled back:

>From my log: Feb 25 14:53:26 postamt postfix/local[22546]: 0EAA8220697: to=<username at postamt.charite.de>, relay=local, delay=0.61, delays=0.16/0.04/0/0.42, dsn=5.7.0, status=bounced (permission denied. Command output: Warning: Growing pool 'Environment' with: 4096 Quota exceeded ) I'm not sure if "Warning: Growing pool 'Environment' with: 4096" should

>From my logs: Feb 27 08:10:33 postamt dovecot: IMAP(username): expunge: uid=2793, box=Trash, msgid=<E2FEA6DFF2340C438369E79466FB7E94F43547 at EXCHANGE01.charite.de>, size=3025 Feb 27 08:10:33 postamt dovecot: IMAP(username): expunge: uid=2794, box=Trash, msgid=<20080226140752B6F6EC3EF7$08D09877C3 at REALTIMEPCR>, size=12833 Feb 27 08:10:33 postamt dovecot: IMAP(username): expunge: