- dovecot - dovecot.org

identify 143 vs 993 clients
by mj 01 Jun '20

01 Jun '20

Hi, I am trying to find a nice way to identify dovecot clients that are still configured to use port 143 to connect to our mailserver, from the dovecot logs. I would then ask them to move over to 993, and finally disable port 143 altogether. When looking at the dovecot logs, it seems this is not logged in any obvious way. Of course I could use netflow etc, but that would not give us usernames, but IP's, etc. So, is there a nice way to somehow indicate in the dovecot logs, if a client connected on 143 or on 993? Thanks!

13 25

Running doveadm without config file?
by Joseph Tam 01 Jun '20

01 Jun '20

It would be useful to run the "doveadm" utility on a non-dovecot server e.g. generating password hashes: # echo plaintextpass | doveadm pw -s BLF-CRYPT doveadm(user): Fatal: Error reading configuration: stat(/etc/dovecot/dovecot.conf) failed: No such file or directory Is there a way to circumvent the need for a configuration file? Joseph Tam <jtam.home(a)gmail.com>

2 4

Current thinking on backups ?
by Laura Smith 30 May '20

30 May '20

Hi, What are people doing for backups ? My current process is LVM snapshot and backup from that to NFS share. But there seems to be hints around the internet that people use/abuse "doveadm backup" for backup purposes even though it seems its original intention was for transferring mailboxes between dovecot instances. Assuming its ok to "doveadm backup" to an NFS share, is it ok to use "doveadm backup" when dovecot has replication setup (replication-notify etc.) ? Or will it interfere ? Thanks! Laura

4 4

Operation not permitted - fchown() failed for /run/dovecot/login
by Dshah 30 May '20

30 May '20

# dovecot --version 2.3.10.1 (a3d0e1171) Dovecot is unable to start, I see error " Fatal: fchown() failed for /run/dovecot/login: Operation not permitted" what could be the problem? any help please $ls -la /var/mail/ drwxr-xr-x 1 root root 4096 May 29 17:32 . drwxr-xr-x 1 root root 4096 May 28 17:08 .. drw------- 2 root root 4096 May 29 17:32 domains ====# cat /etc/dovecot/dovecot.conf===== auth_mechanisms = plain login auth_username_format = %Lu auth_verbose = yes auth_debug = yes auth_debug_passwords = no log_timestamp = "%Y-%m-%d %H:%M:%S " login_greeting = IMAP server ready disable_plaintext_auth = no protocols = imap pop3 log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/var/mail/domains/%d/%n first_valid_gid = 105 first_valid_uid = 102 last_valid_gid = 105 last_valid_uid = 102 service anvil { client_limit = 2100 } ssl_cert = </secret/tls.crt ssl_key = </secret/tls.key ssl_ca = </secret/ca.crt namespace inbox { inbox = yes mailbox Trash { auto = create special_use = \Trash } mailbox Spam { auto = no special_use = \Junk } mailbox Ham { auto = no } mailbox Sent { auto = subscribe special_use = \Sent } } # service auth { # unix_listener auth-master { # mode = 0600 # user = vmail # } # unix_listener /var/spool/postfix/private/auth { # mode = 0666 # user = postfix # group = postfix # } # user = root # } # service auth-worker { # user = root # } # protocol lda { # log_path = /home/vmail/dovecot-deliver.log # auth_socket_path = /var/run/dovecot/auth-master # postmaster_address = postmaster(a)razalabs.com # } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } userdb { driver = static args = uid=102 gid=105 home=/var/mail/domains/%d/%n allow_all_users=yes } passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf.ext } =================/etc/dovecot/dovecot-sql.conf.ext=============== driver = mysql connect = host=localhost dbname=mail user=root password=pass default_pass_scheme = CRYPT password_query = SELECT email as user, password FROM users WHERE email='%u'; =================dovecot-sql.conf.ext=============== =================/etc/dovecot/dovecot-sql.conf.ext=============== driver = mysql connect = host=localhost dbname=mail user=root password=pass default_pass_scheme = CRYPT password_query = SELECT email as user, password FROM users WHERE email='%u'; =================dovecot-sql.conf.ext=============== and postfix =================/etc/postfix/main.cf=============== inet_protocols = all meta_directory = /etc/postfix shlib_directory = /usr/lib/postfix myhostname = mail.my-domain.com mynetworks = 127.0.0.0/8 message_size_limit = 30720000 virtual_alias_domains = virtual_alias_maps = proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf, mysql:/etc/postfix/mysql-virtual_email2email.cf virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql-virtual_domains.cf virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql-virtual_mailboxes.cf virtual_mailbox_base = /var/mail/domains virtual_uid_maps = static:102 virtual_gid_maps = static:105 smtpd_sasl_type = dovecot smtpd_sasl_path = /var/spool/postfix/private/auth smtpd_sasl_auth_enable = yes broken_sasl_auth_clients = yes smtpd_sasl_authenticated_header = yes smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_use_tls = yes smtpd_tls_cert_file = /secret/tls.crt smtpd_tls_key_file = /secret/tls.key #virtual_create_maildirsize = yes #virtual_maildir_extended = yes proxy_read_maps = $local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks virtual_transport = dovecot dovecot_destination_recipient_limit = 1 smtpd_milters = inet:127.0.0.1:8891 milter_default_action = accept =================/etc/postfix/main.cf===============

1 1

migrating dovecot to new server
by David Mehler 30 May '20

30 May '20

