- dovecot - dovecot.org

Dovecot FTS with Solrcloud
by Patrik Peng 10 Jul '20

10 Jul '20

Greetings We are looking into a solution to set up full text search for our multiple Dovecot instances. According to the Dovecot Wiki, fts_solr is one of the recommended plugins to use. Since we have more than just a few hundred mailboxes, I guess one Solr instance will not suffice. So I took a look at SolrCloud and set up a small cluster with three nodes and shards. I have no preceding experience with Solr or SolrCloud and now it's not clear to me, how dovecot can interact with this cluster. Has anyone ever tried to setup dovecot FTS with a SolrCloud cluster and is willing to share his findings? Regards Patrik

1 0

BUG report: dbox movealt doesn't move reverse (to default location)
by Vitalii 09 Jul '20

09 Jul '20

Hi, Here is the problem that occured: #sudo doveadm -D altmove -u vv(a)vito.pp.ua all works properly and moves all storage to alt dir. However, to move it back to default storage I add '-r' by manual: #sudo doveadm -D altmove -u vv(a)vito.pp.ua -r all That seems behave like the original command ignoring '-r'. my dovecot conf: # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-9-amd64 x86_64 Debian 10.4 # Hostname: qemu7.internetguru.ca auth_mechanisms = plain login disable_plaintext_auth = no imapc_features = rfc822.size fetch-headers imapc_host = imap.gmail.com imapc_port = 993 imapc_ssl = imaps imapc_user = %u listen = *,[::] log_timestamp = "%Y-%m-%d %H:%M:%S " mail_attachment_dir = /wd640/mdbox-att/%d/%n mail_max_userip_connections = 100 mail_prefetch_count = 20 mail_privileged_group = vmail passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { quota = dict:user::file:/var/vmail/%d/%n/.quotausage sieve = /var/vmail/%d/%n/.sieve sieve_max_redirects = 25 } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } user = root } service imap-login { client_limit = 1000 process_limit = 512 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } 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/postfix/smtpd.cert ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } protocol lda { mail_plugins = sieve quota postmaster_address = postmaster(a)some.ca } protocol lmtp { mail_plugins = quota sieve postmaster_address = postmaster(a)some.ca } I am using debian 10. P.S. I have not found much information about dbox attachments commands. Seems none needs them.

1 0

Urgent Help required
by Kishore Potnuru 09 Jul '20

09 Jul '20

Hi All, I request your help on this. I have 2 dovecot test servers (IMAP protocol) installed with the following configuration. ============= [root@devap01 ~]# cat /etc/redhat-* Red Hat Enterprise Linux Server release 6.10 (Santiago) [root@devap01 ~]# dovecot --version 2.0.9 [root@devap01 ~]# postconf | grep mail_version mail_version = 2.6.6 =============== I have another server also "devap02" with the same configuration. Couple of points/questions/queries here. 1. I know these servers are having old dovecot versions. I would like to upgrade to the latest versions. Could you please suggest the steps for upgrading to the latest version in redhat (step by step details are helpful please) . If I upgrade to the latest version, will there be any impact on the existing configuration/setup? 2. Now I have added these 2 servers behind the Load Balancer. Enabled 110/143 ports on the Load Balancer FQDN (test.pop3.testing.com) and opened the firewall ports. Here I configured IMAP settings from microsoft outlook to see the emails. I gave the Incoming Mail Server & Outgoing mail server as "test.pop3.testing.com". It is configured without errors in Outlook. But I see these 2 types issues (shared storage & individual storage) a) individual separate storage - When I send 10 emails to LB FQDN ( test.pop3.testing.com) the emails are going to 2 backend servers. But when i see the emails from Outlook inbox, it shows 5 emails from one server for some time. After sometime it shows other 5 emails in the inbox. But, I am not able to see all 10 emails at same time in my inbox. Please suggest how to fix this issue? In this scenario, I have separate individual storage in both the servers. b) common shared storage - I have tried a different scenario also. I also have one common NFS storage. So, I have configured that storage in both the servers. So when I sent 10 emails, I see all the 10 emails from both the servers as it is common shared storage. But, I am not getting those 10 emails delivered into my Outlook. I have made all the configuration correctly. Please suggest what is the mistake here. Dovecot.conf ========================================================= [root@devap01 ~]# cat /etc/dovecot/dovecot.conf disable_plaintext_auth = no listen = * log_path = /var/log/dovecot.log mail_location = maildir:/r3/mail/virtual/%d/%n/Maildir/ passdb { args = /etc/dovecot/passwd driver = passwd-file } pop3_uidl_format = %g protocols = imap pop3 ssl = yes ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = uid=vmail gid=vmail home=/r3/mail/virtual/%d/%n driver = static } mail_debug = no verbose_ssl = no ========================================================= Please help me here. Thanks, Kishore Potnuru

