- dovecot - dovecot.org

temporary block incoming messages to specific user
by Marc 20 Apr '22

20 Apr '22

Is it possible to block incoming messages from being delivered to a specific user in such a way that the MTA will try again later. I do not want these message to bounce. (eg while doing some manual maintenance on the user)?

3 2

JMAP Support Status
by David Klingenberg 15 Apr '22

15 Apr '22

Hello, has there been any development on JMAP support in Dovecot? Also, I have noticed you planned to do some generic optimizations which could possibly make it easier to implement JMAP. What is status on that? https://dovecot.org/pipermail/dovecot/2021-March/121620.html Best Regards, David Klingenberg

4 5

NFS Config vs Ceph / GlusterFS
by dovecot＠ptld.com 15 Apr '22

15 Apr '22

Do all of the configuration considerations pertaining to using NFS on https://doc.dovecot.org/configuration_manual/nfs/ equally apply to using something like Ceph / GlusterFS? And if people wouldn't mind chiming in with which (NFS, Ceph & GlusterFS) they feel is better for maildir mail storage on dedicated non-container servers? Which is better for robustness / stability? Which is better for speed / performance? Thank you.

4 4

how to change the name of the dovecot pam file being used?
by Marc 15 Apr '22

15 Apr '22

Is there a way to configure the name of the pam file?

2 1

ssl_min_protocol appears to be ignored?
by Myriam Luce 14 Apr '22

14 Apr '22

Hi, I'm trying to enable TLS1.0 support for an old client. Per dovecot -n # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0-107-generic x86_64 Ubuntu 20.04.4 LTS ext4 # Hostname: In 10-ssl.conf, I have set ssl_min_protocol = TLSv1 (It doesn't show in dovecot -n, I suspect because it's equal to default value?) I restarted dovecot with systemctl. Then, from another machine, openssl s_client -connect zeserver.com:993 -tls1 fails with this output: CONNECTED(00000003) 140166917489984:error:141E70BF:SSL routines:tls_construct_client_hello:no protocols available:../ssl/statem/statem_clnt.c:1112: --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 0 bytes and written 7 bytes Verification: OK --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE No ALPN negotiated Early data was not sent Verify return code: 0 (ok) --- The same command with -tls1_2 works as intended (certificate printing, imap prompt). Am I forgetting something somewhere, or is this an actual bug?

3 2

Re: Dovecot and OAuth2 and gmail
by Richard 14 Apr '22

14 Apr '22

> Date: Wednesday, April 13, 2022 17:10:36 -0400 > From: Steve Litt <slitt(a)troubleshooters.com> > > Hi all, > > I'm not sure Dovecot has anything to do with this, but I'd rather > ask and know for sure. > > I do the following: > > Gmail IMAP=>fetchmail=>procmail=>Dovecot IMAP > > Then, I view my Dovecot hosted email with Claws-Mail. > > I understand that on May 31, 2022, current methods to access Gmail > IMAP will turn into pumpkins because of insistence on OAuth2. Do I > need to do anything to Dovecot to get ready for this Mass > Extinction Event? > > Do you think I'll need to dump fetchmail for something else? > While it's a little obtuse, a reading of: <https://support.google.com/accounts/answer/6010255#zippy=%2Cif-less-secure-…> specifically the "fix problems" / "use an app password" section, would seem to indicate that app passwords will continue to work for gmail access after May 30. What google is turning off is "third-party apps or devices which ask you to sign in to your Google Account using only your username and password", i.e., using your google login password with "less secure" 3rd party apps. So, you need to set up, and configure your application to use, app passwords.

2 1

Dovecot and OAuth2 and gmail
by Steve Litt 14 Apr '22

14 Apr '22

Hi all, I'm not sure Dovecot has anything to do with this, but I'd rather ask and know for sure. I do the following: Gmail IMAP=>fetchmail=>procmail=>Dovecot IMAP Then, I view my Dovecot hosted email with Claws-Mail. I understand that on May 31, 2022, current methods to access Gmail IMAP will turn into pumpkins because of insistence on OAuth2. Do I need to do anything to Dovecot to get ready for this Mass Extinction Event? Do you think I'll need to dump fetchmail for something else? Thanks, SteveT Steve Litt March 2022 featured book: Making Mental Models: Advanced Edition http://www.troubleshooters.com/mmm

1 0

Permissions and ownership on /dev/shm/dovecot
by doug 12 Apr '22

12 Apr '22

Hi, Environment: Dovecot 2.3.18 running on CentOS 7, mdbox, LDAP users I'm in the process of moving my mailboxes to NFS and moving with lock and index files in temp storage following instructions from https://doc.dovecot.org/configuration_manual/nfs. I set mail_location as: mail_location = mdbox:/mailstore/%u/mail:VOLATILEDIR=/dev/shm/dovecot/%u:LISTINDEX=/dev/shm/dovecot/%u/dovecot.list.index What I discovered is /dev/shm/dovecot is created by the initial user who accesses their mail from a client, and with permissions 700. This prevents subsequent users from creating their own index and lock files. # ls -l /dev/shm/dovecot total 0 drwx------ 2 mary users 60 Mar 25 10:00 mary Sample error message from maillog during mail delivery and from a dsync script. Mar 25 10:37:15 mailsrv1 dovecot: imap(doug)<19284><WKcX5gvbRe7AqFhA>: Error: mkdir(/dev/shm/dovecot/doug) failed: Permission denied (euid=1002(doug) egid=100(users) missing +x perm: /dev/shm/dovecot, dir owned by 97:100 mode=0700) dsync(test): Error: mkdir(/dev/shm/dovecot/test) failed: Permission denied (euid=2003(test) egid=100(users) missing +x perm: /dev/shm/dovecot, dir owned by 97:100 mode=0700) I couldn't locate documentation or discussions on how to set the ownership or permissions for /dev/shm/dovecot in the Dovecot configuration files. As a hack, I added this to /usr/libexec/dovecot/prestartscript. ! [[ -d /dev/shm/dovecot ]] && mkdir /dev/shm/dovecot chown dovecot:users /dev/shm/dovecot chmod 770 /dev/shm/dovecot This solved the problem, but left me wondering if I missed something obvious or if I am setting myself up for a problem later on, like with a Dovecot version upgrade. I could run these commands at bootup out of rc.local or a systemd script rather than customizing a Dovecot provided script. Is there a appropriate way of doing this that I missed? TIA, Doug

3 6

Re: Permissions and ownership on /dev/shm/dovecot
by doug 11 Apr '22

11 Apr '22

1 0

Set up per user sieve rules
by Austin Witmer 11 Apr '22

11 Apr '22

Hello! I am struggling to wrap my mind around how to set up sieve rules for my individual users on my mail server. I set up a global sieve script file at "/var/lib/dovecot/sieve/default.sieve” and that works great. My users maildirs are located at /mnt/volume1/mailserver/maildir/user. Do I need to create a sieve script file inside of that folder for sieve scripts to work on an individual basis? If so, what permissions will that script file need? Thanks in advance for your help! Austin Witmer

4 9