similar to: trying to enable features

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,

http://dovecot.org/releases/1.0/dovecot-1.0.6.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.6.tar.gz.sig * IDLE: Interval between mailbox change notifies is now 1 second, because some clients keep a long-running IDLE connection and use other connections to actually read the mails. * SORT: If Date: header is missing or broken, fallback to using INTERNALDATE (as the SORT draft

http://dovecot.org/releases/1.0/dovecot-1.0.6.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.6.tar.gz.sig * IDLE: Interval between mailbox change notifies is now 1 second, because some clients keep a long-running IDLE connection and use other connections to actually read the mails. * SORT: If Date: header is missing or broken, fallback to using INTERNALDATE (as the SORT draft

I get: Making all in auth make[3]: Entering directory /usr/src/dovecot/src/auth' rm -f libpassword.a ar cru libpassword.a mycrypt.o password-scheme.o password-scheme-md5crypt.o password-scheme-otp.o password-scheme-rpa.o ranlib libpassword.a gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-sql -I../../src/lib-settings -I../../src/lib-ntlm -I../../src/lib-otp

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

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] ->

All over a sudden the getquota plugin in SquirrelMail doesn't work anymore. I activated debugging an got: IMAP command sent: a001 GETQUOTAROOT "INBOX" IMAP response received: Array ( [0] => * QUOTAROOT "INBOX" "" [1] => * QUOTA "" () ) A manual test results in: . GETQUOTAROOT "INBOX" * QUOTAROOT "INBOX"

from dovecot -n: plugin: fts: squat quota: maildir quota_rule: Trash:storage=100M quota_warning: storage=10%% /usr/local/scripts/quota-warning 90 quota_warning2: storage=5%% /usr/local/scripts/quota-warning 95 quota_warning3: storage=1%% /usr/local/scripts/quota-warning 99 trash: /usr/local/etc/dovecot-trash.conf The quota warning that used to work in 1.0.10 (with the

Core was generated by /usr/local/libexec/dovecot/imap'. Program terminated with signal 6, Aborted. #0 0xb7fb6410 in __kernel_vsyscall () (gdb) bt #0 0xb7fb6410 in __kernel_vsyscall () #1 0xb7e85f15 in raise () from /lib/i686/cmov/libc.so.6 #2 0xb7e87891 in abort () from /lib/i686/cmov/libc.so.6 #3 0x080ce499 in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x80e8f54

I tried to disable courier-pop3 today in favour of dovecot pop3. Prior to that I ran: find /home -maxdepth 1 -type d | xargs --replace /usr/local/scripts/courier-dovecot-migrate.pl --overwrite --recursive --convert {} ( /home is hashed two levels deep: /home/a/a/aanton/Maildir/ ) After that, I got lots of errors like: Aug 9 13:02:40 postamt dovecot: IMAP(azenclu): Maildir

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,

I'm getting "Maximum number of mail processes exceeded" messages when 512 imap Processes are active. Dovecot reports: Warning: fd limit 1024 is lower than what Dovecot can use under full load (more than 1712). Either grow the limit or change login_max_processes_count and max_mail_processes settings But in my /var/service/dovecot/run script I use: #!/bin/sh mkdir /var/core chmod

Since upgrading to dovecot 1.0.5, I started to see the following error in maillog: dovecot: IMAP(username): Connection closed: Broken pipe Any insight that anyone can offer would be greatly appreciated. I've attached a complete list of all dovecot log entries in maillog in the hope that it will help you identify the issue. Thanks in advance. Joseph D. Wagner -------------- next part

Hi, i start today my new mail server with dovecot with about 2000 User on it. i don't know if it's a problem or not but when a client connect in pop3 the message keep on the server. Sep 21 10:53:37 cnetmbox dovecot: pop3-login: Login: user=<XXXXXX at XXXXXX.it>, method=PLAIN, rip=XXX.XXX.XXX.XXX, lip=XXX.XXX.XXX.XXX Sep 21 10:53:37 cnetmbox dovecot: POP3(XXXXXXXXXX at XXXXXXXX.it):

Hello, the dovecot-example.conf states: # Authentication cache size in kilobytes. 0 means it's disabled. # Note that bsdauth, PAM and vpopmail require cache_key to be set for caching # to be used. #auth_cache_size = 0 # Time to live in seconds for cached data. After this many seconds the cached # record is no longer used, *except* if the main database lookup returns # internal failure. We

I now have Dovecot in production and things are apparently trouble-free. The one known problem is that initial client inbox load can take 30 seconds - 2 minutes. For instance: 'I got fed up waiting and went and got coffee'...this with a 3MB mbox inbox...and my mail server is a substantial machine consuming 25% CPU just for this person's IMAP session. I realize that a certain

Hi, First of all congratulations for you development. It?s really good. We have a customer that has a copy of all inbound and outbound mail in an account. When he tries to open the mail, the process of index all mail consume all cpu and memory. How can we avoid this kinds of things? Thank you in advance, Lucas

>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

http://dovecot.org/tmp/dovecot-1.0.1rc3.tar.gz Looks like I managed to do a lot of changes today. So I'll wait a few more days before v1.0.1 release. The important changes since rc2: + deliver: Added -e parameter to write rejection error to stderr and exit with EX_NOPERM instead of sending the rejection by executing sendmail. + dovecot --log-error logs now a warning, an error and a

Core was generated by /usr/local/libexec/dovecot/imap'. Program terminated with signal 6, Aborted. (gdb) bt #0 0xb7f6f410 in __kernel_vsyscall () #1 0xb7e3ef15 in raise () from /lib/i686/cmov/libc.so.6 #2 0xb7e40891 in abort () from /lib/i686/cmov/libc.so.6 #3 0x080ce979 in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x80e9534 "Trying to close mailbox %s with open