- dovecot - dovecot.org

email-address Tokenizer Splits Hyphenated Local-Parts, Causing Inaccurate FTS Search Results
by Daniel 11 Apr '25

11 Apr '25

I’m using Dovecot FTS with the flatcurve backend in a mailcow: dockerized setup. When searching for an email address with a hyphenated local-part (e.g., ma-g(a)example.com) the email-address tokenizer splits the local-part on hyphens, producing tokens like ma, g, and ma-g(a)example.com. This prevents searching for ma-g as a single term. With fts_flatcurve_substring_search = yes, searching for ma-g matches unrelated addresses containing ma (e.g., manager(a)example.com) leading to irrelevant results. Dovecot version: 2.3.21.1 (d492236fa0) Including only relevant part of dovecot config: plugin { fts = flatcurve fts_autoindex = yes fts_autoindex_exclude = \Junk fts_autoindex_exclude2 = \Trash fts_autoindex_max_recent_msgs = 999999 fts_tokenizers = generic email-address fts_tokenizer_email_address = maxlen=100 fts_tokenizer_generic = algorithm=simple maxlen=100 fts_flatcurve_substring_search = yes fts_languages = en es de ru fts_filters = normalizer-icu snowball stopwords fts_filters_en = lowercase snowball english-possessive stopwords fts_filters_ru = lowercase snowball stopwords fts_index_timeout = 300s } service indexer-worker { process_limit = 12 vsz_limit = 512 MB } Steps to Reproduce: Index an email with ma-g(a)example.com in the From field also index email contains "ma" and "g" in the From field. Check tokenization: doveadm fts tokenize -u user(a)example.com "ma-g(a)example.com" Output: ma g example com ma-g(a)example.com Search: doveadm search -u user(a)example.com FROM ma-g Results include manager(a)example.com due to ma matching. Expected Behavior: FROM ma-g should match only emails with ma-g(a)example.com, treating ma-g as a single term or exact local-part. Expected tokens: doveadm fts tokenize -u user(a)example.com "ma-g(a)example.com" Output: ma-g ma g example com ma-g(a)example.com Actual Behavior: The tokenizer splits ma-g into ma and g. Substring search matches "ma" or "g" in unrelated addresses (e.g., manager(a)example.com, greg(a)example.com) Without substring search, ma-g matches nothing unless searching the full address. Impact: Searching hyphenated local-parts for short email address local-parts is unreliable, especially for common fragments like ma, flooding results with irrelevant matches. Request: Add a configuration option, such as "fts_tokenizer_email_address_keep_hyphenated = yes|no" (default: no, for compatibility), to include the hyphenated local-part of an email address as an additional token. For example, with "yes", tokenizing "ma-g(a)example.com" would produce "ma-g", "ma", "g", "example", "com", and "ma-g(a)example.com". This allows searches for "FROM ma-g" to match emails with "ma-g(a)example.com" exactly, while preserving "ma" and "g" for substring searches. Consider "yes" as a future default, as including hyphenated local-parts aligns with RFC 5322 and user expectations for precise email searches, especially for common hyphenated addresses like "first-last(a)domain.com". If changing defaults, provide upgrade notes for users relying on the current token set. Is there any workaround to search hyphenated local-parts accurately? Best regards, Daniel Levin

1 0

Enable Full-Text search for attachments?
by Alexander Skwar 10 Apr '25

10 Apr '25

Hello Is it possible to enable a full-text search (FTS) for attachments (PDF, Text, Docx, …) using the open source dovecot server? If so, how would I do that? I've read https://doc.dovecot.org/2.3/configuration_manual/fts/ but that wasn't clear to me. Thanks, Alexander

2 2

2.4.1: oauth2 - Error: lua: db-lua: 'auth_passdb_lookup' is not a function
by Luigi Trovato 10 Apr '25

10 Apr '25

