- dovecot - dovecot.org

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 21 Feb '24

21 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

Valid Docs for Dovecot with postgresql
by burkhardt＠konsultaner.de 19 Feb '24

19 Feb '24

Hi! The docs for dovecot with postgres are outdated and I somehow cannot connect from my dovecot instance to my postgresql database. I tried a lot but the debug output dosn't help me. What user is actually trying to connect to the postgresql? the dovecot user or root or the actual user from the connection config? I want to connect locally. Do I use password or md5 or peer with a map to connect? (tried all) simple console with pgsql command works fine. I found a couple of "How tos" but nothing helped. Are there any potential version conflict? I'm on 2.3.16 with postgresql 16. Thanks! Richi Hi! The docs for dovecot with postgres are outdated and I somehow cannot connect from my dovecot instance to my postgresql database. I tried a lot but the debug output dosn't help me. What user is actually trying to connect to the postgresql? the dovecot user or root or the actual user from the connection config? I want to connect locally. Do I use password or md5 or peer with a map to connect? (tried all) simple console with pgsql command works fine. I found a couple of "How tos" but nothing helped. Are there any potential version conflict? I'm on 2.3.16 with postgresql 16. Thanks! Richi

3 4

[Dovecot] doveadm delete folders ?
by Robert Schetterer 19 Feb '24

19 Feb '24

Hi , is there a feature like doveadm expunge savedbefore ... for imap folder delete ? -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

5 10

"Invalid uid in reply"
by J. B. Crawford 18 Feb '24

18 Feb '24

Hello, I am in the process of moving a previously working dovecot setup to a new authentication system. The identity management system, kanidm, uses a Pam module and NSS backend to provide user info. Authentication works normally on the machine, but Dovecot is having a lot of trouble, logging: Error: Invalid uid in reply Error: Invalid gid in reply I ran doveadm -D user jesse(a)waffle.tech as a test, and I see: Feb 17 21:58:33 doveadm(jesse(a)waffle.tech)<17666><>: Debug: auth-master: userdb lookup(jesse(a)waffle.tech): Started userdb lookup Feb 17 21:58:33 doveadm(jesse(a)waffle.tech)<17666><>: Debug: auth-master: conn unix:/run/dovecot/auth-userdb: Connecting Feb 17 21:58:33 doveadm(jesse(a)waffle.tech)<17666><>: Debug: auth-master: conn unix:/run/dovecot/auth-userdb (pid=17635,uid=0): Client connected (fd=9) Feb 17 21:58:33 doveadm(jesse(a)waffle.tech)<17666><>: Debug: auth-master: userdb lookup(jesse(a)waffle.tech): auth USER input: jesse system_groups_user=jesse uid=4123057063 gid=4123057063 home=/var/mail/jesse mail=maildir:/var/mail/jesse/Maildir Feb 17 21:58:33 doveadm(jesse(a)waffle.tech)<17666><>: Debug: auth-master: userdb lookup(jesse(a)waffle.tech): Finished userdb lookup (username=jesse system_groups_user=jesse uid=4123057063 gid=4123057063 home=/var/mail/jesse mail=maildir:/var/mail/jesse/Maildir) Feb 17 21:58:33 doveadm(jesse(a)waffle.tech)<17666><>: Error: Invalid uid in reply Feb 17 21:58:33 doveadm(jesse(a)waffle.tech)<17666><>: Error: Invalid gid in reply We can see the UID and GID in the debug output, but it comes out blank in the final info. I'm having a hard time finding what the cause could be, is it possible that these UID/GID values are too large? that's about the only thing I can think of right now. This is Dovecot 2.3.21 (47349e2482) on Fedora 39. Thanks, jc -- J. B. Crawford jesse(a)jbcrawford.us (575) 303-9001

2 2

long mail_location value formatting
by k v 17 Feb '24

17 Feb '24

Hello! The mail_location value with all the necessary keys can be quite long, for example: mail_location = mdbox:~/mdbox:VOLATILEDIR=/dev/shm/dovecot/volatile/%d/%n:LISTINDEX=/dev/shm/dovecot/listindex/%d/%n/dovecot.list.index:ALT=/var/dovecot-alt/%d/%n/mdbox When trying to split a value into multiple lines like: mail_location = \ mdbox:~/mdbox: \ VOLATILEDIR=/dev/shm/dovecot/volatile/%d/%n: \ LISTINDEX=/dev/shm/dovecot/listindex/%d/%n/dovecot.list.index: \ ALT=/var/dovecot-alt/%d/%n/mdbox according to the documentation https://doc.dovecot.org/configuration_manual/config_file/index.html#long-li…, each new line adds a whitespace, which breaks the value: doveadm config mail_location mail_location = mdbox:~/mdbox: VOLATILEDIR=/dev/shm/dovecot/volatile/%d/%n: LISTINDEX=/dev/shm/dovecot/listindex/%d/%n/dovecot.list.index: ALT=/var/dovecot-alt/%d/%n/mdbox doveadm mailbox list -u mail(a)example.com doveadm(mail(a)example.com): Error: Namespace '': Unknown setting: VOLATILEDIR Is it possible to split the value into multiple lines for better readability? Maybe add functionality to trim extra spaces when reading the mail_location value?

1 1

Doveadm on virtual users. Auth works but user don't
by jenawork＠iol.it 17 Feb '24

17 Feb '24

Hello All. I stumbled in a strange problem. I have some users stored in LDAP directory. They have uid in name.surname form and multiple mail attributes in the form of arbitraty(a)domain-n.it The Auth process works with virtual users on passdb (I can log with arbitraty(a)domain-1.it and arbitraty(a)domain-2.it) The usedb lookup works perfectly, and dovecot correctly creates the mailboxes in the form /home/domain/name.surname/arbitraty(a)domain-1.it/Maildir and /home/domain/name.surname/arbitraty(a)domain-2.it/Maildir The doveadm auth login arbitraty(a)domain-1.it command perfectly works, allowing the login to name.surname and the userdb lookup with the correct parameters. The doveadm user and the doveadm backup commands return "arbitraty(a)domain-1.it" not found I need it to migrate from an old cyrus imap to the new server Do someone have any idea? Thank you very much. (dovecot 2.3.19.1) Example: case 1: doveadm auth login "carlo.mor(a)sybill.it" Password: passdb: carlo.mor(a)sybill.it auth succeeded extra fields: user=carlo.mor original_user=carlo.mor(a)sybill.it userdb extra fields: carlo.mor uid=1001 gid=3001 home=/home/domain/carlo.mor/carlo.mor(a)sybill.it auth_mech=PLAIN auth_user=carlo.mor(a)sybill.it doveadm user "carlo.mor(a)sybill.it" userdb lookup: user carlo.mor(a)sybill.it doesn't exist field value

1 0