March 2010 - dovecot - dovecot.org

[Dovecot] Shared mailboxes unix permissions
by Thomas Hummel 16 Apr '10

16 Apr '10

Hello Timo, I'm running dovecot-1.2.11/Maildir and plan to migrate to single UID mailboxes some day, but for now, I've got "system" users and I'm testing permissions handling in order to set up shared mailboxes. The private namespace mailboxes location is location = maildir:/courriel/boites/%u:CONTROL=/courriel/meta/%u:INDEX=/var/dovecot-test/indexes/%1u/%u I've . created a 'doveshared' unix group . added 'mail_access_groups = doveshared' . chmod/chgrp the maildir and control dirs like this : drwxrws--- 7 doveimap doveshared 4096 Mar 31 18:47 /courriel/boites/doveimap drwxrws--- 5 doveimap doveshared 4096 Mar 31 18:47 /courriel/meta/doveimap [which were empty] . added 'acl_shared_dict = file:/var/dovecot-test/dict/shared-mailboxes' with drwxrwxs-- 2 root doveshared 512 Mar 31 18:44 /var/dovecot-test/dict [which were empty] Everything gets created with the permission I was expecting, except : -rw------- 1 doveimap doveshared 8 Mar 31 18:47 /courriel/meta/doveimap/dovecot-uidvalidity -rw------- 1 doveimap doveshared 0 Mar 31 18:44 /courriel/meta/doveimap/dovecot-uidvalidity.4bb37be4 and -rw------- 1 doveimap doveshared 0 Mar 31 18:44 /var/dovecot-test/dict/shared-mailboxes I can't see the explanation in http://wiki.dovecot.org/SharedMailboxes/Permissions and the 'dovecot-shared' file doesn't help (besides, my understanding is that in 1.2x, it's for backward compatibility reason). Any idea ? Thanks -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

2 3

[Dovecot] Testing 2.0b3 - problem with pop3
by Odhiambo Washington 07 Apr '10

07 Apr '10

I am testing the version on FreeBSD 7.3-PRELEASE (I doubt it's the issue) and I am having a problem with pop3. Here is what I see in the log when I attempt to connect to port 110: Feb 22 18:15:03 master: Warning: SIGHUP received - reloading configuration Feb 22 18:15:08 pop3-login: Panic: file login-settings.c: line 216 (login_settings_read): assertion failed: (input.roots[count] == NULL) Feb 22 18:15:08 master: Error: service(pop3-login): child 70115 killed with signal 6 (core dumped) Feb 22 18:15:08 master: Error: service(pop3-login): command startup failed, throttling And the output of doveconf can be seen at http://62.8.64.102/~wash/2.0b3.txt I've basically made my best effort to reflect the settings I had on 2.0b1 into this version. What could the problem be? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ "If you have nothing good to say about someone, just shut up!." -- Lucky Dube

7 10

[Dovecot] Managing IMAP ACL from script
by Неворотин Вадим 06 Apr '10

06 Apr '10

I need to change ALC for mailboxes from a script on my server. As I understand now I can correctly change ACL only via telnet using IMAP commands. And moreover I need to know user's password for it. Is there any plans to add inheritance of ACL and ability to manage it directly from a server? And if it is in which version? Will 2.0 fully support ACL? Now I use Dovecot 1.2.10.

2 1

[Dovecot] Dovecot+LDAP issues
by Daniel Gomes 05 Apr '10

05 Apr '10

Dear list members, I am having some problems with a LDAP passdb authentication on Dovecot. Before I forget, the specs: it's a Ubuntu 7.10 server running Dovecot 1.0.5 connecting to 2 different machines running LDAP servers: gold with OpenLDAP 2.4.19 and extra with OpenLDAP 2.4.9 (extra is a replication slave of gold). The initial setup of dovecot was with a MySQL passdb, which is still the first passdb, now followed by my new LDAP passdb, all with a static userdb. Here is my dovecot-ldap.conf (the LDAP passdb) (I switched the domain with example.com for privacy sake): ----------------------------------------------------------------- #Servidor hosts = gold.example.com extra.example.com tls = yes ldap_version = 3 base = ou=people,dc=example,dc=com scope = onelevel #uid/gid user_global_uid = 5000 user_global_gid = 5000 #Bind para ler coisas dn = cn=dovecot,ou=people,dc=example,dc=com dnpass = secret sasl_bind = no sasl_mech = #passdb: usar password lookups para autenticar utilizadores auth_bind = no pass_attrs = userPassword=password #, =userdb_home=/home/vmail/%d/%n pass_filter = (&(maildrop=%u)(mailacceptinguser=1)) default_pass_scheme = PLAIN-MD5 ----------------------------------------------------------------- This setup is currently working for some tests users (the others are still being auth'ed with the old MySQL passdb). Unfortunately, I seemed to have run into a big problem on an occasion when dovecot was unable to connect my first server (gold) and hence went to the second one (extra). Backtracking from the logs (starting with dovecot-error.log): Mar 31 13:11:50 bunker dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server Mar 31 13:11:50 bunker dovecot: auth-worker(default): LDAP: ldap_result() failed: Can't contact LDAP server -------------------- This is when the users stopped being able to login via imap, with the following message being shown on dovecot-info.log: Mar 31 13:13:00 bunker dovecot: auth(default): ldap(user(a)domain.com,xxx.xxx.xxx.xxx): unknown user (I know, an auth_debug log would be handy here, but it wasn't activated at the time). I went on to investigate and from the slapd logs I noticed that the second LDAP server (extra) was being contacted for the passdb lookups, thus proving that dovecot considered the gold to be dead (it wasn't, but that's a different matter). Anyway, the problem is that dovecot doesn't seem to be able to retrieve the user information from extra. As the slapd log shows: Mar 31 13:41:37 extra slapd[31473]: conn=4 op=140 SRCH base="ou=people,dc=example,dc=com" scope=1 deref=0 filter="(&(?=undefined)(?=undefined))" Mar 31 13:41:37 extra slapd[31473]: conn=4 op=140 SRCH attr=userPassword Mar 31 13:41:37 extra slapd[31473]: conn=4 op=140 SEARCH RESULT tag=101 err=0 nentries=0 text= For some reason, dovecot sends an undefined filter to extra, even though the same filter works without issues with gold (and remember they are "clones"). I just can't see how this is caused by any of my configurations! Any ideas? Thanks in advance, -- Daniel Gomes

