- dovecot - dovecot.org

limits in high-security mode with ssl
by sergio 27 Sep '19

27 Sep '19

Hello. I'm using dovecot in high-security mode: service_count = 1 for imap-login service starttls is requires, so the maximum number of active connections is process_limit (which is set to 1024) for the same imap-login service. But with this setup I got: doveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (1324) doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (1227) 1. Where did 1324 and 1227 come from? 2. How configuration should be updated so these warnings disappear? -- sergio.

1 0

doveadm / vsize
by Paul Macdonald 27 Sep '19

27 Sep '19

Hi, i want to keep track of user mailbox size, I'm using doveadm mailbox status -u <user> vsize INBOX for a given mailbox this is under reporting ( by a lot) is this recursive? what shoud i be using to get an accurate disk usage metric? thanks Paul. -- ------------------------- Paul Macdonald IFDNRG Ltd Web and video hosting ------------------------- t: 0131 5548070 m: 07970339546 e: paul(a)ifdnrg.com w: http://www.ifdnrg.com ------------------------- IFDNRG 40 Maritime Street Edinburgh EH6 6SA ---------------------------------------------------- Virtual Servers from £50.00pm High specification Dedicated Servers from £150.00pm ----------------------------------------------------

3 4

Re: Website Down? Not down.
by dundir＠gmail.com 27 Sep '19

27 Sep '19

Its not down, its most likely your providers DNS resolution. www.dovecot.org resolves to: ipv4 : 94.237.85.39 ipv6: 2a04:3542:1000:910:acc1:5bff:fe5e:3b83 Best Regards, D.

3 2

Website down?
by ＠lbutlr 27 Sep '19

27 Sep '19

I am not able to reach the dovecot site on any one of three connections (home, office, mobile). Trying to look up DNS shows no records. -- But just because you've seen me on your TV Doesn't mean I'm any more enlightened than you

1 0

File manager or browser for IMAP?
by Steve Litt 26 Sep '19

26 Sep '19

Hi all, I could really use a file manager or browser to browse my Dovecot IMAP. Ideally it would have hotkeys to move, copy, delete and send. The send part needn't be coded: Just a call to a shellscript which can handle the send the way it's locally the most convenient. Anyone know of such a file manager or browser for IMAP? SteveT Steve Litt Author: The Key to Everyday Excellence http://www.troubleshooters.com/key Twitter: http://www.twitter.com/stevelitt

11 13

Typo in wiki
by Mika Pflüger 26 Sep '19

26 Sep '19

Hi, on https://wiki2.dovecot.org/Plugins/LastLogin the link to the new documentation page is wrong and leads to a 404. The correct link is https://doc.dovecot.org/plugin-settings/last-login-plugin/ . I tried correcting it myself in the wiki, but the Captcha was too hard for me. Cheers, Mika

2 1

Dovecot UIDs and POP.
by Plutocrat 26 Sep '19

26 Sep '19

Hi, I recently performed a mail server migration for a client under fairly serious time constraints (ahem, yes one of those jobs). I would normally use imapsync to get all the mail copied to the new server, but under the circumstances, I had to write a script to rsync each of the mailboxes over ssh, from one server to another. This all worked fine, except for the fact that if a client was using a POP email client, when they connected to the new server, they re-downloaded all their mail, creating duplicates of everything in their Outlook client. Of course they weren't happy about this. IMAP email clients were OK. No duplicates, and everything was fine. So while I was migrating the mail, I did try for a while to understand the format of the UID files, but failed to do so in the available time, so the client just had to deal with duplicate emails. But now the smoke has cleared, I'd like to understand the problem a little better, and I was hoping someone on this forum could explain it to me, and the changes I'd need to make to the files so that the POP client DIDN'T download the duplicate emails. Here's what I understand. The list of dovecot files in an account looks like this: -rw-r----- 1 admin mail 0 Jul 11 2018 dovecot-acl-list -rw-r----- 1 admin mail 14K Sep 20 08:36 dovecot.index -rw-r----- 1 admin mail 216K Sep 20 17:24 dovecot.index.cache -rw-r----- 1 admin mail 29K Sep 20 17:24 dovecot.index.log -rw-r----- 1 admin mail 388 Dec 17 2017 dovecot.list.index -rw-r----- 1 admin mail 1.6K Jul 11 2018 dovecot.list.index.log -rw-r----- 1 admin mail 24 Jul 11 2018 dovecot.mailbox.log -rw-r----- 1 admin mail 53 Sep 12 09:42 dovecot-quota -rw-r----- 1 admin mail 52K Sep 20 17:24 dovecot-uidlist -rw-r----- 1 admin mail 8 Jul 11 2018 dovecot-uidvalidity -rw-r----- 1 admin mail 0 Jul 4 2016 dovecot-uidvalidity.5779bbeb It seems that the dovecot-uidlist is an index of all the mail files in the account. As far as I can gather, this should be the same on both servers after I've rsynced them over ssh: The files and the list of them in dovecot-uidlist should correspond. So what is it that the POP client looks at and decides to re-download all the emails? And how could I have stopped it from doing that, and get it to realize that the list of emails it holds internally is the same as the list on the server? What would I need to change in the dovecot files? Thanks for any insight into the process. As a secondary question -- and perhaps I should put this in a separate message -- I did notice that "doveadm sync" would apparently have helped me with this, but I wasn't able to get that to work either. I believe it was something to do with the fact that all the mailboxes were under the same linux user account on the target server, and I couldn't figure out all the paths and permissions in time. Would 'doveadm sync' have fixed all the UID and duplicate POP email issues? P.

6 11

NFS Locking and Submission Service Authentication
by Asai 26 Sep '19

26 Sep '19

