May 2021 - dovecot - dovecot.org

New Configuration
by Eric Shields | Mass Transit Honchkrow 29 May '21

29 May '21

Hi, I'm setting up an email server behind a NAT, and I have the necessary DNS records, iptables/ufw rules, and ACLs in place. However, I cannot sign in with my chosen username, which does exist on the same computer I'm hosting the server on. I am using PAM, not a database, to hold credential information, and SSL certificates are active. However, I am getting signal 15 for the following processes: anvil, config, and auth. I can confirm through telnet that the ports I am using are open, and these ports are also open on the WAN side, which I believe is needed. Do you have any pointers for me, or any additional clarifying details? - 🚏

2 1

Different Maildir Locations
by Gabx 28 May '21

28 May '21

Hi, on my vps (debian stable) I have an email system with postfix, dovecot, virtual users and domains. I have 3 users with different mail_locations. the first mail_location = maildir: ~ / Maildir the second mail_location = maildir: ~ / user1 / Maildir the third mail_location = maildir: ~ / user2 / mail In postfix the above schema is represented in virtual_mailbox_maps. In dovecot mail_location is set maildir:~/Maildir. The first user receives regular mail, the other two none. I tried to see if in dovecot there was the possibility to configure the mail_location specifically for each single user, but with namespaces and userdb I am a bit confused and I have not found specific examples for my case. regards Gab -- GPG fingerprint: 5A6A F742 ACEA C9A7 93A8 8D5E 7AEF 5A02 D080 89F7 Contact: xmpp://gabx@jabber.tcpreset.net

3 14

replicator: Panic: data stack: Out of memory when allocating ...
by Jörg Faudin Schulz 28 May '21

28 May '21

frequently, the replicator fails on allocating memory: replicator: Panic: data stack: Out of memory when allocating ... bytes. I already have increased default_vsz_limit=1024M but this only increased the ... value. What can be done here? dovecot_branch=release-2.3.14

2 3

Mailbox problem on centos O/S after some "fiddling"
by John Richards 28 May '21

28 May '21

Good day from Somerset, England Version 2.2.10 Problem after a huge centos update Data:- Server has 8 mailboxes under /var/mail/"user name" history:- After update, mail to ONE user was going into mqueue as undeliverable Had to delete and recreate the user. somewhere along the line (ME!) /var/mail/;imap var/mail/new were deleted After new user and reboot server no one could access mailboxes with password error except ONE user randomly....This created the /var/mail/.mbox folder and sub folders but with the owner as the user name. Then any mail for other users was put in the /var/new folder and just sat there. only the "owner" of this folder could get mail, everyone else was prohibited with password error. chown the folder (owner:group) to root did nothing BUT When .mbox was give PUBLIC execute permissions (771) suddenly everything works fine! I do not understand why dovecot creates this folder as we ONLY ever use pop3 (currently with plain text auth but going to secure when this sorted) for mail and also why when it writes the blank folder it "owns" it with the user accessing it (also the /var/mail/new folder takes the same owner) I have trolled everywhere and spent a whole day on this so any clues would be very gratefully accepted as do not like to leave this folder as 771 (note the folder INBOX within it is only 770 and the log file in that is 660) Is this INBOX needed at all for pop3 ? rgds John Richards UK ================= dovecot -n # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-514.2.2.el7.x86_64 x86_64 CentOS Linux release 7.3.1611 (Core ) ext4 auth_mechanisms = plain login disable_plaintext_auth = no mail_location = mbox:/var/mail/:INBOX=/var/mail/%u 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 { driver = shadow } protocols = pop3 service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } ssl_cert = </etc/pki/tls/certs/watchetwebdesign.co.uk.crt ssl_key = </etc/pki/tls/private/watchetwebdesign.co.uk.key userdb { driver = passwd }

2 1

NFS Locking Question
by Zane Zak 28 May '21

28 May '21

Hi! I'm hoping to get some clarification on NFS locking before deploying a new setup. We have a single exim server that delivers mail to mbox files in /var/mail. We have a separate server running dovecot that reads mail from these mbox files. So only one exim server and one dovecot server, but they're separate VMs and handle locking with dotlocks. I was noticing frequent mbox file corruption. I then set "mail_nfs_storage = yes", and have seen no mbox corruption since. However, I'm now seeing messages like this in the logs for every read... Error: nfs_flush_fcntl: fcntl(/var/mail/username, F_RDLCK) failed: Bad file descriptor Is there a configuration change that needs to be made on the dovecot or the NFS servers, or are these messages harmless. Thanks! ZZ

2 1

mail-crypt-plugin: encrypted user keys
by Daniel Schuermann 28 May '21

28 May '21

Hi, I tried to enable encrypted folder keys using mail-crypt-plugin. It works as expected when using unencrypted folder keys. When I add mail_crypt_require_encrypted_user_key = yes as shown below, I somehow manage to crash dovecot: dovecot: lmtp(82060): Fatal: master: service(lmtp): child 82060 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set service lmtp { drop_priv_before_exec=yes }) dovecot: lmtp(67814): Panic: file mail-user.c: line 229 (mail_user_deinit): assertion failed: ((*user)->refcount== 1) lmtp(root): Info: msgid=<07e3a23b2aaea60b(a)mx.2718282.net>: save failed to INBOX: generate_keypair(INBOX) failed: mail_crypt_require_encrypted_user_key set, cannot generate user keypair without password or key My config files: # 2.3.14 (cee3cbc0d): /etc/mail/imap.conf # OS: OpenBSD 6.9 amd64 auth_verbose = yes debug_log_path = /var/log/dovecot info_log_path = /var/log/dovecot mail_attribute_dict = file:%h/Maildir/dovecot-attributes mail_debug = yes namespace inbox { ... } passdb { args = /etc/mail/imap-sqlite.conf driver = sql } plugin { mail_crypt_curve = secp521r1 mail_crypt_require_encrypted_user_key = yes mail_crypt_save_version = 2 } protocols = imap lmtp service imap-login { ... } ssl = required ssl_cert = </etc/ssl/rsa.crt ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes userdb { args = /etc/mail/imap-sqlite.conf driver = sql override_fields = uid=vmail gid=vmail } # file: /etc/mail/imap-sqlite.conf driver = sqlite connect = /etc/mail/sqlite.db default_pass_scheme = BLF-CRYPT user_query = SELECT '/home/vmail/'||destination AS home FROM virtuals WHERE email = '%u' password_query = SELECT email as user, password, '%w' AS \ userdb_mail_crypt_private_password FROM credentials WHERE email = '%u'

