- dovecot - dovecot.org

json_parse_number broken by compiler optimization
by Christian Ehrhardt 13 Apr '21

13 Apr '21

Hi, the recent Ubuntu (re)builds uncovered an issue with dovecot 1:2.3.13+dfsg1-1 build log: https://launchpadlibrarian.net/529849650/buildlog_ubuntu-hirsute-amd64.dove… A coworker tried 2.3.14 but got the same result. What fails is the json_parser build time test like: test-json-parser.c:161: Assert(#25) failed: null_strcmp(json_output[pos].value, value) == 0 I was looking into that a bit more and what I found is that it is dependent on the new toolchain of gcc 10.2.0-1. Not all calls to json_parse_* fail, e.g. the first one looks all good and passes I was iterating the tests using a report function defined like (gdb) define repcon >c >p pos >p json_output[pos].type >p type >p json_output[pos].value >p value >call null_strcmp(json_output[pos].value, value) >end The first one to be bad was: Breakpoint 2, test_json_parser_success (full_size=<optimized out>) at test-json-parser.c:161 161 test_assert_idx(null_strcmp(json_output[pos].value, value) == 0, pos); $84 = 25 $85 = JSON_TYPE_NUMBER $86 = JSON_TYPE_NUMBER $87 = 0x555555633b25 "-12.456" $88 = 0x555555693110 "" $89 = 45 Earlier and later parsing was happy, for example Breakpoint 2, test_json_parser_success (full_size=<optimized out>) at test-json-parser.c:161 161 test_assert_idx(null_strcmp(json_output[pos].value, value) == 0, pos); $90 = 27 $91 = JSON_TYPE_NUMBER $92 = JSON_TYPE_NUMBER $93 = 0x555555633b32 "12.456e9" $94 = 0x555555693110 "12.456e9" $95 = 0 (gdb) We have two things we compare here. 1. json_output[] which is a static define and for this value is 67 »···{ JSON_TYPE_NUMBER, "-12.456" }, 2. the return value that json_parse_next returns. 25 »···" \"sub2\":-12.456,\n" 148 »···»···»···»···ret = json_parse_next(parser, &type, &value); I tried a non negative number and got success which is suspicious Breakpoint 5, test_json_parser_success (full_size=<optimized out>) at test-json-parser.c:164 164 test_assert_idx(null_strcmp(json_output[pos].value, value) == 0, pos); $122 = 25 $123 = JSON_TYPE_NUMBER $124 = JSON_TYPE_NUMBER $125 = 0x555555633b2c "12.456" $126 = 0x555555693110 "12.456" $127 = 0 (gdb) Also the return value otherwise LGTM, it is recognized as a number: 540 } else if ((ret = json_parse_number(parser, value_r)) >= 0) { (gdb) n 541 *type_r = JSON_TYPE_NUMBER; So parsing worked one might think, but the value was not set. (gdb) p *value_r $833 = 0x555555693110 "" It turns out json_parse_number is too optimized. Too optimized for debugging further into json_parse_number. But also optimization is causing the issue. With -O0 or -O1 it works fine, even putting the lower optimization level just around json_parse_number it is enough to avoid the issue. Not a fix but "avoidance" for now: --- a/src/lib/json-parser.c +++ b/src/lib/json-parser.c @@ -386,6 +386,8 @@ static int json_parse_int(struct json_pa return 1; } +#pragma GCC push_options +#pragma GCC optimize ("-O0") static int json_parse_number(struct json_parser *parser, const char **value_r) { int ret; @@ -415,6 +417,7 @@ static int json_parse_number(struct json *value_r = str_c(parser->value); return 1; } +#pragma GCC pop_options static int json_parse_atom(struct json_parser *parser, const char *atom) { I was trying to see what happened and tracked each str_append_c that happened inside json_parse_number. A breakpoint on str_append_c and backtraces showed that we clearly do the "right" parsing. From the backtraces I've seen it does (just from positions): For example (gdb) bt #0 str_append_c (chr=<optimized out>, str=0x5555556930d0) at str.h:44 #1 json_parse_digits (parser=<optimized out>) at json-parser.c:366 => that is a digit It does "- digit digit dot digit digit digit" This perfectly matches the input value, but still the result stays empty: (gdb) p (char*)(str->data) $738 = 0x555555693110 "" In comparison - when parsing the latter 12.456e9 which works I see two odd things: 1. the value isn't cleared despite str_truncate(parser->value, 0); at the beginning of json_parse_number 2. the value (this time) is read exactly as I assumed Breakpoint 17, json_parse_number (value_r=0x7fffffffe1a0, parser=0x555555692ee0) at json-parser.c:394 394 str_truncate(parser->value, 0); Breakpoint 18, str_append_c (chr=<optimized out>, str=0x5555556930d0) at str.h:44 44 buffer_append_c(str, chr); (gdb) p (char*)(str->data) $741 = 0x555555693110 "sub3" ^^ not cleared, still has "sub3" even later on Breakpoint 18, str_append_c (chr=<optimized out>, str=0x5555556930d0) at str.h:44 44 buffer_append_c(str, chr); (gdb) p (char*)(str->data) $742 = 0x555555693110 "1ub3" ^^ reading left to right one char at a time "over the old value", which didn't update the data. So it seems in json_parse_number the ordering of a) str_truncate(parser->value, 0); b) the parsing itself is messed up by optimization. We already know from the above that reducing just this function to -O1 or less avoids the issue. But what is it really - I don't know? Maybe you have a better idea what is going on, the issue should be reproducible when building dovecot with the toolchain present on the latest Ubuntu being 21.04 (Hirsute) right now. -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd

