- dovecot - dovecot.org

Variable expansion in password field
by Simone Lazzaris 14 Apr '20

14 Apr '20

Hi list! I've recently updated a small dovecot cluster from 2.2.29 to 2.3.10. I've found an issue with variable expansion. My user/password database is on a mysql table, with password saved in plain text field. The cluster receives mail via lmpt and users fetch them via imap. On the 2.2.29 version, no issues. After the upgrade, I've found some lines in the log: Apr 14 14:36:05 archive-front1 dovecot: lmtp(19671, fakeusername(a)fakedomain.com) Error: lmtp-server: conn 212.183.164.212:34642 [4]: rcpt fakeusername(a)fakedomain.com: Failed to initialize user: Failed to expand plugin setting password = 'sd78F6aS9%Lggxf': Unknown variable '%g' (I've faked /some/ information for obvious reasons, but I've kept the password after the '%' sign). Apparently, dovecot 2.3.10 is trying to expand some variables IN the password field. I'm trying to fool him expanding the '%' into '%%' on the password query, but without luck... I can also contact the user and make him choose a different password, without '%'. Anyway, I feel that this behaviour should be seen as a bug. Am I missing something? -- Simone Lazzaris QCom SpA

2 1

%d ignored from auth-passwdfile.conf.ext configuration file
by Andrei Petru Mura 13 Apr '20

13 Apr '20

