- dovecot - dovecot.org

Letsencrypt/OpenSSL test - Verify return code: 21
by B Shea 11 Apr '21

11 Apr '21

OS: Ubuntu 20.04.2 (on mutli-core VM) Dovecot (Ubuntu default/repo version): 2.3.7.2 (3c910f64b) OpenSSL (Ubuntu default/repo version): 1.1.1f 31 Mar 2020 Reproducing- Run: "openssl s_client -showcerts -connect imap.example.com:993 -servername imap.example.com" (using a diff domain obviously) Produces error: "Verify return code: 21 (unable to verify the first certificate)" (Meaning it is missing a CA verify from what I understand?) The "Verify return code: 21" error ONLY came to my attention after I had a customer complain about adding an email account to an Android phone (using the Google/Gmail default email app). -> "Certificate cannot be trusted" was shown by app when verifying imap connection. I could force it to be used, but this still bothered me, obviously. *The same certificate bundle is also used by smtp/postifx and www/nginx and works just fine. Also the openssl test shows 'verified' on both* I am posting to list mainly because on an older version of Dovecot I have running (default repo version for Ubuntu 18), I do not have this problem shown during testing with openssl. I did not have to change the ssl_cert or ssl_ca value in config. It has identical local.conf settings other than that. Granted it is also an older openssl version, too. So, I feel this may be a bug with Dovecot (or possibly OpenSSL). I finally 'fixed' it myself by using the LE 'fullchain.pem' certificate as the location for the 'ssl_cert' entry (and chain.pem for the ca entry). Previously, it was using the normal cert.pem file location. This is still the way it's setup on the other older machine and still works fine. Changes- |ssl_ca = </etc/letsencrypt/live/{CertName}/chain.pem (or 'fullchain.pem' should work) *ssl_cert = </etc/letsencrypt/live/{CertName}/fullchain.pem* (was 'cert.pem' previously) ssl_key = </etc/letsencrypt/live/{CertName}/privkey.pem| You can also view the problem here for more info : https://superuser.com/a/1640778/47628 Thanks ahead for any insight into this..

3 4

Debug: SSL_get_servername() failed
by Rowan ＠ Jetboy 10 Apr '21

10 Apr '21

I've setup Postfix to Dovecot LMTP delivery with mandatory TLS. Emails are being delivered with TLSv1.3 with no errors. However, setting: verbose_ssl = yes exposes this on each connection: lmtp(405619): Debug: SSL_get_servername() failed What it this mean, and what should I do about it?

2 1

How to prevent, or change priority, of dovecot's FAILed relay-submission to relay's IPv6 address, and submit ONLY/first to IPv4?
by PGNet Dev 09 Apr '21

09 Apr '21