4 8

sieve filter bevor.spam, arnt take effect
by Maurizio Caloro 13 Apr '21

13 Apr '21

Hello Please willing to filter "bevor spam" mail... filtering arnt take effect .. please i dont see the mistake. Thanks for any possible update. Debian buster -- root@nmail:/etc/dovecot# dpkg -l | grep dovecot dovecot-core 1:2.3.4.1-5+deb10u6 dovecot-imapd 1:2.3.4.1-5+deb10u6 dovecot-lmtpd 1:2.3.4.1-5+deb10u6 dovecot-managesieved 1:2.3.4.1-5+deb10u6 dovecot-mysql 1:2.3.4.1-5+deb10u6 dovecot-sieve 1:2.3.4.1-5+deb10u6 root@nmail:/etc/dovecot/sieve# cat before.sieve # Sieve rules that are run before the user's filters. # Messages flagged as spam are moved into the Junk folder. require [ "fileinto", "mailbox" ]; if header :contains "X-Spam-Flag" "YES" { fileinto :create "INBOX.Junk"; stop; } -- already executed # sieve before.sieve -- service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { mode = 0600 user = postfix group = postfix } } -- root@nmail:/etc/dovecot/conf.d# <mailto:root@nmail:/etc/dovecot/conf.d#> cat 90-sieve.conf ## ## Settings for the Sieve interpreter ## plugin { # The path to the user's main active script. If ManageSieve is used, this the # location of the symbolic link controlled by ManageSieve. # sieve = ~/sieve/.dovecot.sieve sieve = file:%h/sieve;active=%h/.dovecot.sieve # Directory for :personal include scripts for the include extension. This # is also where the ManageSieve service stores the user's scripts. sieve_dir = ~/sieve # Path to a script file or a directory containing script files that need to be # executed before the user's script. If the path points to a directory, all # the Sieve scripts contained therein (with the proper .sieve extension) are # executed. The order of execution within a directory is determined by the # file names, using a normal 8bit per-character comparison. Multiple script # file or directory paths can be specified by appending an increasing number. sieve_before = /etc/dovecot/sieve/before.sieve } -- root@nmail:/etc/dovecot# doveconf -n # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-16-amd64 x86_64 Debian 10.9 # Hostname: nmail.caloro.ch auth_mechanisms = plain login auth_verbose = yes info_log_path = /var/log/mail.log log_timestamp = %b %d %H:%M:%S Dovecot/ mail_access_groups = vmail mail_location = maildir:~/Maildir 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 ihave 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-sql.conf.ext driver = sql } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/sieve/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = mca(a)caloro.ch <mailto:mca@caloro.ch> protocols = imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-client { mode = 0660 user = mail } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } 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 = 0666 user = vmail } unix_listener stats-writer { group = vmail mode = 0666 user = vmail } } ssl = required ssl_cert = </etc/letsencrypt/live/nmail.caloro.ch/fullchain.pem ssl_cipher_list = ECDHE-RSA-CHACHA20-POLY1305:ALL:!LOW:!SSLv2:!EXP:!aNULL ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lda { mail_plugins = " quota sieve" } protocol imap { mail_plugins = " quota imap_quota" ssl_cert = </etc/letsencrypt/live/nmail.caloro.ch/fullchain.pem ssl_key = # hidden, use -P to show it } protocol lmtp { mail_plugins = " sieve" } Mauri

