- dovecot - dovecot.org

health check passthrough not 100% in combination with haproxy
by Marc 02 Nov '21

02 Nov '21

I have been trying to get a simple health check in haproxy to work. But somehome the haproxy request is differently handled then a curl request, which generates a socket error in haproxy. The health script echos these lines, with this config[2] echo -ne "HTTP/1.1 200 OK\r\n" echo -ne "Content-Length: 0\r\n" echo -ne "\r\n" exit 0 The curl request generates ok, haproxy generates socket error. The haproxy=yes, reuseport=yes do not seem to resolve anything. If stop dovecot and run "dovecot-health-check.sh | nc -l 192.168.10.46 5001" then the haproxy check is ok. So I guess the script is ok. But what is dovecot then doing with it's output when haproxy is requesting it? [1] https://discourse.haproxy.org/t/httpck-on-bash-script-results-in-socket-err… [2] service health-check { executable = script -p /usr/local/sbin/dovecot-health-check.sh inet_listener health-check { port = 5001 haproxy = no reuse_port = no } }

3 6

Ldap dict for shared mailboxes
by Kees van Vloten 02 Nov '21

02 Nov '21

Hi everybody, I am trying to construct a LDAP dict for shared mailboxes. There is a lot of documentation available but nothing specific to this usecase. I could not find anything useful on Google nor in the mailinglist archives :-( The best start point seems to be the doc on shared mailbox dictionaries (https://doc.dovecot.org/configuration_manual/shared_mailboxes/shared_mailbo…) in particular the example for SQL dict. But obviously LDAP is different than SQL. The dictionaries page (https://doc.dovecot.org/configuration_manual/dict/) has LDAP example but it looks like it does not contain all the bit and pieces I need. Following the structure of the SQL example, I come to something like this: map { pattern = shared/shared-boxes/user/$to/$from base_dn = ou=shared mailboxes,dc=example,dc=com filter = (&(objectClass=group)(mail=%{from}) fields { from_user=$from to_user=$to } } The "to_user" / "$to" should be filled with the 'uid' or 'email' of a nested group lookup of the 'member' fields of the group. What are the mechanics to get that done? Does anyone has an example or pointer to documentation or is a LDAP dict for shared-mailboxes not possible / supported? And in the latter case, suggestions about possible alternatives are welcome :-) FYI. the LDAP implementation I am using is a recent Samba4 ad-dc. - Kees.

1 0

limiting cpu time of dovecot/imap
by Marc 01 Nov '21

01 Nov '21

What would be the best way to 'throttle' dovecot/imap processes of specific users?

2 1

Dovecot does not start on MacOS 12.01
by Don Feliciano 01 Nov '21

01 Nov '21

I've been happily running Dovecot on my Mac for many years (installed via Homebrew). After upgrading to Monterey (MacOS 12.01), it no longer starts: $ sw_vers ProductName: macOS ProductVersion: 12.0.1 BuildVersion: 21A559 $ uname -a Darwin dfelicia-mac 21.1.0 Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:23 PDT 2021; root:xnu-8019.41.5~1/RELEASE_X86_64 x86_64 $ sudo dovecot -F Oct 27 10:11:18 service(log): Fatal: setrlimit(RLIMIT_DATA, 268435456): Invalid argument $ mount /dev/disk1s2s1 on / (apfs, sealed, local, read-only, journaled) devfs on /dev (devfs, local, nobrowse) /dev/disk1s5 on /System/Volumes/VM (apfs, local, noexec, journaled, noatime, nobrowse) /dev/disk1s3 on /System/Volumes/Preboot (apfs, local, journaled, nobrowse) /dev/disk1s6 on /System/Volumes/Update (apfs, local, journaled, nobrowse) /dev/disk1s1 on /System/Volumes/Data (apfs, local, journaled, nobrowse) $ sudo dovecot -n # 2.3.16 (7e2e900c1a): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.16 (09c29328) # OS: Darwin 21.1.0 x86_64 apfs # Hostname: dfelicia-mac default_internal_group = mail default_internal_user = _dovecot default_login_user = _dovenull first_valid_uid = 100 listen = 127.0.0.1 log_path = /var/log/dovecot.log mail_location = maildir:/usr/local/var/mail/%u 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 } passdb { args = login driver = pam } protocols = imap service imap-login { inet_listener imap { address = 127.0.0.1 port = 143 } inet_listener imaps { address = 127.0.0.1 ssl = no } } ssl = no userdb { driver = passwd } $ ulimit -Ha core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited file size (blocks, -f) unlimited max locked memory (kbytes, -l) unlimited max memory size (kbytes, -m) unlimited open files (-n) unlimited pipe size (512 bytes, -p) 1 stack size (kbytes, -s) 65532 cpu time (seconds, -t) unlimited max user processes (-u) 2784 virtual memory (kbytes, -v) unlimited

3 10

2.3.17 - breaks with fts-xapian.
by Juan Felipe Arjona 01 Nov '21

01 Nov '21

Hello: I just upgraded my Debian server with dovecot 2.3.17, and it breaks when using the plugin fts-xapian. Apparently is a bug in Dovecot, please see: https://github.com/grosjo/fts-xapian/issues/99 Thanks, Juan

3 2

Errors after freebsd upgrade
by Hanns Mattes 01 Nov '21

01 Nov '21

Hi, after upgrading Freebsd from ports dovecot is throwing the following error Oct 30 18:04:15 freebsd dovecot[59232]: doveadm(xxx(a)example.com)<84061><S3CoJf9sfWFdSAEAUmejdw>: Fatal: master: service(doveadm): child 84061 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set service doveadm { drop_priv_before_exec=yes }) I (surely) may have missed something while upgrading (I've learned a lot about backup/snapshot-strategies with zfs, but to late to apply). How can I debug the erro? Regards Hanns

2 1

Design Check
by Felix Ingram 31 Oct '21

31 Oct '21

Hello all, I'm building a mail system and would like to check whether my design is feasible. I'm fairly certain that it is but I think I don't have the right words and concepts lined up properly in my head. The end system will provide temporary/disposable email addresses that can be accessed by multiple people. People would be able to send email to addresses that match the following format: user1(a)foobar.mydomain.com user2(a)foobar.mydomain.com user1(a)barbaz.mydomain.com user2(a)barbaz.mydomain.com I would like all emails to the "foobar" subdomain to end up in their own mailbox and all emails to the "barbaz" subdomain to go to their own mailbox. (I think that means I need a foobar and barbaz user on Dovecot). Users of the system should be able to see all of the emails, including the original addresses they were sent to. e.g. user1(a)foobar.mydomain.com and user2(a)foobar.mydomain.com both get delivered to the "foobar" mailbox, and users can see all emails, including that they were sent to "user1" and "user2" The users of the system would be able to access any of the foobar, barbaz, etc mailboxes - I believe that means that they would need to be set as master users. I will be creating a web interface for users to get/set their credentials, so can add those users on an adhoc basis, but I will need to have the "foobar", "barbaz", etc users created whenever an email arrives (we won't know ahead of time). The plan is to have postfix accepting the emails before passing them to Dovecot. I don't believe postfix needs to do much processing but that this would be the place to transform the address into the correct user/mailbox name. So my questions are: 1. Does the above sound reasonable? 2. Can Dovecot auto-create users as needed? 3. Will I be able to preserve the original email? 4. Are master users the right approach? There is no strong requirement for privacy between mailboxes - there is no issue with one user being able to read all email. There is also no requirement to be able to send email but that is a feature request for the future - we would want people to be able to send as the original address when that's implemented. Any pointers gratefully received. Thanks in advance, Felix

4 9

v2.3.17 - dsync says invalid option -- E
by Daniel J. Luke 31 Oct '21

31 Oct '21

Hello, I've got some scripts that archive off mail that stopped working with 2.3.17. Specifically this worksin 2.3.16: sudo -n /usr/local/bin/dsync -u dluke -m Sent -o mail_location=mbox:~/tmp/ mirror maildir:~/Maildir/ but fails on 2.3.17 with the following error message: dsync: invalid option -- E -- Daniel J. Luke

3 5

Re: Dovecot 2.3.17 can not start - too many parameters
by Robert Nowotny 29 Oct '21

29 Oct '21

Michael, it seems the rumors are right. After shortening the file /etc/ssl/ca-certificates.crt to one entry, it works. Of course this is not a solution, so a fix will be needed. I use the "/etc/ssl/certs/ca-certificates.crt" which is included with Ubuntu impish yours sincerely Robert Am 29.10.2021 um 21:09 schrieb Michael Kliewe: Hi, I have heard rumors that this happens when you provide a CA bundle file which is big. If you just provide a single CA file it works. Something has changed there, maybe the developers have more details about this change. King regards Michael Am 29.10.2021 um 19:25 schrieb Robert Nowotny: Dovecot 2.3.17 can not start - too many parameters. but the same config is working on 2.3.16 (and for a long time already ...) started via systemd unit file : ================== [Unit] Description=Dovecot IMAP/POP3 email server Documentation=man:dovecot(1) Documentation=http://wiki2.dovecot.org/ After=local-fs.target network.target dnsmasq.service NetworkManager-wait-online.service network-online.target Requires=network.target network-online.target dnsmasq.service local-fs.target [Service] Type=forking ExecStart=/usr/local/sbin/dovecot -c /etc/dovecot/dovecot.conf PIDFile=/usr/local/var/run/dovecot/master.pid ExecReload=/usr/local/bin/doveadm reload ExecStop=/usr/local/bin/doveadm stop PrivateTmp=true NonBlocking=yes LimitNOFILE=8192 [Install] WantedBy=multi-user.target ================== log: Oct 29 18:48:58 lxc-imap dovecot[1781]: doveconf: Fatal: execvp(/usr/local/sbin/dovecot) failed: Argument list too long Oct 29 18:48:58 lxc-imap systemd[1]: dovecot.service: Control process exited, code=exited, status=89/n/a Oct 29 18:48:58 lxc-imap systemd[1]: dovecot.service: Failed with result 'exit-code'. but when I run doveconf -n, it is working under 2.3.17 I needed to revert to version 2.3.16 to send this email ;-) running on Ubuntu impish yours sincerely Robert Nowotny Rotek GmbH

1 0

Dovecot 2.3.17 can not start - too many parameters
by Robert Nowotny 29 Oct '21

29 Oct '21

Dovecot 2.3.17 can not start - too many parameters. but the same config is working on 2.3.16 (and for a long time already ...) started via systemd unit file : ================== [Unit] Description=Dovecot IMAP/POP3 email server Documentation=man:dovecot(1) Documentation=http://wiki2.dovecot.org/ After=local-fs.target network.target dnsmasq.service NetworkManager-wait-online.service network-online.target Requires=network.target network-online.target dnsmasq.service local-fs.target [Service] Type=forking ExecStart=/usr/local/sbin/dovecot -c /etc/dovecot/dovecot.conf PIDFile=/usr/local/var/run/dovecot/master.pid ExecReload=/usr/local/bin/doveadm reload ExecStop=/usr/local/bin/doveadm stop PrivateTmp=true NonBlocking=yes LimitNOFILE=8192 [Install] WantedBy=multi-user.target ================== log: Oct 29 18:48:58 lxc-imap dovecot[1781]: doveconf: Fatal: execvp(/usr/local/sbin/dovecot) failed: Argument list too long Oct 29 18:48:58 lxc-imap systemd[1]: dovecot.service: Control process exited, code=exited, status=89/n/a Oct 29 18:48:58 lxc-imap systemd[1]: dovecot.service: Failed with result 'exit-code'. but when I run doveconf -n, it is working under 2.3.17 I needed to revert to version 2.3.16 to send this email ;-) running on Ubuntu impish yours sincerely Robert Nowotny Rotek GmbH

2 1