- dovecot - dovecot.org

[Dovecot] SASL abort causes 5s delay, triggered by UW libc-client
by Arne Nordmark 12 Mar '11

12 Mar '11

Since upgrding to Debian squeeze, the web mail system (Imp4/Horde3) suffers delays every time a new IMAP connection is needed. Tracing the authentication conversation, we find: 08:45:55.270609: 00000000 AUTHENTICATE GSSAPI 08:45:55.271277: + 08:45:55.271761: * 08:45:55.271782: 00000000 BAD Authentication aborted by client. 08:45:55.271815: 00000001 AUTHENTICATE PLAIN 08:46:00.271008: + and the PLAIN login succeeds. Imp4 is using php5-imap which is using libc-client, and the delays makes the interface so slow to hardly usable. For reasons best known to its authors, libc-client first initiates GSSAPI authentication, then checks if there is a Kerberos ticket it can use (there is none), then realizes its mistake and aborts SASL, and tries PLAIN. At this point dovecot delays for 5000ms. While not defending libs-client's odd behaviour of not checking for tickets first, it has probably done so for a long time, and dovecot from Debian lenny does not delay at this point. I am lost as how to get around this without changing the code. The "nodelay" parameter can not be used with PAM passdb, according to the documentation. I would be inclined to call always call client_auth_failed with nodelay=TRUE in the SASL_SERVER_REPLY_AUTH_ABORTED case. Arne Nordmark Config: # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0 ext3 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap listen: *, [::] ssl_ca_file: /etc/ssl/certs/mechca_cert.pem ssl_cert_file: /etc/ssl/certs/ano4/ano4_crt.pem ssl_key_file: /etc/ssl/certs/ano4/ano4_key.pem login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail mail_location: maildir:/var/mail/maildir/%u mbox_write_locks: fcntl dotlock lda: postmaster_address: postmaster(a)ano.mech.kth.se mail_plugins: sieve auth default: mechanisms: plain gssapi failure_delay: 0 debug: yes passdb: driver: pam userdb: driver: passwd socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: root plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/sieve

2 1

[Dovecot] Dovecot 2.X, built from source, no extensions?
by Enright, Mike 10 Mar '11

10 Mar '11

Greetings list. Pardon the ignorance. I am working on CentOS 5.2. Unfortunately the repo version of Dovecot is 1.0.X. This works fine mind you but it doesn't have ORDEREDSUBJECT Threading support, which I need. I downloaded 2.0.11 and built from source, but now I don't see any Threading support, not even REFERENCES. I looked to see if I was missing a ./configure option but if I am, it has eluded me. Any guidance would be appreciated. # dovecot -n # 2.0.11: /usr/etc/dovecot/dovecot.conf # OS: Linux 2.6.18-92.1.18.el5PAE i686 CentOS release 5.2 (Final) ext3 auth_mechanisms = plain login disable_plaintext_auth = no mail_location = maildir:/var/vmail/%d/%n/Maildir passdb { args = /usr/etc/dovecot/dovecot-mysql.conf driver = sql } plugin/quota = maildir:storage=10240:messages=1000 protocols = imap service auth { unix_listener /var/run/dovecot/auth-master { mode = 0600 user = vmail } user = root } service imap-login { client_limit = 256 process_min_avail = 10 service_count = 0 vsz_limit = 128 M } ssl = no userdb { args = uid=6000 gid=6000 home=/var/vmail/%d/%n allow_any_users=yes driver = static } # telnet localhost imap Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready. 1 capability * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN 1 OK Capability completed. Cheers Mike Enright Senior Software Engineer Office: +1 239-425-9161 (Florida) Fax: +1 239-425-6845 [cid:C388744A-AA0D-4A0C-A96D-3038C56EC9E5] Interop Technologies 13500 Powers Court Fort Myers, FL 33912 www.interoptechnologies.com<http://www.interoptechnologies.com/>

3 3