my server is a linux, dual-stack IPv4/IPv6 host it runs multiple services, including, but not limited to, postfix & dovecot the hostname is internal.mx.example.com its DNS config, host internal.mx.example.com internal.mx.example.com has address 10.1.1.15 internal.mx.example.com has IPv6 address fd80:10:1::15 internal.mx.example.com mail is handled by 5 internal.mx.example.com. here, for dovecot dovecot --version 2.3.13 (89f716dc2) submission is configured to relay to the same-host postfix instance, listening @ port 465 ./conf.d/10-master.conf ... protocols = imap submission lmtp sieve ... submission_relay_host = internal.mx.example.com submission_relay_port = 465 submission_relay_ssl = smtps submission_relay_ssl_verify = yes submission_relay_trusted = yes whereas other services listen at both IPv4 & IPv6 addresses, with IPv6 preferred over IPv4, postfix listens ONLY on IPv4, postconf inet_protocols inet_protocols = ipv4 and, as intended, simply refuses ipv6 connections telnet 10.1.1.15 465 Trying 10.1.1.15... Connected to 10.1.1.15. Escape character is '^]'. ^] telnet> quit Connection closed. telnet -6 fd80:10:1::15 465 Trying fd80:10:1::15... telnet: connect to address fd80:10:1::15: Connection refused on each/every mail submit -- via dovecot -- dovecot makes the connection 2021-04-03 19:35:35 submission(mailer(a)mx.example.com)</tnO6xm/PIqsHgsH>: Debug: smtp-server: conn 10.1.2.163:35388 [1]: Server accepted connection (fd=7) 2021-04-03 19:35:35 submission(mailer(a)mx.example.com)</tnO6xm/PIqsHgsH>: Debug: smtp-server: conn 10.1.2.163:35388 [1]: Connection created 2021-04-03 19:35:35 submission(mailer(a)mx.example.com)</tnO6xm/PIqsHgsH>: Debug: smtp-client: conn internal.mx.example.com:465 [1]: Connection created 2021-04-03 19:35:35 submission(mailer(a)mx.example.com)</tnO6xm/PIqsHgsH>: Debug: smtp-client: conn internal.mx.example.com:465 [1]: Disconnected looks up IP address 2021-04-03 19:35:35 submission(mailer(a)mx.example.com)</tnO6xm/PIqsHgsH>: Debug: smtp-client: conn internal.mx.example.com:465 [1]: Looking up IP address 2021-04-03 19:35:35 submission(mailer(a)mx.example.com)</tnO6xm/PIqsHgsH>: Debug: smtp-client: conn internal.mx.example.com:465 [1]: Performing asynchronous DNS lookup 2021-04-03 19:35:35 submission(mailer(a)mx.example.com)</tnO6xm/PIqsHgsH>: Debug: smtp-server: conn 10.1.2.163:35388 [1]: Sent: 235 2.7.0 Logged in. finds BOTH IPs -- IPv4 & IPv6 2021-04-03 19:35:35 submission(mailer(a)mx.example.com)</tnO6xm/PIqsHgsH>: Debug: smtp-client: conn internal.mx.example.com:465 [1]: DNS lookup successful; got 2 IPs then first tries to connect via the host's IPv6 address, 2021-04-03 19:35:35 submission(mailer(a)mx.example.com)</tnO6xm/PIqsHgsH>: Debug: smtp-client: conn internal.mx.example.com:465 [1]: Connecting to fd80:10:1::15:465 2021-04-03 19:35:35 submission(mailer(a)mx.example.com)</tnO6xm/PIqsHgsH>: Debug: smtp-client: conn internal.mx.example.com:465 ([fd80:10:1::15]:465) [1]: Connecting 2021-04-03 19:35:35 submission(mailer(a)mx.example.com)</tnO6xm/PIqsHgsH>: Debug: smtp-client: conn internal.mx.example.com:465 ([fd80:10:1::15]:465) [1]: Waiting for connect (fd=8) to finish for max 0 msecs ############ FAILS ############ 2021-04-03 19:35:35 submission(mailer(a)mx.example.com)</tnO6xm/PIqsHgsH>: Debug: smtp-client: conn internal.mx.example.com:465 ([fd80:10:1::15]:465) [1]: Client connection failed (fd=8) then proceeds to connect to the host's IPv4 address 2021-04-03 19:35:35 submission(mailer(a)mx.example.com)</tnO6xm/PIqsHgsH>: Debug: smtp-client: conn internal.mx.example.com:465 ([fd80:10:1::15]:465) [1]: Connecting to 10.1.1.15:465 2021-04-03 19:35:35 submission(mailer(a)mx.example.com)</tnO6xm/PIqsHgsH>: Debug: smtp-client: conn internal.mx.example.com:465 (10.1.1.15:465) [1]: Connecting 2021-04-03 19:35:35 submission(mailer(a)mx.example.com)</tnO6xm/PIqsHgsH>: Debug: smtp-client: conn internal.mx.example.com:465 (10.1.1.15:465) [1]: Waiting for connect (fd=11) to finish for max 0 msecs 2021-04-03 19:35:35 submission(mailer(a)mx.example.com)</tnO6xm/PIqsHgsH>: Debug: smtp-client: conn internal.mx.example.com:465 (10.1.1.15:465) [1]: Client connected (fd=11) 2021-04-03 19:35:35 submission(mailer(a)mx.example.com)</tnO6xm/PIqsHgsH>: Debug: smtp-client: conn internal.mx.example.com:465 (10.1.1.15:465) [1]: Connected to server (from 10.1.1.15:52880) 2021-04-03 19:35:35 submission(mailer(a)mx.example.com)</tnO6xm/PIqsHgsH>: Debug: smtp-client: conn internal.mx.example.com:465 (10.1.1.15:465) [1]: Starting SSL handshake 2021-04-03 19:35:35 submission(mailer(a)mx.example.com)</tnO6xm/PIqsHgsH>: Debug: smtp-client: conn internal.mx.example.com:465 (10.1.1.15:465) [1]: SSL handshake successful ... and submission continues/completes I need to get Dovecot to stop trying/failing @ those IPv6 address submission connections. Either by (1) trying IPv4 *first*, before IPv6, to avoid the FAIL on submission or (2) turning off submission relay by IPv6 altogether, as I'll never use it What's the config required to do either/both?

