- dovecot - dovecot.org

director + lmtp + ldap user
by Lazy 25 Dec '14

25 Dec '14

Hi, recently I have migrated our prevoius dovecot-lda to 2.2 with director + lmtp. And we are having some issues. When lmtp delivers to ldap uid names everything works except sieve vacation (login is not found in headers so reply is not sent). When using full email addresses in rcpt to vacation works but usernames are inconsistent (one user can login using his email address, or aliases, or uid). To fix that in ldap settings a have added uid=user which should be setting the username to approperate values. Most of the times it works but some deliveries are using email addresses not ldap uid's which seems to break dict quota's. It's must be related to auth cache (flushing the cache fixes the issue temporarly for given account). I think that the cache can be "polluted" by some other dovecot service. Does anyone have an idea where this can be comming from ? doveadm auth lookup -f user mon(a)test.com returns expected ldap uid no email address Thanks in advance for any help. Michal Grzedzicki from dovecot-ldap.conf.ext from backends user_attrs = uid=user, mailMessageStore=home, mailQuotaSize=quota_rule=*:bytes=%$ user_filter = (&(&(!(accountStatus=deleted))(objectClass=qMailUser))(|(mail=%u)(uid=%u)(mailAlternateAddress=%u))) pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=qMailUser)(|(mail=%u)(uid=%u)(mailAlternateAddress=%u))) iterate_attrs = uid=user iterate_filter = (&(&(objectClass=qmailUser)(!(accountStatus=deleted)))) director is doing the authorization and passing it to the backend using a master user protocol lmtp { passdb { args = proxy=y nopassword=y port=24 } } backend doveconf -n # 2.2.15: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.7 auth_cache_negative_ttl = 5 mins auth_cache_size = 10 M auth_cache_ttl = 5 mins auth_debug = yes auth_master_user_separator = * auth_mechanisms = plain login auth_username_format = %u auth_verbose = yes base_dir = /var/run/dovecot/ deliver_log_format = msgid=%m f:%f s:%s %$ disable_plaintext_auth = no first_valid_gid = 300 first_valid_uid = 300 import_environment = TZ last_valid_gid = 300 last_valid_uid = 300 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lda_original_recipient_header = Delivered-To login_greeting = Imap ready. mail_debug = yes mail_gid = 300 mail_location = maildir:~/Maildir:INDEX=/var/dovecot_indexes%h mail_plugins = quota expire notify mail_log mail_uid = 300 maildir_very_dirty_syncs = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave duplicate namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox SPAM { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { expire = SPAM expire_dict = redis:host=127.0.0.1:prefix=expire/ mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid from subject size quota = dict:User quota::redis:host=127.0.0.1:prefix=user/ quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve_global_dir = /etc/sieve_global sieve_max_redirects = 20 } postmaster_address = postmaster(a)iq.pl protocols = imap pop3 lmtp sieve recipient_delimiter = service auth { unix_listener auth-userdb { mode = 0777 } } service dict { unix_listener dict { group = vmail user = vmail } } service doveadm { inet_listener { port = 2424 } } service imap-login { process_min_avail = 8 service_count = 0 } service imap { process_limit = 14000 } service lmtp { inet_listener lmtp { address = dovecot1 port = 24 } process_min_avail = 5 user = vmail } service managesieve-login { inet_listener sieve { address = 0.0.0.0 port = 4090 } protocol = sieve } service pop3-login { process_min_avail = 8 service_count = 0 } service pop3 { process_limit = 10000 } service quota-warning { executable = script /usr/local/bin/quota_warning.sh unix_listener quota-warning { user = vmail } user = vmail } ssl = no syslog_facility = local2 userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } verbose_proctitle = yes protocol lmtp { auth_username_format = %u info_log_path = /var/log/dovecot-lmtp mail_plugins = quota expire notify mail_log sieve syslog_facility = local3 } protocol lda { mail_plugins = quota expire notify mail_log sieve syslog_facility = local3 } protocol imap { mail_max_userip_connections = 30 mail_plugins = quota expire notify mail_log imap_quota }

1 0

Maildir permissions on creation?
by Von Random 24 Dec '14

24 Dec '14

Hello. In my configuration dovecot reads home from mysql and uses no variables within it. It uses Maildir++ storage with virtual users. I also happen to use LMTP. I want to use a backup solution that does not involve running itself as root. Neither do I want to run it as dovecot's mail user. And there lies the problem: dovecot creates maildirs with 0700 and files within them inherit that set of permissions. And there seems to be no sane way to control it. I think I've figured out what to patch in order to change that default, but if possible, I'd like to avoid doing that. tl;dr: is it possible to change the default set of permissions for new maildirs created by dovecot?

1 0