[Dovecot] permission recomendation for dovecot configuration files and binaries
by Arkadiusz Miskiewicz 10 Mar '11

10 Mar '11

I'm trying to figure out which permissions will be the best to handle most of tasks (for use in rpm package) for configuration files. Basically /etc/dovecot/ dir /etc/dovecot/* files /etc/dovecot/conf.d/ dir /etc/dovecot/conf.d/files dovecot binaries, deliver mainly For example deliver needs to read configuration files and needs to write into destination. Doesn't seem to be sane to allow MTA user read dovecot configs but that is requires for deliver to work etc. Are there any sane/tested recommendations that would fit most situations (remember, that's going to be rpm package default config) ? -- Arkadiusz Miśkiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/

1 0

[Dovecot] Dovecot 2.0 - size of the mailbox
by Cristiane França 10 Mar '11

10 Mar '11

Hi, The Dovecot 2.0 has some limit size for the mailbox? The server is 64 bits and would like to have mailbox with bigger size that 2 GB.

2 1

Re: [Dovecot] POP3 error
by Thierry de Montaudry 10 Mar '11

10 Mar '11

On 08 Mar 2011, at 13:24, Chris Wilson wrote: > Hi Thierry, > > On Tue, 8 Mar 2011, Thierry de Montaudry wrote: >> On 07 Mar 2011, at 19:15, Timo Sirainen wrote: >>> On Mon, 2011-03-07 at 19:03 +0200, Thierry de Montaudry wrote: >>>>>>>>> Mar 7 11:19:51 xxx dovecot: pop3-login: Error: net_connect_unix(pop3) failed: Resource temporarily unavailable >>>>> .. >>>> As it is happening at least once a day, is there anything I can do to >>>> trace it? and whatever I'll do, will it slow down those machines? >>> >>> Set verbose_proctitle=yes (won't slow down) and get list of all >>> Dovecot processes when it happens. And check how much user and system >>> CPU it's using and what the load is. >> >> Got the same problem this morning, here is the CPU usage and ps aux for >> dovecot. plus the different error I could pick up in the log, most of >> them are repeated a couple of times. >> >> I suspect it a problem with system resources, but can find any message >> to tell me what. Mail are stored on 17 NFS servers (CentOS), plus 3 >> servers for indexes only. >> >> CPU load is very high, but mainly from httpd running our webmail >> interface, which uses the local imap server. > [...] >> top - 11:10:14 up 14 days, 12:04, 2 users, load average: 55.04, 29.13, 14.55 >> Tasks: 474 total, 60 running, 414 sleeping, 0 stopped, 0 zombie >> Cpu(s): 99.6%us, 0.3%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.1%si, 0.0%st >> Mem: 16439812k total, 16353268k used, 86544k free, 33268k buffers >> Swap: 4192956k total, 140k used, 4192816k free, 8228744k cached > > You're lucky this server is still alive and that you could even run top > and ps on it. > > There's nothing to debug in dovecot here. Your server is overloaded by > about 55 times. Buy 55 times as many servers or do something about your > webmail interface (maybe a separate webmail cluster). > > Cheers, Chris. > As you can see the numbers (55.04, 29.13, 14.55) the load was busy getting higher when I took this snapshot and this was not a normal situation. Usually this machine's load is only between 1 and 4, which is quite ok for a quad core. It only happens when dovecot start generating errors, and pop3, imap and http get stuck. It went up to 200, and I was still able to stop web and mail daemons, then restart them, and everything was back to normal.

7 20

[Dovecot] Dovecot + Sieve does not work
by Jimmi 10 Mar '11

10 Mar '11