3 5

[Dovecot] Question about SASL auth
by Mark Sapiro 03 Apr '10

03 Apr '10

I have recently upgraded from Dovecot 1.2.10 to 2.0.beta3. I have Postfix 2.3.3 and use Dovecot to provide SASL auth for Postfix. # dovecot -n # 2.0.beta3: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) auth_mechanisms = plain apop login auth_worker_max_count = 5 mail_location = mbox:~/Mail:INBOX=/var/spool/mail/%u mail_privileged_group = mail mbox_write_locks = fcntl dotlock passdb { args = /usr/local/etc/dovecot.passwd deny = no driver = passwd-file master = no pass = no } passdb { deny = no driver = pam master = no pass = no } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } ssl_cert = </etc/postfix/sbh16-cert.pem ssl_key = </etc/postfix/sbh16-key.pem userdb { driver = passwd } Since upgrading to 2.0.beta3 I have started seeing notices like Mar 6 07:06:20 sbh16 postfix/smtpd[30273]: warning: SASL: Connect to private/auth failed: Resource temporarily unavailable Mar 6 07:06:20 sbh16 postfix/smtpd[30273]: fatal: no SASL authentication mechanisms in my maillog. I don't see them too often (an average of about 2 occurences per day), and they seem to be related to spam or some kind of attack. I am able to send using SASL authentication from my own client OK. The relevant postfix config settings are smtpd_sasl_auth_enable = yes smtpd_sasl_path = private/auth smtpd_sasl_type = dovecot Postfix and its configuration haven't changed from what I used with Dovecot 1.2.10. With Dovecot 1.2.10, I rarely if ever saw these failures. Is this a case of the socket being in use when another auth request arrives or is it something else? And if it is the socket in use, is there some change in 2.0.beta that would cause the socket to be busy longer? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 7

[Dovecot] simple steps with sieve
by Gavin Hamill 03 Apr '10

03 Apr '10

Today is my first day with sieve, so be gentle :) I'm trying to set up a pretty webmail interface to our Dovecot 1.2.4 server using roundcube. The managesieve config + roundcube 'managesieve' plugin work fine, and I'm able to use roundcube's UI to generate .dovecot.sieve files. We use winbind + LDAP lookups to do some exotic mail rewriting... ultimately user.name(a)domain.com gets rewritten to 'ar-cloh@localhost', and in /home/AD/ar-cloh/.dovecot.sieve there is only this: require ["vacation"]; # rule:[gdh_test] if anyof (header :contains "Subject" "test") { vacation "test away"; } When I send an email to the user, I see this in the mail.log Oct 19 15:39:43 ar-smtp-1 dovecot: deliver(ar-cloh): sieve: msgid=<1255963176.14420.31.camel@gdh-work>: discarding vacation response for message implicitly delivered to <ar-cloh@ar-smtp-1> I don't understand; sending a vacation for implicitly-delivered messages sounds exactly like what I want - is there any way to say 'do this anyway' ? gdh

8 18

Re: [Dovecot] New install authentication probs
by Andy Smith 01 Apr '10

