- dovecot - dovecot.org

dovecot oauth
by la.jolie＠paquerette 27 Oct '21

27 Oct '21

Hello, I upgraded my servers from Debian Buster (v10) to Bullseye (v11). Before the upgrade, I had Roundcube / Dovecot working with LemonLdap (via OAuth). After the upgrade, i can't connect to Roundcube anymore. - roundcube (v1.5-rc) stayed the same - Dovecot upgraded from v1:2.3.4.1-5+deb10u6 to v1:2.3.13+dfsg1-2 I already discussed on the LemonLdap mailing list and the analysis was: "Seems like your app is not sending client_id and client_secret correctly then It can do that either as POST parameters or in the Authorization header" I downgraded Dovecot to Buster version (v1:2.3.4.1-5+deb10u6) and Roundcube / Dovecot are working again. What could have change between these 2 versions to have that error? My dovecot Oauth config: ---- debug = yes ## url for verifying token validity. Token is appended to the URL tokeninfo_url = https://auth.mydomain.name/oauth2/userinfo?access_token= ## introspection endpoint, used to gather extra fields and other information. introspection_url = https://auth.mydomain.name/oauth2/introspect ## How introspection is made, valid values are ## auth = GET request with Bearer authentication ## get = GET request with token appended to URL ## post = POST request with token=bearer_token as content introspection_mode = post ## TLS settings tls_ca_cert_file = /etc/ssl/certs/ca-certificates.crt ## username attribute in response (default: email) username_attribute = email ---- The error I found in the logs: ---- ==> nginx/portal.log <== 11.22.33.44 - - [25/Oct/2021:16:31:59 +0200] "POST /oauth2/introspect HTTP/1.1" 401 355 "-" "dovecot-oauth2-passdb/2.3.13" - ==> error <== Oct 25 16:31:59 XXX LLNG[413575]: [error] No authentication provided to get token, or authentication type not supported ==> mail.log <== Oct 25 16:31:59 XXX dovecot[1390]: auth: Debug: http-client: conn 11.22.33.44:443 [12]: Got 401 response for request [Req72: POST https://auth.mydomain.name/oauth2/introspect] Unauthorized (took 705 ms + 0 ms in queue) Oct 25 16:31:59 XXX dovecot[1390]: auth: Error: oauth2(yyyyy(a)mydomain.name,127.0.0.1,<bTQoOS7PRLV/AAAB>): oauth2 failed: Object doesn't begin with '{' ---- Thanks, Kenny

2 2

Doveadm fetch slow and 100%CPU with a specific message-id
by Alessio Cecchi 26 Oct '21

26 Oct '21

Hi, I'm using doveadm fetch in order to find the mailbox where a messagge is stored: doveadm fetch -u alessio(a)domain.com "mailbox" HEADER Message-ID '1234(a)domain.com' If the messagge-id is ... long more than? ... I don't know, the lookup is very very slow, here an example: with message-id 9c102380c557e7e146a33cb4b49ab802(a)cbweb.cecchi.net respons time: 3 secs with message-id kZ1ZoAa8QnsfZ64hTe9P3K0OOjL24xTq7vUMB3Qw3E(a)www.myxmail.com response time: 80 secs and java/solr use the 100% CPU Both messages are in the same folder (Trash) If I add -D to doveadm it stuck some seconds every time connect to Solr: Oct 25 18:30:08 doveadm(alessio(a)domain.com): Debug: http-client: queue http://127.0.0.1:8983: Connection to peer 127.0.0.1:8983 claimed request [Req1: GET http://127.0.0.1:8983/solr/dovecot/select?wt=xml&fl=uid,score&rows=26&sort=…] Oct 25 18:30:08 doveadm(alessio(a)domain.com): Debug: http-client: conn 127.0.0.1:8983 [1]: Claimed request [Req1: GET http://127.0.0.1:8983/solr/dovecot/select?wt=xml&fl=uid,score&rows=26&sort=…] Oct 25 18:30:08 doveadm(alessio(a)domain.com): Debug: http-client: request [Req1: GET http://127.0.0.1/solr/dovecot/select?wt=xml&fl=uid,score&rows=26&sort=uid+a…...: Sent header Oct 25 18:30:08 doveadm(alessio(a)domain.com): Debug: http-client: peer 127.0.0.1:8983: No more requests to service for this peer (1 connections exist, 0 pending) [...] Oct 25 18:30:08 doveadm(alessio(a)domain.com): Debug: http-client: queue http://127.0.0.1:8983 My dovecot version is 2.3.16 and Solr 7.7. Why? Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