Hi, On my Debian Squeeze server I installed Dovecot 1.2.16 from http://xi.rename-it.nl/debian/ and configured as follow: # dovecot -n # 1.2.16: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-110209 i686 Debian 6.0 ext3 log_path: /var/log/dovecot.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap sieve disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login first_valid_uid: 100 mail_privileged_group: postfix mail_location: maildir:/home/virtual/%d/%n mbox_write_locks: fcntl dotlock imap_client_workarounds: outlook-idle lda: postmaster_address: postmaster(a)7girello.net mail_plugins: sieve log_path: /var/log/dovecot-deliver.log info_log_path: /var/log/dovecot-deliver.log auth default: mechanisms: plain login user: postfix passdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: virtual group: virtual plugin: sieve: /home/virtual/%d/%n/.dovecot.sieve sieve_dir: /home/virtual/%d/%n/sieve/ After that in Roundcube 0.5.1 downloaded from http://roundcube.net/ I enabled the managesieve plugin but when I go to the filter page RC says that he cannot connect the server. I then realized that the port 4190 is not open and I cannot understand why. In my dovecot.conf I have the section: protocol managesieve { # Specify an alternative address:port the daemon must listen on # (default: *:2000) listen = localhost:4190 } that is not shown in the output of 'dovecot -n'. Did I missed something? Thanks in advance -- jimmi

3 6

[Dovecot] Dovecot LDA and Postfix/local for local users.
by iti＠promax.media.pl 10 Mar '11

10 Mar '11

Hello, I would like to configure dovecot lda for local users. My dovecot vesion is 1.2.15. Dovecot documentation for System users says that only thing I should add to main.cf is: mailbox_command = /usr/local/libexec/dovecot/deliver (path to deliver) After that should I commented postfix/local process from master cf ? regards, Jarek

3 3

[Dovecot] Fatal: postmaster_address setting not given
by Richard Edmonds 09 Mar '11

09 Mar '11

Hi, I'm getting: "Fatal: postmaster_address setting not given" errors in my log file dovecot ver: 1.2.12 Recently I tried to follow: http://postfixmail.com/blog/index.php/postfixadmin-on-ubuntu-9-10/ on ubuntu 10.10 (which works fine on ubunto 9.10) I note that in 10.10 their is no dovecot-postfix.conf so I made the appropriate changes to dovecot.conf instead and changed master.cf dovecot transport line since I saw someone recently had the same problem: dovecot unix - n n - - pipe flags=DRhu user=vmail:mail argv=/usr/lib/dovecot/deliver -c /etc/dovecot/dovecot.conf -f ${sender} -d ${recipient} I still have that problem however. Authentication seems ok but delivery fails. Any possibility of help on this one? vecot unix - n n - - pipe flags=DRhu user=vmail:mail argv=/usr/lib/dovecot/deliver -c /etc/dovecot/dovecot.conf -f ${sender} -d ${recipient} I still have that problem however. Authentication seems ok but delivery fails. Any possibility of help on this one? </body> </html>

2 2

[Dovecot] ID command bug & patch
by Mike Abbott 09 Mar '11

09 Mar '11

When I set imap_id_log=* in dovecot-2.0.11 and a client sends, say, tag id ("a" "b" "c" "d") then dovecot logs: ID sent: a=b, b=c, c=d The following patch makes it log instead: ID sent: a=b, c=d --- a/dovecot/src/lib-imap/imap-id.c (revision 113366) +++ b/dovecot/src/lib-imap/imap-id.c (working copy) @@ -164,6 +164,7 @@ str_append_c(reply, '='); str_append(reply, str_sanitize(value, 80)); } + args++; } return str_len(reply) == 0 ? NULL : str_c(reply); }

2 1

Re: [Dovecot] auth on tcp socket?
by Hajo Locke 09 Mar '11

09 Mar '11

Hello, > You should read Wietses post again. > > He told you to not rely on not documented settings since they can > silently disappear. > > With postfix you can rely on the documented behaviour. So it is > natural that there will be no warning for officially unsupported > features. > yes, i know that. nobody should use undocumented features. auth-service on tcp-socket was added by timo after my Suggestion last november. so when asking this on postfix's-side iam not really interested in current docs but wanted to suggest the update on implemention and docs to get it as official feature for next releases. as an user all i can do is telling some facts and ask... Hajo

2 1