Greetings, We're in the process of upgrading our Dovecot server to new hardware and new expanded storage. We planned on using an NFS share for the mail storage, as we're running Postfix / Dovecot on a VM and wanted to separate out the mail storage from the VM for backup reasons. I read as much as I could find on line regarding configuring Dovecot to use NFS, and set it up as best I could, but I'm still running into lock errors e.g.: Sep 25 10:30:35 triata4 dovecot: imap(user(a)triata.globalchange.media)<75580><enQ/AWSTkQkKCgDu>: Error: fcntl(/vmail/triata.globalchange.media/user/dovecot.index.log, write-lock, F_SETLKW) locking failed: No locks available Sep 25 10:30:35 triata4 dovecot: imap(user(a)triata.globalchange.media)<75580><enQ/AWSTkQkKCgDu>: Error: mail_index_wait_lock_fd() failed with file /vmail/triata.globalchange.media/user/dovecot.index.log: No locks available Also, I have been trying to configure the Dovecot submission service to authenticate with Postfix, but I keep running into errors which are related to how I'm configuring the authentication. How do we set the user@domain and password string for submission in the configs? Thank you. Please see doveconf -n below, if you see any other errors in this config, I'd be grateful if you pointed them out: # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 (7372921a) # OS: Linux 3.10.0-957.27.2.el7.x86_64 x86_64 CentOS Linux release 7.6.1810 (Core) nfs auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain debug_log_path = /var/log/dovecot-debug.log deliver_log_format = msgid=%m: from=%f: %$ hostname = triata.globalchange.media mail_debug = yes mail_fsync = always mail_home = /vmail/%d/%n/home mail_location = maildir:/vmail/%d/%n 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 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 = separator = / type = private } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } plugin { mail_log_fields = uid box msgid from flags sieve = file:/vmail/%d/%n/sieve;active=/vmail/%d/%n/.dovecot.sieve } protocols = imap lmtp submission sieve service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { unix_listener lmtp { mode = 0666 } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service managesieve { process_limit = 1024 } service submission-login { inet_listener submission { port = 587 } } ssl_cert = </etc/letsencrypt/live/triata.globalchange.media/fullchain.pem ssl_key = # hidden, use -P to show it submission_relay_host = triata.globalchange.media submission_relay_password = # hidden, use -P to show it submission_relay_port = 587 submission_relay_ssl = starttls submission_relay_trusted = yes submission_relay_user = %u userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } protocol lda { mail_plugins = }

3 4

Spam Blocking by filtering on username / id
by Plutocrat 26 Sep '19

26 Sep '19

This is probably quite an easy question, but I haven't been able to find the answer. I'm running a server where all the email addresses are in the format "user(a)domain.com". I've noticed that a large number of fake login attempts use the format "user" eg. reception, service, root, admin. Is it possible to prevent any such logins to these email users without an @domain.com? Or maybe ignore them. Or drop them from the logging. P.

5 5

'director_tag' field returned from passdb lookup results in 'unknown passdb extra field'
by Dan 25 Sep '19

25 Sep '19

Hello all, I'm working with director in tandem with 'director_tags' to group some backend hosts. I've assigned the groups to the hosts by appending a '@' character after the IP address of a backend host under director_mail_servers: ... director_mail_servers = 192.168.0.1@foo 192.168.0.2@bar 192.168.0.3@foobar ... I can confirm that the backend hosts possess the correct tags by issuing: # doveadm director status mail server ip tag vhosts state state changed users 192.168.0.1 foo 100 up - 0 192.168.0.2 bar 100 up - 0 192.168.0.3 foobar 100 up - 0 And examining that the tags have been assigned correctly. My passdb lookup is using mysql, and it appears as such: passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } This file looks like: driver = mysql connect = host=localhost dbname=xxx user=xxx password=xxx password_query = select director_tag, username, domain, password, 'Y' as `proxy` from users where username = '%n' and domain = '%d' iterate_query = select director_tag, username, domain from users I have a database that contains the following columns: username, domain, password, home, UID, GID, active, and director_tag To assign users to a backend, I went off of the documentation that states: > " A passdb lookup can return "director_tag" field containing the wanted tag name. " To fulfill this, I return the 'director_tag' in the passdb lookup, through password_query. The mapping seems to work. When I change the row in the database, the user gets proxied to the new backend on the next connection. However, My question is, Why does this appear in the logs? "dovecot[1963]: imap-login: Debug: Ignoring unknown passdb extra field: director_tag" How could this be an unknown passdb extra field, when the documentation states that you may return a field containing this key? In the file core/src/login-common/client-common-auth.c - Starting at line 142, there is no if condition checking for 'director_tag'. This causes that line to be output to debug handle. Is this intentional? Thank you for your time. Full configuration: auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = yes director_mail_servers = 192.168.0.1@foo 192.168.0.2@bar 192.168.0.3@foobar director_servers = x.x.x.x y.y.y.y director_user_expire = 5 mins disable_plaintext_auth = no doveadm_port = 24245 haproxy_trusted_networks = x.x.x.x y.y.y.y 127.0.0.1 login_greeting = Dovecot At Your Service 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 passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocols = imap pop3 service director { fifo_listener login/proxy-notify { mode = 0666 user = $default_login_user } inet_listener { port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director inet_listener imap { haproxy = yes port = 143 } inet_listener imaps { haproxy = yes port = 993 ssl = yes } } service ipc { unix_listener ipc { user = dovecot } } service pop3-login { executable = pop3-login director inet_listener pop3 { haproxy = yes port = 110 } inet_listener pop3s { haproxy = yes port = 995 ssl = yes } } ssl_cert = </etc/dovecot/private/dovecot.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol doveadm { auth_socket_path = director-userdb }

2 1