4 9

Problem with shared after upgrade
by Yves 25 Oct '21

25 Oct '21

Hi, Old (and production) version : dovecot --version 2.1.9 New version : dovecot --version 2.3.16 (7e2e900c1a) Exactly same configuration, for shared configuration : namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = shared/%%u/ separator = / subscriptions = yes type = shared } But : On Old version, with my imap client (Thunderbird), I see : <account> / shared / <shared account> / INBOX <account> / shared / <shared account> / all the others folders On new version, I see : <account> / shared / <shared account> / all the others folders But not <account> / shared / <shared account> / INBOX I debug it, and seem to be OK : doveadm acl debug -u <account> shared/<shared account>/INBOX doveadm(<account>): Info: Mailbox 'INBOX' is in namespace 'shared/<shared account>/' doveadm(<account>): Info: Mailbox path: /home/dovecotmail/<shared account>/Maildir doveadm(<account>): Info: All message flags are shared across users in mailbox doveadm(<account>): Info: User <account> has rights: lookup read write write-seen write-deleted insert post expunge create delete admin doveadm(<account>): Info: Mailbox found from dovecot-acl-list doveadm(<account>): Info: User <shared account> found from ACL shared dict doveadm(<account>): Info: Mailbox shared/<shared account>/INBOX is visible in LIST And in debug log : Oct 23 12:35:01 imap(<account>)<18244><IrkoZALP4eRQfHif>: Debug: Mailbox shared/<shared account>: Rotated transaction log /home/dovecotmail/<account>/Maildir/shared/<shared account>/.INBOX/dovecot.index.log (seq=982, reset=no) Oct 23 12:35:01 imap(<account>)<18244><IrkoZALP4eRQfHif>: Debug: Mailbox shared/<shared account>: Recreated /home/dovecotmail/<account>/Maildir/shared/<shared account>/.INBOX/dovecot.index (file_seq=982) because: .log file format version 1.2 is too old Debug is ok for me ? Any idea ? Thanks

2 2

doveconf non-syntax check
by William Edwards 23 Oct '21

23 Oct '21

I use doveconf to check if my config is valid: root@unix:/etc/dovecot# doveconf <My config as stdout, as expected> root@unix:/etc/dovecot# echo $? 0 doveconf doesn't report any errors, as my config is syntactically valid. However, due to a non-syntax error, Dovecot doesn't start: root@unix:/etc/dovecot# ls /usr/local/snicerts/thisdoesntexist.key ls: cannot access '/usr/local/snicerts/thisdoesntexist.key': No such file or directory root@unix:/etc/dovecot# dovecot -F doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 4: ssl_key: Can't open file /usr/local/snicerts/thisdoesntexist.key: No such file or directory root@unix:/etc/dovecot# echo $? 89 Does Dovecot provide a config checker that checks more than just the syntax, but also issues like the one above? If not, maybe it's useful to add a 'quiet' option (i.e. no stdout) to doveconf. -- With kind regards, William Edwards

2 2

logging for doveadm replicator?
by Norman King 23 Oct '21

23 Oct '21

Hi. We have a doveadm replicator config set up to do 2 way sync of all users on our mail server. Currently running doveadm replicator status gives the following. ``` root@mail:~# doveadm replicator status Queued 'sync' requests 0 Queued 'high' requests 0 Queued 'low' requests 1 Queued 'failed' requests 0 Queued 'full resync' requests 677 Waiting 'failed' requests 4 Total number of known users 1577 ``` Is there anything i can do to get these full resyncs to happen faster? doveadm replicator dsync-status routinely shows most of the slots as not connected. Where can i start to either see logs of the replicator plugin to see if i can diagnose why it's so far behind? or is there a way to force these syncs to happen faster? Thanks. -- regards Norman King Compass Foundation sysadmin/tech support Phone, 856-974-5335 ext 221 support(a)compassfoundation.io Website <https://compassfoundation.io>

2 3

action based on IMAP ID fields
by Jörg Backschues 22 Oct '21

22 Oct '21

Hello, is it possible based on the information we get from the IMAP ID fields sent by a client to start some actions e.g. reject an IMAP client with a certain OS version? -- Kind Regards Jörg Backschues

3 2

Create a separated mailbox for archived mails
by Claudio Corvino 22 Oct '21

22 Oct '21

