February 2024 - dovecot

Fw: User-configurable time-based mail deletion in specific folders
by Rupert Gallagher 10 Mar '24

10 Mar '24

> Things like this should be done locally on the Mailclient (MUA), IMHO. If you are a company, then you must delete old e-mails automatically, by GDPR law. -------- Original Message -------- On Feb 21, 2024, 23:25, Steven Varco < dovecot.org(a)bbs.varco.ch> wrote: > Am 21.02.2024 um 21:25 schrieb Peter Reinhold : > > Hi > I have been wondering about if Dovecot has a feature that would allow users to > setup a rule for a given folder, that mails older than X days should be > deleted? > Or is > this something that would need to be done by an external script? Yes. It goes beyond of what I expect from an IMAP server. > I have looked a bit at autoexpunge, and while the basic feature looks to be > what I need, it doesn't seem to be configurable down to a specific folder on a > single user. Things like this should be done locally on the Mailclient (MUA), IMHO. Steven -- https://steven.varco.ch/ https://www.tech-island.com/ _______________________________________________ dovecot mailing list -- dovecot(a)dovecot.org To unsubscribe send an email to dovecot-leave(a)dovecot.org > Things like this should be done locally on the Mailclient (MUA), IMHO. If you are a company, then you must delete old e-mails automatically, by GDPR law. -------- Original Message -------- On Feb 21, 2024, 23:25, Steven Varco < dovecot.org(a)bbs.varco.ch> wrote: > Am 21.02.2024 um 21:25 schrieb Peter Reinhold : > > Hi > I have been wondering about if Dovecot has a feature that would allow users to > setup a rule for a given folder, that mails older than X days should be > deleted? > Or is > this something that would need to be done by an external script? Yes. It goes beyond of what I expect from an IMAP server. > I have looked a bit at autoexpunge, and while the basic feature looks to be > what I need, it doesn't seem to be configurable down to a specific folder on a > single user. Things like this should be done locally on the Mailclient (MUA), IMHO. Steven - - https://steven.varco.ch/ https://www.tech-island.com/ _______________________________________________ dovecot mailing list - - dovecot(a)dovecot.org To unsubscribe send an email to dovecot-leave(a)dovecot.org

6 8

JMAP status?
by Brad Koehn 09 Mar '24

09 Mar '24

Just wondering how/if JMAP support is coming along. It seems to offer major protocol advantages to a connection-oriented protocol like IMAP; I’m curious to see how it performs in the real world. Just wondering how/if JMAP support is coming along. It seems to offer major protocol advantages to a connection-oriented protocol like IMAP; I’m curious to see how it performs in the real world.

3 2

Bug/Warning not sure which
by Richard Shetron 04 Mar '24

04 Mar '24

Hello, My sysadmin and I spent a couple hours trying to figure out a POP3 problem that has worked for about 20 or so years. We run our own dns for sgeinc.com. I've always used mail.sgeinc.com as my incoming and outgoing server. At various times mail has been an alias for another machine. It's currently on the same address as sge.sgeinc.com. On the update forced on us on 2/22/24 or 2/23/24 it stopped working. It still works as an outgoing server but incoming POP3 it stopped working. It started working when I changed my incoming server to sge.sgeinc.com. You might want to look into it or not. We chased the initial problem to, we think, ssh-keygen in /usr/local/bin/ which was Not found but is there. Thanks root@sge:/usr/local/bin# dovecot -n # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0-172-generic x86_64 Ubuntu 20.04.6 LTS # Hostname: sge.sgeinc.com auth_mechanisms = plain login mail_location = maildir:~/Maildir 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 } protocols = " imap lmtp pop3" service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { group = postfix mode = 0660 user = postfix } } service pop3-login { inet_listener pop3 { port = 110 } } ssl = required ssl_cert = </etc/letsencrypt/live/sgeinc.com/fullchain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd }

5 6

better delivery mechanism to maildir?
by dovecot.org＠schildbach.de 03 Mar '24

03 Mar '24

As many of you probably are, I'm using Postfix together with Dovecot. Postfix delivers mail for my users by writing them directly to the filesystem (maildir). I wonder is there a better alternative? I'd like to separate the two services on different physical machines, so a shared filesystem isn't trivial any more. (I'd also like to stay with maildir storage and rather not do SQL or similar.) Can mail be delivered via IMAP for example? Or is there some other delivery protocol I don't know about that both Dovecot and Postfix support? Thanks!

4 7