Hello, I'm needing to migrate my dovecot installation it's 2.3 on FreeBSD 12.1 to a new server. I'd ideally like to back up all the mails in the maildir location, copy that over, load in my configuration files, and bring the system back up. I doubt it's that easy, any pitfalls I should watch out for? Thanks. Dave.

4 4

director -> POP3s/IMAPs -> mailbox host
by patosec 28 May '20

28 May '20

Hello again, I did a lot of trial and error already, but I can't seem to find a way to encrypt my dovecot director to dovceot mailbox traffic. Is there a way to configure dovecot director to only use ssl/tls encrypted connections for specific tagged mailbox clusters? (or all clusters, in fact does not matter if it could be restricted to tags) Looks like there is also no documentation available for this sort of configuration. I tried setting my mailbox nodes to "ssl = require" butt after doing so I can't login through director proxy anymore. It always looks like ssl/tls termination is finally done on director side. Anyone tried this already or has a running setup doing encryption from lets say frontend to backend? Thanks, greetings Patrick

2 2

service doveadm - how to debug proxying with director
by patosec 28 May '20

28 May '20

Hello everyone, I'm on a small dovecot director -> dovecot mailbox setup and I try to get doveadm command proxying to work. Though I don't get the expected output. My directors do not forward the doveadm commands to the expected backend host. Doveadm is working as expected on the backend hosts, the director hosts just dont log anything about the proxying that should happen or anything else about the doveadm commands at all. Can someone guide me in a direction on what to try next or maybe got a working config regarding doveadm proxying? Thanks in advance! Some technical data regarding my problem: Dovecot Version: 2.3.10 (0da0eff44) Output of a 'doveadm director status' command: mail server ip tag vhosts state state changed users 10.0.0.81 tag1 100 up - 0 10.0.0.82 tag1 100 up - 1 Output of a 'doveadm director ring status' command: director ip port type last failed status ping ms input output buffered buffered peak last read last write 10.0.0.193 9090 self never ring synced 5 - - - - - - 10.0.0.194 9090 right never synced 0 2051 6400 0 757 2020-05-28 09:56:37 2020-05-28 09:56:37 10.0.0.195 9090 left never synced 0 4929 1804 0 37 2020-05-28 09:56:37 2020-05-28 09:56:37 This is my dovecot-director hosts configuration (doveadm related part): service doveadm { inet_listener { # any port you want to use for this: port = 24245 } } local 0.0.0.0 { # password to use for client authentication doveadm_password = secret # allow client to only use specified list of commands (default is all): #doveadm_allowed_commands = } # same port as doveadm's inet_listener doveadm_port = 24245 protocol doveadm { # NOTE: director-userdb socket is actually used only for passdb lookups, not userdb lookups auth_socket_path = director-userdb } And here the dovecot-backend hosts configuration (doveadm related part): ### director conf service doveadm { inet_listener { # any port you want to use for this: port = 24245 } } local 0.0.0.0 { # password to use for client authentication doveadm_password = secret # allow client to only use specified list of commands (default is all): #doveadm_allowed_commands = } A 'doveadm user -u test(a)test.com' command on the backend host: userdb: test(a)test.com user : test(a)test.com home : /var/spool/imap/test(a)test.com quota : maildir:User quota quota_rule: *:storage=1048576:messages=153000 A 'doveadm user -u test(a)test.com' command on the director host: userdb: test(a)test.com user : test(a)test.com

2 3

Determinant of umask for sieve_pipe_bin_dir scripts?
by Laura Smith 27 May '20

27 May '20

Hi, What determines the umask of sieve_pipe_bin_dir scripts ? The results from my script are always being set to 0600. My script is simple and shown below, even if I adjust the right line to add " && chmod 644", the actual resulting file still remains at 0600 ?!? #!/bin/bash # Usage: imapsieve_copy <email> <spam|ham> MSG_USER="$1" MSG_TYPE="$2" RUN_UUID=$(cat /proc/sys/kernel/random/uuid) BASE_DIR="/foo/bar" TARGET_DIR="${BASE_DIR}/${MSG_TYPE}" TARGET_FILE="${TARGET_DIR}/${RUN_UUID}" cat > "${TARGET_FILE}" < /dev/stdin && pigz -9 "${TARGET_FILE}"

2 2

How to make IMAPS SSL Cert for Dovecot that works with Thunderbird
by hanasaki＠gmail.com 27 May '20

27 May '20

Hello all, What are the instructions for making an SSL cert for Dovecot IMAPS? Two methods have been tried, and work, with Evolution; however generate the following error when Thunderbird tries to connect. Thank you, method 1 : self signed openssl req -newkey rsa:4096 -sha512 -x509 -days 365 -nodes -keyout mykey.key -out mycert.pem method 2 : Let's Encrypt (LE) CA Created with Certbot ERROR TLS handshaking: SSL_accept() failed: error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate: SSL alert number 42, session=<+oooooo>

5 10

doveadm: extra lines?
by Felipe Gasper 27 May '20

27 May '20

Hello, I’m sending doveadm “kick” commands to doveadm-server via the doveadm protocol. When “kick” sends back a NOTFOUND error, though, it’s sending back additional output. strace shows: write(3<UNIX:[3158354->3156665]>, "\t\tkick\tmyssltest\n", 17) = 17 ... read(3<UNIX:[3158354->3156665]>, "\n-NOTFOUND\n\n-\n", 8192) = 14 Going by the protocol documentation (https://wiki2.dovecot.org/Design/DoveadmProtocol) there appear to be 3 extra bytes at the end of the server’s response: "\n-\n". Is this a bug in doveadm-server? Or am I misreading the protocol documentation? Thank you! cheers, -Felipe Gasper

1 2