9 15

Dovecot - Xoauth2 - keycloak
by la.jolie＠paquerette 09 Jul '20

09 Jul '20

Hello, Still trying to make roundcube / Dovecot works with Keycloak. Dovecot can't seem to validate the access_token that Roundcube gave. ----- Jul 08 20:48:05 auth: Debug: http-client[1]: request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…] Sent header Jul 08 20:48:05 auth: Debug: http-client[1]: peer 11.22.33.44:443: No more requests to service for this peer (1 connections exist, 0 pending) Jul 08 20:48:05 auth: Debug: http-client[1]: conn 11.22.33.44:443 [0]: Got 404 response for request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…] (took 11 ms + 19 ms in queue) Jul 08 20:48:05 auth: Debug: oauth2(my.mail@whatever,::1,<Z2mDOfSpJJ8AAAAAAAAAAAAAAAAAAAAB>): oauth2: callback(0, Invalid token) ---- The access_token used by Dovecot is the right one. Dovecot also has the right login (my.mail@whatever) The Nginx and Keycloak logs show this: ---- - - [08/Jul/2020:23:25:18 +0200] "POST /auth/realms/test_saml/protocol/openid-connect/token HTTP/1.1" 200 3171 "-" "Guzzle/5.3.1 curl/7.64.0 PHP/7.3.14-1~deb10u1" - - [08/Jul/2020:23:42:05 +0200] "GET /auth/realms/test_saml/protocol/openid-connect/tokeneyJhbGciOiJFUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJEZzR2aWtndzN2MWVpQVgxMU10YkFIaXRaUnM2R2RlVzN3b3hGTTBpd1NnIn0.eyJleHAiOjE1OTQyNDE0NjUsImlhdCI6MTU5NDI0MTI4NSwiYXV0aF90aW1lIjoxNTk0MjM0ODI3LCJqdGkiOiI0NjRlZjc5NS0yZDYzLTQzYjktYjU4My1iYTY2MmFkMWRhYzUiLCJpc3MiOiJodHRwczovL3Nzby5udWJvLmNvb3AvYXV0aC9yZWFsbXMvdGVzdF9zYW1sIiwiYXVkIjoiYWNjb3VudCIsInN1YiI6IjhlZWNiODVjLTZlMDYtNGZhNC1iYTAwLTdlMGRlM2MyMWYxNCIsInR5cCI6IkJlYXJlciIsImF6cCI6InJvdW5kY3ViZSIsInNlc3Npb25fc3RhdGUiOiJmOTYyNWM3OS02OTM5LTRkZjEtOGM2Yi1hYWM5Y2EzYWJkY2YiLCJhY3IiOiIwIiwiYWxsb3dlZC1vcmlnaW5zIjpbImh0dHA6Ly9yYy5udWJvLmRvbWFpbmVwdWJsaWMubmV0Il0sInJlYWxtX2FjY2VzcyI6eyJyb2xlcyI6WyJvZmZsaW5lX2FjY2VzcyIsInVtYV9hdXRob3JpemF0aW9uIl19LCJyZXNvdXJjZV9hY2Nlc3MiOnsiYWNjb3VudCI6eyJyb2xlcyI6WyJtYW5hZ2UtYWNjb3VudCIsIm1hbmFnZS1hY2NvdW50LWxpbmtzIiwidmlldy1wcm9maWxlIl19fSwic2NvcGUiOiJvcGVuaWQgbWljcm9wcm9maWxlLWp3dCBwcm9maWxlIGVtYWlsIG9mZmxpbmVfYWNjZXNzIiwidWlkIjoicXVlbmVubmkiLCJ1cG4iOiJxdWVuZW5uaSIsImVtYWlsX3ZlcmlmaWVkIjpmYWxzZSwibmFtZSI6Iktlbm55IExvdXZlYXV4IExvdXZlYXV4IiwiZ3JvdXBzIjpbIm9mZmxpbmVfYWNjZXNzIiwidW1hX2F1dGhvcml6YXRpb24iXSwicHJlZmVycmVkX3VzZXJuYW1lIjoicXVlbmVubmkiLCJnaXZlbl9uYW1lIjoiS2VubnkgTG91dmVhdXgiLCJmYW1pbHlfbmFtZSI6IkxvdXZlYXV4IiwiZW1haWwiOiJrZW5ueUBudWJvLnNpdGUifQ.TsUBiZ5nSTuA9ojr6bao5NQUHeNRmcYQZsC95rrhYca9FsFG4xG8mT53X9eOSNEqzRMJiPHaDuAh-3Bq8Rjdlg HTTP/1.1" 404 1465 "-" "dovecot-oauth2-passdb/2.3.4.1" DEBUG [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-2) RESTEASY002315: PathInfo: /realms/test_saml/protocol/openid-connect/tokeneyJhbGciOiJFUzI1N iIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJEZzR2aWtndzN2MWVpQVgxMU10YkFIaXRaUnM2R2RlVzN3b3hGTTBpd1NnIn0.eyJleHAiOjE1OTQyNDQ3MDQsImlhdCI6MTU5NDI0NDUyNCwiYXV0aF90aW1lIjoxNTk0MjQ0MzQ3LCJqdGk iOiIyYTg3MjQ3NS0zMGMxLTRmMDctODg5Ny04YmQ4OTJjMGI1MjEiLCJpc3MiOiJodHRwczovL3Nzby5udWJvLmNvb3AvYXV0aC9yZWFsbXMvdGVzdF9zYW1sIiwiYXVkIjoiYWNjb3VudCIsInN1YiI6IjhlZWNiODVjLTZlMDYtNGZhN C1iYTAwLTdlMGRlM2MyMWYxNCIsInR5cCI6IkJlYXJlciIsImF6cCI6InJvdW5kY3ViZSIsInNlc3Npb25fc3RhdGUiOiJmMjY0OTQyMy0xNmZkLTQzMTgtYTVkYy04NWJhNmU3YTQ4MWYiLCJhY3IiOiIwIiwiYWxsb3dlZC1vcmlnaW5 zIjpbImh0dHA6Ly9yYy5udWJvLmRvbWFpbmVwdWJsaWMubmV0Il0sInJlYWxtX2FjY2VzcyI6eyJyb2xlcyI6WyJvZmZsaW5lX2FjY2VzcyIsInVtYV9hdXRob3JpemF0aW9uIl19LCJyZXNvdXJjZV9hY2Nlc3MiOnsiYWNjb3VudCI6e yJyb2xlcyI6WyJtYW5hZ2UtYWNjb3VudCIsIm1hbmFnZS1hY2NvdW50LWxpbmtzIiwidmlldy1wcm9maWxlIl19fSwic2NvcGUiOiJvcGVuaWQgbWljcm9wcm9maWxlLWp3dCBwcm9maWxlIGVtYWlsIG9mZmxpbmVfYWNjZXNzIiwidWl kIjoicXVlbmVubmkiLCJ1cG4iOiJxdWVuZW5uaSIsImVtYWlsX3ZlcmlmaWVkIjpmYWxzZSwibmFtZSI6Iktlbm55IExvdXZlYXV4IExvdXZlYXV4IiwiZ3JvdXBzIjpbIm9mZmxpbmVfYWNjZXNzIiwidW1hX2F1dGhvcml6YXRpb24iX SwicHJlZmVycmVkX3VzZXJuYW1lIjoicXVlbmVubmkiLCJnaXZlbl9uYW1lIjoiS2VubnkgTG91dmVhdXgiLCJmYW1pbHlfbmFtZSI6IkxvdXZlYXV4IiwiZW1haWwiOiJrZW5ueUBudWJvLnNpdGUifQ.TsUBiZ5nSTuA9ojr6bao5NQUHe NRmcYQZsC95rrhYca9FsFG4xG8mT53X9eOSNEqzRMJiPHaDuAh-3Bq8Rjdlg --- Dovecot does a GET request where the access_token is directly attached to the 'tokeninfo_url' option. Is that the correct/normal way? Shouldn't it be a POST with data passed as params? Or is it Keycloak that should accept that request? Thanks Kenny