3 6

error 42 ssl certificate expired
by Christopher Wensink 13 Apr '21

13 Apr '21

Dovecot Team, I need a little help. I came in this morning and it seems like the SSL Certificates expired for dovecot (on an internal mail server) and nobody can move email into their folders on this server. In Thunderbird they just see in the status bar: HISTORY: checking mail server capabilities... In /var/log/maillog: -------- Apr 12 09:02:26 mario2 dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=10.5.1.85, lip=10.5.1.17, TLS: SSL_read() failed: error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate: SSL alert number 42, session=<H5iu9sa/Me0KBQFV> I have tried: -Restarting Dovecot -Restarting the whole mail server -Re-creating the .pem files, first moving the old files in /etc/pki/dovecot/certs and /etc/pki/dovecot/private from dovecot.pem to dovecot-old.pem, - Re-creating a new dovecot.pem using the mkcert.sh script in the doc folder in /usr/share/doc/dovecot-2.2.36/, - restarting dovecot - changing the cert values in dovecot-openssl.cnf I also tried creating new .crt and key files using this tutorial: https://msol.io/blog/tech/create-a-self-signed-ssl-certificate-with-openssl/ I need some assistance, thank you for your help. Chris -- Christopher Wensink IS Administrator Five Star Plastics, Inc 1339 Continental Drive Eau Claire, WI 54701 Office: 715-831-1682 Mobile: 715-563-3112 Fax: 715-831-6075 cwensink(a)five-star-plastics.com www.five-star-plastics.com

4 8

Letsencrypt/OpenSSL test - Verify return code: 21
by Brady Shea 12 Apr '21

12 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 2

connection closed every ten minutes
by Marco Fioretti 12 Apr '21

12 Apr '21

Greetings, I use mutt on Ubuntu to access my IMAP mailboxes, on my Centos email server that runs dovecot. Everything has worked without problems for years. About one week ago, the connection between mutt and dovecot became unstable. Before, I could leave mutt connected for days in a row, no problem. Now, everything still works fine, except... I get every ten minutes I get "connection timed out" in Mutt's status line, and hundreds of messages like Apr 12 16:12:49 SERVERNAME dovecot: imap(ACCOUNTNAME): Logged out in=164 out=757 what puzzles me is that I did not touch anything both on my server and on my desktop, except an "apt-get update" some days before this started. But cannot see how it would be related anyway, nor have I found anything online like this. Any help to understand what happened and fix it is very welcome. Marco

1 0

AW: sieve filter bevor.spam, arnt take effect
by mauric＠gmx.ch 12 Apr '21

12 Apr '21

