- dovecot - dovecot.org

[Dovecot] file client-common.c: line 25 (client_unlink): assertion failed: (clients_count > 0)
by Frank Bonnet 16 Mar '09

16 Mar '09

Hello since few days I got this in dovecot log I use 1.1.11 on Debian etch 64 bits Thanks for any info dovecot: Mar 12 16:57:37 Panic: imap-login: file client-common.c: line 25 (client_unlink): assertion failed: (clients_count > 0) dovecot: Mar 12 16:57:37 Error: child 5247 (login) killed with signal 6 (ip=80.125.173.19) dovecot: Mar 12 17:10:04 Panic: imap-login: file client-common.c: line 25 (client_unlink): assertion failed: (clients_count > 0) dovecot: Mar 12 17:10:04 Error: child 6678 (login) killed with signal 6 (ip=92.132.140.150) dovecot: Mar 12 17:10:58 Panic: imap-login: file client-common.c: line 25 (client_unlink): assertion failed: (clients_count > 0) dovecot: Mar 12 17:10:58 Error: child 6812 (login) killed with signal 6 (ip=90.3.120.43) dovecot: Mar 12 17:11:07 Panic: imap-login: file client-common.c: line 25 (client_unlink): assertion failed: (clients_count > 0) dovecot: Mar 12 17:11:07 Error: child 6827 (login) killed with signal 6 (ip=90.3.120.43) dovecot: Mar 12 17:11:13 Panic: imap-login: file client-common.c: line 25 (client_unlink): assertion failed: (clients_count > 0) dovecot: Mar 12 17:11:13 Error: child 6839 (login) killed with signal 6 (ip=90.3.120.43) dovecot: Mar 12 17:11:15 Panic: imap-login: file client-common.c: line 25 (client_unlink): assertion failed: (clients_count > 0) dovecot: Mar 12 17:11:15 Error: child 6841 (login) killed with signal 6 (ip=90.3.120.43)

3 8

[Dovecot] Dovecot and high availability
by d dimov 16 Mar '09

16 Mar '09

Hello dear all. Please accept apologies if the topic was discussed already, tried searching the archives but found few details. What I am looking for would be the best way to making Dovecot highly available in an environment where: two Alteons are load-balancing two Dovecot servers, each Alteon seing both of them; the clients are using exclusively POP3; low volume; in case of a Dovecot server failure service should fail over to the other node with preferably no manual intervention. Failover could mean Alteons just ignoring the failed host and routing all requests to the healthy one. Would it be shared NFS volume mounted on both of the servers from some NAS, maildirs put on that volume and both Dovecots seing the mailboxes simultaneously? Any risks? Is there a good document describing such a setup? Thank you in advance and please indicate if I missed relevant details. Best regards, Dimov

1 0

[Dovecot] Mailing list convert scripts not working on wiki
by Phill Edwards 16 Mar '09

16 Mar '09

I'm trying to download Julian Fitzell's scripts to convert mbox to Maildir format from the wiki page at http://wiki.dovecot.org/Migration/MailFormat But when I click on the links for the scripts it just sends me back to the same page rather than downloading the scripts. The links in question are http://wiki.dovecot.org/Migration/MailFormat?action=AttachFile&do=get&targe… and http://wiki.dovecot.org/Migration/MailFormat?action=AttachFile&do=get&targe… How can I get the scripts? Regards, Phill

2 2

[Dovecot] MoinMoin wiki updated
by Timo Sirainen 16 Mar '09

16 Mar '09

I finally upgraded to MoinMoin v1.8.2 from old v1.5.8. Let me know if something doesn't work right.

1 0

[Dovecot] fstat(mboxname.lock) failed: Bad file descriptor
by Mark Sapiro 16 Mar '09

16 Mar '09

I have just upgraded from 1.2.beta1 to 1.2.beta2. My configuration is: [root@sbh16 ~]# dovecot -n # 1.2.beta2: /usr/local/etc/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) protocols: pop3 pop3s imap imaps ssl_cert_file: /etc/postfix/sbh16-cert.pem ssl_key_file: /etc/postfix/sbh16-key.pem login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login mail_privileged_group: mail mail_location: mbox:~/Mail:INBOX=/var/spool/mail/%u mbox_write_locks: fcntl dotlock mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 pop3_lock_session(default): no pop3_lock_session(imap): no pop3_lock_session(pop3): yes auth default: mechanisms: plain apop login worker_max_count: 5 passdb: driver: passwd-file args: /usr/local/etc/dovecot.passwd passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix [root@sbh16 ~]# This represents one change from the previous config. Previously with pop3_lock_session = yes, I needed mail_access_group = mail. With the upgrade to beta2, I changed that to mail_privileged_group = mail as shown above. Now, during a session lasting several seconds, I see the following in maillog: Mar 15 09:35:51 sbh16 dovecot: pop3-login: Login: user=<mark>, method=APOP, rip=68.183.193.239, lip=72.52.113.16, TLS Mar 15 09:36:01 sbh16 dovecot: POP3(mark): fstat(mark.lock) failed: Bad file descriptor Mar 15 09:36:04 sbh16 dovecot: POP3(mark): Disconnected: Logged out top=0/0, retr=1/1919972, del=0/328, size=5381253 Mar 15 09:36:04 sbh16 dovecot: child 9023 (pop3) killed with signal 11 (core dumps disabled) This does not occur with shorter sessions lasting only a few seconds or less. The only symptom is the log messages. The client sees nothing unusual, at least in this case where the session is a retrieval of one large message. I haven't tried long sessions retrieving multiple messages. If I remove pop3_lock_session = yes, the issue does not occur. I don't think I need it. I put it in a long time ago to attempt to solve a problem that was actually caused by something else. Since removing it does seem to avoid this issue, I will leave it out, but I'm reporting this anyway as it seems there may be some underlying problem. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 2