2 1

Re: Urgent Help required
by Kishore Potnuru 08 Jul '20

08 Jul '20

Hi, Our organisation has dependencies. There is a separate team/department who creates the servers for us. When they build a new RHEL system, the system will come up with various in-house softwares/tools. Those tools are not compatible as of now with RHEL8. So, our organisation is going with redhat 7.7 only as of today which is supported for all in-house tools also. This is my current situation: 1) I have 2 test servers which are loaded with the following configuration. ============= [root@devap01 ~]# cat /etc/redhat-* Red Hat Enterprise Linux Server release 6.10 (Santiago) [root@devap01 ~]# dovecot --version 2.0.9 [root@devap01 ~]# postconf | grep mail_version mail_version = 2.6.6 =============== So, I would like to install the max possible dovecot version on the above servers for the testing purpose. I would like to implement the HA/Resilience with those 2 servers. I have shared storage and individual storage in this environment. But I am seeing some issues with both of them ( I explained details in my first email thread). please see if you can help. 2) If it is successful, I will get two RHEL 7.7 servers to implement the same in LIVE environment for HA/Resilience. First I am going with compatibility issues to resolve in my environment. Once that is resolved, I will go with HA/Resilience implementation. Please let me know if you need any more details. Thanks & Regards, Kishore Potnuru On Wed, Jul 8, 2020 at 8:57 PM Marc Roos <M.Roos(a)f1-outsourcing.eu> wrote: > > > >>> with broken or vulnerable software is there really a benefit? > >> > >> LTS distributions back port necessary patches > > >Then the OP should be able to update to a dovecot that doesn't have the > issue, right? > > I have no idea what his issue is, and why he is stuck even in specific > releases. I have been running dovecot on el6 and el7 for years and years > without issues. > > > > > > > >