Hello, I just upgraded 2.4.0 to 2.4.1 and when trying to authenticate with oauth2 I have this error: auth-worker(lonestar(a)lonestar.it,127.0.0.1)<28029><vtg3yW0yBNh/AAAB>: request [11]: Error: lua: db-lua: 'auth_passdb_lookup' is not a function imap-login: Info: Logged in: user=<lonestar(a)lonestar.it>, method=XOAUTH2, rip=127.0.0.1, lip=127.0.0.1, mpid=28281, secured, session=<vtg3yW0yBNh/AAAB> I actually don't have any auth_passdb_lookup defined in the lua script, only auth_password_verify and auth_userdb_lookup, but it was previously working without errors -- Ciao, Luigi Hello, I just upgraded 2.4.0 to 2.4.1 and when trying to authenticate with oauth2 I have this error: auth-worker(lonestar(a)lonestar.it,127.0.0.1)<28029><vtg3yW0yBNh/AAAB>: request [11]: Error: lua: db-lua: 'auth_passdb_lookup' is not a function imap-login: Info: Logged in: user=<lonestar(a)lonestar.it>, method=XOAUTH2, rip=127.0.0.1, lip=127.0.0.1, mpid=28281, secured, session=<vtg3yW0yBNh/AAAB> I actually don't have any auth_passdb_lookup defined in the lua script, only auth_password_verify and auth_userdb_lookup, but it was previously working without errors -- Ciao, Luigi

1 1

2.4 Error: login_trusted_networks: Invalid network '::1'
by James 10 Apr '25

10 Apr '25

Good afternoon, With this line added to the default dovecot.conf: login_trusted_networks = ::1 I get this error: Apr 10 12:41:22 mailhost dovecot: [ID 702911 mail.info] master: Dovecot v2.4.1-4 (7d8c0e5759) starting up for imap, lmtp Apr 10 12:41:37 mailhost dovecot: [ID 702911 mail.error] imap-login: Error: getaddrinfo() failed: non-recoverable name resolution failure Apr 10 12:41:37 mailhost dovecot: [ID 702911 mail.error] imap-login: Error: login_trusted_networks: Invalid network '::1': user=<>, rip=2a02:1234:abcd:1::3, lip=2a02:1234:abcd:a::2, session=<sA2GEWsyNfIqAoAQ0BwAAQAAAAAAAACH> Version 2.4.1 Works with 2.3.21.1 and many versions before. It complains with any IPv6 address in login_trusted_networks.

1 0

crypt_private_key_file retrived from userdb/ldap doesn't work
by luis.neapolis＠gmail.com 10 Apr '25

10 Apr '25

Hello, if I try to retrieve crypt_private_key_file from userdb/ldap doesn't work, infact if I have: crypt_global_private_key main{ crypt_private_key_password=secret crypt_private_key_file=/path/to/file } all is ok. If I want to have: crypt_global_private_key main{ crypt_private_key_password=secret crypt_private_key_file= } userdb ldap { driver = ldap ..... fields { mail_crypt_global_private_key/main/crypt_private_key_file=inline:%{ldap:key} } } I have into logs: lmtp(134879): Fatal: Raw user initialization failed: mail_crypt_plugin: nuovo: Couldn't parse private key : Unknown key format I am sure that the key is correctly base64 encoded, infact if I pick the ldap value of %{ldap:key} and I decode base64 I have the pkey crypted key. Any suggestion?

2 4

Multiple namespaces with individual quota values from LDAP
by Andreas Oster 10 Apr '25

10 Apr '25

Hi all, I have successfully managed to get individual user qota for inboxes with values from LDAP working on Dovecot 2.4. I achieved this with the help of a posting from Aki Tuomi: <-- I'd recommend moving the storage_size out of quota "User Quota", since it's then easier to override: quota "User quota" { driver = count ... } quota_storage_size = 10G Aki --> However, in my setup I am using a separate namespace for mail "archiving" on a slower storage. I would like to also restrict the available storage space for users individually in this namespace. To achieve this I ideally would like to fetch the value from a different LDAP attribute. Can this be achieved with dovecot 2.4 ? In version 2.3 this was not a problem. Thank you very much for your kind help. Best regards Andraes

2 2

SQL userdb homedir
by Scott Q. 08 Apr '25

08 Apr '25