[Dovecot] pop-proxy to redundant servers ?
by Jan-Frode Myklebust 15 Mar '09

15 Mar '09

I'm considering putting two servers with failover IP-addresses in front of our pop/imap cluster, with dovecot in proxy-mode running on both servers. But, can dovecot handle more than one backend server for each user ? I.e. I would want to point the dovecot proxy to send userX to backend-server1, or backend-server2 if backend-server1 is down. Is something like that possible ? -jf

2 2

[Dovecot] Can't compile v1.2.beta2 w/o linux-quota
by Pascal Volk 15 Mar '09

15 Mar '09

Hi Timo, make dies with an error: quota-fs.c: In function ‘fs_quota_get_linux’: quota-fs.c:456: error: ‘no’ undeclared (first use in this function) quota-fs.c:456: error: (Each undeclared identifier is reported only once quota-fs.c:456: error: for each function it appears in.) make[4]: *** [quota-fs.lo] Error 1 One of the configure options was: --without-linux-quota Regards, Pascal -- The trapper recommends today: deadbeef.0907402(a)localdomain.org

2 2

[Dovecot] v1.1.12 and v1.2.beta2 released
by Timo Sirainen 14 Mar '09

14 Mar '09

http://dovecot.org/releases/1.1/dovecot-1.1.12.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.12.tar.gz.sig http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta2.tar.gz http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta2.tar.gz.sig I thought I'd do a double-release since it's Friday the 13th. v1.2.0 is getting closer, mainly some ACL fixes left. Changes in v1.2.beta2 since beta1: * Authentication userdb: Renamed system_user to system_groups_user. Probably pretty much no one used this feature. * deliver no longer creates temp files to /tmp. They're instead created to the users' mailbox directories. - IMAP: Fixed SORT command crashing - POP3 was broken in beta1 - Fixes to virtual mailboxes - Fixes to IMAP ACL support Changes in both v1.1.12 and v1.2.beta2: * Added :MAILBOXDIR= to mail_location to specify the root dir for mailboxes. dbox users should migrate to ":MAILBOXDIR=mailboxes", because that's going to be the default in v1.2+. + Linux: Adding -D parameter to login_executable makes login processes dump core to login_dir if they crash. - IMAP: SELECT didn't always return first unseen message in reply - POP3: pop3_lock_session=yes didn't use mail_privileged_group while dotlocking. - mbox: Don't crash if >=8192 bytes long line begins with "From ". - Maildir: More fixes to handling over 26 keywords. - Several logging fixes and improvements - Fixed authentication caching with non-plaintext mechanisms when using a blocking passdb (e.g. MySQL) - Fixed DIGEST-MD5 authentication with user@domain style usernames.

2 1

[Dovecot] setting up both system password users AND virtual users
by Jim Pazarena 14 Mar '09

14 Mar '09

I'm afraid that I am a rookie at dovecot, and cannot seem to figure the configuration for a dual system & virtual setup. For now I am using POP3 ---only--- I've got the "system" working, but cannot figure out how to add the virtual system. The docs aren't quite clear enough for me to understand. The wiki example for dynamic passwd-file locations shows: mail_location = maildir:/home/%d/%n/Maildir userdb passwd-file etc etc I am using mbox, not maildir, AND I've already used mail_location for my system accounts with the following line: mail_location = mbox:~/mail/:INBOX=/mail/%u In the case of my virtual users, the mail is stored in INBOX=/mail/VIRTUAL/%d/%u and the password file is stored in /exim/etc/VIRTUAL/%d/passwd would someone kindly help me with this? thanks!

3 2

[Dovecot] pam_authenticate() failed: authentication error
by Zbigniew Szalbot 14 Mar '09

14 Mar '09

Hello, I would like to ask for your help. I have noticed some error messages issued by dovecot. Mar 13 20:00:57 relay dovecot: auth-worker(default): pam(example(a)example.com): pam_authenticate() failed: authentication error (/etc/pam.d/dovecot missing?) Not surprisingly $ l /etc/pam.d/dovecot ls: /etc/pam.d/dovecot: No such file or directory The funny thing is that authentication does work but I guess I have something misconfigured. I'd appreciate if you could help me. I am on a FreeBSD system (7.0) if that matters. Thank you! -- Zbigniew Szalbot

5 8