- dovecot - dovecot.org

[Dovecot] RC6 startup failure: "Login prcess died too early"
by S JList 07 Aug '06

07 Aug '06

Greetings. I have been running Dovecot-1.0rc2 on a test server for the last couple of weeks. No problems. However, when I installed RC6 this morning, Dovecot refused to launch completely. Here's the relevant snippet from /var/log/maillog: Aug 7 10:08:36 mercury dovecot: Dovecot v1.0.rc6 starting up Aug 7 10:08:37 mercury dovecot: Login process died too early - shutting down Aug 7 10:08:37 mercury dovecot: child 26127 (login) killed with signal 11 Aug 7 10:08:37 mercury dovecot: child 26128 (login) killed with signal 11 Both RC2 and RC6 compiled cleanly with "--with-pop3d". For reasons beyond my control, I have to set protocols = imap pop3 disable_plaintext_auth = no ssl_disable = yes I do have a valid /etc/pam.d/dovecot file (we're using PAM). I made certain that the localized settings for /usr/local/etc/dovecot.conf matched what they were in RC2 for RC6. (I did use the RC6 dovecot-example.conf as source for RC6, then made the local changes. I also tried testing RC6 with my old RC2 config file--same failure). So, RC2 starts just fine. RC6 fails to start with the messages logged above. Can anyone give me any pointers? RHEL (Linux Kernel 2.6.9-34.0.2.ELsmp), built from source, nothing out-of-the-ordinary. Right now, I've reverted back to RC2. TIA. S JList sjlist(a)heidelberg.edu

2 3

[Dovecot] rc6 build pb
by Thomas Hummel 07 Aug '06

07 Aug '06

Hello, with rc6 on FreeBSD 6.1-STABLE, I encounter the following when running make after the usual configure [ Note : that worked with rc5 ] /usr/local/bin/zsh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -L/usr/local/lib -o dovecot-auth -export-dynamic auth.o auth-cache.o auth-client-connection.o auth-master-connection.o auth-master-listener.o auth-module.o auth-request.o auth-request-handler.o auth-stream.o auth-worker-client.o auth-worker-server.o db-ldap.o db-sql.o db-passwd-file.o main.o mech.o mech-anonymous.o mech-plain.o mech-login.o mech-cram-md5.o mech-digest-md5.o mech-ntlm.o mech-gssapi.o mech-rpa.o mech-apop.o passdb.o passdb-blocking.o passdb-bsdauth.o passdb-cache.o passdb-ldap.o passdb-passwd.o passdb-passwd-file.o passdb-pam.o passdb-checkpassword.o passdb-shadow.o passdb-vpopmail.o passdb-sql.o userdb.o userdb-blocking.o userdb-ldap.o userdb-passwd.o userdb-passwd-file.o userdb-prefetch.o userdb-static.o userdb-vpopmail.o userdb-sql.o libpassword.a ../lib-settings/libsettings.a ../lib-ntlm/libntlm.a ../lib-sql/libsql.a ../lib/liblib.a -lcrypt -lpam -lldap -export-dynamic ../../libtool:1: no such file or directory: /usr/bin/sed -e 1s/^X// libtool: ignoring unknown tag ../../libtool:1: no such file or directory: /usr/bin/sed -e 1s/^X// *** Warning: inferring the mode of operation is deprecated. *** Future versions of Libtool will require --mode=MODE be specified. ../../libtool:1: no such file or directory: /usr/bin/sed -e 1s/^X// ../../libtool:1: no such file or directory: /usr/bin/sed -e 1s/^X// ../../libtool:1: no such file or directory: /usr/bin/sed -e 1s/^X// ../../libtool:1: no such file or directory: /usr/bin/sed -e 1s/^X// ../../libtool:1: no such file or directory: /usr/bin/sed -e 1s/^X// ../../libtool:1: no such file or directory: /usr/bin/sed -e 1s/^X// ../../libtool:1: no such file or directory: /usr/bin/sed -e 1s/^X// ../../libtool:1: no such file or directory: /usr/bin/sed -e 1s/^X// ../../libtool:1: no such file or directory: /usr/bin/sed -e 1s/^X// ../../libtool:1: no such file or directory: /usr/bin/sed -e 1s/^X// ../../libtool:1: no such file or directory: /usr/bin/sed -e 1s/^X// ../../libtool:1: no such file or directory: /usr/bin/sed -e 1s/^X// ../../libtool:1: no such file or directory: /usr/bin/sed -e 1s/^X// (eval):1: no such file or directory: /usr/bin/sed -e 1s/^X// ../../libtool:1: no such file or directory: /usr/bin/sed -e 1s/^X// mkdir /.libs mkdir: /.libs: Permission denied *** Error code 1 Stop in /tmp/dovecot-1.0.rc6/src/auth. *** Error code 1 Stop in /tmp/dovecot-1.0.rc6/src. *** Error code 1 Stop in /tmp/dovecot-1.0.rc6. *** Error code 1 Stop in /tmp/dovecot-1.0.rc6. munster2% pwd /tmp/dovecot-1.0.rc6 -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