I am trying to use a stored procedure in sql for returning the various fields for the user. I'm concerned about what happens if the stored procedure fails to retrieve the homedir and other fields, for whatever reason. What should it return to notify dovecot of failure ? a single null field, all fields as null, empty result set ? Thank you I am trying to use a stored procedure in sql for returning the various fields for the user. I'm concerned about what happens if the stored procedure fails to retrieve the homedir and other fields, for whatever reason. What should it return to notify dovecot of failure ? a single null field, all fields as null, empty result set ? Thank you

1 0

Per-User quota with LDAP
by Damien Brémont 07 Apr '25

07 Apr '25

Hi all, I'm trying to setup Per-User quota with LDAP on dovecot 2.4.1 When I try to recalc quota for user, data is retrieved from LDAP server # doveadm quota recalc -u user dovecot: auth: Debug: conn unix:/run/auth-userdb (pid=34516,uid=0): Server accepted connection (fd=20) dovecot: auth: Debug: master in: USER#0111#011user#011protocol=doveadm dovecot: auth(user): Debug: : Performing userdb lookup dovecot: auth(user): Debug: ldap: Performing passdb lookup dovecot: auth(user): Debug: ldap: pass search: base=ou=user,dc=madrid-ias,dc=eu scope=subtree filter=(&(objectClass=posixAccount)(uid=user)) fields=uid,homeDirectory,uidNumber,gidNumber,quotaBytes dovecot: auth(user): Debug: ldap: result: uid=user gidNumber=8 homeDirectory=/home/users_LDAP/user uidNumber=10017 *quotaBytes=32000000* dovecot: auth(user): Debug: ldap: Finished passdb lookup dovecot: auth(user): Debug: : Finished userdb lookup dovecot: auth: Debug: userdb out: USER#0111#011user#011home=/home/users_LDAP/user#011uid=10017#011gid=8#011*quota_storage_size=32000000B* dovecot: auth: Debug: conn unix:/run/auth-userdb (pid=34516,uid=0): auth-master client: Disconnected: Connection closed (fd=20) (created 159 msecs ago, handshake 159 msecs ago) Same when an email is delivered: Debug: master userdb out: USER#0113606183937#011user#011home=/home/users_LDAP/user#011uid=10017#011gid=8#011*quota_storage_size=32000000B*#011auth_mech=PLAIN#011auth_token=8a4a9216541654643f33119dd9a280c672c#011local_name=127.0.0.1 But finally the quota limit is still the default value # doveadm quota get -u user Quota name Type Value Limit % User quota STORAGE 6294796 *10485760 60* User quota MESSAGE 29190 - 0 All my dovecot configuration is available below. About Postfix, dovecot-lda is called with -d option: mailbox_command = /usr/lib/dovecot/dovecot-lda -f "$SENDER" -d "$USER" If you have any idea. Thanks in advance for you help. Best Damien BTW, some "%" seem to be missing in the 2.4 documentation https://doc.dovecot.org/main/core/plugins/quota.html before {ldap:quotaBytes}B *Dovecot version:* 2.4.1-4+ubuntu24.04 *dovecot -n:* # OS: Linux 6.8.0-57-generic x86_64 Ubuntu 24.04.2 LTS ext4 # 4 default setting changes since version 2.4.0 dovecot_config_version = 2.4.0 auth_mechanisms = plain login default_client_limit = 12015 default_process_limit = 3003 default_vsz_limit = 256M dovecot_storage_version = 2.3.0 fts_autoindex = yes fts_autoindex_max_recent_msgs = 999 fts_search_add_missing = yes ldap_base = ou=MyOU,dc=domain,dc=com ldap_uris = ldap://localhost log_debug = category=auth mail_driver = maildir mail_home = /home/users_LDAP/%{user}/Maildir mail_path = /home/users_LDAP/%{user}/Maildir mail_plugins { quota = yes } protocols = imap pop3 sieve ssl_min_protocol = TLSv1.3 passdb ldap { fields { user = %{ldap:uid} userdb_gid = %{ldap:gidNumber} userdb_home = %{ldap:homeDirectory} userdb_quota_storage_size = %{ldap:quotaBytes}B userdb_uid = %{ldap:uidNumber} } bind = yes filter = (&(objectClass=posixAccount)(uid=%{user})) } namespace inbox { mail_driver = maildir mail_path = /home/users_LDAP/%{user}/Maildir hidden = no inbox = yes list = yes prefix = separator = / subscriptions = yes type = private mailbox Drafts { special_use = "\\Drafts" } mailbox Junk { special_use = "\\Junk" } mailbox Trash { special_use = "\\Trash" } mailbox Sent { special_use = "\\Sent" } mailbox "Sent Messages" { special_use = "\\Sent" } } service imap-login { inet_listener imap { } inet_listener imaps { port = 993 ssl = yes } } service pop3-login { inet_listener pop3 { } inet_listener pop3s { } } service submission-login { inet_listener submission { } inet_listener submissions { } } service lmtp { unix_listener lmtp { } } service imap { } service pop3 { } service submission { } service auth { unix_listener auth-userdb { mode = 0777 user = mail } unix_listener /var/spool/postfix/private/auth { mode = 0666 } } service auth-worker { } service dict { unix_listener dict { } } ssl_server { cert_file = /etc/letsencrypt/live/cert/fullchain.pem key_file = /etc/letsencrypt/live/cert/privkey.pem } protocol lda { mail_plugins { sieve = yes } } protocol imap { mail_max_userip_connections = 50 mail_plugins { imap_sieve = yes imap_quota = yes } } service managesieve-login { vsz_limit = 64M inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service managesieve { } quota "User quota" { driver = count storage_size = 10G quota_warning warn-95 { quota_storage_percentage = 95 execute quota-warning { args = 95 %{user} } } quota_warning warn-80 { quota_storage_percentage = 80 execute quota-warning { args = 80 %{user} } } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh user = dovecot unix_listener quota-warning { user = mail } } sieve_script personal { active_path = ~/.dovecot.sieve driver = file path = ~/sieve } Hi all, I'm trying to setup Per-User quota with LDAP on dovecot 2.4.1 When I try to recalc quota for user, data is retrieved from LDAP server # doveadm quota recalc -u user dovecot: auth: Debug: conn unix:/run/auth-userdb (pid=34516,uid=0): Server accepted connection (fd=20) dovecot: auth: Debug: master in: USER#0111#011user#011protocol=doveadm dovecot: auth(user): Debug: : Performing userdb lookup dovecot: auth(user): Debug: ldap: Performing passdb lookup dovecot: auth(user): Debug: ldap: pass search: base=ou=user,dc=madrid-ias,dc=eu scope=subtree filter=(&(objectClass=posixAccount)(uid=user)) fields=uid,homeDirectory,uidNumber,gidNumber,quotaBytes dovecot: auth(user): Debug: ldap: result: uid=user gidNumber=8 homeDirectory=/ home/users_LDAP/user uidNumber=10017 quotaBytes=32000000 dovecot: auth(user): Debug: ldap: Finished passdb lookup dovecot: auth(user): Debug: : Finished userdb lookup dovecot: auth: Debug: userdb out: USER#0111#011user#011home=/home/users_LDAP/ user#011uid=10017#011gid=8#011quota_storage_size=32000000B dovecot: auth: Debug: conn unix:/run/auth-userdb (pid=34516,uid=0): auth-master client: Disconnected: Connection closed (fd=20) (created 159 msecs ago, handshake 159 msecs ago) Same when an email is delivered: Debug: master userdb out: USER#0113606183937#011user#011home=/home/users_LDAP/ user#011uid=10017#011gid=8#011quota_storage_size=32000000B#011auth_mech=PLAIN#011auth_token=8a4a9216541654643f33119dd9a280c672c#011local_name=127.0.0.1 But finally the quota limit is still the default value # doveadm quota get -u user Quota name Type Value Limit % User quota STORAGE 6294796 10485760 60 User quota MESSAGE 29190 - 0 All my dovecot configuration is available below. About Postfix, dovecot-lda is called with -d option: mailbox_command = /usr/lib/dovecot/dovecot-lda -f "$SENDER" -d "$USER" If you have any idea. Thanks in advance for you help. Best Damien BTW, some "%" seem to be missing in the 2.4 documentation https:// doc.dovecot.org/main/core/plugins/quota.html before {ldap:quotaBytes}B Dovecot version: 2.4.1-4+ubuntu24.04 dovecot -n: # OS: Linux 6.8.0-57-generic x86_64 Ubuntu 24.04.2 LTS ext4 # 4 default setting changes since version 2.4.0 dovecot_config_version = 2.4.0 auth_mechanisms = plain login default_client_limit = 12015 default_process_limit = 3003 default_vsz_limit = 256M dovecot_storage_version = 2.3.0 fts_autoindex = yes fts_autoindex_max_recent_msgs = 999 fts_search_add_missing = yes ldap_base = ou=MyOU,dc=domain,dc=com ldap_uris = ldap://localhost log_debug = category=auth mail_driver = maildir mail_home = /home/users_LDAP/%{user}/Maildir mail_path = /home/users_LDAP/%{user}/Maildir mail_plugins { quota = yes } protocols = imap pop3 sieve ssl_min_protocol = TLSv1.3 passdb ldap { fields { user = %{ldap:uid} userdb_gid = %{ldap:gidNumber} userdb_home = %{ldap:homeDirectory} userdb_quota_storage_size = %{ldap:quotaBytes}B userdb_uid = %{ldap:uidNumber} } bind = yes filter = (&(objectClass=posixAccount)(uid=%{user})) } namespace inbox { mail_driver = maildir mail_path = /home/users_LDAP/%{user}/Maildir hidden = no inbox = yes list = yes prefix = separator = / subscriptions = yes type = private mailbox Drafts { special_use = "\\Drafts" } mailbox Junk { special_use = "\\Junk" } mailbox Trash { special_use = "\\Trash" } mailbox Sent { special_use = "\\Sent" } mailbox "Sent Messages" { special_use = "\\Sent" } } service imap-login { inet_listener imap { } inet_listener imaps { port = 993 ssl = yes } } service pop3-login { inet_listener pop3 { } inet_listener pop3s { } } service submission-login { inet_listener submission { } inet_listener submissions { } } service lmtp { unix_listener lmtp { } } service imap { } service pop3 { } service submission { } service auth { unix_listener auth-userdb { mode = 0777 user = mail } unix_listener /var/spool/postfix/private/auth { mode = 0666 } } service auth-worker { } service dict { unix_listener dict { } } ssl_server { cert_file = /etc/letsencrypt/live/cert/fullchain.pem key_file = /etc/letsencrypt/live/cert/privkey.pem } protocol lda { mail_plugins { sieve = yes } } protocol imap { mail_max_userip_connections = 50 mail_plugins { imap_sieve = yes imap_quota = yes } } service managesieve-login { vsz_limit = 64M inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service managesieve { } quota "User quota" { driver = count storage_size = 10G quota_warning warn-95 { quota_storage_percentage = 95 execute quota-warning { args = 95 %{user} } } quota_warning warn-80 { quota_storage_percentage = 80 execute quota-warning { args = 80 %{user} } } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh user = dovecot unix_listener quota-warning { user = mail } } sieve_script personal { active_path = ~/.dovecot.sieve driver = file path = ~/sieve }

