- dovecot - dovecot.org

Using PAM and passwdfile together
by Jim Garrison 02 Jul '15

02 Jul '15

Dovecot 2.0.9 on Centos 6.6 I have some local users and some Postfix virtual mailboxes. The config currently has: > # 2.0.9: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.32-504.12.2.el6.x86_64 x86_64 CentOS release 6.6 (Final) > first_valid_uid = 190 > log_path = /var/log/dovecot.log > mail_access_groups = mail > mail_location = mbox:~/mail:INBOX=/var/mail/%u > mbox_write_locks = fcntl > passdb { > driver = pam > } > passdb { > args = scheme=MD5 username_format=%u /etc/dovecot/auth/%d.passwd > driver = passwd-file > } > protocols = imap pop3 > ssl_ca = </etc/pki/tls/certs/ca-bundle.crt > ssl_cert = </etc/pki/dovecot/certs/mailcert.pem > ssl_key = </etc/pki/dovecot/private/mailkey.pem > ssl_parameters_regenerate = 48 > userdb { > driver = passwd > } > userdb { > args = uid=199 gid=199 home=/var/mail/vhosts/%d/%n mail=mbox:/var/mail/vhosts/%d/%n:INBOX=/var/mail/vhosts/%d/%n/mail > driver = static > } Each time a virtual mailbox user logs in, PAM writes a set of Authentication Failure messages to /var/log/secure when it attempts to find the virtual user, which it then successfully authenticates in the passwd-file. Is there a way to prevent PAM from loggin this spurious error and having dovecot log an authentication failure only if BOTH methods fail? -- Jim Garrison (jhg(a)acm.org) PGP Keys at http://www.jhmg.net RSA 0x04B73B7F DH 0x70738D88

2 1

dovecot-lmtp
by Steven Hopps 02 Jul '15

02 Jul '15

Hi, I'm trying to use dovecot-lmtp so that I can filter messages with sieve, however it doesn't appear to be working. I followed the instructions on wiki2.dovecot.org. I'm running Debian Wheezy. I've got runit configured to execute postfix and dovecot, which may be the source of the problem (runit executes /usr/sbin/dovecot -F). I've got mail_debug turned on and there is nothing in the mail log about lmtp. Any help would be appreciated. -- Steven Hopps || shopps(a)pridetechdesign.com 424-888-0443 || http://www.pridetechdesign.com = Ask about my Security Tune-Up & 24/7 Server Monitoring! =

2 4

Dovecot deleting files and directories
by Jan Ekholm 01 Jul '15

01 Jul '15

Hi, I’m a new Dovecot user and using version 2.2.18 on an OpenSuse system. In general it all works quite nicely and clients can connect to Dovecot and manage mails normally. The layout used is maildir. The users are all virtual, i.e. they do not exist on the Linux system. They all log in without any authentication due to a very specialized and internal setup. However, sometimes Dovecot simply deletes mails from the maildir structure. It also seems to delete entire users too. This is not a simple case of clients deleting mails, but the entire folder for the user seems to sometimes get nuked. I’ve also seen that only the mails and Dovecot’s admin files (indexes etc) are deleted. The log file is not really too informative, mostly lines of this form: Jul 01 14:00:36 imap(firstname.lastname(a)domain.x): Info: Disconnected: IMAP session state is inconsistent, please relogin. in=781 out=2630 Jul 01 14:00:36 imap(operators-east(a)east.domain.x): Debug: Namespace : /opt/mail/operators-east doesn't exist yet, using default permissions Jul 01 14:00:36 imap(operators-east(a)east.domain.x): Debug: Namespace : /opt/mail/operators-east doesn't exist yet, using default permissions Jul 01 14:00:36 imap(operators-east(a)east.domain.x): Debug: Namespace : Using permissions from /opt/mail/operators-east: mode=0700 gid=default Jul 01 14:00:36 imap(firstname.lastname(a)domain.x): Debug: Namespace : /opt/mail/firstname.lastname doesn't exist yet, using default permissions Jul 01 14:00:36 imap(firstname.lastname(a)domain.x): Debug: Namespace : /opt/mail/firstname.lastname doesn't exist yet, using default permissions Jul 01 14:00:36 imap(firstname.lastname(a)domain.x): Debug: Namespace : Using permissions from /opt/mail/firstname.lastname: mode=0700 gid=default Jul 01 14:01:03 imap-login: Info: Login: user=<firstname.lastname(a)domain.x>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=9326, secured, session=<2+YiPc4ZGwB/AAAB> Jul 01 14:01:03 imap(firstname.lastname(a)domain.x): Debug: Effective uid=1001, gid=100, home=/opt/mail/firstname.lastname Jul 01 14:01:03 imap(firstname.lastname(a)domain.x): Debug: maildir++: root=/opt/mail/firstname.lastname, index=, indexpvt=, control=, inbox=/opt/mail/firstname.lastname, alt= Jul 01 14:01:07 imap-login: Info: Login: user=<operators-east(a)east.domain.x>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=9333, secured, session=<11NpPc4ZHAB/AAAB> Jul 01 14:01:07 imap(operators-east(a)east.domain.x): Debug: Effective uid=1001, gid=100, home=/opt/mail/operators-east Jul 01 14:01:07 imap(operators-east(a)east.domain.x): Debug: maildir++: root=/opt/mail/operators-east, index=, indexpvt=, control=, inbox=/opt/mail/operators-east, alt= I’ve changed the name and domain. Not sure if the namespace complaints have anything to do with the directories on disk, but normally they are there when the logging comes. Below is the used config file. I can’t see anything that would trigger deletions and there is no logging or similar about it. To me it’s quite serious that an IMAP server randomly deletes mails and its own files. ########################################################################################### # support only IMAP, no pop3 protocols = imap # listen only on IPv4 (the default is: "* ::") listen = * # where logging gets sent log_path = /var/log/dovecot.log # disable SSL ssl = no disable_plaintext_auth = no # we're using maildir without any extra folders in the user's home directory (set in userdb) mail_location = maildir:~ # user ids default_login_user = dovenull default_internal_user = dovecot # auth config auth_verbose = yes auth_mechanisms = plain # password scheme. Uses an external Python application to verify the password. It gets # sent the username and password and can perform authentication. The current one # simply accepts anything. passdb { driver = checkpassword args = /opt/dovecot-2.2.18/bin/checkpassword.py } # user database userdb { driver = static args = uid=navie gid=users home=/opt/mail/maildir/%n } ########################################################################################### Anything obviously wrong? I’ve seen that mail_location and mail_home should not be the same, but using mail_location = maildir:~/mail gives the exact same behavior. Best regards, Jan Ekholm

2 1

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