- dovecot - dovecot.org

v2.3.17 quota-dict related sql errors
by Pascal Volk 06 Feb '22

06 Feb '22

Hi there, I've updated Dovecot from v2.3.14 (cee3cbc0d) to v2.3.17 (e2aa53df5b). Right after the update, dovecot begun flooding the mail.log and PostgreSQL's log. My dict sql configuration: ,--[ .../dovecot/dovecot-dict-sql.conf.ext ]-- | map { | pattern = priv/quota/storage | table = userquota | username_field = uid | value_field = bytes | } | map { | pattern = priv/quota/messages | table = userquota | username_field = uid | value_field = messages | } `-- This worked for decades. Since the update dovecot is passing the user's email address, instead the user's UID to the query. And therefor I have lots of errors in the log files: see attached `mail.log' and `postgresql-14-main.log' excerpts. The `userquota' table looks like this: Table "public.userquota" Column | Type | Collation | Nullable | Default ----------+---------+-----------+----------+--------- uid | bigint | | not null | bytes | bigint | | not null | 0 messages | integer | | not null | 0 ... Foreign-key constraints: "fkey_userquota_uid_users" FOREIGN KEY (uid) REFERENCES users(uid) ON DELETE CASCADE (full database structure: https://bitbucket.org/pvo/vmm/src/vmm-0.7.0/pgsql/create_tables.pgsql) Regards, Pascal -- Ubuntu is an ancient African word meaning “I can’t install Debian.” -- unknown

3 4

Can't get it to work with conf.d files
by Ruben Safir 06 Feb '22

06 Feb '22

I am trying to set up dovecot to be a sasl auithenticator for postfix but it can't get it to function even on the most fundemental level /usr/bin/dovecot -a -F -c /etc/dovecot/dovecot.conf # 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/15-mailboxes.conf line 48: Unknown setting: service { namespace { namespace and before this, when I tried to get 10-ssl to work it said the same thing - unknonw setting Somewhere it is messed up in the syntax of the config files and I don't know where or how to run it down in a debugger. Here is the config file mail2:[root]:/etc/dovecot# grep "^#" -v /etc/dovecot/dovecot.conf|grep -v "^$" protocols = pop3 submission base_dir = /var/run/dovecot/ dict { #quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } !include conf.d/*.conf !include_try local.conf mail2:[root]:/etc/dovecot# -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and extermination camps, but incompatible with living as a free human being. -RI Safir 2013

1 0

Can't get it to work with conf.d files
by Ruben Safir 06 Feb '22

06 Feb '22

I am trying to set up dovecot to be a sasl auithenticator for postfix but it can't get it to function even on the most fundemental level /usr/bin/dovecot -a -F -c /etc/dovecot/dovecot.conf # 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/15-mailboxes.conf line 48: Unknown setting: service { namespace { namespace and before this, when I tried to get 10-ssl to work it said the same thing - unknonw setting Somewhere it is messed up in the syntax of the config files and I don't know where or how to run it down in a debugger. -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and extermination camps, but incompatible with living as a free human being. -RI Safir 2013

1 0

Received invalid SSL certificate: unable to get certificate CRL
by Laura Smith 06 Feb '22

06 Feb '22

I'm having a frustrating problem trying to use "doveadm sync" to pull mails off a server for migration purposes. # 2.3.17.1 (476cd46418): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.17.1 (a1a0b892) # OS: Linux 5.10.0-11-amd64 x86_64 Debian 11.2 I have tried both explicit "ssl_client_ca_dir = /etc/ssl/certs" and commenting it out (i.e. relying on OpenSSL default per the docs) I always get the same: Info: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Internet Security Research Group/CN=ISRG Root X1 (check ssl_client_ca_* se ttings?) Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Internet Sec urity Research Group/CN=ISRG Root X1 (check ssl_client_ca_* settings?) - disconnecting openssl s_client -starttls imap -servername $name -connect $name:143 is happy though: --- Certificate chain 0 s:CN = <REDACTED> i:C = US, O = Let's Encrypt, CN = R3 1 s:C = US, O = Let's Encrypt, CN = R3 i:C = US, O = Internet Security Research Group, CN = ISRG Root X1 2 s:C = US, O = Internet Security Research Group, CN = ISRG Root X1 i:O = Digital Signature Trust Co., CN = DST Root CA X3 --- --- No client certificate CA names sent Peer signing digest: SHA256 Peer signature type: RSA-PSS Server Temp Key: X25519, 253 bits --- SSL handshake has read 4954 bytes and written 412 bytes Verification: OK --- New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384 Server public key is 2048 bit Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE No ALPN negotiated Early data was not sent Verify return code: 0 (ok) ---

4 10

How to "activate" a mail directory?
by Peter Nabbefeld 06 Feb '22

06 Feb '22

Hello, as I need a mailbox locally only just for filtering, I've tried to manually create it (using Maildir as backend): 1. Created a folder in the appropriate location under /home/vmail with subfolders cur, new, tmp. 2. Set the same user:group as for the other folders (i.e. vmail:vmail). 3. Restarted Dovecot and Email-Client (Thunderbird). However, I cannot subscribe to the new folder. What am I missing here? Kind regards, Peter

2 2

Re: [EXT] AW: Re: Dovecot installation problem (libssl_iostream_openssl.so is not portable!)
by Aki Tuomi 04 Feb '22

04 Feb '22

I am not able to reproduce your issue, which makes it very hard to fix this.. Please keep responses on the list. Aki > On 04/02/2022 20:21 Dimitri <dimitri_emich(a)protonmail.com> wrote: > > > Hi Aki, > > yes, i even have reinstalled the whole OS, but still the same error. > > > Sent with ProtonMail Secure Email. > > ------- Original Message ------- > > Aki Tuomi <aki.tuomi(a)open-xchange.com> schrieb am Freitag, 4. Februar 2022 um 19:17: > > > On 04/02/2022 20:14 Dimitri dimitri_emich(a)protonmail.com wrote: > > > > No One? > > > > Nobody there who can help me? > > Did you ensure you cleaned up openssl 3.0 files before trying again? > > Aki

1 0

Dovecot installation problem (libssl_iostream_openssl.so is not portable!)
by Dimitri 04 Feb '22

04 Feb '22

No One? Nobody there who can help me?

2 1

Password Mismatch when connecting from Email Client
by Dr Francis Greaves 04 Feb '22

04 Feb '22

Dear All I have Postfix version 3.3.0, Dovecot Version 2.2.33.2 and PostfixAdmin version 3.3.10 using MySQL on a small device running Ubuntu VERSION="18.04.6 LTS (Bionic Beaver)" for my internal LAN Mail. I have a user mailto:admin@fsoft.nnet with a mailbox setup in PostfixAdmin with a password as 'Test75?' Everything is running fine, but I cannot get my Email Client Thunderbird to connect. I have setup the debugging to see that the correct password is being used, which it is, but I have this error: dovecot: auth-worker(26468): sql(mailto:admin@fsoft.nnet,10.6.10.10,<gB77wjLXGLsKBgoK>): Password mismatch (given password: Test75?) showing that dovecot disagrees!!! Why is this? Is it something to do with the permissions in PostfixAdmin? I did find https://serverfault.com/questions/696715/password-mismatch-in-dovecot-with-… where someone had the same problem. He just tried various passwords until he found one that worked!!!! I have not found any other post about this exact problem. Any help much appreciated. Regards Francis

7 12

Problem with chrooted user, manage-sieve plugin, lmtp and Thunderbird manage sieve extension: wrong symbolic link to active script
by Lev Serebryakov 04 Feb '22

04 Feb '22

I'm not sure, is it dovecot-managesieve plugin or Thunderbird extension. I have virtual users which are "chrooted" to their Maildirs, like this: user_query = SELECT '/usr/home/hosted/v-mail/%d/%n' AS chroot, \ '/' AS home, 'maildir:~/' AS mail, email.uid AS uid, email.gid AS gid FROM \ <snipped> It works perfectly. I'm using sieve and manage-sieve plugins for dovecot. `.dovecot.sieve` link is relative, like this: v-mail@onlyone:~/serebryakov.spb.ru/lev # ls -l .dovecot.sieve lrwxr-xr-x 1 root v-mail 17 Feb 4 18:19 .dovecot.sieve -> sieve/TOTAL.sieve It works. But when I deactivate/activate script via Manage sieve extension in Thunderbird link becomes absolute (with respect to chroot): v-mail@onlyone:~/serebryakov.spb.ru/lev # ls -l .dovecot.sieve lrwxr-xr-x 1 root v-mail 17 Feb 4 18:19 .dovecot.sieve -> /sieve/TOTAL.sieve and delivery agent (LMTP) start to complain: v-mail@onlyone:~/serebryakov.spb.ru/lev # grep .dovecot.sieve /var/log/dovecot.log Feb 04 18:18:42 lmtp(lev(a)serebryakov.spb.ru)<36054><iPQqEtJD/WHWjAAAlMIKZw>: Warning: sieve: file storage: Active sieve script symlink /usr/home/hosted/v-mail/serebryakov.spb.ru/lev/.dovecot.sieve is broken: Invalid/unknown path to storage (points to /sieve). I'm not sure, is it problem of manage-sieve plugin, lmtp sieve plugin or Thunderbird Sieve extension... -- // Black Lion AKA Lev Serebryakov

1 0

Feature request: use`openid_configuration_url` to guess OIDC endpoints and keys
by Éloi Rivard 04 Feb '22

04 Feb '22

Since version 2.3.16 dovecot has a openid_configuration_url [1] configuration parameter. Here is the documentation about this parameter: > Support for RFC 7628 OpenID Discovery (OIDC) can be achieved with > openid_configuration_url setting. Setting this causes Dovecot to report OIDC > configuration URL as openid-configuration element in error JSON. After reading the RFC I understand this brings some context to the error messages, but at first glance I would have expected more from this parameter. - Dovecot could read the userinfo_endpoint option [2] in the OIDC discovery endpoint to guess the IDP userinfo endpoint [3], and make the dovecot introspection_url parameter optional. - Dovecot could read the introspection_endpoint option [4] in the OIDC discovery endpoint to guess the IDP introspection endpoint [5], and make the dovecot tokeninfo_url parameter optional. RFC8414 is still a draft though, but there seems to be a convention about this parameter be called either token_introspection_endpoint or introspection_endpoint. Maybe both could be checked? - Dovecot could read the jwks_uri [4] option in the OIDC discovery endpoint to guess the IDP public keys, and make the local_validation_key_dict dovecot parameter optional. I would suggest to keep the values in introspection_url, tokeninfo_url and local_validation_key_dict if defined, but use the values found in the OIDC discovery endpoint by default. I think this would really help using OAUTH with dovecot. What do you think? [1] https://doc.dovecot.org/configuration_manual/authentication/oauth2/#openid-… [2] https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderMetadata [3] https://openid.net/specs/openid-connect-core-1_0.html#UserInfo [4] https://datatracker.ietf.org/doc/html/rfc8414#section-2 [5] https://datatracker.ietf.org/doc/html/rfc7662

1 0

Dovecot v2.3.18 released
by Aki Tuomi 04 Feb '22

04 Feb '22

Hi all! We are pleased to release v2.3.18 of Dovecot. Debian/Stretch support has now been dropped. CentOS 8 packages have been replaced with RedHat Enterprise Linux 8 packages. These should be compatible with all the various variants. https://dovecot.org/releases/2.3/dovecot-2.3.18.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.18.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Regards, Aki Tuomi Open-Xchange oy -- * Removed mail_cache_lookup_finished event. This event wasn't especially useful, but it increased CPU usage significantly. * fts: Don't index inline base64 encoded content in FTS indexes using the generic tokenizer. This reduces the FTS index sizes by removing input that is very unlikely to be searched for. See https://doc.dovecot.org/configuration_manual/fts/tokenization for details on how base64 is detected. Only applies when using libfts. * lmtp: Session IDs are now preserved through proxied connections, so LMTP sessions can be tracked. This slightly changes the LMTP session ID format by appending ":Tn" (transaction), ":Pn" (proxy connection) and ":Rn" (recipient) counters after the session ID prefix. + Events now have "reason_code" field, which can provide a list of reasons why the event is happening. See https://doc.dovecot.org/admin_manual/event_reasons/ + New events are added. See https://doc.dovecot.org/admin_manual/list_of_events/ + fts: Added fts_header_excludes and fts_header_includes settings to specify which headers to index. See https://doc.dovecot.org/settings/plugin/fts-plugin#plugin-fts-setting-fts-h… for configuration details. + fts: Initialize the textcat language detection library only once per process. This can reduce CPU usage if fts_languages setting has multiple languages listed and service indexer-worker { service_count } isn't 1. Only applies when using libfts. + lib-storage: Reduced CPU usage significantly for some operations that accessed lots of emails (e.g. fetching all flags in a folder, SORT, ...) + lib: DOVECOT_PREREQ() - Add micro version which enables compiling external plugins against different versions of Dovecot. + lmtp: Added new lmtp_verbose_replies setting that makes errors sent to the LMTP client much more verbose with details about why exactly backend proxy connections or commands are failing. + submission: Support implicit SASL EXTERNAL with submission_client_workarounds=implicit-auth-external. This allows automatically logging in when SSL client certificate is present. - *-login: Statistics were disabled if stats process connection was lost. - auth: Authentication master user login fails with SCRAM-* SASL mechanisms. - auth: With auth_cache_verify_password_with_worker=yes, passdb extra fields in the auth cache got lost. - doveadm: Fixed crash if zlib_save_level setting was specified, but zlib_save was unset. v2.3.15 regression. - doveadm: Proxying can panic when flushing print output. v2.3.17 regression. Fixes: Panic: file ioloop.c: line 865 (io_loop_destroy): assertion failed: (ioloop == current_ioloop) - doveadm: stats add --group-by parameter didn't work. - fts: Using email-address fts tokenizer could result in excessive memory usage with garbage email input. This could cause the indexer-worker processes to fail due to reaching the VSZ memory size limit. Only applies when using libfts. - imap: A SEARCH command timing out while fts returns indexes may timeout returning "NO [SERVERBUG]", while it should return "NO [INUSE]" instead. - imap: LIST-EXTENDED doesn't return STATUS for all folders. Sending LIST .. RETURN (SUBSCRIBED STATUS (...)) did not return STATUS for folders that are not subscribed when they have a child folder that is subscribed as mandated by IMAP RFCs. - imapc: Mailbox vsize calculation crashed with Panic: file index-mailbox-size.c: line 344 (index_mailbox_vsize_hdr_add_missing): assertion failed: (mails_left > 0) - indexer: If indexer-worker crashes, the request it was processing gets stuck in the indexer process. This stops indexing for the folder until indexer process is restarted. v2.3.14 regression. - indexer: Process was slowly leaking memory for each indexing request. - lib-event: Unnamed events were wrongly filtered out for event/metric filters like "event=abc OR something_independent_of_event_name". - lib-index: 64-bit big endian CPUs handle last_used field in dovecot.index.cache wrong. - lib-ssl-iostream: Fix buggy OpenSSL error handling without assert-crashing. If there is no error available, log it as an error instead of crashing. The previous fix for this in v2.3.11 was incomplete. Fixes Panic: file istream-openssl.c: line 51 (i_stream_ssl_read_real): assertion failed: (errno != 0) - lmtp: Out-of-memory issues can happen when proxying large messages to LMTP backend servers that accept the message data too slow. - master: HAProxy header parsing has read buffer overflow if provided header size is invalid. This happens only if inet_listener { haproxy=yes } is configured and only if the remote IP address is in haproxy_trusted_networks. - old_stats: Plugin kept increasing memory usage, which became noticeable with long-running imap sessions. - stats: Dynamically adding same metric multiple times causes multiple stats. - submission-login: Authentication does not accept OAUTH2 token (or other very long credentials) because it considers the line to be too long. - submission-login: Process can crash if HELO is pipelined with an invalid domain. - submission-proxy: Don't use SASL-IR if it would make the AUTH command line longer than 512 bytes. - submission: Service would crash if relay server authentication failed. - virtual: FTS search in a virtual folder could crash if there are duplicate mailbox GUIDs. This mainly happened when user had both INBOX and INBOX/INBOX folders and the namespace prefix was INBOX/. Fixes Panic: file hash.c: line 252 (hash_table_insert_node): assertion failed: (opcode == HASH_TABLE_OP_UPDATE) - virtual: If mailbox opening fails, the backend mailbox is leaked and process crashes when client disconnects. Fixes Panic: file mail-user.c: line 232 (mail_user_deinit): assertion failed: ((*user)->refcount == 1) - virtual: Searching headers in virtual folders didn't always use full-text search indexes, if fts_enforced=no or body.

2 1

posible guide
by d 03 Feb '22

03 Feb '22

2 1

Notification about branch and versioning changes
by Aki Tuomi 03 Feb '22

03 Feb '22

Dear subscribers, This year we will be releasing a new Dovecot major release. In preparations for this, we are doing some repository changes, which will affect you if you are using our git repositories. These changes will become effective after 14th of February. Following branch name changes are going to be implemented: - main => this is going to be the main branch in future - master => release-2.3 Note that Dovecot version number on main branch is going to change. The next major CE release will be 2.4.x. The change to a main branch and its version numbering also apply to Pigeonhole. We will also align Pigeonhole release version to match Dovecot, ie. the next major is 2.4.x and not 0.6. We will send more information about the upcoming major release as it progresses. Regards, Aki Tuomi Open-Xchange oy

1 0

Pigeonhole v0.5.18 released
by Aki Tuomi 03 Feb '22

03 Feb '22

Hi all! We are pleased to release v0.5.18 of Pigeonhole. Debian/Stretch support has now been dropped. CentOS 8 packages have been replaced with RedHat Enterprise Linux 8 packages. These should be compatible with all the various variants. https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.18.t… https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.18.t… Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Regards, Aki Tuomi Open-Xchange oy -- - duplicate: Users without a home directory can crash with Sieve when using duplicate database. v2.3.17 regression. - imapsieve: When mail was expunged when processing imapsieve events, a crash could occur. Fixes Panic: file mail-index-map.c: line 558 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0) - managesieve-login: Proxy didn't support forwarding the forward_* passdb fields. - redirect: Sieve would crash if redirect after keep-equivalent action failed. - sieve: Interpreter crashes when the Sieve index extension is used with index zero. - vnd.dovecot.filter: Envelope sender string may become corrupted when Sieve scripts are using vnd.dovecot.filter. This could end up corrupting mbox's From line and return wrong envelope sender string in

1 0

Re: dovecot Digest, Vol 212, Issue 56
by Steve 02 Feb '22

02 Feb '22

Greetings! A signed documentation you can find here: https://meta-calculator.com/tsaenauuovecumpttrqol/oieell-eiemnudai-mosboers… -----Original Message----- On Tuesday, 29 December 2020, 10:00 wrote: > Send dovecot mailing list submissions to dovecot(a)dovecot.org To subscribe > or unsubscribe via the World Wide Web, visit > https://dovecot.org/mailman/listinfo/dovecot or, via email, send a message > with subject or body 'help' to dovecot-request(a)dovecot.org You can reach > the person managing the list at dovecot-owner(a)dovecot.org When replying, > please edit your Subject line so it is more specific than "Re: Contents of > dovecot digest..." Today's Topics: 1. Re: .imap folders (Elise) 2. > dovecot+ldap with keepalive (Maciej Milaszewski) > ---------------------------------------------------------------------- > Message: 1 Date: Mon, 28 Dec 2020 17:16:30 +0100 From: Elise To: Aki Tuomi > Cc: Dovecot Mailing List Subject: Re: .imap folders Message-ID: > Content-Type: text/plain; charset=windows-1252; format=flowed Op 28-12-20 > om 12:56 schreef Aki Tuomi: > in your mail location, where you have > specified `mbox:~/...` > > We do not recommend using mbox mail format for > read-write, as the > support for that is limited. Noted, that did the > trick, thanks. /Elise ------------------------------ Message: 2 Date: Mon, > 28 Dec 2020 22:48:19 +0100 From: Maciej Milaszewski To: dovecot(a)dovecot.org > Subject: dovecot+ldap with keepalive Message-ID: Content-Type: text/plain; > charset=utf-8 Hi I have dovecot-2.36.4 (director +5 nodes) - backend to > auth is openldap+keepalived to second ldap For test i shutdown my ldap > server - keepalive? works perfectly VIP switched - ldapserach works ok (all > connect to second ldap) but I noticed strange dovecot behavior - some user > get "no response" or "waiting waiting" in dovecot i use: > auth_cache_negative_ttl = 5 mins auth_cache_size = 20 M auth_cache_ttl = 5 > mins service lmtp { ? inet_listener lmtp { ??? address = 127.0.0.1 > 10.0.100.4 ??? port = 24 ? } ? process_min_avail = 5 protocol lmtp { ? > auth_socket_path = director-userdb ? mail_plugins = quota expire notify > mail_log ? passdb { ??? args = proxy=y nopassword=y port=24 ??? driver = > static ??? name = ? } ? syslog_facility = local3 } in ldap server i have: > idletimeout???? 256 Any idea ? ------------------------------ Subject: > Digest Footer _______________________________________________ dovecot > mailing list dovecot(a)dovecot.org > https://dovecot.org/mailman/listinfo/dovecot ------------------------------ > End of dovecot Digest, Vol 212, Issue 56 > ****************************************

1 0

How to use virtual "All" and "Flagged" mailbox?
by A B 01 Feb '22

01 Feb '22

Hello, I'm trying to use the virtual "All" and "Flagged" mailboxes as described in 15-mailboxes.conf. The information here ( https://doc.dovecot.org/configuration_manual/virtual_plugin/) doesn't really touch on how to actually interact with the virtual mailboxes. My presumption is that when I mark an email message in the Inbox as FLAGGED (and I can confirm the \Flagged flag has been set) then I should then be able to either (1) see a copy of that message in the virtual.Flagged folder, or (2) when I use an imap command to get the message nums or whatever from the virtual.Flagged folder/mailbox, it should return the message that is flagged in the inbox as a result. Additionally, I'm presuming that for each new user that automatically gets added, I would have to create my own script that would add the dovecot-virtual file, dovecot doesn't do that on its own. When I view the user's directory I see these folders were created: --- [snippet] drwxrwx---. 5 vmail vmail 135 Jan 25 17:01 .virtual.All/ drwxrwx---. 5 vmail vmail 158 Jan 25 17:14 .virtual.Flagged/ [.virtual.Flagged]# ll total 20 drwxrwx---. 5 vmail vmail 158 Jan 25 17:14 ./ drwxrwx---. 20 vmail vmail 4096 Jan 25 17:33 ../ drwxrwx---. 2 vmail vmail 6 Jan 25 16:58 cur/ -rw-rw----. 1 vmail vmail 868 Jan 25 16:58 dovecot.index.cache -rw-rw----. 1 vmail vmail 384 Jan 25 17:01 dovecot.index.log -rw-rw----. 1 vmail vmail 51 Jan 25 17:01 dovecot-uidlist -rw-r--r--. 1 vmail vmail 8 Jan 25 17:14 dovecot-virtual -rw-rw----. 1 vmail vmail 0 Jan 25 16:58 maildirfolder drwxrwx---. 2 vmail vmail 6 Jan 25 16:58 new/ drwxrwx---. 2 vmail vmail 6 Jan 25 16:58 tmp [.virtual.Flagged]# cat dovecot-virtual * flagged --- Side note: This set-up uses the php-imap library to interact with Dovecot. Any help, or just concept of how the virtual/All virtual/Flagged directories work would be really appreciated. CONFIGURATION: dovecot -n # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf # OS: Linux 4.18.0-348.2.1.el8_5.x86_64 x86_64 CentOS Linux release 8.5.2111 xfs # Hostname: [DOMAIN REDACTED] auth_debug = yes auth_verbose = yes auth_verbose_passwords = yes first_valid_uid = 1000 lda_mailbox_autocreate = yes log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/home/vmail/%d/%n/Maildir mail_plugins = " quota" mbox_write_locks = fcntl namespace { location = virtual:/home/vmail/%d/%n/Maildir/virtual:LAYOUT=maildir++ prefix = virtual. separator = . type = private } namespace inbox { inbox = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } mailbox virtual.All { auto = create comment = All my messages special_use = \All } mailbox virtual.Flagged { auto = create comment = All my flagged messages special_use = \Flagged } prefix = INBOX. separator = . type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { driver = pam } plugin { quota = maildir:User quota quota_grace = 10%% quota_max_mail_size = 30M quota_rule = *:storage=100M quota_rule2 = INBOX.Trash:storage=+10M quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO } protocols = imap pop3 service auth-worker { user = root } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-master { mode = 0600 user = vmail } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } service imap-login { inet_listener imaps { port = 993 ssl = yes } } service pop3-login { inet_listener pop3s { port = 995 ssl = yes } } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { port = 12340 } } service stats { unix_listener stats-reader { group = vmail mode = 0660 user = vmail } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } } ssl = required ssl_cert = </etc/letsencrypt/live/[DOMAIN REDACTED]/fullchain.pem ssl_cipher_list = PROFILE=SYSTEM ssl_key = # hidden, use -P to show it userdb { args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes driver = static } userdb { driver = passwd } protocol lda { auth_socket_path = /var/run/dovecot/auth-master log_path = /home/vmail/dovecot-deliver.log postmaster_address = postmaster@[DOMAIN REDACTED] } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } protocol imap { mail_plugins = " quota imap_quota virtual" }

2 4

Quota: read how much diskspace is available?
by Hans van Zijst 01 Feb '22

01 Feb '22

Hi, I've been trying to get domain quotas to work for a while, but to no avail so far. Is there a way to let Dovecot simply check how much space is still available in a directory? I'm using GlusterFS as my mailstore, so I can configure quotas per directory. All I need is a way to let Dovecot check quota in a way like "df /var/vmail/<domain>". Kind regards, Hans

1 0

Set mail crypt private password with OAUTH?
by Max Kostikov 31 Jan '22

31 Jan '22

We currently use Dovecot and mailbox encryption via the mail-crypt-plugin. With standard password authentication, we set the value of the individual password to encrypt the contents of the userdb_mail_crypt_private_password mailbox in the SQL query. Is it possible to set the userdb_mail_crypt_private_password value when authenticating via OAUTH2 ? -- Best regards, Max Kostikov

3 16

PLAIN password scheme issue with {}
by Kris von Mach 31 Jan '22

31 Jan '22

Hello, Using PLAIN password scheme and a user having a password with {} for example {RnDR8DaD} causes the authentication to fail: auth-worker(85632): Error: conn unix:auth-worker (uid=143): auth-worker<3333>: sql(user(a)domain.com,123.45.68.78,<EBh0ouPWULvTF5AQ>): Unknown scheme RnDR8DaD Is there some sort of a workaround for this other than requesting user not to use {} at beginning and end of their password?

2 1

silly quesiton
by steph.mag220＠netcourrier.com 31 Jan '22

31 Jan '22

Hi, Up to now, I used PAM of each user in order to send and receive email. ( BTW, sending email, a use authentication was required and we used the login and passwd of the user on the system Now, for dovecot, I start to use MD5 passwrd.. and that sounds to be OK auth_mechanisms = plain login cram-md5 passdb { driver = passwd-file # Path for passwd-file. Also set the default password scheme. args = scheme=cram-md5 /etc/cram-md5.pwd } But changing the passwrd for the user1.. he can retrieve emails from dovecot, but cannot send anymore, because sending emails kept the old passwrd. ( using the PAM) 1) How can I says sendmail to use the same passwd file ( with MD5) than dovecot ? 2) Ideally, I would like to create virtual users for the same mailbox Is that possible ? like 2 files Users and PAsswrds pointing out the mailbox : maildir :/home/mailbox/user1 ex : user1(a)foo.com passwrd1 /home/mailbox/generic_mails and user2 passwrd2 home/mailbox/generic_mails How can I do that ? Thanks for your help

14 35

Re: dovecot Digest, Vol 225, Issue 73
by David Matthews 31 Jan '22

31 Jan '22

> 5. Re: can't authenticate (Christian Mack) hi Christian log with debugging resulting from a login attempt pasted at end - to try and make it more readable I removed everything in each line up to "dovecot:" At no point is a password revealed, even in hashed form. Should also say that the problem is identical on a backup laptop also running devuan 4; I'm not sure if I ever used that machine with dovecot before it was upgraded from devuan 3. Also I tried creating a new user to see if that account could authenticate; it cannot. >So you only can increase the logging in dovecot for authentication to >debugging. >auth_debug=yes ________________________________________________________________________________ auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/lib20_auth_var_expand_crypt.so auth: Debug: Read auth token secret from /run/dovecot/auth-token-secret.dat auth: Debug: auth client connected (pid=2467) auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured#011session=osv6w6PW4tB/AAAB#011lip=127.0.0.1#011rip=127.0.0.1#011lport=143#011rport=53474#011resp=<hidden> auth: Debug: pam(fred,127.0.0.1,<osv6w6PW4tB/AAAB>): Performing passdb lookup auth-worker(2469): Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth auth-worker(2469): Debug: Module loaded: /usr/lib/dovecot/modules/auth/lib20_auth_var_expand_crypt.so auth-worker(2469): Debug: conn unix:auth-worker (pid=2468,uid=118): Server accepted connection (fd=13) dovecot: auth-worker(2469): Debug: conn unix:auth-worker (pid=2468,uid=118): Sending version handshake auth-worker(2469): Debug: conn unix:auth-worker (pid=2468,uid=118): auth-worker<1>: Handling PASSV request auth-worker(2469): Debug: conn unix:auth-worker (pid=2468,uid=118): auth-worker<1>: pam(fred,127.0.0.1,<osv6w6PW4tB/AAAB>): Performing passdb lookup auth-worker(2469): Debug: conn unix:auth-worker (pid=2468,uid=118): auth-worker<1>: pam(fred,127.0.0.1,<osv6w6PW4tB/AAAB>): lookup service=dovecot auth-worker: Error: fatal error: failed to reserve page summary memory auth-worker(2469): Debug: conn unix:auth-worker (pid=2468,uid=118): auth-worker<1>: pam(fred,127.0.0.1,<osv6w6PW4tB/AAAB>): #1/1 style=1 msg=Password: auth-worker: Error: auth-worker: Error: runtime stack: auth-worker: Error: runtime.throw(0x7f3b2a6a8292, 0x25) auth-worker: Error: #011runtime/panic.go:1116 +0x74 fp=0x7f3b2a3b5b30 sp=0x7f3b2a3b5b00 pc=0x7f3b2a4d6474 auth-worker: Error: runtime.(*pageAlloc).sysInit(0x7f3b2a894428) auth-worker: Error: #011runtime/mpagealloc_64bit.go:80 +0x185 fp=0x7f3b2a3b5bc0 sp=0x7f3b2a3b5b30 pc=0x7f3b2a4ccb25 auth-worker: Error: runtime.(*pageAlloc).init(0x7f3b2a894428, 0x7f3b2a894420, 0x7f3b2a8aeb18) auth-worker: Error: #011runtime/mpagealloc.go:317 +0x77 fp=0x7f3b2a3b5be8 sp=0x7f3b2a3b5bc0 pc=0x7f3b2a4ca517 auth-worker: Error: runtime.(*mheap).init(0x7f3b2a894420) auth-worker: Error: #011runtime/mheap.go:743 +0x24b fp=0x7f3b2a3b5c10 sp=0x7f3b2a3b5be8 pc=0x7f3b2a4c74cb auth-worker: Error: runtime.mallocinit() auth-worker: Error: #011runtime/malloc.go:480 +0x109 fp=0x7f3b2a3b5c38 sp=0x7f3b2a3b5c10 pc=0x7f3b2a4acc09 auth-worker: Error: runtime.schedinit() auth-worker: Error: #011runtime/proc.go:563 +0x65 fp=0x7f3b2a3b5c90 sp=0x7f3b2a3b5c38 pc=0x7f3b2a4d9e25 auth-worker: Error: runtime.rt0_go(0x7ffd65c5e428, 0x2, 0x7ffd65c5e428, 0x7f3b2a3b6700, 0x7f3b2af22ea7, 0x0, 0x7f3b2a3b6700, 0x7f3b2a3b6700, 0xbe848d2612a1e5f4, 0x7ffd65c5cabe, ...) auth-worker: Error: #011runtime/asm_amd64.s:214 +0x129 fp=0x7f3b2a3b5c98 sp=0x7f3b2a3b5c90 pc=0x7f3b2a508c09 auth: Error: auth worker: Aborted PASSV request for fred: Worker process died unexpectedly auth: Debug: pam(fred,127.0.0.1,<osv6w6PW4tB/AAAB>): Finished passdb lookup dovecot: auth: Debug: auth(fred,127.0.0.1,<osv6w6PW4tB/AAAB>): Auth request finished auth-worker(2469): Fatal: master: service(auth-worker): child 2469 returned error 2 auth-worker(2471): Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth dovecot: auth-worker(2471): Debug: Module loaded: /usr/lib/dovecot/modules/auth/lib20_auth_var_expand_crypt.so auth-worker(2471): Debug: conn unix:auth-worker (pid=2468,uid=118): Server accepted connection (fd=13) auth-worker(2471): Debug: conn unix:auth-worker (pid=2468,uid=118): Sending version handshake auth: Debug: client passdb out: FAIL#0111#011user=fred#011code=temp_fail imap-login: Disconnected (auth service reported temporary failure): user=<fred>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, session=<osv6w6PW4tB/AAAB> ________________________________________________________________________________ >Perhaps you also want to set >auth_debug_passwords=yes >for getting the actual password in plain text. >(Don't forget to disable that afterwards!) ________________________________________________________________________________ auth-worker: Error: fatal error: failed to reserve page summary memory auth-worker: Error: auth-worker: Error: runtime stack: auth-worker: Error: runtime.throw(0x7fc7df48b292, 0x25) auth-worker: Error: #011runtime/panic.go:1116 +0x74 fp=0x7fc7df198b30 sp=0x7fc7df198b00 pc=0x7fc7df2b9474 auth-worker: Error: runtime.(*pageAlloc).sysInit(0x7fc7df677428) auth-worker: Error: #011runtime/mpagealloc_64bit.go:80 +0x185 fp=0x7fc7df198bc0 sp=0x7fc7df198b30 pc=0x7fc7df2afb25 auth-worker: Error: runtime.(*pageAlloc).init(0x7fc7df677428, 0x7fc7df677420, 0x7fc7df691b18) auth-worker: Error: #011runtime/mpagealloc.go:317 +0x77 fp=0x7fc7df198be8 sp=0x7fc7df198bc0 pc=0x7fc7df2ad517 auth-worker: Error: runtime.(*mheap).init(0x7fc7df677420) auth-worker: Error: #011runtime/mheap.go:743 +0x24b fp=0x7fc7df198c10 sp=0x7fc7df198be8 pc=0x7fc7df2aa4cb auth-worker: Error: runtime.mallocinit() auth-worker: Error: #011runtime/malloc.go:480 +0x109 fp=0x7fc7df198c38 sp=0x7fc7df198c10 pc=0x7fc7df28fc09 auth-worker: Error: runtime.schedinit() auth-worker: Error: #011runtime/proc.go:563 +0x65 fp=0x7fc7df198c90 sp=0x7fc7df198c38 pc=0x7fc7df2bce25 auth-worker: Error: runtime.rt0_go(0x7ffc6c109f48, 0x2, 0x7ffc6c109f48, 0x7fc7df199700, 0x7fc7dfd05ea7, 0x0, 0x7fc7df199700, 0x7fc7df199700, 0x1de9f8dc88f21cc1, 0x7ffc6c1085de, ...) auth-worker: Error: #011runtime/asm_amd64.s:214 +0x129 fp=0x7fc7df198c98 sp=0x7fc7df198c90 pc=0x7fc7df2ebc09 auth: Error: auth worker: Aborted PASSV request for fred: Worker process died unexpectedly auth: Debug: pam(fred,127.0.0.1,<RFd4WqPWytB/AAAB>): Finished passdb lookup auth: Debug: auth(fred,127.0.0.1,<RFd4WqPWytB/AAAB>): Auth request finished auth-worker(2282): Fatal: master: service(auth-worker): child 2282 returned error 2 auth-worker(2284): Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth auth-worker(2284): Debug: Module loaded: /usr/lib/dovecot/modules/auth/lib20_auth_var_expand_crypt.so auth-worker(2284): Debug: conn unix:auth-worker (pid=2281,uid=118): Server accepted connection (fd=13) auth-worker(2284): Debug: conn unix:auth-worker (pid=2281,uid=118): Sending version handshake auth: Debug: client passdb out: FAIL#0111#011user=fred#011code=temp_fail imap-login: Disconnected (auth service reported temporary failure): user=<fred>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, session=<RFd4WqPWytB/AAAB> -- David Matthews mail(a)dmatthews.org

2 1

Dovecot installation problem (libssl_iostream_openssl.so is not portable!)
by Dimitri 31 Jan '22

31 Jan '22

Hi there, i try to install dovecot from source with the following configuration: > ./configure --prefix=/test/core/dovecot --with-ssldir=/test/core/dovecot/tls the configuration runs fine with the following output at the end: > Install prefix . : /test/core/dovecot > File offsets ... : 64bit > I/O polling .... : epoll > I/O notifys .... : inotify > SSL ............ : yes (OpenSSL) > GSSAPI ......... : no > passdbs ........ : static passwd passwd-file shadow checkpassword > : -pam -bsdauth -ldap -sql > userdbs ........ : static prefetch passwd passwd-file checkpassword > : -ldap -sql > CFLAGS ......... : -std=gnu99 -g -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -mfunction-return=keep -mindirect-branch=keep -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/test/dep/openssl/include > SYSTEMD ........ : notify - /lib/systemd/system/dovecot.service > SQL drivers .... : > : -pgsql -mysql -sqlite -cassandra > Full text search : squat > : -lucene -solr But when i start to build (make) after a while i get the following error: > *** Warning: Linking the executable test-iostream-ssl against the loadable module > *** libssl_iostream_openssl.so is not portable! > libtool: link: gcc -std=gnu99 -g -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -mfunction-return=keep -mindirect-branch=keep -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/test/dep/openssl/include -o .libs/test-iostream-ssl test-iostream-ssl.o ./.libs/libssl_iostream_openssl.so ./.libs/libssl_iostream.a ../lib-test/.libs/libtest.a ../lib/.libs/liblib.a -L/test/dep/openssl/lib64 -lssl -lcrypto -ldl -Wl,-rpath -Wl,/test/core/dovecot/lib/dovecot > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `ERR_free_strings' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `ENGINE_cleanup' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_library_init' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `OBJ_cleanup' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `CRYPTO_cleanup_all_ex_data' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `OpenSSL_add_all_algorithms' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_CTX_set_tmp_rsa_callback' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `EVP_cleanup' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_load_error_strings' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_CTX_need_tmp_RSA' > collect2: error: ld returned 1 exit status > make[3]: *** [Makefile:655: test-iostream-ssl] Error 1 > make[3]: Leaving directory '/test/tmp/dovecot-2.3.17.1/src/lib-ssl-iostream' > make[2]: *** [Makefile:573: all-recursive] Error 1 > make[2]: Leaving directory '/test/tmp/dovecot-2.3.17.1/src' > make[1]: *** [Makefile:702: all-recursive] Error 1 > make[1]: Leaving directory '/test/tmp/dovecot-2.3.17.1' > make: *** [Makefile:546: all] Error 2 I've searched for the error and find some posts about set explicitly CPPFLAGS and LDFLAGS and something about missing shared libraries of openssl. My openssl have shared libraries (libcrypto.so libssl.so ...) and the explicit use of CPPFLAGS and LDFLAGS to my openssl hasn't changed anything I use Openssl 3.0 but i've tested also 1.1.1m and 1.1.1g for example, same error! Dovecot is the latest 2.3.17.1 My OS is Ubuntu 21.04 Can anyone help me with this please? Thanks!

2 1

Sync via ssh fails when ssl is active
by Johan 31 Jan '22

31 Jan '22

I have computers at two different locations and one computer running dovecot at each place. I sync my emails between these two servers using ssh and I haven't had any problems with this lately until I upgraded dovecot recently. I now get the following error at location "alfa" when trying to sync with dovecot at location "delta" Jan 20 16:13:09 doveadm: Error: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 16: ssl_cert: Can't open file /etc/letsencrypt/live/delta.oxyl.net/fullchain.pem: Permission denied Jan 20 16:13:09 dsync-local(johan(a)oxyl.net)<FWBVNQN86WH52iQA1AGq6A>: Error: read(vmail(a)192.168.119.12) failed: EOF (version not received) Jan 20 16:13:09 dsync-local(johan(a)oxyl.net)<FWBVNQN86WH52iQA1AGq6A>: Error: Remote command returned error 89: ssh -q -p 22 -o StrictHostKeyChecking=no -i /datastorage/epost/vmail/.ssh/id_ecdsa -lvmail 192.168.119.12 doveadm dsync-server -ujohan(a)oxyl.net Trying to sync from "delta" i get the same error but the domain is changed in the error-message to 'alfa.oxyl.net' I can read mail at both locations using STARTTLS. There is no error in dovecot.log when I restart the service. If I disable ssl and comment out ssl_cert/ssl_key in 10-ssl.conf I have no trouble performing sync between servers. If I run the ssh-command in the error-message as user vmail I get the same ssl-error as above. Any ideas how to solve this? /Johan Pålsson

4 6

Dsync replication - delayed replication (Sync lock)
by Daniel Botting 31 Jan '22

31 Jan '22

Hi, *Our setup:* Two Debian 10 machines that are setup to replicate mail between them, we have round robin DNS setup so a user can connect to either server. *What should happen:* Mail is delivered to either server and replicated across straight away to their mailbox on the other server so it does not matter which one they are connected to they will receive it fairly soon after delivery. *What actually happens:* In some instances the user will experience a delayed receipt of messages if they are not connected to the server that the message is initially delivered to, sometimes the delay is 5/10 minutes, we had a recent support ticket submitted where it was over an hour. Error message seen in mail.err: Sep 1 10:16:15 <host name> dovecot: dsync-local(<username>)<WELSGEERTl8FEAAAZJ7A9A>: Error: Couldn't lock /path/to/mailbox/.dovecot-sync.lock: fcntl(/path/to/mailbox/.dovecot-sync.lock, write-lock, F_SETLKW) locking failed: Timed out after 30 seconds (WRITE lock held by pid 3697) Process 3697 is dovecot/doveadm-server. *Doveconf -n output:* # 2.3.10.1 (a3d0e1171): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.10 (67bf5bd7) # OS: Linux 4.19.0-10-amd64 x86_64 Debian 10.5 # Hostname: <server hostname> auth_verbose = yes default_vsz_limit = 0 doveadm_password = # hidden, use -P to show it first_valid_gid = 8 first_valid_uid = 8 last_valid_gid = 8 last_valid_uid = 8 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_gid = 8 mail_location = maildir:~/Maildir mail_plugins = " notify replication" mail_uid = 8 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex im ap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext editheader imapfla gs 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-ldap.conf.ext driver = ldap } plugin { mail_replica = tcps:<server being replicated to>:<port being used> sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +editheader +imapflags } postmaster_address = postmaster@<domain address> protocols = " imap sieve pop3" replication_max_conns = 12 service aggregator { fifo_listener replication-notify-fifo { user = mail } unix_listener replication-notify { user = mail } } service auth { unix_listener /var/run/dovecot-exim-bridge { mode = 0660 user = Debian-exim } } service doveadm { inet_listener { port = <port being used for replication> ssl = yes } } service imap-login { inet_listener imap { port = 143 } } inet_listener imaps { port = 993 ssl = yes } process_limit = 512 process_min_avail = 4 service_count = 1 } service imap { process_limit = 1024 } service managesieve-login { inet_listener sieve { port = <sieve port> } process_min_avail = 1 service_count = 8 vsz_limit = 256 M } service managesieve { process_limit = 1024 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl = required ssl_cert = </path/to/ssl/cert/fullchain.pem ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL ssl_client_ca_dir = /etc/ssl/certs ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap override_fields = home=/var/mail/%u uid=mail gid=mail } protocol lda { mail_plugins = " notify replication sieve" } protocol imap { mail_max_userip_connections = 32 mail_plugins = " notify replication" } protocol sieve { mail_max_userip_connections = 10 managesieve_logout_format = bytes=%i/%o managesieve_max_line_length = 65536 } Kind regards Daniel

3 3

NTLM fails: dovecot: auth: Fatal: Unknown authentication mechanism 'NTLM'
by David Koski 31 Jan '22

31 Jan '22

After upgrading Debian to 11 I found Dovecot at version 2.3.13 (89f716dc2). Now auth method NTLM fails and is not even listed: # doveadm pw -l SHA1 SSHA512 SCRAM-SHA-256 BLF-CRYPT PLAIN HMAC-MD5 OTP SHA512 SHA DES-CRYPT CRYPT SSHA MD5-CRYPT PLAIN-MD4 PLAIN-MD5 SCRAM-SHA-1 SHA512-CRYPT CLEAR CLEARTEXT ARGON2I ARGON2ID SSHA256 MD5 PBKDF2 SHA256 CRAM-MD5 PLAIN-TRUNC SHA256-CRYPT SMD5 DIGEST-MD5 LDAP-MD5 /var/log/dovecot.log Jan 22 16:20:32 auth: Fatal: Unknown authentication mechanism 'NTLM' Jan 22 16:20:32 master: Error: service(auth): command startup failed, throttling for 2.000 secs Jan 22 16:20:34 auth: Fatal: Unknown authentication mechanism 'NTLM' Jan 22 16:20:34 master: Error: service(auth): command startup failed, throttling for 4.000 secs Jan 22 16:20:38 auth: Fatal: Unknown authentication mechanism 'NTLM' Jan 22 16:20:38 master: Error: service(auth): command startup failed, throttling for 8.000 secs Jan 22 16:20:46 auth: Fatal: Unknown authentication mechanism 'NTLM' Jan 22 16:20:46 master: Error: service(auth): command startup failed, throttling for 16.000 secs # doveconf -n # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.10.0-11-amd64 x86_64 Debian 11.2 # Hostname: imail.khmfdbyekekelj1rmytwnfh1bc.dx.internal.cloudapp.net auth_mechanisms = plain login ntlm debug_log_path = /var/log/dovecot-debug.log info_log_path = /var/log/dovecot-info.log log_path = /var/log/dovecot.log maildir_stat_dirs = yes 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 compat { alias_for = hidden = yes inbox = no list = no location = prefix = INBOX. separator = . } 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 = separator = . } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_plugins = " quota trash sieve" sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap sieve" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-client { mode = 0660 } } service stats { unix_listener stats-reader { group = vmail mode = 0660 user = vmail } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } } ssl_cert = </etc/letsencrypt/live/imail1.sutinen.com/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 { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = " quota trash sieve" postmaster_address = admin-kosmosisland.com(a)kosmosisland.com } protocol lda { mail_plugins = " quota trash sieve" } Regards, David Koski

3 4