- dovecot - dovecot.org

Re: config best practice
by Joseph Tam 19 Jun '14

19 Jun '14

From: Egbert <egbert(a)vandenbussche.nl> > The dovecot config is still pretty much in 1.x style; one flat file > called dovecot.conf. I can easily switch to a dovecot.conf with the > "!include" lines and rename my flat config file to local.conf. I've > tested that and it works fine. I could also try to move all lines in > local.conf to the different XX-.conf files in the conf.d subdir. What is > wise and best practice? Should one edit the files in conf.d? Or will the > files in conf.d be overwritten on an update of dovecot? Then I'll better > stick to the way of working with the dovecot.conf with the !includes and > local.conf and assume that all files in conf.d are default settings. I think you will hear from proponents of both styles. I would say use whatever works best for you. I personally use one dovecot.conf without any includes because I like having all my configs in one place. Less editing mutiple files, and less forgetting some configuration squirreled away in some conf.d file. Joseph Tam <jtam.home(a)gmail.com>

1 0

LDAP and MySQL in the same configuration
by Nicolas Cauchie 18 Jun '14

18 Jun '14

Hello there, Simple question, I'm losting hope when I search on Google : Is there a way to authenticate users from a LDAP database and to fetch their quotas stored in a MySQL database, both in the same configuration ? Thanks Nicolas --

1 0

Problem syncing mailboxes using doveadm sync
by Przemysław Orzechowski 18 Jun '14

18 Jun '14

Hi command im using command bellow on destination server rtying to make keep it in sync after initialy doing doveadm backup -R doveadm -Dv -o imapc_host=src.srv -o imapc_user=test(a)domain.tld -opop3c_user=test(a)domain.tld -o imapc_password='pass' -o pop3c_password='pass' -o mail_fsync=never -o mail_prefetch_count=20 sync -f -1 -R -u test(a)domain.tld imapc: Im using dovecot on both source and destination server (source is dovecot 1.0.10 destination is 2.2.9) Destination box is Ubuntu 14.04 LTS with dovecot installed using apt. When i create new mail message on the serrver where i run this command its not propagated to the remote (old) server Is this command wrong ?

3 4

RFE: dnsbl-support for dovecot
by Reindl Harald 17 Jun '14

17 Jun '14

after having my own dnsbl feeded by a honeypot and even mod_security supports it for webservers i think dovecot sould support the same to prevent dictionary attacks from known bad hosts, in our case that blacklist is 100% trustable and blocks before SMTP-Auth while normal RBL's are after SASL i admit that i am not a C/C++-programmer, but i think doing the DNS request and in case it has a result block any login attemt should be not too complex setup a own honeypot and feed rbldnsd with the sources is quite easy and in case of a own, trustable RBL where no foreigners report somebody by mistake it's relieable and scales well over many machines and services as long services supporting it mod_security: http://blog.inliniac.net/2007/02/23/blocking-comment-spam-using-modsecurity…

4 9

[Dovecot] Replication with virtual users and static userdb possible ?
by deano-dovecot＠areyes.com 17 Jun '14

17 Jun '14

Is it possible to get replication working in a virtual user setup that uses a static userdb ? My environment is fairly simple and typical - there's a single system user (vmail) that owns all the home dirs (/var/mail/domain.com/user). The virtual users (userid@domain.com:secretpassword) are kept in a single file (/var/mail/domain.com/PASSWD) that's unique per domain, and referenced as a static userdb : passdb { driver = passwd-file args = scheme=plain username_format=%u /var/mail/%d/PASSWD } userdb { driver = static args = uid=vmail gid=vmail home=/var/mail/%d/%n } I know the wiki http://wiki2.dovecot.org/Replication states that user listing must be enabled, but that's not available for a static userdb. The wiki http://wiki2.dovecot.org/UserDatabase/Static also says that it shouldn't be a problem because it will use do a passdb lookup instead (except for PAM which isn't used here). Unfortunately, it's not working. I've testing with ssh : dsync_remote_cmd = ssh -l vmail %{host} doveadm dsync-server -u%u -l%{lock_timeout} -n%{namespace} mail_replica = remote:vmail@server2.domain.com as well as with straight tcp (SSL for later) mail_replica = tcp:server2.domain.com:999 /var/log/mail.err shows the problems ... Jun 3 11:30:53 server1 dovecot: auth: Error: Trying to iterate users, but userdbs don't support it Jun 3 11:30:53 server1 dovecot: replicator: Error: User listing returned failure Jun 3 11:30:53 server1 dovecot: replicator: Error: listing users failed, can't replicate existing data Anyone else have it working ? I'm sure it's something simple that I've just overlooked. Thanks - D.

2 4

replicator, ldap virtual users and static userdb
by Alan McGinlay 17 Jun '14

17 Jun '14

Hi! I am trying to use the static userdb with virtual users stored in ldap and the replicator plugin. What is the best way to implement this? I was not able to find documentation about it. Thanks!

1 0

[Dovecot] Problem in Search IMAP with spaces in Subject
by Giovanni Mancuso 17 Jun '14

17 Jun '14

