June 2015 - dovecot - dovecot.org

LDAP default value variable interpolation
by Leon Kyneur 01 Jul '15

01 Jul '15

I'm wondering if there is a way I can dynamically generate an LDAP default value by using variables. I have a configuration that works something like this on my front end proxy: pass_attrs = mail=user,\ =nopassword=y,\ =proxy=y,\ =host=mail.%d The above works perfectly well even though it seems a bit hack. I want to fetch the host field from LDAP and default it to "mail.%d" if the attribute isn't populated for the user. I have tried the following : pass_attrs = mail=user,\ =nopassword=y,\ =proxy=y,\ =host=%{ldap:mailHost:mail.%d} however the interpolation doesn't occur on the default. Just wondering if there is a way to achieve this? thanks

2 2

Getting regularly mailbox desyncs while syncing with imapc
by Michael 30 Jun '15

30 Jun '15

Hello list! I sync approximately ~1000 Mailboxes actually without any problems, except my very own mailbox - Dovecot 2.2.18 (mdbox format) running here. The server from where I sync my mails from runs Dovecot 1.2.4 (with mbox format). The last log line that I receive is: dsync(ms(a)ddnetservice.de): Warning: Mailbox changes caused a desync. You may want to run dsync again. dovecot error log: 2015-06-30 13:09:50 imap(ms(a)ddnetservice.de): Error: Corrupted transaction log file /var/vmail/ddnetservice.de/ms/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.log seq 2: indexid changed 1435401731 -> 1435662589 (sync_offset=0) This is the command for running my syncs: doveadm -o imapc_user=<remote_user> -o imapc_password=<remote_pw> -o imapc_host=<remote_host> -o imapc_features="rfc822.size fetch-headers" -o mail_prefetch_count=20 -v -D sync -R -u<local_user> imapc: &> $LOGS/$BOX.log A re-run of this command for my mailbox doesn't fix the problem. The "Inbox" remains empty. Only a "doveadm force-resync -ums(a)ddnetservice.de" fixes this problem with the exception that the Inbox still remains empty. So after force-resyncing I need to run the sync again and my Inbox remains consistent until the next imapc sync run. Actually the desync message is self-explanatory, but I wonder why this behaviour only occurs for my own Inbox (only Inbox, other directories aren't affected) and not anywhere else. Is there any possiblity to debug this? Could also the amount of new incoming mails cause this or do I have maybe a bugged mail in my original mailbox that is causing my trouble? Any hint is appreciated. Thanks, Michael

1 0

Same-server mail transfer
by Andrew Obertas 30 Jun '15

30 Jun '15

Hello, What would be the best way to perform a same-server Maildir transfer, while retaining the IMAP structure already in place, between users with the same GID but different UIDs? I've tried doveadm import but I presume it is encountering a permissions error due to the different UIDs. Worst case scenario, I could move everything over manually and then update the UIDs. I feel like there should be a more elegant solution though that I'm not immediately grasping however. -- Best regards, Andrew Obertas Junior Systems Administrator Infinet Communications Group

1 0

replication - remove/delete in storage
by lejeczek 29 Jun '15

29 Jun '15

hi, novice question - is replication supposed to replicate maildir in it's entirety? I get new mails replicated but not operations of removal/deletion, is this normal? many thanks

2 3

authenticate LDAP to email server
by robert k Wild 29 Jun '15

29 Jun '15

hi all, first things first my version and config - # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-504.el6.x86_64 x86_64 CentOS release 6.6 (Final) auth_mechanisms = plain login mail_location = maildir:~/Maildir mbox_write_locks = fcntl passdb { driver = pam } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } - i have installed dovecot+postfix email server and a LDAP server, if i create users on the LDAP server can dovecot pick up the usernames and create a mailbox for the individual users as atm if i want to create an email address for users i add the user to the email server and make a directory for the users mailbox and have to chmod and chown also just another question, can i set up mail groups on dovecot? cheers rob -- Regards, Robert K Wild.

4 12

cram-md5 cache problem
by d tbsky 28 Jun '15

28 Jun '15

