- dovecot - dovecot.org

Timeout Leak
by Luciano Mannucci 16 Mar '17

16 Mar '17

Hello all, I've got 3 occurences of this message in my log file: auth: Warning: Timeout leak: 0x805e480 (auth-request-handler.c:550) Can I ignore it, or is it a syhmptom of something wrong? I'm running dovecot 2.2.28 (bed8434). I'll post my doveconf -n if it is worth investigating further... Cheers, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster(a)sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/

2 2

'doveadm who' behind nginx mail proxy
by Edgaras Lukoševičius 16 Mar '17

16 Mar '17

Hello, we have configured nginx to work as mail proxy for backend dovecot servers. Dovecot servers behind nginx proxy are showing internal nginx ip address for every client when running 'doveadm who' instead of showing real client IP addresses. Is is possible to configure this setup to show real client IP addresses when running 'doveadm who' on internal dovecot servers or to configure nginx to show which user-ip pairs are proxied to which servers?

1 0

LDAP locking problems - home related
by Ganael Laplanche 16 Mar '17

16 Mar '17

Hi list, # dovecot --version 2.2.13 We use Dovecot LDA and I've discovered lots of messages stating that lock files cannot be written: Mar 16 12:02:03 mailhost dovecot: lda(someuser): Error: file_dotlock_open(/home/sg/someuser/.dovecot.lda-dupes) failed: No such file or directory That user's home directory is fetched from LDAP and does not exist locally on our 'mailhost' machine, so those error messages do make sense; I would like to fix that situation. In our current Dovecot configuration, only mail_location is set: mail_location = maildir:/var/mail/%u I would like to ignore the erroneous 'home' attribute fetched from LDAP and specify a common mail_home, i.e. set: mail_home = /var/mail/%u/home but if I understand correctly, that global mail_home configuration directive would still be overridden by the LDAP 'home' attribute fetched from passdb: [...] pass_attrs = supannAliasLogin=user,userPassword=password,\ homeDirectory=userdb_home,uidNumber=userdb_uid,gidNumber=userdb_gid [...] Can I just remove homeDirectory from pass_attrs to skip fetching 'home' from LDAP and then set the global mail_home ? Also, if that works: We would switch from a situation where a home is set (but wrong) to one where it becomes valid. Can there be any side-effect in that case (apart from fixing locking problems) ? Finally, will mail_home (leaf) directory be created if it does not exist yet (parent directory exists) ? Best regards, -- Ganael Laplanche <ganael.laplanche(a)centralesupelec.fr> Unix Systems Engineer @CentraleSupelec Rennes

1 1

Dovecot 2.2.27 proxy - enforcing per client IP connection limits
by Adi Pircalabu 16 Mar '17

16 Mar '17

Hi, Trying to keep abusive/buggy IMAP clients at bay on a number of Dovecot proxy servers, I've reconfigured them to use "mail_max_userip_connections = 50" in the "protocol imap" section, followed by restarting Dovecot. Yet, I'm still seeing 160+ established connections from a single IP address for the same email account. Am I missing anything? # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 2.6.32-642.4.2.el6.x86_64 x86_64 CentOS release 6.8 (Final) auth_cache_negative_ttl = 5 mins auth_cache_size = 16 M auth_cache_ttl = 18 hours default_client_limit = 6120 default_process_limit = 500 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 index ihave duplicate mime foreverypart extracttext imapflags notify mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_extensions = +notify +imapflags } protocols = imap pop3 lmtp sieve service auth { client_limit = 6120 } service imap-login { process_limit = 2048 process_min_avail = 20 service_count = 0 vsz_limit = 256 M } service imap { process_limit = 2048 } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 0 vsz_limit = 128 M } service managesieve { process_limit = 1024 } service pop3 { process_limit = 1024 } [...] protocol imap { imap_capability = IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE mail_max_userip_connections = 50 } -- Adi Pircalabu

3 6

Postfix Ignoring lmtp, delivering straight to maildir
by Doug Barton 16 Mar '17

16 Mar '17