2 1

RE: Urgent Help required
by Marc Roos 08 Jul '20

08 Jul '20

>>The other side of the question is, Why is the software always so "vulnerable" and "broken" in the first >>place as to be unsuitable for Long Term Support? >> >>If the software code worked when it was released some number of years ago, then why doesn't it still work >>the same way today as it it did when it was released? Whenever I hear people complain about computers and/or software. I always suggest them to use something like the abacus of 2000 bc. You should be glad for what they do for you ;) And since humans operate them, you will find annoyances as with doctors amputating the wrong limb.

1 0

Re: Urgent Help required
by Kishore Potnuru 08 Jul '20

08 Jul '20

Thank you for your reply. 1. Am i able to upgrade directly from 2.0 to 2.3? or I should go periodically from 2.0 to 2.1, then 2.1 to 2.2, then 2.2 to 2.3....? 2. could you please suggest me steps to pick the correct package to upgrade in the above version (2.1, 2.2, 2.3)? 3. which location i need to download the packages? 4. I am using redhat servers. Am i able to directly download and upgrade the software from my redhat linux server? please advise step-by-step instructions for this? Thanks, Kishore Potnuru On Wed, Jul 8, 2020 at 11:00 AM Apostolis Hardalias <a.hardalias(a)skroutz.gr> wrote: > > On 7/8/20 12:53 PM, Kishore Potnuru wrote: > > Hi All, > > > > I request your help on this. > > > > I have 2 dovecot test servers (IMAP protocol) installed with the > > following configuration. > > ============= > > [root@devap01 ~]# cat /etc/redhat-* > > Red Hat Enterprise Linux Server release 6.10 (Santiago) > > > > [root@devap01 ~]# dovecot --version > > 2.0.9 > > > > [root@devap01 ~]# postconf | grep mail_version > > mail_version = 2.6.6 > > =============== > > > > I have another server also "devap02" with the same configuration. > > > > Couple of points/questions/queries here. > > > > 1. I know these servers are having old dovecot versions. I would like > > to upgrade to the latest versions. Could you please suggest the steps > > for upgrading to the latest version in redhat (step by step details > > are helpful please) . If I upgrade to the latest version, will there > > be any impact on the existing configuration/setup? > > Check the documents posted here: > > https://doc.dovecot.org/installation_guide/upgrading/from-2.0-to-2.1/ > > https://doc.dovecot.org/installation_guide/upgrading/from-2.1-to-2.2/ > > https://doc.dovecot.org/installation_guide/upgrading/from-2.2-to-2.3/ > > Depending on your setup, you may also need to check for changes to > additional software (e.g. amavis) > > > > > 2. Now I have added these 2 servers behind the Load Balancer. Enabled > > 110/143 ports on the Load Balancer FQDN (test.pop3.testing.com > > <http://test.pop3.testing.com>) and opened the firewall ports. Here I > > configured IMAP settings from microsoft outlook to see the emails. I > > gave the Incoming Mail Server & Outgoing mail server as > > "test.pop3.testing.com <http://test.pop3.testing.com>". It is > > configured without errors in Outlook. But I see these 2 types issues > > (shared storage & individual storage) > > > > a) individual separate storage - When I send 10 emails to LB FQDN > > (test.pop3.testing.com <http://test.pop3.testing.com>), the emails are > > going to 2 backend servers. But when i see the emails from Outlook > > inbox, it shows 5 emails from one server for some time. After sometime > > it shows other 5 emails in the inbox. But, I am not able to see all 10 > > emails at same time in my inbox. Please suggest how to fix this issue? > > In this scenario, I have separate individual storage in both the servers. > > I'm not sure if you've set it up already because it's unclear from the > configuration you posted but, you may wanna have a look at: > https://wiki.dovecot.org/Replication > > I suggest using replication after you've upgraded since earlier versions > of dovecot had a few issues. > > > > b) common shared storage - I have tried a different scenario also. > > I also have one common NFS storage. So, I have configured that storage > > in both the servers. So when I sent 10 emails, I see all the 10 emails > > from both the servers as it is common shared storage. But, I am not > > getting those 10 emails delivered into my Outlook. I have made all the > > configuration correctly. Please suggest what is the mistake here. > > > > Dovecot.conf > > ========================================================= > > > > [root@devap01 ~]# cat /etc/dovecot/dovecot.conf > > disable_plaintext_auth = no > > > > listen = * > > log_path = /var/log/dovecot.log > > mail_location = maildir:/r3/mail/virtual/%d/%n/Maildir/ > > passdb { > > args = /etc/dovecot/passwd > > driver = passwd-file > > } > > pop3_uidl_format = %g > > protocols = imap pop3 > > ssl = yes > > ssl_cert = </etc/pki/dovecot/certs/dovecot.pem > > ssl_key = </etc/pki/dovecot/private/dovecot.pem > > > > userdb { > > args = uid=vmail gid=vmail home=/r3/mail/virtual/%d/%n > > driver = static > > } > > mail_debug = no > > verbose_ssl = no > > ========================================================= > > > > Please help me here. > > > > Thanks, > > Kishore Potnuru >

