- dovecot - dovecot.org

Authentication hangs on before SSL initialization
by Matt 21 Nov '24

21 Nov '24

I'm running into below probem; my ath is stuck on initializing SSL. Certificates are fine, cert-chain is tested and auth no further errors are shown. Comparing to the default configuration from the docs it's pretty the same and up-to-date so I'm curious what cloud cause this. Also CHMOD on files has been checked. Nov 21 02:50:29 auth: Debug: Loading modules from directory: /usr/lib/dovecot/auth Nov 21 02:50:29 auth: Debug: Module loaded: /usr/lib/dovecot/auth/lib20_auth_var_expand_crypt.so Nov 21 02:50:29 auth: Debug: Module loaded: /usr/lib/dovecot/auth/libdriver_sqlite.so Nov 21 02:50:29 auth: Debug: Read auth token secret from /run/dovecot/auth-token-secret.dat Nov 21 02:50:29 auth: Debug: auth client connected (pid=477) Nov 21 02:50:29 imap-login: Debug: SSL: where=0x10, ret=1: before SSL initialization Nov 21 02:50:29 imap-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization Nov 21 02:50:29 imap-login: Debug: SSL: where=0x2002, ret=-1: before SSL initialization Maybe someone has a suggestion... Thanks!

2 1

Migrating GMail to Dovecot using imapc
by Jan Naumann 21 Nov '24

21 Nov '24

Dear Dovecot community, I try to migrate a GMail mailbox to Dovecot using `doveadm backup -R imapc:`. Since it seems that GMail disabled the login without XOAUTH2, I cannot figure out how to authenticate dovecot to GMail. Could you point me in the right direction? Thank you in advance! Best regards, Jan Here the commands and config I am using: # dovecot --version 2.3.19.1 (9b53102964) # doveadm -D -c gmail.conf backup -R -u user-gmail imapc: # cat gmail.conf !include /etc/dovecot/dovecot.conf imapc_host=imap.gmail.com imapc_port=993 imapc_ssl=imaps imapc_features=rfc822.size fetch-headers gmail-migration mail_prefetch_count=20 imapc_sasl_mechanisms=XOAUTH2 OAUTHBEARER PLAIN rawlog_dir = /tmp/rawlog imapc_rawlog_dir = /tmp/rawlog imapc_user=user(a)googlemail.com imapc_password=pw # cat /tmp/rawlog/20241118-114553.246444.1.in 1731926753.488821 * OK Gimap ready for requests from <ip> <base64> 1731926753.503819 * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 XYZZY SASL-IR AUTH=XOAUTH2 AUTH=PLAIN AUTH=PLAIN-CLIENTTOKEN AUTH=OAUTHBEARER 1731926753.503819 1 OK Thats all she wrote! <base64> 1731926753.806967 + <base64> # cat /tmp/rawlog/20241118-114553.246444.1.out 1731926753.488935 1 CAPABILITY 1731926753.504048 2 AUTHENTICATE XOAUTH2 <base64>

9 15

Dovecot Director Proxy (Error: lmtp-server: conn Failed to initialize user: Namespace '': Mail storage autodetection failed with home=(not set))
by abdelhaq.jalboush＠gmail.com 20 Nov '24

20 Nov '24

dovecot --version 2.3.21 (47349e2482) I have Postfix and two dovecot directors I am trying to setup them as proxy in front of two dovecot backends, I am using openldap, when I set passdb { driver = static args = proxy=y nopassword=y } it is working fine. but If I try to authenticate on the proxy I get this error: lmtp(22086): Error: lmtp-server: conn [3]: rcpt : Failed to initialize user: Namespace '': Mail storage autodetection failed with home=(not set) here is my openldap file /etc/dovecot/dovecot-openldap-proxy.conf.ext: uris = ldaps:// dn = CN=,OU=,DC=,dc= dnpass = debug_level = 0 auth_bind = yes ldap_version = 3 base = OU=,DC=,dc= scope = subtree user_attrs = mail=user pass_attrs = userPassword=password pass_filter = (&(objectClass=person)(mail=%u)) dovecot -n on the director side: # 2.3.21 (47349e2482): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.21 (f6cd4b8e) # OS: Linux 6.8.0-1018-aws x86_64 Ubuntu 24.04.1 LTS # Hostname: stg-vm-dir01 auth_debug = yes auth_mechanisms = plain login auth_socket_path = director-userdb auth_verbose = yes director_mail_servers = 10.100.10.15 10.100.15.16 director_servers = 10.100.15.201 10.100.15.202 info_log_path = /var/log/dovecot.log listen = * lmtp_proxy = yes log_path = /var/log/dovecot.log mail_gid = vmail mail_privileged_group = mail mail_uid = vmail 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-openldap-proxy.conf.ext driver = ldap } protocols = imap pop3 lmtp service director { fifo_listener login/proxy-notify { mode = 0600 user = $default_login_user } inet_listener { port = 9090 } unix_listener director-admin { mode = 0600 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } service ipc { unix_listener ipc { user = dovecot } } service lmtp { inet_listener lmtp { port = 24 } } service pop3-login { executable = pop3-login director inet_listener pop3 { port = 0 } inet_listener pop3s { port = 995 ssl = yes } } service submission-login { inet_listener submission { port = 587 } } ssl_cert = </etc/dovecot/ssl/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 protocol lmtp { auth_socket_path = director-userdb }

