- dovecot - dovecot.org

Sieve vacation function sends auto-reply with generic From: Address
by Thomas Boroske 25 Sep '23

25 Sep '23

Good day to you all. I have a question regarding the dovecot sieve vacation function that I am unable to answer myself by reading the documentation. A while ago we moved our dovecot server to a newer system (and newer dovecot version 2.3.16 ). This worked mostly fine, except there is now an issue with the auto-reply emails send from sieve vacation scripts. While the sending of the auto reply generally works fine, the emails always appear to come from the "sysgroup(a)ida.ing.tu-bs.de" address rather than the original recipient of the message. This is bad since the recipient of the auto reply then has no idea who the person on vacation actually is (unless there is a name in the message body). The sieve scripts are managed by roundcube webmail, an example entry for a vacation rule looks like this: require ["vacation"]; # rule:[Vacation] if true { vacation :days 7 :subject "Nicht im Büro" :from "tbtest(a)ida.ing.tu-bs.de" "Ich bin nicht da!"; } This looks ok to me. The problem is that the "tbtest" address is not used in the generated reply, instead sysgroup(a)ida.ing.tu-bs.de is used as a from address for all recipients. Note that the sysgroup@ address appears nowhere in the dovecot config, but it does in /etc/postfix/sender-canonical like that: root(a)ida.ing.tu-bs.de sysgroup(a)ida.ing.tu-bs.de @ida.ing.tu-bs.de sysgroup(a)ida.ing.tu-bs.de @net.ida sysgroup(a)ida.ing.tu.bs.de The /etc/dovecot/conf.d/90-sieve.conf is mostly on default values, the remaining config settings are these: plugin { sieve = file:~/Maildir/sieve;active=~/Maildir/.dovecot.sieve sieve_extensions = +editheader #Send vacation auto responder with correct Address sieve_vacation_send_from_recipient = yes sieve_vacation_use_original_recipient = no } I have attached the output of "dovecot -n" below. Many thanks for any ideas on what could be the issue! Kind regards, Thomas -- Dipl. Inf. Thomas Boroske Institute of Computer and Network Engineering TU Braunschweig Hans-Sommer-Str. 66, D-38106 Braunschweig, Germany www.ida.ing.tu-bs.de

2 2

All list=yes namespaces must use the same separator - don't they?
by Francis Augusto Medeiros-Logeay 25 Sep '23

25 Sep '23