6 15

Nightclub & Bar Show-Attendees List
by Emily Olson 09 Apr '21

09 Apr '21

Hi, Hope you're doing well! I am following up to check if you are interested in acquiring the pre-registered attendees List. Event Name : Nightclub & Bar Show Date : JUN/28 - JUN/30/2021 Location : Las Vegas, NV, United States Total Attendees: 17,000 Let me know your interest to send you further information. Regards, Emily Olson, Sr. Marketing Analyst.

1 0

debug SMTP commands sent/received to/from the submission service
by Victor Sudakov 09 Apr '21

09 Apr '21

Dear Colleagues, I'm trying to debug SMTP commands clients send to the submission service. I've tried protocol submission { rawlog_dir = /var/tmp/dovecot } but /var/tmp/dovecot remains empty. What am I missing? I'd use Wireshark but the communication between SMTP clients and Dovecot is encrypted after STARTTLS, so Wireshark is pretty useless here. Can you please point me to the right direction to log all SMTP commands? All is happening on Debian/buster, Dovecot 2.3.4.1. -- Victor Sudakov VAS4-RIPE http://vas.tomsk.ru/ 2:5005/49@fidonet

3 5

Dovecot in my book
by Robert LA LAU 09 Apr '21

09 Apr '21

Hello everybody, I just wanted to let you know that Dovecot installation and configuration are extensively discussed in my first book (among other subjects). Not trying to spam; I just thought you might like to know. The book is available in English: https://www.apress.com/book/9781484269596 in French: https://www.editions-eni.fr/livre/installation-et-configuration-d-un-serveu… and in Dutch: https://webshop.boomberoepsonderwijs.nl/101-6714_configuratie-van-een-inter… Any remarks and suggestions are welcomed. Keep up the good work! Have a nice weekend, Rob LA LAU -- | Contact : | ISBN : | | | robert(a)librobert.net | 978-90-372-5751-9 | www.librobert.net | 978-2-409-02602-7 | +33.6.41.38.44.94 | 978-1-4842-6959-6

1 0

Re: Dovecot 2.3.14 - Invalid mailbox name: Name must not have '/'
by Markus Valentin 08 Apr '21

08 Apr '21

> On 03/31/2021 4:08 PM Juergen Edner <juergen(a)eisfair.org> wrote: > >> can anyone please shed some light on the changes of v2.3.14 and what need to be done to get the shared folders working again as in v2.3.13. > >> I cannot see any invalid characters in the folder names. I would also appreciate any advise on how I can debug the program any further. > > can you provide us with the output of `doveconf -n` please? > attached you will find the desired command output. > Hi Juergen, thanks for your input and the details. This is a new bug introduced in 2.3.14 which happens when combining the listescape plugin and a shared namespace. We are tracking it as DOV-4477. Markus

1 0

Incorrect value sent to solr
by Łukasz Szczepański 08 Apr '21

08 Apr '21

Hello, I've recently stumbled upon an error in fts-solr plugin. Dovecot sends "rows" parameter to solr when someone is searching in mailbox, but value of rows can be bigger than int in java. If I understand correctly, rows is equal to the last message id on current imap folder. I have mailbox where last uid value is 2206267083 and when I tried to search in this mailbox I got error 400 - Bad Request. On a Solr side I got an error: java.lang.NumberFormatException: For input string: "2206267083" NumberFormat expect an int which max value is 2147483647. Quick test reviles that rows parameter isn't required for correct response from solr. I think that dovecot should check if the value of rows is a correct int, and if not, just skip this argument. Dovecot version: 2.3.11.3 (502c39af9) Solr version: 8.7.0 ------------------ Łukasz Szczepański +48 58 3509284 www.webd.pl [1] Globtel Internet Links: ------ [1] http://www.webd.pl

4 10

Quota - Invalid bytes limit
by Gonzalo Palacios Goicolea 08 Apr '21

08 Apr '21