2 4

sharing sso between regular mail client and web applications
by Marc 20 Nov '24

20 Nov '24

I am testing a bit with sso with keycloak, I was wondering if/how it is possible that your logged in session between eg Thunderbird and dovecot can be used as a single sign on in webapplications. So as long as you have an active session with dovecot you can access all your web applications without the need to login.

2 1

bug? dsync extremely much slower on forward than reverse direction
by Bjørnar Ness 18 Nov '24

18 Nov '24

I have been experimenting with dsync lately, and to my surprise I found that dsync in forward direction is extremely slow compared for reverse (-R) direction for the exact same data, disk caches flushed both times. I have created a docker-compose setup to prove my findings. Am I missing something here, or is this a bug? link to tests: https://github.com/bjne/dovecot-dsync-benchmark -- Bj(/)rnar

1 0

Fatal: sql proxy::sqlite-proxy: Can't open configuration file
by Matt 14 Nov '24

14 Nov '24

Hi, I'm running into a problem where I'm not sure anymore if it's possible to proxy to an SQLite database file using a dict for authentication. The docs are unclear about it and I thought it was not possible as it's not a connection for SQLite but a file-read where the documentation shows different. ov 14 13:57:52 auth: Debug: Loading modules from directory: /usr/lib/dovecot/auth Nov 14 13:57:52 auth: Debug: Module loaded: /usr/lib/dovecot/auth/lib20_auth_var_expand_crypt.so Nov 14 13:57:52 master: Error: service(auth): command startup failed, throttling for 4.000 secs Nov 14 13:57:52 auth: Debug: Module loaded: /usr/lib/dovecot/auth/libdriver_sqlite.so Nov 14 13:57:52 auth: Fatal: sql proxy::sqlite-proxy: Can't open configuration file proxy::sqlite-proxy: No such file or directory doveconf -n does show me the dict being loaded, the file exists as well but it still says not found. dict { sqlite-proxy = sqlite:/etc/dovecot/conf.d/dicts/sqlite/sqlite-connection.conf.ext } What am I missing here ? Thanks, Matt

2 4

openid / roundcube example
by Marc 14 Nov '24

14 Nov '24

Does anyone have a current config example using openid and with roundcube. I like to add this next to 'regular' logins'. I was able to login once but know I am getting these in the logs " No requests to service for this peer (1 connections exist, 0 pending)" I have added the 2 passdb with links to dovecot-oauth2.token.conf.ext from this manual[1], but it is not really clear if I need these and can just add a config file with openid_configuration_url [1] https://doc.dovecot.org/2.3/configuration_manual/authentication/oauth2/

1 3

2.3.21.1 and oauth
by v＠minakov.pro 14 Nov '24

14 Nov '24

Hello! I'm using dovecot with keycloak for oauth authentication. My config is: client_id = dovecot client_secret = MY_SECRET introspection_url = https://MY_KEYCLOAK/realms/master/protocol/openid-connect/token/introspect introspection_mode = post pass_attrs = pass=%{oauth2:access_token} Everything worked great on version 2.3.20. After upgrading to version 2.3.21.1 oauth stopped working with errors: auth: Debug: http-client: conn [::1]:443 [1]: Got 401 response for request [Req1: POST https://MY_KEYCLOAK/realms/master/protocol/openid-connect/token/introspect] Unauthorized (took 5 ms + >Aug 16 00:23:58 auth: Error: oauth2(MY_EMAIL,127.0.0.1,<HADwdb8f+PN/AAAB>): oauth2 failed: Introspection failed: No username returned I tried all combination of configurations, debugging and versions of keycloak. Seems something was broken in this version of dovecot.

3 3

lda_original_recipient_header for LMTP?
by dovecot＠ptld.com 12 Nov '24

12 Nov '24

How to get the X-Original-To: header added for LMTP? I tried adding: lda_original_recipient_header = X-Original-To But that didn't add the header for mail over LMTP. I couldn't find anything else in the docs.

1 0

Locking box for backups
by Steve Atkins 12 Nov '24

12 Nov '24

I’m running 2.3.19.1 on a system that isn’t set up to support filesystem snapshots. So I’d like to back up my mdbox mailboxes at a filesystem level (with rsync, or something equivalent). I’m assuming that to get a consistent backup I should lock the mailbox while I copy it. How should I acquire a (write) lock on an mdbox mailbox? Cheers, Steve

2 1