Hi, I am trying to configure shared mailboxes, so I enabled the acl and the imap_acl plugins. But I got the "All list=yes namespaces must use the same separator" error when I added this: namespace { type = shared #separator = # Mailboxes are visible under "shared/user@domain/" # %%n, %%d and %%u are expanded to the destination user. prefix = shared/%%u/ # Mail location for other users' mailboxes. Note that %variables and ~/ # expands to the logged in user's data. %%n, %%d, %%u and %%h expand to the # destination user's data. location = maildir:/var/mail/vmail/%%d/%%n:INDEX=/var/mail/vmail-index/index/%%d/%%n:INDEXPVT=/var/mail/vmail-index/index/%%d/%%n # Use the default namespace for saving subscriptions. subscriptions = no # List the shared/ namespace only if there are visible shared mailboxes. list = children } I don't have any separator configured explicitly, and when I see the config, the value is empty. So I don't really know what is the problem here. Any hints? Best, Francis -- Francis Augusto Medeiros-Logeay Oslo, Norway

1 0

expunge & sh error
by Данила Колесников 24 Sep '23

24 Sep '23

Hello! I would like to expunge Inbox mailbox every 60 days This mailbox is not in the config any I try to use "doveadm expunge". But my sh configs doesn't works: Fatal: Invalid search date parameter: 60d If I enter the contents of the config directly into the console - everything works correctly the same code in sh - ends with an error. It is bug or I do mistake? root@mail:~# doveconf -n # 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.16 (09c29328) # OS: Linux 5.15.0-84-generic x86_64 Ubuntu 22.04.2 LTS # Hostname: mail.onelec.ru auth_mechanisms = plain login auth_verbose = yes base_dir = /run/dovecot/ disable_plaintext_auth = no log_path = /var/log/dovecot.log login_greeting = Mail Delivery Agent mail_access_groups = mail mail_location = maildir:%h/mail/%d/%n mail_privileged_group = mail namespace { inbox = yes list = yes location = mailbox Archive { auto = subscribe autoexpunge = 30 days special_use = \Archive } mailbox "Deleted Messages" { auto = no autoexpunge = 1 weeks special_use = \Trash } mailbox Drafts { auto = subscribe autoexpunge = 1 weeks special_use = \Drafts } mailbox Junk { auto = no autoexpunge = 1 weeks special_use = \Junk } mailbox Sent { auto = subscribe autoexpunge = 90 days special_use = \Sent } mailbox "Sent Mail" { auto = no autoexpunge = 90 days special_use = \Sent } mailbox "Sent Messages" { auto = no autoexpunge = 90 days special_use = \Sent } mailbox Spam { auto = subscribe autoexpunge = 1 weeks special_use = \Junk } mailbox Trash { auto = subscribe autoexpunge = 1 weeks special_use = \Trash } prefix = separator = / type = private } passdb { args = scheme=MD5-CRYPT username_format=%n /etc/exim4/domains/%d/passwd driver = passwd-file } plugin { quota = maildir:User quota } protocols = imap pop3 service auth { extra_groups = mail unix_listener auth-client { group = mail mode = 0660 user = dovecot } user = dovecot } service stats { unix_listener stats-writer { group = mail mode = 0660 user = dovecot } } ssl_cert = </usr/local/hestia/ssl/certificate.crt ssl_cipher_list = ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:DHE-RSA-AES256-SHA256 ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = username_format=%n /etc/exim4/domains/%d/passwd driver = passwd-file } protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota } local_name mail.bearlion.ru { ssl_cert = </home/bearlion/conf/mail/bearlion.ru/ssl/bearlion.ru.pem ssl_key = # hidden, use -P to show it } local_name mail.onelec.ru { ssl_cert = </home/onelec/conf/mail/onelec.ru/ssl/onelec.ru.pem ssl_key = # hidden, use -P to show it } local_name mail.radiokey.ru { ssl_cert = </home/radiokey/conf/mail/radiokey.ru/ssl/radiokey.ru.pem ssl_key = # hidden, use -P to show it }

2 1

possible doveadm expunge bug
by Noel Butler 24 Sep '23

24 Sep '23

In my boredom, I was cleaning up my own public mailbox, do I really need lists/newsletters/forums posts from the 90's .. I think not, but lets still keep 5 years and expunge the rest... or try to... but expunge doesnt want too... This error or lack of action, occurs on any mailbox, as an example doveadm expunge -u my@email mailbox Lists.FreeRadius SAVEDBEFORE $ now for $, pick your value 5 y/Y for years doesn't appear to exist, so converting it into 30 odd weeks, 30w or 30W did nothing, but rough convert it down to days 1800D appears to do something - showing a delay before returning to command line, but in reality it does nothing, 1800, 1500, 1200, nothing, only when I drop it to 1000D does it actually work, which is not suitable, since I'd like to keep 5 years worth. Running doveadm -Dv exp... shows no errors just usual debug output about the base modules, quota stuff, and opening mailbox message followed then by user session closed, nothing at all anywhere that points to an error for executing this task, I did deliberately break it by altering the mailbox name to test and it rightfully did report the error the mailbox doesn't exist. I thought it might be size related, freeradius one of the smaller lists having about 150k to nanog the biggest with over 400k message, but I have others, like monthly newsletters with over 20yrs worth, but only 250 to 300 messages in their mailboxes that also fail, so it can't be barfing out at the size. Aki, any ideas? Or have I have hit a ridiculously low 1000D hard coded limit? ...and I know some troll will comment, so let me say yes I know I can and will likely have to use nix's "find" to actually cull them, but if doveadm has an expunge option, it should do what it is asked of it :) # doveconf -a # 2.3.20 (80a5ac675d): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.20 (149edcf2) # OS: Linux 5.15.117 x86_64 Slackware 15.0 ext4 - Yes I know 2.3.21 was released 2 days ago, but I'm not seeing anything in changelog/NEWS that's related -- Regards, Noel Butler This Email, including attachments, may contain legally privileged information, therefore at all times remains confidential and subject to copyright protected under international law. You may not disseminate this message without the authors express written authority to do so. If you are not the intended recipient, please notify the sender then delete all copies of this message including attachments immediately. Confidentiality, copyright, and legal privilege are not waived or lost by reason of the mistaken delivery of this message.

2 2

Dovecot OIDC question
by dovecot＠deeztek.net 23 Sep '23

23 Sep '23

Exploring the possible use of SSO using OIDC with Dovecot. Trying to understand the functionality of OIDC as it pertains to e-mail clients like Thunderbird, Outlook etc... My OIDC provider will authenticate a user by intercepting the connection attempt to the resource, present a login screen and after success it will redirect to the resource. When it comes to e-mail clients, how would that process work if at all? Thanks

1 0

2.3.21 broke XOAUTH authentication against Keycloak
by tj＠interseclab.org 23 Sep '23

23 Sep '23