2 1

missing +w perm
by Jeff Abrahamson 28 May '21

28 May '21

I've started seeing the following error in mail.err for precisely one user on precisely one domain: Error: mkdir(/var/mail/vmail//jeff/mail) failed: Permission denied (euid=1000(jeff) egid=1001(jeff) missing +w perm: /var/mail/vmail/, dir owned by 4000:4000 mode=0755) Error: Mailbox INBOX: Failed to autocreate mailbox: Internal error occurred. In mail.log I see a bit more: Warning: Failed to parse address from `From_'-line: Missing domain Error: mkdir(/var/mail/vmail//jeff/mail) failed: Permission denied (euid=1000(jeff) egid=1001(jeff) missing +w perm: /var/mail/vmail/, dir owned by 4000:4000 mode=0755) Error: mkdir(/var/mail/vmail//jeff/mail) failed: Permission denied (euid=1000(jeff) egid=1001(jeff) missing +w perm: /var/mail/vmail/, dir owned by 4000:4000 mode=0755) Error: Mailbox INBOX: Failed to autocreate mailbox: Internal error occurred. Refer to server log for more information. save failed to open mailbox INBOX: Mailbox INBOX: Failed to autocreate mailbox: Internal error occurred. And yet there's no apparent problem sending and receiving mail for user jeff, for all domains handled by the server. Other users have no issues. The /var/mail/vmail/ hierarchy is all owned by vmail:vmail (4000:4000) and directories are all 0755. I suspect a red herring except it's been continuing for a week now. I was reading this page (following some searching), but it doesn't seem pertinent in the end. https://wiki2.dovecot.org/MailLocation/mbox#A.2BAC8-var.2BAC8-mail.2BAC8_do… Any suggestions what this might be? -- Jeff Abrahamson +33 6 24 40 01 57 +44 7920 594 255 http://p27.eu/jeff/ http://mobilitains.fr/

2 2

backup v rsync
by Jeff Abrahamson 27 May '21

27 May '21

I've been migrating from a dovecot 2.2.22 instance to a dovecot 2.3.7.2 instance. (Said differently, from an ubuntu 16.04 host to a 20.04 host.) It's a tiny site: only a handful of users actually had to migrate, most either died on the old one or were born on the new one. The main user in need of migration was me. After fiddling with dsync and not getting it working, I threw in the towel. This is a migration I had to do once for precisely one user. I had been using the old host exclusively, so it was easy to shut down both dovecot instances the time it took me to rsync my data from one to the other. Now that seems to work, almost. Mail is being delivered to my inbox, anyway. Most other folders are looking inaccessible to my mail client (thunderbird, for this test). The main difference between the two servers, aside from the above, is a switch from mail_location = maildir:~/Maildir to mail_home = /var/mail/vmail/%d/%n mail_location = maildir:/var/mail/vmail/%d/%n/mail:LAYOUT=fs mail_privileged_group = mail I corrected permissions and ownership when I copied the data. Now I think the problem is that LAYOUT=fs means that I should have a slightly different folder hierarchy now. The question is how best to fix this. I have things like this .Archives.2020 .Archives.2020/new .Archives.2020/tmp .Archives.2020/cur when I think I should have things like this Archives Archives/2021 Archives/2021/new Archives/2021/tmp Archives/2021/cur And, again, this is one-off, so a manual fix seems most appropriate. I'm quite tempted simply to shut down the dovecot instance for a minute at a quiet moment (mail retries...) and rename directories as indicated above. I only have to rename five directories. Having gotten myself in a bit of a muddle on this, I thought perhaps a reality check that I'm not about to make it worse would be appropriate. Many thanks. -- Jeff Abrahamson +33 6 24 40 01 57 +44 7920 594 255 https://www.p27.eu/jeff/ https://www.mobilitains.fr/

2 2

API command for ACL Delete
by Rhodri Jones 27 May '21

27 May '21

I asked previously for info about the API options for doveadm acl delete but I think my question was misunderstood. I want to know the command I would use (with curl for instance) that corresponds with: doveadm acl delete -u <targetmailbox> INBOX user=<targetuser> Using the python client for doveadm http API I can see the valid parameters but I don't seem to be able to get the correct syntax. (doveadm) aclDelete ? invalid parameter: ? valid parameters for aclDelete: - userFile (string) - allUsers (boolean) - mailbox (string) - user (string) - socketPath (string) - id (string) --

2 2

API command for ACL Delete
by Rhodri Jones 26 May '21

26 May '21

Can anyone tell me how to do the following using the API. doveadm acl get -u <targetmailbox> INBOX doveadm acl delete -u <targetmailbox> INBOX user=$user Are the ACL API options documented somewhere? Thanks --

2 1