First I'd like to thank all the developers and contributors to dovecot. I've been using it for many years, and deeply appreciate your fine work. :) dovecot --version 2.2.22 (fe789d2) I have a working installation with postfix and dovecot, and I want to add sieve to it, so I am trying to configure postfix to use lmtp instead of 'virtual' for its delivery service. However it is ignoring that request, and for every message I get "status=sent (delivered to maildir)" and it shows up in my Inbox. On my mail host I have 1 normal user, let's say the username is 'myuser'. I have postfix configured to accept mail for several different domains, and each domain has a lot of different mail usernames (I use this for mailing lists and such). I use the virtual_maps feature of postfix, and have a map file that looks like this: abuse(a)dougbarton.us myuser hostmaster(a)dougbarton.us myuser dougb(a)dougbarton.us myuser ... All of this works great, and mail for all the different usernames and domains gets delivered into my one real user's Maildir, and I can see the mail with my IMAP clients. I've configured sieve in dovecot, and I can see the socket for lmtp in /var/spool/postfix/private/. I can also see the managesieve port in netstat, and I can use a sieve client to connect to it and edit scripts, etc. So according to all the tutorials I've read my next step is this in postfix' main.cf: virtual_transport = lmtp:unix:private/dovecot-lmtp which I did, and postfix restarts with no errors. But, it seems to avoid lmtp altogether, and as I mentioned above it delivers straight to my Maildir Inbox every time. I do have a sieve file, and the ~/dovecot.sieve symlink exists. I created a very simple filter: require ["fileinto", "imap4flags"]; if header :contains "Subject" "test" { fileinto "Junk"; } which my sieve client says is correct syntax. Still no joy. :-/ Any thoughts or suggestions are welcome. (And sorry this is so long, but based on my extensive searches it seems my configuration is a bit unique, so I explained it in some length.) Doug

3 5

Backing Up and Restoring mailboxes
by Jerry 15 Mar '17

15 Mar '17

I am going to be wiping clean my system and doing a complete upgrade. I have dovecot installed. I want to back up the mail system, and then be able to restore it. I thought that I could do this. doveadm -Dv backup -u user(a)example.com maildir:~/DoveBU Then I was going to gunzip that directory and put it onto a USB Drive. Now, after updating the system, I thought that I could just unzip the file from the USB drive. My question is, what command do I run to return the files to the same place they were originally. Assuming the structure was: "/var/mail/vmail/", what would I do? Thanks -- Jerry

1 0

FW: Unable to create needed folders
by Ken Zachreson 15 Mar '17

15 Mar '17