hi: I was using scientific linux 6 and had cache problem. I upgrade to scientific linux 7 but the problem is the same, so I try to find out why. dovecot version: 2.2.10. postfix + postfixadmin environment. use dovecot-lda to deliver local mail. if I enable cache with "auth_cache_size = 102400" and enable cram-md5 with "auth_mechanisms = plain login cram-md5". I have cache problem: if I change password at postfixadmin, I can not use the new password to login imap when old password is cached. dovecot log below: Jun 28 11:50:32 auth: Debug: client in: AUTH 6 CRAM-MD5 service=imap securedsession=xjn534sZ9gB/AAAB lip=127.0.0.1 rip=127.0.0.1 lport=143 rport=36342 Jun 28 11:50:32 auth: Debug: client passdb out: CONT 6 PDQzNTU5NTA4MTQxODg5NzUuMTQzNTQ2MzQzMkBtYWlsLmxoeS5jb20udHc+ Jun 28 11:50:32 auth: Debug: client in: CONT<hidden> Jun 28 11:50:32 auth: Debug: cache(test(a)test.example.com,127.0.0.1,<xjn534sZ9gB/AAAB>): hit: <hidden> user=test(a)test.example.com userdb_home=/share/postfix/domains/test.example.com/test/home userdb_mail=maildir:/share/postfix/domains/test.example.com/test userdb_uid=143 userdb_gid=143 Jun 28 11:50:32 auth: Info: cram-md5(test(a)test.example.com,127.0.0.1,<xjn534sZ9gB/AAAB>): password mismatch Jun 28 11:50:34 auth: Debug: client passdb out: FAIL 6 user=test(a)test.example.com Jun 28 11:50:34 imap-login: Debug: Ignoring unknown passdb extra field: Jun 28 11:50:34 imap-login: Info: Disconnected (auth failed, 1 attempts in 2 secs): user=<test(a)test.example.com>, method=CRAM-MD5, rip=127.0.0.1, lip=127.0.0.1, secured, session=<xjn534sZ9gB/AAAB> if I disable "cram-md5" with "auth_mechanisms = plain login". everything is fine. dovecot log below: Jun 28 11:32:24 auth: Debug: cache(test(a)test.example.com,127.0.0.1,<WNsin4sZ6gB/AAAB>): hit: <hidden> user=test(a)test.example.com userdb_home=/share/postfix/domains/test.example.com/test/home userdb_mail=maildir:/share/postfix/domains/test.example.com/test userdb_uid=143 userdb_gid=143 Jun 28 11:32:24 auth: Info: cache(test(a)test.example.com,127.0.0.1,<WNsin4sZ6gB/AAAB>): Password mismatch Jun 28 11:32:24 auth-worker(3711): Debug: sql(test(a)test.example.com,127.0.0.1): query: SELECT username as user, password, '/share/postfix/domains/test.example.com/test/home' as userdb_home, 'maildir:/share/postfix/domains/test.example.com/test' as userdb_mail, 143 as userdb_uid, 143 as userdb_gid FROM mailbox WHERE username = 'test(a)test.example.com' AND active = '1' Jun 28 11:32:24 auth: Debug: client passdb out: OK 15 user=test(a)test.example.com Jun 28 11:32:24 auth: Debug: master in: REQUEST 1951268865 3672 15 0b198494a7e732324f6d6c507b25c13e session_pid=3956 request_auth_token Jun 28 11:32:24 auth: Debug: prefetch(test(a)test.example.com,127.0.0.1,<WNsin4sZ6gB/AAAB>): success Regards, tbskyd

1 0

Out of bounds read error in wildcard_match.c
by Hanno Böck 27 Jun '15

27 Jun '15

Hi, I discovered an out of bounds read error in the file wildcard_match.c. Here's the code: /* find the end of each string */ while (*(++mask)); mask--; while (*(++data)); data--; The problem with this: It will search for the end of the strings (zero-terminated), but it'll only start at position 1, not at position 0 (because the ++ in front of the variable will first increment and then return the value). However these strings can be empty. This can be fixed by changing ++mask to mask++ (and same for data), then there must be a -=2 instead of -- afterwards. See attached patch. I found this by compiling dovecot with address sanitizer and running the test suite. cu, -- Hanno Böck http://hboeck.de/ mail/jabber: hanno(a)hboeck.de GPG: BBB51E42

1 0

"Sensible" location for Sieve scripts
by Andrew Beverley 26 Jun '15

26 Jun '15

I'm configuring some Sieve scripts for virtual users. I'd like to keep the Sieve scripts somewhere "sensible". Currently, all the mail goes into /var/mail/vhosts/<domain>/<mailbox> So I thought a good place for the sieve script might be in there as well, for example: /var/mail/vhosts/example.com/username/sieve Is there any reason *not* to store the sieve scripts in the same location as the mail? Thanks, Andy