I have Roundcube and Dovecot2 setup to authenticate against Keycloak using the XOAUTH2 method, as follows: introspection_url = https://[...]/realms/[...]/protocol/openid-connect/token/introspect introspection_mode = post username_attribute = email client_id = [...] client_secret = [...] tls_ca_cert_file = /etc/ssl/certs/ca-certificates.crt Since upgrading to 2.3.21 XOAUTH2 fails to authenticate with: dovecot: auth: Error: oauth2([...],[...],<[...]>): oauth2 failed: Introspection failed: No username returned WARN [org.keycloak.events] (executor-thread-45) type=INTROSPECT_TOKEN_ERROR, realmId=[...], clientId=null, userId=null, ipAddress=[...], error=client_not_found WARN [org.keycloak.events] (executor-thread-45) type=INTROSPECT_TOKEN_ERROR, realmId=[...], clientId=null, userId=null, ipAddress=[...], error=invalid_request, detail='Authentication failed.' Downgrading to 2.3.20 fixes the issue. I believe this change is to blame: lib-oauth2: Dovecot would send client_id and client_secret as POST parameters to the introspection server. These need to be optionally in Basic auth instead. Is there anything I should change in my Keycloak/Dovecot config or is this a bug?

2 1

Change location where .dovecot.lda-dupes* file/dir are created
by sahsanu 22 Sep '23

22 Sep '23

Hello, I'm using Dovecot 2.3.19.1 and Pigeonhole 0.5.19 on Debian 12.1 and I'm trying to use sieve extensions vacation and redirect but I'm having issues because of the creation of file /home/USER/.dovecot.lda-dupes and dir /home/USER/.dovecot.lda-dupes.locks The error in logs is pretty clear, lda doesn't have perms to create any of them because /home/USER/ is owned by root # namei -mo /home/user2/ f: /home/user2/ drwxr-xr-x root root / drwxr-xr-x root root home drwxr-xr-x root root user2 I'm using Hestia Control Panel and it chroot the users and that is the reason the user's home is owned by root. Mail users are virtual and the maildir home is /home/user2/mail/domain2.tld/postmaster (%h/mail/%d/%n) but the .dovecot.lda-dupes* file and dir are trying to use /home/user2/ instead of /home/user2/mail/domain2.tld/postmaster/ where they have perms and that should solve the issue. So, the question, is there any way to create .dovecot.lda-dupes* file/dir in virtual user's home %h/mail/%d/%n instead of user's home %h? or, is there any other solution/workaround where I don't need to change /home/USER/ owner/perms? If you want to check them, below are the logs and my dovecot conf. Appreciate your support. Best regards, sahsanu This is the sieve log using vacation extension: sieve: info: started log at 2023-09-21 13:17:06 +0200. error: msgid=<102288b1348f270d83363f71bb7bcc81(a)example.com>: vacation action: failed to check for duplicate vacation response: internal error occurred: refer to server log for more information. [2023-09-21 13:17:06]. This is the dovecot log using sieve vacation extension: Sep 21 13:17:06 lda(postmaster(a)domain2.tld)<2711250><SHdgDzImDGXSXikAElSLcQ>: Error: duplicate db: transaction: file_dotlock_open(/home/user2/.dovecot.lda-dupes) failed: Permission denied Sep 21 13:17:06 lda(postmaster(a)domain2.tld)<2711250><SHdgDzImDGXSXikAElSLcQ>: Error: duplicate db: transaction: Failed to lock /home/user2/.dovecot.lda-dupes.locks/duplicate.lock.ea887f77f1f61464f902ada5e7bfb022: mkdir_parents(/home/user2/.dovecot.lda-dupes.locks) failed: Permission denied This is the sieve log using redirect extension: sieve: info: started log at 2023-09-21 16:51:46 +0200. error: msgid=<8f1cdb9c-0997-4e32-a28f-65e5f3f8dca6.maildroid@localhost>: redirect action: failed to check for duplicate forward: internal error occurred: refer to server log for more information. [2023-09-21 16:51:46]. This is the dovecot log using sieve redirect extension: Sep 21 16:51:46 lda(postmaster(a)domain2.tld)<2785960><03j9DoJYDGWogioAElSLcQ>: Error: duplicate db: transaction: file_dotlock_open(/home/user2/.dovecot.lda-dupes) failed: Permission denied Sep 21 16:51:46 lda(postmaster(a)domain2.tld)<2785960><03j9DoJYDGWogioAElSLcQ>: Error: duplicate db: transaction: Failed to lock /home/user2/.dovecot.lda-dupes.locks/duplicate.lock.291440db1d5e4457ecf50cd02882634b: mkdir_parents(/home/user2/.dovecot.lda-dupes.locks) failed: Permission denied Dovecot conf: # 2.3.19.1 (9b53102964): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.19 (4eae2f79) # OS: Linux 6.1.0-12-amd64 x86_64 Debian 12.1 # Hostname: server.domain1.tld auth_mechanisms = plain login auth_verbose = yes base_dir = /run/dovecot/ log_path = /var/log/dovecot.log login_greeting = Mail Delivery Agent mail_access_groups = mail mail_attribute_dict = file:%h/mail/%d/%n/dovecot-attributes mail_location = maildir:%h/mail/%d/%n 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 imapflags notify imapsieve vnd.dovecot.imapsieve namespace { inbox = yes list = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox "Deleted Messages" { auto = no special_use = \Trash } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = no special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Mail" { auto = no special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } passdb { args = scheme=MD5-CRYPT username_format=%n /etc/exim4/domains/%d/passwd driver = passwd-file } plugin { imapsieve_mailbox1_before = file:/var/mail/sieve/report_spam.sieve imapsieve_mailbox1_causes = COPY APPEND imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/var/mail/sieve/report_ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * imapsieve_url = sieve://127.0.0.1:4190 quota = maildir:User quota sieve = file:~/mail/%d/%n/sieve;active=~/mail/%d/%n/dovecot.sieve sieve_extensions = +notify +imapflags sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_pipe_bin_dir = /etc/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms sieve_vacation_send_from_recipient = yes } protocols = imap sieve service auth { extra_groups = mail unix_listener auth-client { group = mail mode = 0660 user = dovecot } unix_listener auth-master { group = mail mode = 0660 user = dovecot } user = dovecot } service managesieve-login { inet_listener sieve { port = 4190 } } service stats { unix_listener stats-writer { group = mail mode = 0660 user = dovecot } } ssl_cert = </usr/local/hestia/ssl/certificate.crt ssl_cipher_list = ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:DHE-RSA-AES256-SHA256 ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = username_format=%n /etc/exim4/domains/%d/passwd driver = passwd-file } protocol lda { auth_socket_path = /var/run/dovecot/auth-master mail_plugins = " quota sieve" } protocol imap { mail_plugins = quota imap_quota imap_sieve } protocol sieve { managesieve_implementation_string = Dovecot Pigeonhole managesieve_max_line_length = 64 k } protocol pop3 { mail_plugins = quota } local_name domain1.tld { ssl_cert = </home/user1/conf/mail/domain1.tld/ssl/domain1.tld.pem ssl_key = # hidden, use -P to show it } local_name mail.domain1.tld { ssl_cert = </home/user1/conf/mail/domain1.tld/ssl/domain1.tld.pem ssl_key = # hidden, use -P to show it } local_name domain2.tld { ssl_cert = </home/user2/conf/mail/domain2.tld/ssl/domain2.tld.pem ssl_key = # hidden, use -P to show it } local_name mail.domain2.tld { ssl_cert = </home/user2/conf/mail/domain2.tld/ssl/domain2.tld.pem ssl_key = # hidden, use -P to show it }