2 1

[Dovecot] rc6 compilation problem?
by Alan Schmitt 07 Aug '06

07 Aug '06

Hello, I usually have no problem compiling dovecot on my OS X.4 machine (last one I compiled was rc2), but rc6 is giving trouble: if /bin/sh ../../../libtool --tag=CC --mode=compile gcc - DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../src/lib -I../../../src/ lib-dict -I../../../src/lib-index -I../../../src/lib-mail -I../../../ src/lib-storage -I../../../src/lib-storage/index -I../../../src/lib- storage/index/maildir -std=gnu99 -g -O2 -Wall -W -Wmissing- prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts - Wformat=2 -Wbad-function-cast -MT quota-fs.lo -MD -MP -MF ".deps/ quota-fs.Tpo" -c -o quota-fs.lo quota-fs.c; \ then mv -f ".deps/quota-fs.Tpo" ".deps/quota-fs.Plo"; else rm -f ".deps/quota-fs.Tpo"; exit 1; fi gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../src/lib -I../../../ src/lib-dict -I../../../src/lib-index -I../../../src/lib-mail - I../../../src/lib-storage -I../../../src/lib-storage/index -I../../../ src/lib-storage/index/maildir -std=gnu99 -g -O2 -Wall -W -Wmissing- prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts - Wformat=2 -Wbad-function-cast -MT quota-fs.lo -MD -MP -MF .deps/quota- fs.Tpo -c quota-fs.c -fno-common -DPIC -o .libs/quota-fs.o quota-fs.c: In function ‘fs_quota_get_resource’: quota-fs.c:219: warning: passing argument 1 of ‘quotactl’ makes pointer from integer without a cast quota-fs.c:219: warning: passing argument 2 of ‘quotactl’ makes integer from pointer without a cast quota-fs.c:234: error: ‘struct dqblk’ has no member named ‘dqb_curblocks’ make[4]: *** [quota-fs.lo] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Here is what I did: - run configure - edit config.h to remove the use of MADVISE - run make Am I doing something wrong? Alan -- The hacker: someone who figured things out and made something cool happen. .O. ..O OOO

1 0

[Dovecot] flag changes - duped notifications
by Joshua Goodall 07 Aug '06

07 Aug '06

Seeing the following with 1.0-rcX : * OK Dovecot ready. 001 login xxx@xxx xxx 001 OK Logged in. 002 select INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 18 EXISTS * 0 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1146630080] UIDs valid * OK [UIDNEXT 46] Predicted next UID 002 OK [READ-WRITE] Select completed. 003 STORE 1 FLAGS (\Deleted) * 1 FETCH (FLAGS (\Deleted)) * 1 FETCH (FLAGS (\Deleted)) 003 OK Store completed. The flag change results in a duplicated notification. With a large number of deletes over a slower link this causes client problems. JG ________________________________ Joshua Goodall | Senior Systems Engineer Pacific Internet (Australia) Pty Ltd P: +61 3 9674 7552 Australia | Singapore | Hong Kong | Philippines | India | Thailand | Malaysia http://www.pacific.net.au/disclaimer/

1 0

[Dovecot] Stale imap processes
by Martin Jackson 07 Aug '06

07 Aug '06

Hello, I'm new to the list, but I noticed a buildup of stale imap processes after upgrading to 1.0rc2. My IMAP server actually ran over maxpipekva, and I had to reboot it. I got to spend some time learning about kern.ipc.maxpipekva in the process of troubleshooting. I'm running FreeBSD 6.1-RELEASE-p3, and I have a small home office LAN setup. 2 XP client PC's, one which uses primarily Thunderbird 1.5.0.5, one which uses primarily Outlook Express. I had been running with SSL under Thunderbird (only), but disabled that in hopes of fixing the problem. It appears not to have helped. I am using the FreeBSD dovecot port, currently at rc2, with default settings. I use the default authentication scheme, and Maildir storage (my MTA is Postfix). I am running a number of other daemons on this machine but mail is its main function. I am interested in helping to solve this problem; is there anything I can do to help? Thanks, Marty

2 1

Re: [Dovecot] LIST command ignores "hidden=yes" for default namespace
by Bill Boebel 07 Aug '06

07 Aug '06

On Sun, June 11, 2006 1:51 pm, Timo Sirainen <tss(a)iki.fi> said: > On Mon, 2006-05-08 at 22:03 -0400, Bill Boebel wrote: >I'm not sure if this is a bug or just an undesirable feature, but when I >have our namespace configured to match Courier's "INBOX." functionality, >Dovecot forces me to also define a default namespace (with no prefix). >Without the default namespace defined I get "NO Unknown namespace." errors >when trying to subscribe or unsubscribe folders. > > It was a bug when tb-extra-mailbox-sep workaround was enabled. Fixed: > http://dovecot.org/list/dovecot-cvs/2006-June/005709.html > The second part of this still seems to be the case with RC2... the LIST command ignores "hidden=yes". http://www.dovecot.org/list/dovecot/2006-May/013253.html Running with the following namespace settings causes a LIST comand to show the folder listing twice, once the INBOX. prefix and once without. But it should only be listing the folders with the prefix since hidden=yes on the second. The patch I listed in my original post fixes it in RC2 as well. namespace private { separator = . prefix = INBOX. inbox = yes location = maildir:%h } namespace private { separator = . prefix = inbox = no hidden = yes location = maildir:%h }