Hi, I deliver a test email (with 4 spaces in subject) into a maildir: Return-Path: <user(a)example.com> Delivered-To: <user(a)example.com> Received: from suse11 ([10.0.8.7]) by suse11 (Dovecot) with LMTP id Pf6zDTCaiFOUXwAA4Q5jHg for <user(a)example.com>; Fri, 30 May 2014 16:48:16 +0200 From: <user(a)example.com> To: <user(a)example.com> Message-ID: <9704BC6A-28D9-CBF2-A1D6-DD54F6AA9D9D(a)newsvilpec.babel.it> Subject: Test 4 Spaces Test But, if i search this email with 4 spaces in subject i don't find anthing: telnet 0 143 Trying 0.0.0.0... Connected to 0. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN] Dovecot ready. ab login user(a)example.com password ab OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE BINARY MOVE QUOTA ACL RIGHTS=texk] Logged in ab select inbox * FLAGS (\Answered \Flagged \Deleted \Seen \Draft PEC_INBOX) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft PEC_INBOX \*)] Flags permitted. * 1 EXISTS * 1 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1401785069] UIDs valid * OK [UIDNEXT 2] Predicted next UID ab OK [READ-WRITE] Select completed (0.002 secs). a1 SEARCH CHARSET UTF-8 SUBJECT "Test 4 Spaces" * SEARCH a1 OK Search completed (0.001 secs). a1 SEARCH CHARSET UTF-8 SUBJECT "Test 4 Spaces" * SEARCH 1 a1 OK Search completed (0.000 secs). ab logout * BYE Logging out ab OK Logout completed. Connection closed by foreign host. If i run the search with one space i find a mail. I use dovecot v2.2.12 on Linux suse11 x86_64 Thanks

1 1

Accessing a user mailbox from another user
by Angel L. Mateo 17 Jun '14

17 Jun '14

Hello, I'm looking for something maybe similar to master password but for final users and I don't know if there is already a way I could do it with dovecot. I have accounts that are used by a set of users who know their password. But I now want to remove this shared password and the users has to access to this shared account with their own password. Using shared folders is not an option (at least, not the first option) because of the behaviour our users are familiar with, such as: * They have and manage different sieve filters for the account * They have thier own Sent, Drafts, SPAM... for this shared account and their email client recognizes them as it (because they have its own account). What I'm looking for is something similar to master password, but for a user identifying as another regular user, not the "master" one. Do you know if there already is a way to configure a similar behaviour? I'm planning to configure an user and authentication backend (maybe pam) that gets users as <realuser>$<finaluser> and the realuser password, checks if <realuser> should access to <finaluser> and then returns <finaluser> mail location to dovecot. Any idea? -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868887590 Fax: 868888337

1 0

Procmail wiki text -- don't muck with SENDMAIL
by era eriksson 16 Jun '14

16 Jun '14

I tried to edit http://wiki2.dovecot.org/procmail but got stuck on the TextCha. Approaching this list instead seems to be a time-tested secondary approach, and I wasn't completely comfortable making these changes without discussion anyway. So here goes. The SENDMAIL= assignment is not only irrelevant, but actually wrong. The note down in the update section about Ubuntu explains the problem well enough, but it applies to all the sections on the page. My proposed edit was to simply remove SENDMAIL and SENDMAILFLAGS from all the recipes on the page, and then remove the Ubuntu section altogether, because it would no longer add anything useful to the page. If somebody in the Dovecot community with edit access to the wiki wants to implement this change, I would be grateful on behalf of the people who try to use Procmail with Dovecot. -- If this were my real .signature, it would suck less. Well, maybe not.

1 0

connection to director (lmtp) time out
by Patrick Westenberg 16 Jun '14

16 Jun '14

Hi all, I'm running two directors with lmtp proxy as relay transport for my mail exchangers. relay_transport = lmtp:inet:dovecot-directors.example.net dovecot-directors.example.net resolves to 172.17.1.3 and 172.17.1.4 Now, .3 is down and Postfix tries to deliver it to .4 but this connection gets a timeout: (delivery temporarily suspended: connect to 172.17.1.4[172.17.1.4]:24: Connection timed out There is no log entry on the director. Can anyone give me a hint how to solve this or maybe optimize my configuration? Regards Patrick auth_mechanisms = plain login default_process_limit = 150 director_mail_servers = 172.17.1.2 director_servers = 172.17.1.4 172.17.1.3 director_user_expire = 5 mins lmtp_proxy = yes log_path = /var/log/dovecot.log 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 protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { user = dovecot } } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { address = 172.17.1.4 port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director } service lmtp { inet_listener lmtp { address = 172.17.1.4 port = 24 } } service managesieve-login { executable = managesieve-login director inet_listener sieve { port = 4190 } } service pop3-login { executable = pop3-login director } ssl_cert = </etc/ssl/certs/wildcard.example.de.crt ssl_key = </etc/ssl/private/wildcard.example.de.key protocol !smtp { passdb { args = proxy=y nopassword=y starttls=any-cert driver = static } } protocol smtp { passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } } protocol lmtp { auth_socket_path = director-userdb } local 83.149.... { protocol imap { ssl_cert = </etc/ssl/certs/wildcard.example.de.pem ssl_key = </etc/ssl/private/wildcard.example.de.key } } local 83.149... { protocol pop3 { ssl_cert = </etc/ssl/certs/wildcard.example.de.pem ssl_key = </etc/ssl/private/wildcard.example.de.key } } local [2001:1af8:...] { protocol imap { ssl_cert = </etc/ssl/certs/wildcard.example.de.pem ssl_key = </etc/ssl/private/wildcard.example.de.key } } local [2001:1af8:...] { protocol pop3 { ssl_cert = </etc/ssl/certs/wildcard.example.de.pem ssl_key = </etc/ssl/private/wildcard.example.de.key } }

1 0