Hi All, Since upgrading to RHEL7 and dovecot-2.2.36-8.el7.x86_64 we're not able to get quota warnings work. We get the error "User initialization failed: Failed to initialize quota: Invalid quota root quota: Invalid rule *:bytes=: Invalid bytes limit:" /mar 16 10:29:27 lda(user@domain): Quota: Executing warning: quota-warning 90 user@domain// //Mar 16 10:29:27 buzonn5 gonzalo: mar 16 10:29:27 lda(user@domain): Quota: Executing warning: quota-warning 90 user@domain// //Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Loading modules from directory: /usr/lib64/dovecot// //Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Module loaded: /usr/lib64/dovecot/lib10_quota_plugin.so// //Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Module loaded: /usr/lib64/dovecot/lib15_notify_plugin.so// //Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Module loaded: /usr/lib64/dovecot/lib20_mail_log_plugin.so// //Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Module loaded: /usr/lib64/dovecot/lib90_sieve_plugin.so// //Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: auth USER input: user@domain home=/buzones/externos/4/215283255776546 uid=508 gid=503 quota_rule=*:bytes=2147483648// //Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Ignoring overridden (-o) userdb setting: plugin/quota_rule// //Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Effective uid=508, gid=503, home=/buzones/externos/4/215283255776546// //Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Quota root: name=_backup backend=maildir args=ns=// //Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Quota rule: root=_backup mailbox=* bytes=0 messages=0// //Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Error: User initialization failed: Failed to initialize quota: Invalid quota root quota: Invalid rule *:bytes=: Invalid bytes limit:// //Mar 16 10:29:27 buzonn5 dovecot: lda: Fatal: Invalid user settings. Refer to server log for more information./ This is the quota-warning script: /#!/bin/sh// //#Variables// //PERCENT=$1// //USER=$2// //FECHA=`date '+%b %d %H:%M:%S'`// // //#Logueo del evento// //echo "$FECHA lda($USER): Quota: Executing warning: quota-warning $PERCENT $USER" >> /var/log/dovecot/dovecot.log// //logger -p local1.notice -f /var/log/dovecot/dovecot.log "$FECHA lda($USER): Quota: Executing warning: quota-warning $PERCENT $USER"// // //cat << EOF | /usr/libexec/dovecot/dovecot-lda -d $USER -o "plugin/quota_rule=*:bytes=%$"// //From: postmaster at domain// //Subject: Alerta de Capacidad// //Date: `date`// // //El espacio asignado para el almacenamiento de su correo ha superado el $PERCENT% de su capacidad total. Por ello, se recomienda que elimine correos y/o vacie la papelera para liberar espacio.// //Mensaje enviado desde `hostname`// // //Atentamente,// // //--// //Responsable correo // //postmaster at domain// // //EOF// / ----------------------------- This is 90-quota.conf /plugin {// // quota = maildir:_backup:ns=// //}// // //plugin {// // quota_exceeded_message = El espacio asignado para el almacenamiento del correo del destinatario ha superado su capacidad total. Por ello, el correo que usted intenta enviar no se puede entregar al destinatario.// // quota_warning = storage=70%% quota-warning 70 %u// // quota_warning1 = storage=90%% quota-warning 90 %u// // quota_warning2 = storage=95%% quota-warning 95 %u// // quota_warning3 = storage=99%% quota-warning 99 %u// //}// // //service quota-warning {// // executable = script /etc/dovecot/scripts_notification_quota/quota-warning.sh// // user = vmail// // unix_listener quota-warning {// // user = vmail// // }// //}/ Getting user attibutes and quota with doveadms works right: /# doveadm user user@domain// //field value// //uid 508// //gid 503// //home /buzones/externos/4/215283255776546// //mail maildir:/buzones/externos/4/215283255776546/Maildir// //quota_rule *:bytes=2147483648// //# doveadm quota get -u user@domain// //Quota name Type Value Limit %// //_backup STORAGE 1153093 2097152 54// //_backup MESSAGE 44347 - / It also works fine with ldapsearch /# ldapsearch -x -D "cn=mail_admin,cn=users,dc=domain,dc=es" -w ********** -b "dc=domain,dc=es" -h ldap.host mail=user@domain mailquotasize// //# extended LDIF// //#// //# LDAPv3// //# base <dc=domain,dc=es> with scope subtree// //# filter: mail=user@domain// //# requesting: mailquotasize// //#// // //# user@domain, users, domain.es// //dn: cn=user@domain,cn=users,dc=domain,dc=es// //mailquotasize: 2147483648/ I've been googling but I can't find where the problem may be. Can you please help me? This is the whole config: /doveconf -n// //# 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf// //# Pigeonhole version 0.4.24 (124e06aa)// //# OS: Linux 3.10.0-1160.6.1.el7.x86_64 x86_64 Red Hat Enterprise Linux Server release 7.9 (Maipo)// //# Hostname: host.domain// //auth_cache_negative_ttl = 5 mins// //auth_cache_size = 500 M// //auth_cache_ttl = 5 mins// //auth_failure_delay = 5 secs// //default_vsz_limit = 1 G// //disable_plaintext_auth = no// //hostname = host.domain// //imap_logout_format = in(bytes read)=%i out(bytes sent)=%o// //listen = *// //lock_method = dotlock// //mail_fsync = always// //mail_location = maildir:%h/Maildir// //mail_nfs_index = yes// //mail_nfs_storage = yes// //mail_plugins = " quota mail_log notify"// //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 imapflags notify// //mbox_write_locks = fcntl// //mmap_disable = yes// //namespace {// // location = maildir:%h/Maildir/_backup// // prefix = _backup.// // separator = .// // type = private// //}// //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_log_events = delete undelete expunge mailbox_delete mailbox_rename mailbox_create save// // mail_log_fields = uid box msgid from subject// // quota = maildir:_backup:ns=// // quota_exceeded_message = El espacio asignado para el almacenamiento del correo del destinatario ha superado su capacidad total. Por ello, el correo que usted intenta enviar no se puede entregar al destinatario.// // quota_warning = storage=70%% quota-warning 70 %u// // quota_warning1 = storage=90%% quota-warning 90 %u// // quota_warning2 = storage=95%% quota-warning 95 %u// // quota_warning3 = storage=99%% quota-warning 99 %u// // sieve = ~/.dovecot.sieve// // sieve_dir = ~/Maildir/sieve// // sieve_extensions = +notify +imapflags// //}// //postmaster_address = postmaster@domain// //protocols = imap pop3 sieve// //service auth {// // unix_listener auth-userdb {// // group = vmail// // mode = 0777// // user = vmail// // }// //}// //service imap-login {// // inet_listener imap {// // port = 143// // }// // process_min_avail = 20// //}// //service imap {// // process_limit = 2048// //}// //service managesieve-login {// // inet_listener sieve {// // port = 4190// // }// // inet_listener sieve_deprecated {// // port = 2000// // }// // process_min_avail = 20// //}// //service pop3-login {// // inet_listener pop3 {// // port = 110// // }// // process_min_avail = 20// //}// //service pop3 {// // process_limit = 2048// //}// //service quota-warning {// // executable = script /etc/dovecot/scripts_notification_quota/quota-warning.sh// // unix_listener quota-warning {// // user = vmail// // }// // user = vmail// //}// //ssl = no// //ssl_cert = </etc/pki/dovecot/certs/dovecot.pem// //ssl_key = # hidden, use -P to show it// //submission_host = smtpi.domain:25// //syslog_facility = local1// //userdb {// // args = /etc/dovecot/dovecot-ldap.conf.ext// // driver = ldap// //}// //protocol lda {// // mail_plugins = " quota mail_log notify sieve"// //}// //protocol imap {// // mail_max_userip_connections = 10000// // mail_plugins = " quota mail_log notify imap_quota"// //}// //protocol pop3 {// // mail_max_userip_connections = 10// //}/ Thanks and best regards -- *Gonzalo Palacios Goicolea* U.T de Infraestructura de Equipos Centrales /Tecnologías de la Información/ Universidad Autónoma de Madrid • Campus de Cantoblanco Antes de imprimir este correo piense si es necesario.Cuidemos el medioambiente.

2 4

imapsieve and master user
by André Rodier 07 Apr '21

07 Apr '21

Hello all, I have am imap sieve script, running fine. I would like to check, if it is possible, inside the sieve script, if the current user is a master user or not. I believe this is probably not possible. Otherwise, if it is not possible, I would like to check for an external condition, like an existing file in /tmp or in the mail dir folder, for instance. The issue is that I want my imap sieve script behave differently if the master user is connected. Thanks for any piece of advice. Kind regards, André Rodier

2 2