Please kindly want to ask for any possible update ? Von: mauric(a)gmx.ch <mauric(a)gmx.ch> Gesendet: Montag, 12. April 2021 10:44 An: 'dovecot(a)dovecot.org' <dovecot(a)dovecot.org> Betreff: sieve filter bevor.spam, arnt take effect Hello Please willing to filter "bevor spam" mail... filtering arnt take effect .. please i dont see the mistake. Thanks for any possible update. Debian buster -- root@nmail:/etc/dovecot# dpkg -l | grep dovecot dovecot-core 1:2.3.4.1-5+deb10u6 dovecot-imapd 1:2.3.4.1-5+deb10u6 dovecot-lmtpd 1:2.3.4.1-5+deb10u6 dovecot-managesieved 1:2.3.4.1-5+deb10u6 dovecot-mysql 1:2.3.4.1-5+deb10u6 dovecot-sieve 1:2.3.4.1-5+deb10u6 root@nmail:/etc/dovecot/sieve# cat before.sieve # Sieve rules that are run before the user's filters. # Messages flagged as spam are moved into the Junk folder. require [ "fileinto", "mailbox" ]; if header :contains "X-Spam-Flag" "YES" { fileinto :create "INBOX.Junk"; stop; } -- already executed # sieve before.sieve -- service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { mode = 0600 user = postfix group = postfix } } -- root@nmail:/etc/dovecot/conf.d# <mailto:root@nmail:/etc/dovecot/conf.d> cat 90-sieve.conf ## ## Settings for the Sieve interpreter ## plugin { # The path to the user's main active script. If ManageSieve is used, this the # location of the symbolic link controlled by ManageSieve. # sieve = ~/sieve/.dovecot.sieve sieve = file:%h/sieve;active=%h/.dovecot.sieve # Directory for :personal include scripts for the include extension. This # is also where the ManageSieve service stores the user's scripts. sieve_dir = ~/sieve # Path to a script file or a directory containing script files that need to be # executed before the user's script. If the path points to a directory, all # the Sieve scripts contained therein (with the proper .sieve extension) are # executed. The order of execution within a directory is determined by the # file names, using a normal 8bit per-character comparison. Multiple script # file or directory paths can be specified by appending an increasing number. sieve_before = /etc/dovecot/sieve/before.sieve } -- root@nmail:/etc/dovecot# doveconf -n # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-16-amd64 x86_64 Debian 10.9 # Hostname: nmail.caloro.ch auth_mechanisms = plain login auth_verbose = yes info_log_path = /var/log/mail.log log_timestamp = %b %d %H:%M:%S Dovecot/ mail_access_groups = vmail mail_location = maildir:~/Maildir 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 ihave 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-sql.conf.ext driver = sql } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/sieve/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = mca(a)caloro.ch <mailto:mca@caloro.ch> protocols = imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-client { mode = 0660 user = mail } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } 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 = 0666 user = vmail } unix_listener stats-writer { group = vmail mode = 0666 user = vmail } } ssl = required ssl_cert = </etc/letsencrypt/live/nmail.caloro.ch/fullchain.pem ssl_cipher_list = ECDHE-RSA-CHACHA20-POLY1305:ALL:!LOW:!SSLv2:!EXP:!aNULL ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lda { mail_plugins = " quota sieve" } protocol imap { mail_plugins = " quota imap_quota" ssl_cert = </etc/letsencrypt/live/nmail.caloro.ch/fullchain.pem ssl_key = # hidden, use -P to show it } protocol lmtp { mail_plugins = " sieve" } Mauri

1 0

sieve filter bevor.spam, arnt take effect
by mauric＠gmx.ch 12 Apr '21

12 Apr '21

Hello Please willing to filter "bevor spam" mail... filtering arnt take effect .. please i dont see the mistake. Thanks for any possible update. Debian buster -- root@nmail:/etc/dovecot# dpkg -l | grep dovecot dovecot-core 1:2.3.4.1-5+deb10u6 dovecot-imapd 1:2.3.4.1-5+deb10u6 dovecot-lmtpd 1:2.3.4.1-5+deb10u6 dovecot-managesieved 1:2.3.4.1-5+deb10u6 dovecot-mysql 1:2.3.4.1-5+deb10u6 dovecot-sieve 1:2.3.4.1-5+deb10u6 root@nmail:/etc/dovecot/sieve# cat before.sieve # Sieve rules that are run before the user's filters. # Messages flagged as spam are moved into the Junk folder. require [ "fileinto", "mailbox" ]; if header :contains "X-Spam-Flag" "YES" { fileinto :create "INBOX.Junk"; stop; } -- already executed # sieve before.sieve -- service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { mode = 0600 user = postfix group = postfix } } -- root@nmail:/etc/dovecot/conf.d# <mailto:root@nmail:/etc/dovecot/conf.d#> cat 90-sieve.conf ## ## Settings for the Sieve interpreter ## plugin { # The path to the user's main active script. If ManageSieve is used, this the # location of the symbolic link controlled by ManageSieve. # sieve = ~/sieve/.dovecot.sieve sieve = file:%h/sieve;active=%h/.dovecot.sieve # Directory for :personal include scripts for the include extension. This # is also where the ManageSieve service stores the user's scripts. sieve_dir = ~/sieve # Path to a script file or a directory containing script files that need to be # executed before the user's script. If the path points to a directory, all # the Sieve scripts contained therein (with the proper .sieve extension) are # executed. The order of execution within a directory is determined by the # file names, using a normal 8bit per-character comparison. Multiple script # file or directory paths can be specified by appending an increasing number. sieve_before = /etc/dovecot/sieve/before.sieve } -- root@nmail:/etc/dovecot# doveconf -n # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-16-amd64 x86_64 Debian 10.9 # Hostname: nmail.caloro.ch auth_mechanisms = plain login auth_verbose = yes info_log_path = /var/log/mail.log log_timestamp = %b %d %H:%M:%S Dovecot/ mail_access_groups = vmail mail_location = maildir:~/Maildir 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 ihave 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-sql.conf.ext driver = sql } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/sieve/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = mca(a)caloro.ch <mailto:mca@caloro.ch> protocols = imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-client { mode = 0660 user = mail } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } 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 = 0666 user = vmail } unix_listener stats-writer { group = vmail mode = 0666 user = vmail } } ssl = required ssl_cert = </etc/letsencrypt/live/nmail.caloro.ch/fullchain.pem ssl_cipher_list = ECDHE-RSA-CHACHA20-POLY1305:ALL:!LOW:!SSLv2:!EXP:!aNULL ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lda { mail_plugins = " quota sieve" } protocol imap { mail_plugins = " quota imap_quota" ssl_cert = </etc/letsencrypt/live/nmail.caloro.ch/fullchain.pem ssl_key = # hidden, use -P to show it } protocol lmtp { mail_plugins = " sieve" } Mauri

