similar to: "dovecot: Maximum number of mail processes exceeded"

I'm getting some cra shes with 1.1.1, but even with these start options: #!/bin/sh mkdir /var/core chmod 1777 /var/core echo /var/core/%p > /proc/sys/kernel/core_pattern ulimit -n 65535 ulimit -c unlimited /usr/local/sbin/dovecot -F I'm not getting any corefiles - why? It definitely used to work :) Jun 22 00:05:53 postamt dovecot: imap-login: *** glibc detected *** imap-login:

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:

others have found this problem ? this possible bug can be used by user in that way that one password login can use 2 maildirs in filesystem effitively give them all space qoutas and lost of other goodies so to speak: foo at example.com with a password can login with fOO at example.com and fOo at example.com add more chars to get more mailbox :/ confirms ? i found the problem when i had

Hi, Since the 23rd of March, we encounter mailbox corruption for some users (15 out of 5000) using POP mainly via Thunderbird. Symptoms are : -users can login but fail to receive new mails and fail to read their inbox -Dovecot.log : ar 29 11:00:06 Error: POP3(user_login): Couldn't init INBOX: Mailbox isn't a valid mbox -The mailbox start with either 'FFrom or

I'm using 1.2.6 with the managesieve patch and maildir++ quotas (via the maildirsite file). Again, I found that the quota warning is not bering triggered. Testing via: smtp-source -4 -f sender at charite.de -t recipient at charite.de -m 1 -l 1000000 -C 1 mail.charite.de:submission recipient at charite.de being a mailbox with a 10.0 MB limit. I attached dovecot -n and the quota warn script.

>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

Hello, sometimes we get the following errors on out dovecot proxies: dovecot: May 27 20:06:10 Info: imap-login: Disconnected: Connection queue full (no auth attempts): REMOTE=<IP> LOCAL=<IP> TLS handshaking dovecot: May 27 20:06:10 Info: imap-login: Disconnected: Connection queue full (no auth attempts): REMOTE=<IP> LOCAL=<IP> TLS handshaking dovecot: May 27 20:06:10

This is with respect to an error that I am facing in dovecot. The error is that is seen in logs is "Feb 23 00:04:46 mailblade1 dovecot: IMAP(USERNAME): /indexes/USERNAME/.INBOX/dovecot-uidlist: Duplicate file entry at line 7: 1234776125.M559298P3988.s2o.qlc.co.in,S=13111,W=13470:2, (uid 94277 -> 97805)" This error is seen for multiple users. Once this error occurs for a user, the

Two of my users are reporting that their quota is not being recalculated ALTHOUGH they deleted lots and lots of mails. I'm using today's hg checkout of 1.2 beta 4 -- Ralf Hildebrandt Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.computerbeschimpfung.de Wen du nicht mit K?nnen beeindrucken kannst, den verwirre mit Schwachsinn! -------------- next

>From my log: Aug 10 12:23:39 postamt dovecot: IMAP(megow): Inotify instance limit for user exceeded, disabling. Increase /proc/sys/fs/inotify/max_user_instances # wc -l subscriptions 95 # cat /proc/sys/fs/inotify/max_user_instances 128 Why does 95 exceed 128? -- Ralf Hildebrandt Gesch?ftsbereich IT | Abteilung Netzwerk Charit? - Universit?tsmedizin Berlin Campus Benjamin Franklin

Since I have these performance problems after migration to 2.0.5 I'm publishing my config for review. Can anybody spot any obvious signs of trouble? # 2.0.5: /usr/local/etc/dovecot.conf # OS: Linux 2.6.32-24-generic-pae i686 Debian squeeze/sid auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login disable_plaintext_auth = no auth_master_user_separator = * mail_location =

Mar 15 09:46:11 postamt dovecot: pop3(username): Error: Couldn't open INBOX: Timeout while waiting for lock Mar 15 09:46:11 postamt dovecot: pop3(username): Couldn't open INBOX top=0/0, retr=0/0, del=0/0, size=0 Mar 15 09:47:26 postamt dovecot: pop3(username): Error: Couldn't open INBOX: Timeout while waiting for lock Mar 15 09:47:26 postamt dovecot: pop3(username): Couldn't open

Hello, I'm preparing to convert from qpopper + UW-IMAP to dovecot. So far testing has gone very well. One problem we haven't figured out is that long-running POP sessions keep the mailbox locked, so that the MDA times out while trying to deliver. We're using "maildrop" as our MDA if that matters. We don't see this issue for dovecot IMAP sessions. During long-running

Hello all, We've recently migrated the mail server used by our 5000 students, from Tru64/UW-IMAP/Procmail/Postfix/mbox to Debian Etch/Dovecot/Deliver/Postfix/Maildir E-mails are not stored directly on the server (except for index and control files), but on an NAS that exports the students' homedirs on NFS. Each student has a 100MB quota on the NAS. Here is the configuration : vega:~#

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,

These crashes only happen at night/during the evening, way after maximum load: Jan 27 21:19:57 postamt kernel: [1490698.849461] imap[15089]: segfault at 00000008 eip 080b779b esp bfbe20a0 error 4 Jan 27 21:20:50 postamt kernel: [1490752.022142] imap[15251]: segfault at 00000008 eip 080b779b esp bfd241e0 error 4 Jan 27 21:21:53 postamt kernel: [1490814.348208] imap[15482]: segfault at 00000008 eip

>From my log: Dec 29 16:43:58 postamt dovecot: Dovecot v1.1.7 starting up Dec 29 16:43:59 postamt dovecot: Fatal: imap-login: epoll_create(): Too many open files Dec 29 16:43:59 postamt dovecot: Temporary failure in creating login processes, slowing down for now Dec 29 16:43:59 postamt dovecot: Fatal: imap-login: epoll_create(): Too many open files Dec 29 16:43:59 postamt dovecot: Fatal:

I'm getting constantly high numbers of page reclaims & involuntary context switches for dovecot/auth. page reclaims = minor faults = cpu switching back to system-mode, But why is the auth process doing that so excessively? Same for the large number of involuntary context switches... Attached is my "dovecot -n" output. Date: Sun, 07 Nov 2010 20:40:34 +0100 type real

A user logged in with a captial "L" for his username: Jul 7 12:30:31 postamt dovecot: auth(default): cache(Loser,10.47.64.227): miss Jul 7 12:30:31 postamt dovecot: auth(default): shadow(Loser,10.47.64.227): lookup Jul 7 12:30:31 postamt dovecot: auth(default): shadow(Loser,10.47.64.227): unknown user Jul 7 12:30:31 postamt dovecot: auth(default): cache(Loser,10.47.64.227): miss Jul

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,