seeking advice Error: Failed to lookup user
by noemi 28 Feb '24

28 Feb '24

Hi, I'm having some problems after activating the quota plugin: I followed the guide from the doc[0] but I'm having problems with some virtual user. I understand that,with my conf,the quota plugin check the limit of a user and then tell postfix to accept/discard the mail. i have some users under my main domain [conf in /etc/passwd] and some virtual user/domains [conf in virtusertable/virtdomains as files in postfix]. the virtual users use their local user for the login, so dovecot doesn't know they are virtual. I think the problem is here, because it is clear that the quota-status check is made by dovecot using the virtual user and not the local user[1]. understanding the problem doesn't help me in the resolution [other than burn everything and rebuild with a single management for local/virtual users using a db] but i will prefer a more soft approach. any help? my complete conf below[2] thanks, noemi [0] https://blog.sys4.de/postfix-dovecot-mailbox-quota-en.html [1] where the virtual user is mail(a)virtdomain.com and the local user is mail_virtdomain the check is done to user 'mail', thus returning a error: Nov 16 06:36:09 quota-status(other-user)<129776><OOwwMv+3VWXw+gEAKobZ8Q>: Error: Failed to lookup user mail(a)virtdomain.com: Mail access for users with UID 8 not permitted (see first_valid_uid in config file, uid from userdb lookup). [2] # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 6.1.0-10-amd64 x86_64 Debian 11.7 zfs # Hostname: mail-ng.pangea.org auth_mechanisms = plain login auth_username_format = %Ln default_client_limit = 3000 disable_plaintext_auth = no first_valid_uid = 8 log_path = /var/log/mail.log mail_location = maildir:/home/%n/Maildir mail_plugins = " quota" mail_privileged_group = mail 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 { driver = pam } plugin { quota = maildir:User quota quota_exceeded_message = Quota exceeded, please go to https://laweb.pangea.org/contacte/ for instructions on how to fix this. quota_grace = 10%% quota_max_mail_size = 100M quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full and cannot receive any more emails quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = file:~/sieve/;active=~/.dovecot.sieve sieve_user_log = /var/log/sieve.log sieve_vacation_send_from_recipient = yes } protocols = " imap lmtp sieve pop3" service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } service imap-login { process_limit = 1024 service_count = 100 } service imap { process_limit = 1024 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { process_limit = 1024 service_count = 0 } service pop3 { process_limit = 1024 } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { address = 127.0.0.1 port = 7777 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { mode = 0666 user = vmail } user = dovecot } ssl_cert = </etc/letsencrypt/live/mail-ng.pangea.org/fullchain.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } protocol imap { mail_max_userip_connections = 40 mail_plugins = " quota imap_quota" } protocol lmtp { mail_plugins = " quota sieve" }

1 0

Packages for Debian bookworm
by dovecot.org＠schildbach.de 25 Feb '24

25 Feb '24

Is there a reason there are no packages for recent Debian and Ubuntu versions? https://repo.dovecot.org/

2 1

Dovecot Authentication Protocol via SSL?
by dovecot.org＠schildbach.de 24 Feb '24

24 Feb '24

I'm trying to run the Dovecot Authentication Protocol (port 12345) [1] via SSL. Here is my non-SSL config: service auth { inet_listener { port = 12345 haproxy = yes } } Adding ssl=yes to the inner block doesn't seem to change anything, I can't connect via "openssl s_client -connect", for example. I do use SSL for IMAPS, so I know my general SSL configuration is fine and I've got a valid LetsEncrypt cert. Also, Postfix doesn't appear to offer any configuration in terms of running this protocol via SSL. Question: Does it even matter? I'm about to run this protocol over untrusted networks. Is it perhaps designed to handle this situation? I'm using SASL plain authentication. I'm obviously concerned about leaking passwords, but also about leaking usernames and activity logs in general. [1] https://doc.dovecot.org/3.0/developer_manual/design/auth_protocol/

1 0

Add tag support to 'Lua Director'
by William Edwards 24 Feb '24

24 Feb '24