1 0

Sieve doesn't work after LTMP Director implementation
by Gonzalo Palacios Goicolea 12 Apr '21

12 Apr '21

Hi All, We're running dovecot director por proxying imap/pop queries to the backends. Yesterday we add LMTP proxying and it works fine, but we have realized that Sieve filters are no longer working after this change. Is it mandatory to add some config to the directors or backends after implementing LMTP through Director? We use dovecot-pigeonhole-2.2.36-8.el7.x86_64 dovecot-2.2.36-8.el7.x86_64 This is director servers config, if you also need backends config, please let me know doveconf -n # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24 (124e06aa) # OS: Linux 3.10.0-1160.15.2.el7.x86_64 x86_64 Red Hat Enterprise Linux Server release 7.9 (Maipo) # Hostname: hidden auth_cache_negative_ttl = 5 mins auth_cache_size = 64 M auth_cache_ttl = 5 mins auth_failure_delay = 5 secs auth_verbose = yes default_client_limit = 40000 default_process_limit = 5500 director_mail_servers = Hidden director_servers = Hidden disable_plaintext_auth = no doveadm_port = 24245 listen = * lmtp_proxy = yes mail_location = maildir:%h/Maildir 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 mbox_write_locks = fcntl 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 = proxy=y nopassword=y driver = static } plugin { mail_log_events = delete undelete expunge mailbox_delete mailbox_rename mailbox_create save mail_log_fields = uid box msgid from subject sieve = file:~/sieve;active=~/.dovecot.sieve } service director { fifo_listener login/proxy-notify { mode = 0666 user = $default_login_user } inet_listener { port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service doveadm { inet_listener { port = 24245 } } service imap-login { executable = imap-login director } service ipc { unix_listener ipc { user = dovecot } } service lmtp { inet_listener lmtp { address = x.x.x.x port = 24 } } service managesieve-login { executable = managesieve-login director } service pop3-login { executable = pop3-login director } ssl = no ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = # hidden, use -P to show it syslog_facility = local1 protocol lmtp { auth_socket_path = director-userdb } protocol doveadm { auth_socket_path = director-userdb } local 10.10.10.0/24 { doveadm_password = # hidden, use -P to show it } Thanks in advance 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 1

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

[Sieve] Understand Sieve processing
by h8h 07 Apr '21

07 Apr '21

Hi, I have the following configuration: > cat > /etc/dovecot/conf.d/99-local-sieve.conf << EOF; > plugin { > sieve_before = /etc/dovecot/sieve-spam.sieve > sieve_before2 = /mail/sieve/global_before > sieve_after = /mail/sieve/global_after > sieve = /mail/sieve/%d/%n.sieve > sieve_dir = /mail/sieve/%d/%n > } > EOF > cat /etc/dovecot/sieve-spam.sieve > require ["regex", "fileinto", "imap4flags"]; > > if allof (header :regex "X-Spam-Status" "^Yes") { > fileinto "Spam"; > } (I removed the keyword "stop;" to proceed rule processing, which does not work) Now as a user (/mail/sieve/%d/%n.sieve) I want to create my own "Spam" rule: > require ["regex","reject"]; > # rule:[SPAM] > if allof (header :regex "x-spam-status" "^Yes") > { > reject text: > This E-Mail is SPAM. > . > ; > } I activate the traces and see the following if the e-mail is SPAM: > ## Started executing script 'sieve-spam' > 3: jump if result is false > 3: not jumping > 4: fileinto action > 4: store message in mailbox `Spam' > ## Finished executing script 'sieve-spam' If the e-mail is not SPAM: > ## Started executing script 'sieve-spam' > 3: jump if result is false > 3: jumping to line 4 > ## Finished executing script 'sieve-spam' > > > ## Started executing script 'roundcube' > 3: jump if result is false > 3: jumping to line 10 > ## Finished executing script 'roundcube' So my sieve gets only executed if the e-mail is not SPAM. Thats a bit odd. Could you explain how the sieve processing work and how I can solve this problem? dovecot --version 2.2.33.2 (d6601f4ec) on Ubuntu 18.04 LTS Best regards Homy