2 2

Pigeonhole: (Sub-)Folders containing emojis not found
by Alexander Skwar 07 Apr '25

07 Apr '25

Hello $ dovecot --version 2.3.21.1 (d492236fa0) I've got the following rule defined:require ["regex","imap4flags","fileinto"];if anyof (address :regex :comparator "i;octet" "from" ".*@(bls\\.ch|redditmail\\.com|mail\\.tagesanzeiger\\.ch|link\\.ch|app\\.intervista\\.ch|news\\.outdooractive\\.com|spschweiz\\.ch|mail\\.landbote\\.ch|sofalesungen\\.ch)$") { fileinto "🗣 MLs Foren/🗞 Newsletter"; addflag "$label6"; stop;} There are also others, of course. In the Sieve log file “a(a)skwar.xyz.sieve.xn--log-9o0a, I find that the filter did not work: error: msgid=<a48c8bad-1d8f-4c29-a41d-e58f2dc2eed6(a)ind1s01mta1013.xt.local>: fileinto action: failed to store into mailbox '🗣 MLs Foren/🗞 Newsletter': Mailbox doesn't exist: 🗣 MLs Foren/🗞 Newsletter. I'm attaching the message as well. The folders DO exist — both parent “🗣 MLs Foren” and subfolder “🗞 Newsletter”. Why's that? I'm using Mailcow v2025-03a; Dovecot: 2.3.21.1 (d492236fa0). I created the folders and filters in SOGo webmail, which is shipped with Mailcow. Thanks, Alexander -- Alexander -- Complete contact details at https://a.skwar.xyz/ Hello $ dovecot --version 2.3.21.1 (d492236fa0) I've got the following rule defined: require ["regex","imap4flags","fileinto"]; if anyof (address :regex :comparator "i;octet" "from" ".*@ (bls\\.ch|redditmail\\.com|mail\\.tagesanzeiger\\.ch|link\\.ch|app\\.intervista\\.ch|news\\.outdooractive\\.com|spschweiz\\.ch|mail\\.landbote\\.ch|sofalesungen\\.ch)$") { fileinto "🗣 MLs Foren/🗞 Newsletter"; addflag "$label6"; stop; } There are also others, of course. In the Sieve log file “a(a)skwar.xyz.sieve.xn--log-9o0a, I find that the filter did not work: error: msgid=<a48c8bad-1d8f-4c29-a41d-e58f2dc2eed6(a)ind1s01mta1013.xt.local>: fileinto action: failed to store into mailbox '🗣 MLs Foren/🗞 Newsletter': Mailbox doesn't exist: 🗣 MLs Foren/🗞 Newsletter. I'm attaching the message as well. The folders DO exist — both parent “🗣 MLs Foren” and subfolder “🗞 Newsletter”. Why's that? I'm using Mailcow v2025-03a; Dovecot: 2.3.21.1 (d492236fa0). I created the folders and filters in SOGo webmail, which is shipped with Mailcow. Thanks, Alexander -- Alexander -- Complete contact details at https://a.skwar.xyz/