2 4

State of wiki.dovecot.org?
by Sebastian Philipp 20 Sep '23

20 Sep '23

Hi all I just noticed that wiki.dovecot.org is no longer available, and instead redirects to a message stating that the documentation can now be found at doc.dovecot.org. However, there's was quite a lot of information on wiki.dovecot.org that is not available on doc.dovecot.org. One such example is the setup guide for a Dovecot Director cluster [1]. The "corresponding" page on doc.dovecot.org [2] even starts with the following sentence: > See http://wiki.dovecot.org/Director for more details. Are there plans to migrate such pages to doc.dovecot.org as well? If not, could the Wiki be restored? Of course it's possible to access the Wiki contents via web.archive.org, but that's rather cumbersome and slow. Thanks and regards Sebastian [1]: http://web.archive.org/web/20230212020603/https://wiki2.dovecot.org/Director [2]: https://doc.dovecot.org/configuration_manual/director_settings -- Adfinis AG Sebastian Philipp, Systems Engineer GPG Key ID: 0x8C920482C5CDA5FB Güterstrasse 86 | CH-4053 Basel Office: 061 500 31 31 www.adfinis.com

2 1

New Dovecot release?
by Taavi Ansper 20 Sep '23

20 Sep '23

Hi When will there be a new dovecot release. The 2.3.21 version borked our users with large amount of folders (i think over 255 folders) doveadm(REDACTED_USER): Error: /proc/self/status is larger than expected I can't find the debian bug report (or was it mentioned in this same mailing list), but somebody else has mentioned the same issue. I hope this gets fixed in the next version. -- Taavi Ansper taavi.ansper(a)cyber.ee

3 6

dovecot username with domain
by Michael Grant 20 Sep '23

20 Sep '23

I've been using dovecot using system usernames (my unix uname as my IMAP username). But today I tried New Outlook which requires the imap username match my email address. Is there some way to tell dovecot that username@host is the same as uname? (where username@host is an email address and uname is a unix login which might be completely different). Michael Grant

5 7