- dovecot - dovecot.org

[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 06 Aug '06

06 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 06 Aug '06

06 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 06 Aug '06

06 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

[Dovecot] ldap + dovecot
by Gert Horne 06 Aug '06

06 Aug '06

Hi again, I am still struggling with ldap and dovecot. I have my dovecot authenticating against ldap. The problem now seems to be of a permission type. I am also trying to figure out the default_mail_env and valid_chroot_dirs settings. may maillog gives me: IMAP(user): Ambiguous mail location setting, don't know what to do with it: /var/spool/mail/ (try prefixing it with mbox: or maildir:) server dovecot: IMAP(user): Failed to create storage with data: /var/spool/mail/ Can anyone help me please.

1 0

[Dovecot] dovecot.conf
by Magnus Granberg 06 Aug '06

06 Aug '06

Can we move dovecot.config to /etc/dovecot/ ? MVH Magnus Granberg Ume.Nu

6 8

[Dovecot] daemontools
by Rick Romero 05 Aug '06

05 Aug '06

Hi, I just started running RC2 on Thursday. I migrated an old Courier IMAP server, and the only issue I had was that I didn't understand how to enable quotas :) It's impressively fast, and I'm quite happy with it so far. This morning I found that dovecot had crashed, I had exceeded FreeBSD's kern.maxpipekva Has anyone successfully run dovecot under daemontools? I got it to fire up, but it didn't seem to work right.. I'm guessing it's a rights issue, but I haven't delved into it at all. Thanks! Rick

3 3

[Dovecot] Dovecot proxy in front of UWash?
by Vincent Fox 05 Aug '06

05 Aug '06

Is it possible to use Dovecot frontends in front of UWash backends? I need a proxy pool ASAP. There is not sufficient time to migrate the backends for 40,000+ users so they have to stay UW for now. I have been looking at Perdition but concerned about performance under load. Dovecot looks really promising with it's non-forking mode. I need simple dumb frontends no local mail. Other questions: 1) Database? Wiki only talks about SQL, can I have it map username to hostname using LDAP or some other mechanism? 2) Kerberos? I am hazy here, but can I have the frontends auth the user via Kerberbos and things "just work"? Or do I need to stick with PLAIN authentication? 3) Port mappings? Can I have the requests coming in on SSL ports remapped to non-SSL ports on the backends? Thus the backends could have their load reduced somewhat. e.g. client->proxy:993->backend:143

2 1