Hi, I have an MTA configured with Postfix that deliver email to an IMAP/LMTP Dovecot server version 2.3.4.1 configured to bind LDAP/AD for users. I would like to configure Dovecot to create another mailbox to archive mails of users to a separated NFS mount. Here is my /dovecot-ldap.conf/: [...] /ldap_version=3// //auth_bind = yes// //dn = XXX// //dnpass = XXX// //scope = subtree// //user_attrs = sAMAccountName=home=/mnt/mail-storage-dev/%$,=uid=501,=gid=501// //pass_attrs = sAMAccountName=user// //user_filter = (&(objectclass=person)(samaccountname=%n))// //pass_filter= (&(objectclass=person)(samaccountname=%n))/ [...] I think I will add another conf file, let's say /dovecot-ldap-archive.conf /using "url" as LDAP/AD filed to distinguish from normal users: [...] /ldap_version=3// //auth_bind = yes// //dn = XXX// //dnpass = XXX// //scope = subtree// //user_attrs = url=home=/mnt/mail-storage-archive/%$,=uid=501,=gid=501// //pass_attrs = url=user// //user_filter = (&(objectclass=person)(url=%n))// //pass_filter= (&(objectclass=person)(url=%n))/ [...] I then added to "test" user a "url" filed into Active Directory named /test-archive//, b/ut it's not working, when I bind Dovecot with: /doveadm user test-archive/ I receive: /field value// //userdb lookup: user test-archive doesn't exist/ With test user it works: /doveadm user test// //field value// //uid 501// //gid 501// //home /mnt/mail-storage-dev/test// //mail maildir:~/Maildir:INDEX=/var/indexes/test/ What I'm doing wrong? Thanks in advance! // -- *Claudio Corvino IT Systems Administrator*

4 10

local_name in dovecot for SNI and wildcard
by Alessio Cecchi 20 Oct '21

20 Oct '21

Hi, in dovecot configuration the options "local_name" can support wildcard domain name (es. *.mailserver.com)? This because we have a wildcard SSL certificate and I prefer to specifica a wildcard name instead of single. Is fine this? local_name *.mailserver.com { ssl_cert = </etc/dovecot/ssl/mailserver.com.pem ssl_key = </etc/dovecot/ssl/mailserver.com.key } And local_name can support multiple hostname in the same line? local_name pop.mailserver.com imap.mailserver.com { ssl_cert = </etc/dovecot/ssl/mailserver.com.pem ssl_key = </etc/dovecot/ssl/mailserver.com.key } Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

2 1

dovecot-lda -> lmtp server ?
by Scott Q. 17 Oct '21

17 Oct '21

I'm stuck with using Qmail which has no LMTP support, and thus I'm using dovecot-lda which has certain drawbacks. Has anyone found a way to direct dovecot-lda to deliver the mail to the LMTP server or any other way for Qmail to deliver the mail to the LMTP server directly ? Thanks!

2 1

Broken uidlist when using NFS on newer kernels
by Jeremy Hanmer 15 Oct '21

15 Oct '21

I know this has been reported in the past, but I think I have some useful new information on the problem. After an OS upgrade from Ubuntu Xenial (4.4.0 kernel) to Ubuntu Focal (5.4.0 kernel) and corresponding upgrade from Dovecot 2.2.27 to 2.3.7.2, we've started seeing broken uidlist files to an extent that's making larger mail boxes nearly unusable because the file is constantly being regenerated. I've also used the 2.3.16-2+ubuntu20.04 version distributed from dovecot.org and the behavior is unchanged. The environment consists of NFS mounts from a NetApp device, with a couple dozen MX servers receiving mail and about a hundred IMAP/POP servers. This is the exact error (note the blank after "invalid data"): Error: Mailbox INBOX: Broken file /mnt/morty/morty2/gravest/x15775549/Maildir/dovecot-uidlist line 373: Invalid data: I've been able to trigger the problem rather easily by piping an email to dovecot-lda in a loop and reading the resulting dovecot-uidlist file on a different server. What it shows is that occasionally we're seeing the last line of the file prepended with a number of null bytes equal to the line that's being written (for example, if the entry is "35322 :1633719038.M516419P3623238.pdx1-sub0-mail-mx202,S=2777,W=2832", we'll have it prepended by 69 null bytes). This then breaks the IMAP process' ability to read the file. My first thought was to extend the retry functionality so the imap proces makes more attempts to read the file when it detects a problem like this, but would love input from someone more familiar with the codebase.

3 4