2 1

[Dovecot] 1.0 RC6 released
by Timo Sirainen 07 Aug '06

07 Aug '06

http://dovecot.org/releases/dovecot-1.0.rc6.tar.gz http://dovecot.org/releases/dovecot-1.0.rc6.tar.gz.sig Back to rc1's SSL proxying code with some improvements, which hopefully now makes everyone happy. I'm seeing all kinds of problems with namespace prefixes and LIST code. I guess it would be important to fix it before v1.0 since it makes upgrades from other servers easier.. I also tried looking into the "Unknown namespace" problems that happens if you try to create only one namespace with "INBOX." prefix. I couldn't really figure out what causes those errors. Could someone show me what commands the client tries to use which causes it? * Removed login_max_logging_users setting since it was somewhat weird in how it worked. Added login_max_connections to replace it with login_process_per_connection=no, and with =yes its functionality is now within login_max_processes_count. + Added --with-linux-quota configure option to specify which Linux quota version to use, in case it's not correct in sys/quota.h. Usually used as --with-linux-quota=2 + acl plugins: If .DEFAULT file exists in global ACL root directory, use it as the default ACLs for all mailboxes. - Fixes to login process handling, especially with login_process_per_connection=no. - Back to the original SSL proxy code but with one small fix, which hopefully fixes the occational hangs with it - Several fixes to handling LIST command more correctly.

1 0

Re: [Dovecot] Dovecot proxy: Too many open files
by Bill Boebel 07 Aug '06

07 Aug '06

On Sun, August 6, 2006 4:40 pm, Timo Sirainen <tss(a)iki.fi> said: > On Wed, 2006-08-02 at 23:20 -0400, Bill Boebel wrote: >> It appears that when running Dovecot as a proxy-only box with >> "login_process_per_connection = no", it ignores the value of >> login_max_logging_users. > > Not really. It does enforce the maximum users _logging in_ limit, but > for that isn't counted SSL proxies or other proxies.. I rewrote this in > CVS. There's now login_max_connections setting which works pretty much > how expected. Ahh, ok. I will give it a try. Thanks, Bill

1 0

[Dovecot] Dovecot proxy: Too many open files
by Bill Boebel 06 Aug '06

06 Aug '06

It appears that when running Dovecot as a proxy-only box with "login_process_per_connection = no", it ignores the value of login_max_logging_users. And in Linux, since each socket requires a file descriptor, if you don't increase the maximum number of open files that each process is allowed to have open, imap-login will reach the 1024 open file limit and start logging the following errors: imap-login: socket() failed: Too many open files imap-login: Internal login failure: user=... imap-login: socketpair() failed: Too many open files Here are the settings I am testing with: login_process_per_connection = no login_max_logging_users = 225 login_processes_count = 20 login_max_processes_count = 30 And here the output of "lsof -nu dovecot" when one of the imap-login processes reaches its open file limit. In this case PID 20087 had 362 users connected, but it should have allowed no more than 225 users, which would have kept it from reaching the open file limit: (sent directly to Timo since it was too big to post to the list) Also, I am running CVS dovecot-20060725. Bill

2 1

[Dovecot] Using mail_chroot and default_mail_env
by Daniel Kauffman 06 Aug '06

06 Aug '06

Settings for mail_chroot and default_mail_env are not playing well together. It seems that default_mail_env is verified to exist *before* the chroot but is later used *after* the chroot. A configuration like this: * mail_chroot = /var/mail/example.com/username * default_mail_env = maildir:/Maildir Fails with the message: * stat(/Maildir) failed: No such file or directory As a work-around, I created an empty directory named Maildir *outside* of the chroot. The relevant portions of the filesystem now look something like this: * /Maildir * /var/mail/example.com/username/Maildir/... NOTE: The empty /Maildir directory is owned by root. NOTE: Each /var/mail/example.com/username directory and up is owned by root. NOTE: Each /var/mail/example.com/username/Maildir directory and below is owned by the email user. After successful testing with the "static" settings above, I was able to pull the per-user settings for mail_chroot in from PostgreSQL using home to over-ride mail_chroot. If anyone else has been having trouble with mail_chroot + default_mail_env, hopefully this work-around will help. Finally, I should mention my system, just in case I am the only one affected... * Xen + Linux 2.6.16.13 + Debian 3.1 + ( Dovecot 1.0rc2 in chroot ) Regards, Daniel Kauffman

2 1