2 1

Re: Emails to multiple recipients on same server not getting delivered
by Steve Dondley 06 Apr '21

06 Apr '21

> So where are you calling Spamassassin for each email? Hmm... maybe > you need to have -d ${recipient} in your spamassassin call? > Or better yet, call the 'deliver' program from dovecot like I showed > isntead. > > spamass-dovecot_destination_recipient_limit = 1 > virtual_alias_maps = hash:/etc/postfix/virtual-alias-maps > virtual_mailbox_maps = sqlite:/etc/postfix/virtual_users.cf > virtual_transport = spamass-dovecot > I've simplified the configuration by turning off spamassassin and removing any mention of it from master.cf. Things are working now. But I'm still baffled why basically the same master.cf config is working on one server but not another. I wonder if different SA configs might be the problem.

3 2

Sharing a single solr server between multiple dovecot servers
by Steve Dondley 06 Apr '21

06 Apr '21

I am brand new to solr and I'm interested in using sharing it between several dovecot machines I'm running. I'm looking for some big picture guidance on what I need to do to configure solr to work with the different dovecot machines. So far, I managed to set up a single "dovecot" core on the solr server and it is working with one of my dovecot machines. I'm not sure how to proceed from here as I'm very unclear on how solr maintains separate indexes for different users on my different machines. Some basic questions I have are: 1) Do I need a new core for each of the dovecot machines I want to use with solr? 2) If not, how does solr ensure indexes for the different dovecot user do not get comingled? 3) If yes, how do I configure dovecot to tell it which solr core to use? Thanks.

2 1

Avoid duplicate emails in the sent folder
by André Rodier 06 Apr '21

06 Apr '21

Hello, I have a webmail program, that I cannot configure to not save sent emails in the Sent folder. My emails to the SOGo team don't seem to reach the mailing list anymore. So, I have no other choice to think the problem differently, and _maybe_ use Dovecot to fix this issue. Moreover, I think this could be useful for other email clients. First, I have tried to use Sieve, but no success so far: ------ imapsieve_mailbox4_name = * imapsieve_mailbox4_from = Sent imapsieve_mailbox4_causes = APPEND, COPY imapsieve_mailbox4_after = file:/var/lib/dovecot/sieve/sent- checks.sieve ------ And this sieve script: ------ Message-ID header. require [ "variables", "environment", "duplicate", "imapsieve" ]; […] if duplicate :seconds 10 { discard; } ------ Otherwise, can I configure dovecot in a certain way, for instance create a virtual Sent folder. This would not save the email when appended, but still returns the list of sent emails ? But this is not working. Any idea? Thanks for your help! André

3 13

Emails to multiple recipients on same server not getting delivered
by Steve Dondley 05 Apr '21

05 Apr '21