I try to configure dovecot with virtual users. I put my users file in folder /etc/dovecot/my_domain_name/users. My auth-passwdfile.conf.ext file looks like this: passdb { driver = passwd-file args = username_format=%n /etc/dovecot/%d/users } When I try to log in, I get this: dovecot: auth: Error: passwd-file(test,some.ip.addr.here,<rQT+ziijGE1tpoAB>): stat(/etc/dovecot//users) failed: No such file or directory As you can see, %d isn't interpreted. Why is this happening? Any hints? Thanks, Mura Andrei

2 3

Missing permissions
by Andrei Petru Mura 13 Apr '20

13 Apr '20

Hi, Dovecot version 2.2.36 In log files I get this error: dovecot: imap(test): Namespace '': mkdir(/home/mail/domain/test/Maildir) failed: Permission denied (euid=1005(vmail) egid=1005(vmail) missing +w perm: /home/mail/domain, UNIX perms appear ok (ACL/MAC wrong?)) My authentication configuration is this: passdb { driver = passwd-file args = username_format=%n /etc/dovecot/users } userdb { driver = static args = uid=vmail gid=vmail home=/home/mail/domain/%n username_format=%n /etc/dovecot/users } /home/mail/domain/test directory is owned by vmail user. How to fix this? Mura Andrei

4 12

doveadm backup from gmail with imapc
by Ben Mulvihill 11 Apr '20

11 Apr '20

I am trying to backup a gmail account (not the one I am writing from) to dovecot, using doveadm-backup and imapc, but am having ssl connection problems. ted@expectation:~# doveadm backup -D -R -u ted imapc: dsync(ted): Info: imapc(imap.gmail.com:993): Connected to 74.125.71.108:993 (local 10.7.1.179:53852) dsync(ted): Warning: imapc(imap.gmail.com:993): Server disconnected unexpectedly: SSL_connect() failed: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure: SSL alert number 40 - reconnecting (delay 0 ms) dsync(ted): Info: imapc(imap.gmail.com:993): Connected to 74.125.71.109:993 (local 10.7.1.179:59052) dsync(ted): Error: imapc(imap.gmail.com:993): Server disconnected unexpectedly: SSL_connect() failed: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure: SSL alert number 40 - disconnecting dsync(ted): Error: User initialization failed: imapc: Login to imap.gmail.com failed: Disconnected from serv I am using dovecot version 2.2.33.2 on ubuntu, with the configuration below. I have also enabled "allow access from unsecure apps" in my gmail settings. My first thought looking at the error messages was has that perhaps doveadm-backup was trying to connect with ssl3, which is no longer supported by gmail or anyone else nowadays. But apparently the ssl3_read_bytes function in openssl also handles tls, so the reference to ssl3 in the message is misleading, and the real problem must be elsewhere. If anyone can help me debug this I'd be grateful. Many thanks, Ben root@expectation:/etc/dovecot# doveconf -N # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.15.0-91-generic x86_64 Ubuntu 18.04.4 LTS auth_mechanisms = plain imapc_features = rfc822.size gmail-migration fetch-headers imapc_host = imap.gmail.com imapc_password = # hidden, use -P to show it imapc_port = 993 imapc_ssl = imaps imapc_ssl_verify = no imapc_user = MY_GMAIL_ADDRESS mail_location = maildir:~/Maildir mail_prefetch_count = 20 mail_privileged_group = mail 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 { driver = pam name = } protocols = " imap" ssl = yes ssl_cert = </etc/dovecot/private/dovecot.pem ssl_cipher_list = ALL:!LOW:!SSLv2:!SSLv3:!EXP:!aNULL ssl_client_ca_dir = /etc/ssl/certs ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv3 userdb { driver = passwd name = }

6 13

doveadm replicator command
by Ivo 09 Apr '20

09 Apr '20

Can someone please explain to me what do commands "doveadm replicator add" and "doveadm replicator remove" really do. According to https://wiki.dovecot.org/Tools/Doveadm/Replicator they "Add the specified user(s) to the replicator." and "Remove the specified user from replicator.". Do they really do that? Since the default list of users for replication comes from doveadm user '*' (https://wiki.dovecot.org/Replication) I tried removing one user (e.g. xyz) from replication by using "doveadm replicator remove xyz" and it didn't work. Namely, after entering that command the only thing that I noticed is that "doveadm replicator status xyz" does not return any information. BUT, as soon as one mail arrives for that user "doveadm replicator status xyz" displays valid information and mail is replicated. Thanks in advance for any reply. # dovecot --version 2.2.33.2 (d6601f4ec)

1 0

doveadm backup into IMAP folder
by Gionatan Danti 09 Apr '20

09 Apr '20

Hi all, I am migrating a number of account from an old domain to a new one. I would like to store all imported email from the old domain under a specific IMAP folder. For example, if having test(a)domain.old, I would like to import all old email to test(a)domain.new/fromold. While I succeeded using doveadm backup / dsync to successfully replicate the old mailbox to the new one, I am unable to store all imported mail under a specific folder. So, I have some questions: - can the above be done? - if yes, can you confirm that email outside the specific destination folder will not be touched/deleted/whatever by doveadm backup? - does a "dry-run" option exists for doveadm backup / dsync? Thank you all. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it [1] email: g.danti(a)assyoma.it - info(a)assyoma.it GPG public key ID: FF5F32A8

2 1

alternatives for imapproxy
by Maciej Milaszewski 08 Apr '20

08 Apr '20

Hi System debian 8.11 and dovecot-2.2.36.4 My webmail is roundcube with imapproxy. I have one problem. My dovecot servers is are in a cluster with keepalived like: dovecot1----VIP-IP--------dovecot2 All works fine I have a problem with imapproxy when a server dovecot1 had a problem (kernel panic sic!) Keepalived works perfecty and moved VIP to dovecot2 - all works fine for normal users but imapproxy gave a timeout and webmail clinet cannot connect what do you recommend alternative to imapproxy ? I use imapproxy because is fast ...

2 2

Warning: Failed to do incremental sync
by Laura Smith 08 Apr '20

08 Apr '20

Setup dovecot sync along the lines of (https://wiki2.dovecot.org/Replication) I am doing one way replication. The initial full replication happened without issue, but now I'm seeing these errors on the slave server: doveadm: Warning: /data/mail/foo/bar/Maildir/dovecot-uidlist: Duplicate file entry at line 26397: 1562173159.M215923P17350.mxp,S=2290,W=2339 (uid 143128 -> 143142) Warning: Failed to do incremental sync for mailbox Sent Messages, retry with a full sync (Modseq 1766 no longer in transaction log (highest=17617, last_common_uid=17559, nextuid=17560)) Warning: Failed to do incremental sync for mailbox INBOX, retry with a full sync (Modseq 2540 no longer in transaction log (highest=13870, last_common_uid=19912, nextuid=19913)) I guess dovecot automatically tries a full replication because eventually the messages get pushed and "sync failed" status changes from 'y' to '-'

2 1

Dovecot "User-Agent" equivalent
by Plutocrat 08 Apr '20

08 Apr '20

Hi, I was trying to debug an IMAP connection problem. The client accesses an account via webmail, mobile phone, and desktop. I was wondering if there was a way of determining which of these they were using at a given time. My googling turned up the following settings in the imap{} section: protocol imap { imap_id_log = * imap_id_send = "name" * "version" * } ... but setting these didn't seem to log any more information that I could use. Have I misunderstood the usage of these settings? Shouldn't they log a "user agent" type information in /var/log/dovecot.log ? Or are there any other ways I can get information on the client? P.

1 0

\Noselect missing after deleting mailbox
by Onno Molenkamp 07 Apr '20

07 Apr '20

Hi, With mailbox_list_index enabled (which is the default), Dovecot won't return \Noselect when LISTing a mailbox that was deleted but still has subordinate mailboxes. Before creating such a mailbox in the first place, it does return \Noselect. 1 LIST "" Test 1 OK List completed (0.002 + 0.000 + 0.001 secs). 2 CREATE Test/Test 2 OK Create completed (0.014 + 0.000 + 0.014 secs). 3 LIST "" Test * LIST (\Noselect \HasChildren) "/" Test 3 OK List completed (0.001 + 0.000 secs). 4 CREATE Test 4 OK Create completed (0.006 + 0.000 + 0.005 secs). 5 LIST "" Test * LIST (\HasChildren) "/" Test 5 OK List completed (0.001 + 0.000 secs). 6 DELETE Test 6 OK Delete completed (0.011 + 0.000 + 0.011 secs). 7 LIST "" Test * LIST (\HasChildren) "/" Test 7 OK List completed (0.001 + 0.000 secs). Like response 3, response 7 should contain \Noselect. (and it does, when mailbox_list_index is disabled) It looks like Dovecot isn't updating dovecot.list.index properly when deleting such a mailbox. Forcing Dovecot to rebuild the index by deleting dovecot.list.index* will cause \Noselect to re-appear in responses. Onno

1 0