Configuring LMTP/IMAP proxy
by Le Moing, Guenhaël 23 Dec '14

23 Dec '14

Hi, First, my version: [root@centos1 conf.d]# dovecot --version 2.2.15 [root@centos1 conf.d]# I have already configured dovecot that way (on one single VM, so everythinh is stored on the same machine) - A post fix server sending out to LMTP - LMTP is the dovecot LMTP server, configured with "lmtp-proxy= no", - LMTP checks the users receiving messages by using Linux passwd file "userdb" section in auth-passwdfile.conf.ext, - IMAP LOGINS are authenticated using DIGEST-MD5 also configured in auth-passwdfile.conf.ext : - # Authentication for passwd-file users. Included from 10-auth.conf. # # passwd-like file with specified location. # <doc/wiki/AuthDatabase.PasswdFile.txt> passdb { driver = passwd-file args = scheme=DIGEST-MD5 username_format=%n /etc/dovecot/users.DIGEST-MD5 #args = scheme=CRAM-MD5 username_format=%n /etc/dovecot/users.CRAM-MD5 } userdb { driver = passwd # Default fields that can be overridden by passwd-file #default_fields = quota_rule=*:storage=1G default_fields = uid=root gid=root home=/home/%n # Override fields from passwd-file #override_fields = home=/home/virtual/%u } This works fine, I can send messages through SMTP, and read them using IMAP access. But now, I woukd like to have amore structured architecture with : - A LMTP server configured as PROXY : has to identify the user, and proxy the request to the backen LMTP server (where its mailbox will stand) - On backend, I also have to start another LMTP serevr, but not configured in proxy mode of course, - Same for IMAP : IMAP proxy first checking LOGIN credentials, and then forwarding to IMAP server running on backend. As a first step, I would like to continue using my files to authenticate uses (so passwd file , and users.DIGEST-MD5), but final goal will be using a MySQL DB. So my main question are : 1) I just made a test and changed "lmtp_proxy" to "yes" in my 20_lmtp.cong file, but, strangely, this did not cah nge anything ! The LMTP process still receives mails and stores them on the local host , 2) Are there any documentation describing this process in details ? I only found some pieces on wiki pages, but not enough unfortunately ... 3) Are there some configuratiion files ready to use for my configuration. Thanks in advance. Cordialement. Guenhaël. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

2 1

zlib, mdbox and spam filtering scripts
by Philon 22 Dec '14

22 Dec '14

Hi all, I am quite happily running a dovecot setup with maildirs. This was once running courier but since the migration I have never ever looked back. Now, with growing userbase I’m looking into using zlib compression and mdbox instead of maildir. This seems to go quite well using dsync on a testbed server. So let’s go production! Before final decision I came across this: - I’m using a spam learning address, where users forward their mails to train SpamAssassin. - there is a cron script on the server, mime-stripping the attachments and feeding them into SA - works quite well even for the still numerous POP users So well… compression ok, I could add a gunzip into the script and go from there. But mdbox seems only accessible via dovecot. I don’t think that accessing via IMAP makes sense for a local script. So I would block myself out when using mdbox. How are your spam/ham training routines? How do you feed SA? thank you! Philon

3 4

error: iostream-ssl.h: No such file or directory
by Tobi 22 Dec '14

22 Dec '14

Hi list I'm trying to build dovecot 2.2.15 from source on a debian wheezy (64bit). As I wanted to get starttls support for dovecot's lmtp I got the patched files from here: http://hg.dovecot.org/dovecot-2.2/rev/297192cfbd37 My ./configure ./configure --prefix=/usr/local/dovecot-test --with-solr --with-mysql --with-sql --without-shadow --without-pam configure seems to run fine but the following make ends up in client.c:17:26: fatal error: iostream-ssl.h: No such file or directory compilation terminated. make[3]: *** [client.o] Error 1 make[3]: Leaving directory `/usr/local/src/dovecot-2.2.15/src/lmtp' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/dovecot-2.2.15/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/dovecot-2.2.15' make: *** [all] Error 2 Any ideas what I'm missing? libssl-dev is installed via apt Thanks for any idea Cheers tobi

3 2

lmtp usernames with -
by Lazy 19 Dec '14

19 Dec '14

Hello I have a problem with lmtp delivery to usernames with '-' char. Everythong after - is ignored. when delivering to test-test2 the error message is. User doesn't exist: test I suspect this is a sideefect of auth_username_format = %Lu I have tried %Ln without success. Imap works without problems for those users. How can I disable this mapping for lmtp and use verbatim username for lookup. Thanks in advance for any answers.

2 3

Migrate maildir between servers dovecot
by Davide Gmail 18 Dec '14

18 Dec '14