When I send an email to a single user on a server, it is received by the user without a problem. But when sending to multiple users, the emails disappear into a black hole. The logs contain no errors and indicate the emails were sent: Apr 5 13:10:29 email postfix/pipe[31703]: F3A912027D: to=<pete2(a)example.org>, relay=spamassassin, delay=1.6, delays=0.12/0/0/1.5, dsn=2.0.0, status=sent (delivered via spamassassin service (X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on email.example.org X-Spam-Level: X-Spam-Stat)) Apr 5 13:10:29 email postfix/pipe[31703]: F3A912027D: to=<pete3(a)example.org>, relay=spamassassin, delay=1.6, delays=0.12/0/0/1.5, dsn=2.0.0, status=sent (delivered via spamassassin service (X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on email.example.org X-Spam-Level: X-Spam-Stat)) However, when I check the inboxes for the recipients, the email is nowhere to be found. I tried lifting the receiving/concurrent limits but to no effect. I have other servers with very similar configurations to this one but I'm not having issues with them. lmtp is the local delivery agent. My postconf: alias_maps = hash:/etc/aliases biff = no broken_sasl_auth_clients = yes command_directory = /usr/sbin compatibility_level = 2 daemon_directory = /usr/lib/postfix/sbin data_directory = /var/lib/postfix debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5 default_destination_concurrency_limit = 5 home_mailbox = Maildir/ inet_interfaces = all lmtp_destination_concurrency_limit = 5 lmtp_destination_recipient_limit = 5 local_destination_concurrency_limit = 5 local_destination_recipient_limit = 5 mail_owner = postfix mailbox_size_limit = 3145728000 mailbox_transport = lmtp:unix:private/dovecot-lmtp mailq_path = /usr/bin/mailq message_size_limit = 26214400 milter_default_action = accept milter_protocol = 6 mydestination = $myhostname localhost.$mydomain localhost $mydomain mydomain = example.org myhostname = email.example.org mynetworks_style = subnet myorigin = example.org non_smtpd_milters = $smtpd_milters policyd-spf_time_limit = 3600 recipient_bcc_maps = pcre:/etc/postfix/recipient_bcc recipient_delimiter = + sendmail_path = /usr/sbin/sendmail setgid_group = postdrop smtp_tls_note_starttls_offer = yes smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtp_use_tls = yes smtpd_banner = $myhostname ESMTP smtpd_milters = unix:/opendkim/opendkim.sock smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, check_policy_service unix:private/policyd-spf smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = $myhostname smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_sender_login_maps = pcre:/etc/postfix/login_maps.pcre smtpd_sender_restrictions = reject_authenticated_sender_login_mismatch smtpd_tls_cert_file = /etc/letsencrypt/live/email.example.org/fullchain.pem smtpd_tls_key_file = /etc/letsencrypt/live/email.example.org/privkey.pem smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtpd_use_tls = yes unknown_local_recipient_reject_code = 550 virtual_alias_maps = hash:/etc/postfix/virtual virtual_mailbox_limit = 26214400 virtual_transport = lmtp:unix:private/dovecot-lmtp And doveconf: # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-14-cloud-amd64 x86_64 Debian 10.9 # Hostname: email.example.org auth_mechanisms = plain login auth_username_format = %Ln disable_plaintext_auth = no mail_debug = yes mail_location = maildir:~/Maildir mail_privileged_group = mail 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 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/aliases driver = passwd-file } passdb { driver = pam } plugin { recipient_delimiter = + sieve = file:~/sieve;active=~/.dovecot.sieve sieve_default = /var/lib/dovecot/sieve/default.sieve sieve_default_name = Defaults sieve_global = /var/lib/dovecot/sieve } pop3_client_workarounds = outlook-no-nuls protocols = " imap lmtp sieve pop3 sieve" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0666 } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service imap { client_limit = 1 } service lmtp { client_limit = 1 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3-login { inet_listener pop3s { port = 995 ssl = yes } } service submission-login { inet_listener submission { port = 587 } } ssl_cert = </etc/letsencrypt/live/email.example.org/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 { driver = passwd } protocol lmtp { mail_plugins = " sieve" }

3 2

No decode2txt script for search attachments
by Steve Dondley 05 Apr '21

05 Apr '21

I'm looking at the documentation at https://doc.dovecot.org/settings/plugin/fts-plugin/#fts-decoder It says "See the decode2text.sh script included in Dovecot for how to use this." I don't have this script installed and can't find it anywhere on my Debian Buster server. I'm running dovecot version 2.3.4.1 Not sure if the documentation is outdated or what.

2 2

Search seems slow with apache solr
by Steve Dondley 05 Apr '21

05 Apr '21

I'm experimenting with Apache Solr and Dovecot. As far as I can tell, I have dovecot working with Apache Solr as demonstrated by this output: a search text "cash" * SEARCH 4 8 26 35 45 52 54 55 63 a OK Search completed (0.356 + 0.001 + 0.068 secs). However, when using the roundcube search bar and search all messages on a single word, it takes about 18 seconds. This seems slow as I only have about 4300 message in all my folders. But I'm not sure as I have nothing to compare it to. Is there a way I can test whether roundcube is using solr to perform searches?

2 4