Never mind, I am stupid and did not read all available information. Needed to change permissions on /var/mail/* Thank You, Ken Z -----Original Message----- From: Ken Zachreson Sent: Wednesday, March 15, 2017 10:28 AM To: 'dovecot(a)dovecot.org' <dovecot(a)dovecot.org> Subject: Unable to create needed folders Greetings, The log reports that a process cannot create the needed folders. Please review and tell me what I have done wrong. dovecot 2.0.9 # 2.0.9: /etc/dovecot/dovecot.conf doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:85: protocol { ssl_listen } has been replaced by service { inet_listener { address } } # OS: Linux 2.6.32-642.15.1.el6.x86_64 x86_64 CentOS release 6.8 (Final) auth_mechanisms = plain login last_valid_gid = 520 last_valid_uid = 520 mail_location = mbox:~/mail/:INBOX=/var/mail/%u mbox_write_locks = fcntl passdb { args = dovecot driver = pam } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imaps { address = * } } service pop3-login { inet_listener pop3s { address = * } } ssl_ca = /etc/pki/tls/certs/gd_bundle-g2-g1.crt ssl_cert = </etc/pki/tls/certs/c1e209e3ca2e1e5.crt ssl_key = </etc/pki/tls/private/gcrcnet.key userdb { driver = passwd } protocol pop3 { pop3_uidl_format = %08Xv%08Xu } ERROR Message from log Mar 15 10:14:03 MultiTronic6 dovecot: imap-login: Login: user=<wifi.adm>, method=LOGIN, rip=xx.xx.xx.xx, lip=yy.yy.yy.yy, mpid=5973, TLS Mar 15 10:14:03 MultiTronic6 dovecot: imap(wifi.adm): Error: chown(/home/wifi.adm/mail/.imap/INBOX, -1, 12(mail)) failed: Operation not permitted (egid=504(wifi.adm), group based on /var/mail/wifi.adm) Mar 15 10:14:03 MultiTronic6 dovecot: imap(wifi.adm): Error: mkdir(/home/wifi.adm/mail/.imap/INBOX) failed: Operation not permitted Mar 15 10:14:03 MultiTronic6 dovecot: imap(wifi.adm): Connection closed bytes=39/423 Thank You, Ken Zachreson IT Manager, Grand Canyon Resort Corp 928-769-2629 928-769-2638 Help Desk

1 0

Unable to create needed folders
by Ken Zachreson 15 Mar '17

15 Mar '17

Greetings, The log reports that a process cannot create the needed folders. Please review and tell me what I have done wrong. dovecot 2.0.9 # 2.0.9: /etc/dovecot/dovecot.conf doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:85: protocol { ssl_listen } has been replaced by service { inet_listener { address } } # OS: Linux 2.6.32-642.15.1.el6.x86_64 x86_64 CentOS release 6.8 (Final) auth_mechanisms = plain login last_valid_gid = 520 last_valid_uid = 520 mail_location = mbox:~/mail/:INBOX=/var/mail/%u mbox_write_locks = fcntl passdb { args = dovecot driver = pam } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imaps { address = * } } service pop3-login { inet_listener pop3s { address = * } } ssl_ca = /etc/pki/tls/certs/gd_bundle-g2-g1.crt ssl_cert = </etc/pki/tls/certs/c1e209e3ca2e1e5.crt ssl_key = </etc/pki/tls/private/gcrcnet.key userdb { driver = passwd } protocol pop3 { pop3_uidl_format = %08Xv%08Xu } ERROR Message from log Mar 15 10:14:03 MultiTronic6 dovecot: imap-login: Login: user=<wifi.adm>, method=LOGIN, rip=xx.xx.xx.xx, lip=yy.yy.yy.yy, mpid=5973, TLS Mar 15 10:14:03 MultiTronic6 dovecot: imap(wifi.adm): Error: chown(/home/wifi.adm/mail/.imap/INBOX, -1, 12(mail)) failed: Operation not permitted (egid=504(wifi.adm), group based on /var/mail/wifi.adm) Mar 15 10:14:03 MultiTronic6 dovecot: imap(wifi.adm): Error: mkdir(/home/wifi.adm/mail/.imap/INBOX) failed: Operation not permitted Mar 15 10:14:03 MultiTronic6 dovecot: imap(wifi.adm): Connection closed bytes=39/423 Thank You, Ken Zachreson IT Manager, Grand Canyon Resort Corp 928-769-2629 928-769-2638 Help Desk

1 0

autocreate ONLY for new Users
by plataleas 15 Mar '17

15 Mar '17

Hi All We are currently migrating accounts to Dovecot. The existing accounts do have special folders with different names. (i.e. sent, sent-mail) The autocreate-function of "special folders" is useful. However we need this feature ONLY for new users. The existing accounts have a mapping for their own "special folders". There are discussions about this topic on the mailing list: /http://www.dovecot.org/list/dovecot/2014-August/097313.html https://dovecot.org/list/dovecot/2016-May/104296.html/ Did someone manage to implement this ? Are there workarounds? Thanks and regards plataleas

3 6

Custom cache_key for passdb-sql
by Tom Sommer 15 Mar '17

15 Mar '17

The cache_key for the SQL-passdb should be created automatically, but for some reason the service (%s) is not part of the key, and I need it to be I've tried to set a manual cache_key, but that fails: Mar 15 11:54:02 auth: Fatal: sql /etc/dovecot/dovecot-sql.conf cache_key=%s%u%{real_ip}: Can't open configuration file /etc/dovecot/dovecot-sql.conf cache_key=%s%u%{real_ip}: No such file or directory passdb { args = /etc/dovecot/dovecot-sql.conf cache_key=%s%u%{real_ip} driver = sql } Is this not possible? -- Tom

1 0