01 Apr '10

Ola Daniel, thanks for the idea, but actually within the config file the settings are not within the auth default section, its just shown that way from the output of dovecot -n cheers Andy. Quoting Daniel Gomes <daniel.gomes(a)ist.utl.pt>: > Hey Andy, > > I might be way over my head here, but unlike you, in my setup I set > "auth_debug", "auth_verbose" and "auth_debug_password" to "yes" > outside the "auth default" section. Try that and see if you get the > verbose logging you're looking for! > > Cheers, > > On 31-03-2010 19:46, Andy Smith wrote: >> Hi Brad, >> >> thanks for the reply, here is the output: >> >> dovecot -n >> # 1.2.10: /usr/local/etc/dovecot.conf >> # OS: FreeBSD 6.1-RELEASE i386 nfs >> log_path: /tmp/dovecot.log >> protocols: imap >> ssl: no >> disable_plaintext_auth: no >> login_dir: /var/run/dovecot/login >> login_executable: /usr/local/libexec/dovecot/imap-login >> verbose_proctitle: yes >> first_valid_uid: 1000 >> first_valid_gid: 1000 >> mail_privileged_group: mail >> mail_location: maildir:/var/spool/mail/%d/%u >> mail_debug: yes >> imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep >> lda: >> sendmail_path: /usr/sbin/sendmail >> auth default: >> mechanisms: plain digest-md5 cram-md5 >> username_format: %Lu >> verbose: yes >> debug: yes >> debug_passwords: yes >> passdb: >> driver: sql >> args: /usr/local/etc/dovecot-sql.conf >> userdb: >> driver: passwd >> args: blocking=yes >> userdb: >> driver: sql >> args: /usr/local/etc/dovecot-sql.conf >> socket: >> type: listen >> client: >> path: /var/run/dovecot/auth-client >> mode: 432 >> master: >> path: /var/run/dovecot/auth-master >> mode: 384 >> > > -- > Daniel Gomes, 55350 >

4 7

[Dovecot] 2.0.beta3 imapd running hot
by Bernhard Schmidt 01 Apr '10

01 Apr '10