1 1

Dovecot Maildirs multi language
by Luca Müller 07 Jul '20

07 Jul '20

Hello, I'm hosting a few customers on a dovecot Server. Most users speak german and have german as their main language. I configured the IMAP Foldernames in a Dovecot configuration file like this: ##### root@srv04:~# cat /etc/dovecot/conf.d/105-mailboxes.conf imap_capability = +XLIST namespace inbox { inbox = yes location = separator = / mailbox "Entwürfe" { auto = subscribe special_use = \Drafts auto=subscribe } mailbox Junk-E-Mail { special_use = \Junk auto=subscribe } mailbox "Gelöschte Elemente" { special_use = \Trash auto=subscribe } mailbox "Gesendete Elemente" { special_use = \Sent auto=subscribe } mailbox Archive { special_use = \Archive auto=subscribe } } ##### Dovecot Version: 2.3.10 (0da0eff44) ##### Is it possible to change this configuration for specific users or to provide multi language support somehow? Thanks in advance. Best regards, Luca

4 4

dovecot oauth
by la.jolie＠paquerette 06 Jul '20

06 Jul '20

Hello, I'm trying to configure roundcube / dovecot to work with keycloak. I activated xoauth2 oauthbearer in dovecot. But a problem occurs when dovecot tries to contact the keycloak server (logs are below). My problem looks like this one: https://dovecot.org/pipermail/dovecot/2019-December/117768.html The response to this problem was about a bug in oauth driver (https://dovecot.org/pipermail/dovecot/2019-December/117787.html) Mizuki was using Dovecot v2.2.36 (1f10bfa63) I have Dovecot Dovecot v2.3.4.1 (f79e8e7e4) I'm wondering if this bug is still present in my version or if I have another problem. Both my servers (dovecot and keycloak) are using let's encrypt certificates. I tried to configure Keycloak with nginx proxy and without it (access via port 8443) (in case the problem came from the ssl config on the keycloak server), but still the same error. If the bug is fixed, then could someone tell me what do I have to put in the option tls_ca_cert_file? I tried with /etc/letsencrypt/live/my.host/chain.pem and also certs I got from let's encrypt website (https://letsencrypt.org/certificates/ / tried ISRG Root X1 (self-signed) & Let’s Encrypt Authority X3 (IdenTrust cross-signed) & Let’s Encrypt Authority X3 (Signed by ISRG Root X1)) But I always have the same error. Thanks, Kenny My configs: - I'm on a Debian Buster with Dovecot / postfix / roundcube - dovecot -n : --- # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-5-cloud-amd64 x86_64 Debian 10.4 auth_debug = yes auth_mechanisms = xoauth2 oauthbearer login auth_verbose = yes debug_log_path = /var/log/dovecot-debug.log first_valid_gid = 10000 first_valid_uid = 10000 info_log_path = /var/log/dovecot.log last_valid_gid = 20000 last_valid_uid = 20000 lda_mailbox_autocreate = yes log_path = /var/log/dovecot.log mail_debug = yes mail_gid = mail mail_location = maildir:~/Maildir mail_privileged_group = mail 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 } passdb { args = /etc/dovecot/dovecot-oauth2.conf.ext driver = oauth2 mechanisms = xoauth2 oauthbearer } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap" service auth { unix_listener /var/spool/postfix/private/auth { mode = 0600 user = postfix } unix_listener auth-master { mode = 0600 user = mail } unix_listener auth-userdb { mode = 0600 user = mail } } service stats { unix_listener stats-reader { mode = 0600 user = mail } unix_listener stats-writer { mode = 0600 user = mail } } ssl_cert = </etc/letsencrypt/live/my.host/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 ssl_prefer_server_ciphers = yes ssl_require_crl = no userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } userdb { args = gid=mail home=/var/mail/%u driver = static } verbose_ssl = yes protocol lda { info_log_path = /var/log/dovecot-deliver.log log_path = /var/log/dovecot-deliver-errors.log } ------ - dovecot-oauth2.conf.ext ----- tokeninfo_url = https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/token introspection_mode = post introspection_url = https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke… username_attribute = email tls_ca_cert_file = /etc/letsencrypt/live/my.host/chain.pem #tls_ca_cert_file = /etc/ssl/certs/letsencrypt.pem #active_attribute = enableMail #active_value = TRUE debug = yes rawlog_dir = /tmp/oauth2 ----- * Logs: ------- Jul 04 17:00:12 auth: Debug: oauth2(my.mail@whatever,::1,<fG8uk6CpBJ0AAAAAAAAAAAAAAAAAAAAB>): oauth2: Making token validation lookup to https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/token Jul 04 17:00:12 auth: Debug: http-client: host my.keycloak.host: Host created Jul 04 17:00:12 auth: Debug: http-client: host my.keycloak.host: Host session created Jul 04 17:00:12 auth: Debug: http-client: host my.keycloak.host: IPs have expired; need to refresh DNS lookup Jul 04 17:00:12 auth: Debug: http-client: host my.keycloak.host: Performing asynchronous DNS lookup Jul 04 17:00:12 auth: Debug: http-client[1]: request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…... (long token)]: Submitted (requests left=1) Jul 04 17:00:12 auth: Debug: http-client: host my.keycloak.host: DNS lookup successful; got 1 IPs Jul 04 17:00:12 auth: Debug: http-client: peer 151.62.56.14 (shared): Peer created Jul 04 17:00:12 auth: Debug: http-client: peer 151.62.56.14: Peer pool created Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Peer created Jul 04 17:00:12 auth: Debug: http-client[1]: queue https://my.keycloak.host: Setting up connection to 151.62.56.14 (SSL=my.keycloak.host) (1 requests pending) Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Linked queue https://my.keycloak.host (1 queues linked) Jul 04 17:00:12 auth: Debug: http-client[1]: queue https://my.keycloak.host: Started new connection to 151.62.56.14 (SSL=my.keycloak.host) Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Creating 1 new connections to handle requests (already 0 usable, connecting to 0, closing 0) Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Making new connection 1 of 1 (0 connections exist, 0 pending) Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: (151.62.56.14): Connecting Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: (151.62.56.14): Waiting for connect (fd=22) to finish for max 0 msecs Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: HTTPS connection created (1 parallel connections exist) Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: (151.62.56.14): Client connected (fd=22) Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Connected Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Starting SSL handshake Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x10, ret=1: before SSL initialization Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: before SSL initialization Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write client hello Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=-1: SSLv3/TLS write client hello Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=-1: SSLv3/TLS write client hello Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write client hello Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read server hello Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL error: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read server certificate Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read server key exchange Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read server done Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write client key exchange Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write change cipher spec Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write finished Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=-1: SSLv3/TLS write finished Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=-1: SSLv3/TLS write finished ==> dovecot.log <== Jul 04 17:00:12 auth: Info: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 ==> dovecot-debug.log <== Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=-1: SSLv3/TLS write finished Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write finished Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read change cipher spec Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read finished Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x20, ret=1: SSL negotiation finished successfully Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=1: SSL negotiation finished successfully Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL error: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Connection failed (1 connections exist, 0 pending) Jul 04 17:00:12 auth: Debug: http-client: peer 151.62.56.14: Failed to make connection (1 connections exist, 0 pending) Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Failed to establish any connection within our peer pool: SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 (1 connections exist, 0 pending) Jul 04 17:00:12 auth: Debug: http-client[1]: queue https://my.keycloak.host: Failed to set up connection to 151.62.56.14 (SSL=my.keycloak.host): SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 (1 peers pending, 1 requests pending) Jul 04 17:00:12 auth: Debug: http-client[1]: queue https://my.keycloak.host: Failed to set up any connection; failing all queued requests Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Unlinked queue https://my.keycloak.host (0 queues linked) Jul 04 17:00:12 auth: Debug: http-client[1]: request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…... (long token)]: Error: 9003 SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 Jul 04 17:00:12 auth: Debug: http-client[1]: queue https://my.keycloak.host: Dropping request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…... (long token)] Jul 04 17:00:12 auth: Debug: oauth2(my.mail@whatever,::1,<fG8uk6CpBJ0AAAAAAAAAAAAAAAAAAAAB>): oauth2: callback(-1, SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3) ==> dovecot.log <== Jul 04 17:00:12 auth: Error: oauth2(my.mail@whatever,::1,<fG8uk6CpBJ0AAAAAAAAAAAAAAAAAAAAB>): oauth2 failed: SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 ==> dovecot-debug.log <== Jul 04 17:00:12 auth: Debug: http-client[1]: request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…... (long token)]: Destroy (requests left=1) Jul 04 17:00:12 auth: Debug: http-client[1]: request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…... (long token)]: Free (requests left=0) Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Connection close Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Connection disconnect Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: (151.62.56.14): Disconnected: Connection closed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 (fd=22) Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL error: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Detached peer Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Connection destroy -------

2 4

export of information about mail into csv
by Marcel Blenkers 05 Jul '20

05 Jul '20

3 3