1 1

dovecot-pigeonhole 2.4.1 example config files are deprecated
by Peter Varkoly 05 Apr '25

05 Apr '25

dovecot-pigeonhole version 2.4.1 The delivered example configuration files 20-managesieve.conf 90-sieve.conf 90-sieve-extprograms.conf have the syntax of 2.3 and dovecot 2.4.1 can not parse these. Following error messages occurs: Fatal: Error in configuration file /etc/dovecot/conf.d/90-sieve-extprograms.conf line 9: Unknown section name: plugin doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-sieve.conf line 24: Unknown section name: plugin 20-managesieve.conf does not cause error messages but does not correspond to what is described under https://doc.dovecot.org/2.4.1/core/plugins/imap_sieve.html -- Peter Varkoly SW Engineering(Systems) SUSE Software Solutions Germany GmbH Frankenstraße 146 D-90461 Nürnberg T +49-(0)911-740 53 0 E <varkoly(a)suse.com> https://www.suse.com/ (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer dovecot-pigeonhole version 2.4.1 The delivered example configuration files 20-managesieve.conf 90-sieve.conf 90- sieve-extprograms.conf have the syntax of 2.3 and dovecot 2.4.1 can not parse these. Following error messages occurs: Fatal: Error in configuration file /etc/dovecot/conf.d/90-sieve- extprograms.conf line 9: Unknown section name: plugin doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-sieve.conf line 24: Unknown section name: plugin 20-managesieve.conf does not cause error messages but does not correspond to what is described under https://doc.dovecot.org/2.4.1/core/plugins/ imap_sieve.html -- Peter Varkoly SW Engineering(Systems) SUSE Software Solutions Germany GmbH Frankenstraße 146 D-90461 Nürnberg T +49-(0)911-740 53 0 E <varkoly(a)suse.com> https://www.suse.com/ (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer

1 0