3 4

replication notification with chroot users
by Tim Kuijsten 25 Jun '15

25 Jun '15

I'm getting the following error when using dovecot replication: dovecot: imap(foo(a)bar.com): Error: open(/var/dovecot/replication-notify-fifo) failed: No such file or directory I guess this has something to do with the fact that every user is chrooted in it's own homedir. Does dsync support dsync notification when all users are chrooted? lmtp does not seem to have this problem so new mails get replicated, but status changes don't. Thanks. -Tim Config on source: # 2.2.15: /etc/dovecot/dovecot.conf # OS: OpenBSD 5.7 amd64 auth_debug = yes auth_mechanisms = plain login auth_verbose = yes dsync_remote_cmd = /usr/bin/ssh imap.netsend.nl first_valid_gid = 30000 first_valid_uid = 30000 last_valid_gid = 30100 last_valid_uid = 30100 mail_debug = yes mail_home = /srv/vmail/%d/%n mail_location = maildir:~/Maildir mail_plugins = " notify replication" passdb { args = /passwd driver = passwd-file } passdb { args = /passwd_smtponly driver = passwd-file } plugin { mail_replica = remoteprefix:imap.netsend.nl } protocols = imap lmtp service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service auth-worker { chroot = /etc/mail unix_listener /etc/mail/auth-worker { mode = 0600 user = $default_internal_user } user = $default_internal_user } service auth { chroot = /etc/mail unix_listener /var/spool/postfix/private/dovecot-auth { group = _postfix mode = 0600 user = _postfix } } service imap-login { inet_listener imap { port = 0 } process_min_avail = 1 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = _postfix mode = 0600 user = _postfix } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } ssl = required ssl_cert = </etc/ssl/private/2015/chain.crt ssl_cipher_list = ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-CHACHA20-POLY1305:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA384:DHE-RSA-AES256-SHA256:ECDHE-RSA-AES256-SHA:DHE-RSA-AES256-SHA; ssl_dh_parameters_length = 2048 ssl_key = </etc/ssl/private/the.key ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 userdb { args = /passwd default_fields = uid=30000 gid=30000 home=/srv/vmail/%d/%n/./ driver = passwd-file } valid_chroot_dirs = /srv/vmail verbose_ssl = yes protocol imap { mail_max_userip_connections = 20 } config on destination imap.netsend.nl: # 2.2.15: /etc/dovecot/dovecot.conf # OS: OpenBSD 5.7 amd64 auth_debug = yes auth_mechanisms = plain login auth_verbose = yes first_valid_gid = 30000 first_valid_uid = 30000 last_valid_gid = 30100 last_valid_uid = 30100 mail_debug = yes mail_home = /srv/vmail/%d/%n mail_location = sdbox:~/dbox passdb { args = /passwd driver = passwd-file } passdb { args = /passwd_smtponly driver = passwd-file } protocols = imap lmtp service auth-worker { chroot = /etc/mail unix_listener /etc/mail/auth-worker { mode = 0600 user = $default_internal_user } user = $default_internal_user } service auth { chroot = /etc/mail unix_listener /var/spool/postfix/private/dovecot-auth { group = _postfix mode = 0600 user = _postfix } } service imap-login { inet_listener imap { port = 0 } process_min_avail = 1 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = _postfix mode = 0600 user = _postfix } } ssl = required ssl_cert = </etc/ssl/private/2015/chain.crt ssl_cipher_list = ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-CHACHA20-POLY1305:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA384:DHE-RSA-AES256-SHA256:ECDHE-RSA-AES256-SHA:DHE-RSA-AES256-SHA; ssl_dh_parameters_length = 2048 ssl_key = </etc/ssl/private/the.key ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 userdb { args = /passwd default_fields = uid=30000 gid=30000 home=/srv/vmail/%d/%n/./ driver = passwd-file } valid_chroot_dirs = /srv/vmail verbose_ssl = yes protocol imap { mail_max_userip_connections = 20 }

1 0

imap-login: Authenticate PLAIN failed: Unsupported authentication mechanism - with Evolution
by lejeczek 25 Jun '15

25 Jun '15

I wonder if you know if Evolution works with dovecot TLS?

2 2