Hi, There's a thread on this mailing list from 2022 called "The end of Dovecot Director?". I lost that email, hence the new conversation. Sorry about that. TL;DR: Is anyone else needing to migrate from Director interested in adding support for 2.x-style tags to the Lua script on https://doc.dovecot.org/3.0/configuration_manual/howto/director_with_lua/? Others on this list know Lua better than I. Background: Director is being removed from 2.4 (CE) / 3.x (Pro). After some notes from the community, the following manual entry popped up: https://doc.dovecot.org/3.0/configuration_manual/howto/director_with_lua/. It provides a Lua script that serves as a kind-of replacement for Director. It expects a list of backends, and maps users to a backend at connection time. The gotcha is in the last sentence: "There are no built-in tools in Dovecot to manage the database (such as adding backends, kicking users, monitoring backends, etc.). You need to build your own tooling." So, I built a CLI tool that provides the following functionality: - CRUD backends. - CRUD user-to-backend mappings. - Health-checking backends (replacing `poolmon`). - Swapping backends (move all users on backend X to backend Y). There's one to-do, though. Director had the concept of 'tags'. This is useful when one has multiple mail clusters, and users should be routed to a specific mail cluster. The Lua script does not know this concept. If a user does not have a mapping, it simply maps the user to any backend. Which could cause users to end up on the wrong backend. Therefore, it would be useful to add tag support to the Lua script: add `user_to_tags` and `tags` tables. Add a `tag_id` column to the `backends` table. Let the Lua script create a mapping to a backend with the same `tag_id` as the user entry in `user_to_tags`. Same logic as the `director_tag` passdb field (Director on 2.x). Alternatively, drop the 'tags' term: create a `user_to_backends` table with a JSON column taking multiple backend IDs (no foreign key relations = bad consistency). Alternatively, one could ensure that the Lua script never creates a mapping itself by manually creating it before the user connects. Pretty fragile in the real world, obviously. After this final to-do, I'd be happy to open-source my CLI. With kind regards, William Edwards

1 0

Help running dovecot with sieve
by pereirar2z＠gmail.com 23 Feb '24

23 Feb '24

Hi all, I'm running dovecot-pigeonhole-2.3.21-1.x86_64 & dovecot-2.3.21-1.x86_64 + roundcube 1.6.6 on my redhat server. Mailserver is working as expected with the exception fo the Filters. I've installed and configure everything that i'm aware of but unfortunatelly its not working. I think my installation is not loading this module: /usr/lib/dovecot/modules/lib90_sieve_plugin.so. But i have no idea what can I do more. Can you please help me? ###### # 2.3.21 (47349e2482): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.21 (f6cd4b8e) # OS: Linux 4.18.0-513.11.1.el8_9.x86_64 x86_64 Red Hat Enterprise Linux release 8.9 (Ootpa) xfs # Hostname: xxxxxx.xxxxx auth_debug = yes auth_verbose = yes disable_plaintext_auth = no first_valid_uid = 1000 listen = * log_path = /var/log/dovecot.log mail_debug = yes mail_location = maildir:/home/vmail/%d/%n/Maildir mail_plugins = acl mail_log notify mail_privileged_group = mail 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 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 { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_default = /var/lib/dovecot/sieve/default.sieve sieve_dir = ~/sieve sieve_global = /var/lib/dovecot/sieve/global/ } protocols = imap pop3 sieve lmtp service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 4 service_count = 1 vsz_limit = 64 M } service stats { unix_listener stats-reader { group = wheel mode = 0666 user = dovecot } unix_listener stats-writer { group = wheel mode = 0666 user = dovecot } } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = # hidden, use -P to show it userdb { args = uid=vmail gid=vmail home=/home/vmail/%d/%n/Maildir driver = static } verbose_ssl = yes protocol lmtp { mail_plugins = acl mail_log notify quota sieve } protocol sieve { info_log_path = /var/log/dovecot-sieve.log log_debug = category=sieve managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%i/%o managesieve_max_compile_errors = 5 managesieve_max_line_length = 64 k } (END ##### Can you guys see anything wrong here? Any help is highly appreciated! Thank-you

1 0

User-configurable time-based mail deletion in specific folders
by Peter Reinhold 22 Feb '24

22 Feb '24

Hi I have been wondering about if Dovecot has a feature that would allow users to setup a rule for a given folder, that mails older than X days should be deleted? Or is this something that would need to be done by an external script? I have looked a bit at autoexpunge, and while the basic feature looks to be what I need, it doesn't seem to be configurable down to a specific folder on a single user. -- Peter Reinhold Hi I have been wondering about if Dovecot has a feature that would allow users to setup a rule for a given folder, that mails older than X days should be deleted? Or is this something that would need to be done by an external script? I have looked a bit at autoexpunge, and while the basic feature looks to be what I need, it doesn't seem to be configurable down to a specific folder on a single user. -- Peter Reinhold

2 1