Hi, since a couple of weeks I occasionally have an imapd going crazy on me, using up 100% CPU. Current revision is 10962 29865 vmail 20 0 47820 3296 1708 R 99.7 0.9 131:07.85 imap vmail 29865 86.1 0.8 47820 3296 ? R Mar20 131:20 dovecot/imap [berni 2001:a60:f001:1:219:66ff:fe8b:a6e IDLE strace -p <pid> shows a repeating pattern of epoll_wait(8, {{EPOLLOUT, {u32=36560672, u64=36560672}}}, 5, 4872) = 1 gettimeofday({1269133967, 495298}, NULL) = 0 gettimeofday({1269133967, 495333}, NULL) = 0 gettimeofday({1269133967, 495370}, NULL) = 0 with the last argument of epoll_wait (4872) slowly decrementing and then wrapping around to ~30k. Attaching gdb shows the following backtrace: (gdb) bt full #0 array_idx_i (ioloop=0x22bd5f0) at array.h:189 No locals. #1 io_loop_handler_run (ioloop=0x22bd5f0) at ioloop-epoll.c:188 ctx = 0x22bd800 event = <value optimized out> list = <value optimized out> io = <value optimized out> tv = {tv_sec = 26, tv_usec = 307176} t_id = 2 msecs = 26308 ret = 1 i = <value optimized out> call = <value optimized out> #2 0x00007f8f682bc8e8 in io_loop_run (ioloop=0x22bd5f0) at ioloop.c:350 No locals. #3 0x00007f8f682acd63 in master_service_run (service=0x22bd4c0, callback=0x6590) at master-service.c:486 No locals. #4 0x0000000000418551 in main (argc=1, argv=0x22bd3a0) at main.c:313 set_roots = {0x41b840, 0x0} service_flags = <value optimized out> storage_service_flags = MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT postlogin_socket_path = 0x0 (gdb) c Continuing. ^C Program received signal SIGINT, Interrupt. 0x00007fffed1ff9ad in gettimeofday () (gdb) bt full #0 0x00007fffed1ff9ad in gettimeofday () No symbol table info available. #1 0x00007f8f6795f02a in gettimeofday () from /lib/libc.so.6 No symbol table info available. #2 0x00007f8f682bcb39 in io_loop_handle_timeouts_real (ioloop=0x22bd5f0) at ioloop.c:291 item = <value optimized out> tv = {tv_sec = 0, tv_usec = 36427248} tv_call = {tv_sec = 0, tv_usec = 140737170938560} t_id = <value optimized out> #3 io_loop_handle_timeouts (ioloop=0x22bd5f0) at ioloop.c:339 _data_stack_cur_id = 0 #4 0x00007f8f682bd70e in io_loop_handler_run (ioloop=0x22bd5f0) at ioloop-epoll.c:180 ctx = 0x22bd800 event = <value optimized out> list = <value optimized out> io = <value optimized out> tv = {tv_sec = 28, tv_usec = 267997} t_id = 2 msecs = 28268 ret = 1 i = <value optimized out> call = <value optimized out> #5 0x00007f8f682bc8e8 in io_loop_run (ioloop=0x22bd5f0) at ioloop.c:350 No locals. #6 0x00007f8f682acd63 in master_service_run (service=0x22bd4c0, callback=0) at master-service.c:486 No locals. #7 0x0000000000418551 in main (argc=1, argv=0x22bd3a0) at main.c:313 set_roots = {0x41b840, 0x0} service_flags = <value optimized out> storage_service_flags = MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT postlogin_socket_path = 0x0 doveconf -n: mail.svr02.mucip.net:~# doveconf -n # 2.0.beta3: /etc/dovecot/dovecot.conf # OS: Linux 2.6.33 x86_64 Debian squeeze/sid auth_mechanisms = plain login disable_plaintext_auth = no listen = 83.170.6.69, 2001:1b10:1000::110:1:1 mail_gid = 5000 mail_location = maildir:%h/:INDEX=/var/cache/dovecot/%1n/%n mail_uid = 5000 maildir_stat_dirs = yes maildir_very_dirty_syncs = yes passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { quota = dict:user::file:%h/dovecot-quota quota_rule = *:storage=500M sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = postmaster(a)birkenwald.de protocols = imap pop3 lmtp managesieve quota_full_tempfail = yes service auth { unix_listener /var/spool/postfix-mailout/private/auth { group = postfix mode = 0660 user = postfix } unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0660 } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { inet_listener { port = 24 } } service managesieve-login { inet_listener sieve_deprecated { port = 2000 } process_min_avail = 1 } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } ssl_cert = </etc/ssl/private/pop3.mucip.net.crt ssl_key = </etc/ssl/private/pop3.mucip.net.key userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } verbose_proctitle = yes protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } protocol lmtp { mail_plugins = sieve quota } protocol lda { mail_plugins = sieve quota } protocol imap { imap_idle_notify_interval = 600 s mail_plugins = quota imap_quota zlib imap_zlib } At the moment I have two suspects, the imap_zlib plugin and CONDSTORE (which I recently reenabled in Thunderbird after the fixed version got deployed). The client is always Thunderbird 3.0.3+, but from different systems. It does terminate without any error message in the logs when I exit Thunderbird. Now testing without zlib... Bernhard

4 5

Re: [Dovecot] New install authentication probs
by Andy Smith 31 Mar '10

31 Mar '10

Hi Brad, thanks for the reply, here is the output: dovecot -n # 1.2.10: /usr/local/etc/dovecot.conf # OS: FreeBSD 6.1-RELEASE i386 nfs log_path: /tmp/dovecot.log protocols: imap ssl: no disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_privileged_group: mail mail_location: maildir:/var/spool/mail/%d/%u mail_debug: yes imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep lda: sendmail_path: /usr/sbin/sendmail auth default: mechanisms: plain digest-md5 cram-md5 username_format: %Lu verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: passwd args: blocking=yes userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384

1 0

[Dovecot] New install authentication probs
by Andy Smith 31 Mar '10

31 Mar '10

Hi, Im attempting to configure dovecot for the first time, Im trying to use a MySQL DB that is currently used by tpop3d as Ive read they support the same password format. My main prob currently, apart from that it doesnt work lol, is that Ive enabled the following debugging in dovecot.conf auth_debug = yes auth_debug_passwords = yes auth_verbose = yes But Im getting basically zero info on why my authentication is failing. In my log (which for testing Ive defined as a file in /tmp to make sure Im getting all the info logged to one place) I see just: Mar 31 19:00:17 dovecot: Info: Dovecot v1.2.10 starting up Mar 31 19:00:17 auth-worker(default): Info: mysql: Connected to localhost (ukgri d_vmail) Mar 31 19:00:18 auth(default): Info: new auth connection: pid=64188 Mar 31 19:00:18 auth(default): Info: new auth connection: pid=64186 Mar 31 19:00:18 auth(default): Info: new auth connection: pid=64187 each time I attempt to connect via IMAP it adds another new auth connection line to the log but doesnt tell me anything else :(. So Im stuck debugging my authentication due to lack of info. BTW Im testing IMAP via telnet, telnet to IMAP port and attempt LOGIN (I have this working to a courier IMAP installation). Have I done something wrong? Any help appreciated! thanks Andy.

2 1