Hi to all, i have two servers with dovecot 2.2.15 one is actualy on production (server A) and another that i put on production soon (server B) My goal is migrate maildir from server A and server B. How can i achieve that? I read http://wiki2.dovecot.org/Migration/Dsync but i haven't understand well where to put such configuration (in which server). Thanks in advance for any help.

3 2

best file system ?
by absolutely_free＠libero.it 18 Dec '14

18 Dec '14

Hi, I'm going to set up a new storage for our email users (about 10k). It's a network attached storage (Coraid). In your opinion, what is the best file system for mail server (pop3/imap/webmail) purpose? Thank you

12 14

Migrate dovecot maildirbetween servers
by Davide 18 Dec '14

18 Dec '14

Hi to all, i have two servers with dovecot 2.2.15 one is actualy on production (server A) and another that i put on production soon (server B) My goal is migrate maildir from server A and server B. How can i achieve that? I read http://wiki2.dovecot.org/Migration/Dsync but i haven't understand well where to put such configuration (in which server). Thanks in advance for any help. -- *Davide Marchi Teorema Ferrara Srl** **Via Spronello, 7 - Ferrara - 44121 05327831610532783368 davide.marchi(a)mail.cgilfe.it davide.marchi73 Web: http://www.cgilfe.it* * CONFIDENZIALITA'* *Ai sensi del D.Lgs. 196/2003 si precisa che le informazioni contenute in questo messaggio sono riservate ed a uso esclusivo del destinatario/dei destinatari. Qualora il messaggio in parola Le fosse pervenuto per errore, La invitiamo ad eliminarlo senza copiarlo e a non inoltrarlo a terzi, dandocene gentilmente comunicazione.* *Per favore, pensa all'ambiente. Stampa questa email solo se necessario.*

2 1

LDAP: Connection appears to be hanging, reconnecting
by Matthias Egger 17 Dec '14

17 Dec '14

Hello List I have a strange problem here which i try to analyse, but i'm stuck. Maybe someone has a hint? What happened: A few weeks ago one of the LDAPS Servers which is not maintained by us has crashed. From that moment on, users could still login to check their emails, but they were not able to send any email through postfix (which uses smtpd_sasl_type = dovecot) What i do not understand, is why did dovecot not switch to the second configured LDAPS Server? It looks like it retried for ever to reconnect to the crashed LDAP Server. From the moment of the crash we see a lot of Errors like these in our logfiles: Nov 30 16:51:53 servername dovecot: [ID 583609 mail.error] auth: Error: ldap(userone,USERS_IP1,<WKiTeBUJQQBUSAnE>): Connection appears to be hanging, reconnecting AND Nov 30 16:51:59 servername dovecot: [ID 583609 mail.error] auth: Error: plain(usertwo,USERS_IP2,<QgJvcBUJqABTTWrJ>): Request 1982.83548 timed out after 151 secs, state=1 The used dovecot version is 2.2.13, runs on a solaris 10 system and the configuration for passdb and userdb are: passdb { args = /etc/dovecot-ldap.conf default_fields = deny = no driver = ldap master = no name = override_fields = pass = no result_failure = continue result_internalfail = continue result_success = return-ok skip = never } userdb { args = /etc/dovecot-ldap.conf default_fields = driver = ldap name = override_fields = result_failure = continue result_internalfail = continue result_success = return-ok skip = never } And the dovecot-ldap.conf contains (obfuscated): uris = ldaps://server2.tld ldaps://server1.tld ldaps://server4.tld ldaps://server3.tld dn = ... dnpass = ... ldap_version = 3 auth_bind = yes base = ... scope = onelevel user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid user_filter = ... pass_attrs = uid=user pass_filter = ... The strange thing is, that with the very same binaries and configuration (okay, some minimal modifications have been made to bind to the correct interfaces...) a test on our testsystem works as it should. When we shutdown slapd, dovecot recognizes it an connects to the alternate LDAPS. When we shutdown slapd and start a netcat (just to let something listening without responding)... you guess it. Dovecot does recognize it and switches over to the alternate testsystem. So on our testsystem, everything worked as it should. But the productive system did not. And since the LDAPS are not maintained by us it is somewhat hard to try to reproduce something. At least i got the logfiles from server2.tld and server1.tld. But they only show what i still knew. Our server connected to server2.tld until the crash happened. But server1.tld never got any connection. Has someone an idea what i could try to find out why dovecot did not switch to server1.tld? Best regards Matthias Egger -- Matthias Egger ETH Zurich Department of Information Technology maegger(a)ee.ethz.ch and Electrical Engineering IT Support Group (ISG.EE), ETL/F/24.1 Phone +41 (0)44 632 03 90 Physikstrasse 3, CH-8092 Zurich Fax +41 (0)44 632 11 95

2 2