- dovecot - dovecot.org

Certificate and showing a sign-cert not there
by Wayne Spivak 10 Feb '22

10 Feb '22

Hi - I am running Postfix 3.6.4 with Dovecot 2.3.17.1 (476cd46418). I have a multi-signed cert from Entrust. The cert works fine on port 25. However, on Port 587 I get an error: c [root@mcq wbs]# openssl s_client -connect mcq.sbanetweb.com:993 -servername mcq.sbanetweb.com CONNECTED(00000003) depth=0 C = US, ST = New York, L = Bellmore, O = SBA Consulting LTD, CN = mcq.sbanetweb.com verify error:num=20:unable to get local issuer certificate verify return:1 depth=0 C = US, ST = New York, L = Bellmore, O = SBA Consulting LTD, CN = mcq.sbanetweb.com verify error:num=21:unable to verify the first certificate verify return:1 depth=0 C = US, ST = New York, L = Bellmore, O = SBA Consulting LTD, CN = mcq.sbanetweb.com verify return:1 --- Certificate chain 0 s:C = US, ST = New York, L = Bellmore, O = SBA Consulting LTD, CN = mcq.sbanetweb.com i:C = US, O = "Entrust, Inc.", OU = See www.entrust.net/legal-terms <http://www.entrust.net/legal-terms> , OU = "(c) 2012 Entrust, Inc. - for authorized use only", CN = Entrust Certification Authority - L1K [root@mcq wbs]# dovecot -n # 2.3.17.1 (476cd46418): /etc/dovecot/dovecot.conf # OS: Linux 5.16.5-200.fc35.x86_64 x86_64 Fedora release 35 (Thirty Five) # Hostname: mcq.sbanetweb.com auth_mechanisms = plain login disable_plaintext_auth = no 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 { driver = pam } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = postfix mode = 0666 user = postfix } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service submission-login { inet_listener submission { port = 587 } } ssl = required ssl_cert = </etc/postfix/tls/ServerCertificate.pem ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-G CM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AE S128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA25 6:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE- ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES1 28-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE -DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES12 8-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNUL L:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-D ES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_client_ca_dir = /etc/postfix/tls/ ssl_client_ca_file = ChainBundle.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { driver = passwd } protocol imap { mail_max_userip_connections = 15 } Any ideas? Wayne Spivak SBANETWEB.com

5 9

Config for filtering (ignoring) specific mbox mail folders?
by John Hardin 08 Feb '22

08 Feb '22

Folks: I'm migrating to Dovecot to provide IMAP services for my personal network. I have more than a couple of decades of mail in multiple (1000+) mbox mail files, but I don't care to expose all of those to IMAP. Is there any way to filter out what mail folders Dovecot will LIST and provide access to using globs or regular expressions? I'd prefer to avoid rearranging the mbox files (e.g. to subdirectories) if possible. I looked through the Dovecot documentation and didn't see anything promising, and I couldn't find any discussion of the topic online. The feature that looked like it might be closest was Namespaces, but I couldn't see how to use that to ignore specific mbox files. Is there any facility within Dovecot (or a plugin) to filter out / ignore mail folders by name, RE or file glob? Thanks in advance! -- John Hardin KA7OHZ http://www.impsec.org/~jhardin/ jhardin(a)impsec.org pgpk -a jhardin(a)impsec.org key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79

1 0

Re: On mailbox full, retry for 4 days or similar instead of reject
by Jorge Bastos 08 Feb '22

08 Feb '22

Hi Lucas, Oh, it's so damn simple! Thank you!! Thank you all others aswell, i've read all info sent, thanks!! Jorge On 2022-02-07 22:57, Lucas Rolff wrote: > An option is to use > https://doc.dovecot.org/settings/core/#core_setting-quota_full_tempfail > - you can configure it e.g. > > protocol lda { > quota_full_tempfail = yes > } > >> On 7 Feb 2022, at 23:41, Jorge Bastos <mysql.jorge(a)decimal.pt> wrote: >> >> Howdy, >> >> I don't know if this is dovecot specific and i guess it may not be at >> 100% so I ask for help. >> >> I want postfix not to discard the message imediatly when a mailbox is >> full, i mean when postfix tries to deliver it to dovecot lmtp. >> Is it possible to change the behavior to something like what postfix >> does when he tries to deliver a message to an external server and the >> server is unaccessible for 4 days (the default i guess), and if in >> that period discard it. >> >> Does this exists? At least i know gmail does something similar to >> this. >> >> I've tried to google a bit but didn't found info that could lead me to >> this configuration. >> >> Thanks in advanced, >> Jorge

1 1

sieve: destination folder lookup in database?
by Hadmut Danisch 08 Feb '22

08 Feb '22

Hi, is there a way to lookup the action for an incoming mail, especially which folder to move the mail in, in a database? Given Problem: I want to replace the mda mailfilter/maildrop with dovecot/sieve. The mailfilter script is rather short, but looksup the destination folder by querying a berkeley database file with the sender's address to find the target folder, using the sender's address as an index. This way, it can store the target folder for hunders or thousands of senders, without needing to compare every single one of them by if == elsif == else... Is there a similar method for dovecot / sieve? I found that dovecot's sieve has some database connections, e.g. LDAP or https://doc.dovecot.org/configuration_manual/sieve/dict/ but rather to receive the whole sieve script for a given recipient as the owner of the mailbox. Is there a way to determine the target folder where to drop a mail into quickly by the sender's address, even for thousands, without the need to compare every single one of them? regards Hadmut

2 2

sieve script to alter subject of incoming message after lookup
by Marc 08 Feb '22

08 Feb '22

Is it possible with sieve to : 1. get sender of an email 2. lookup if this sender is present in an mailbox 3. if the sender is known, change the subject of the email. if the sender is not known, do nothing. 4. put/leave message in inbox. or maybe use dictionary (not really familiar with this) 1. get sender of an email 2. lookup if this sender is present in an dictionary 3. if the sender is known, change the subject of the email. if the sender is not known, do nothing. 4. put/leave message in inbox. But then I need something like 1. if message is dragged into a specific mailbox/folder 2. add sender to dictionary 1. if message is removed from a specific mailbox/folder 2. remove sender from dictionary

1 0

Different auth logging with cache lookup. (OPEN)
by Eikås Arvid 07 Feb '22

07 Feb '22

dovecot-2.3.5 and centos 7 User and IP are logged in both scenarios. auth-worker(26145): sql(user,1.1.1.1,<XXXXXXXX>): Password mismatch auth-worker(13380): cache(user(a)online.no,1.1.1.1): Password mismatch dovecot-2.3.17 and rhel 8 Feb 03 14:42:53 auth-worker(1676266): Info: conn unix:auth-worker (pid=1675846,uid=97): auth-worker<1>: sql(user,127.0.0.1,<XXXXXXXX>): Password mismatch (given password: xxxx) Feb 03 14:43:48 auth-worker(1676266): Info: conn unix:auth-worker (pid=1675846,uid=97): auth-worker<2>: Password mismatch (given password: xxxx) User and IP is not logged in cache lookup. Is this a design change or a unplanned change? Any ide when it was changed?

1 0

Lucene support for FTS - EOL date.
by Jacek Grabowski 07 Feb '22

07 Feb '22

Hello Actually on the https://doc.dovecot.org/configuration_manual/fts/lucene/ site we can read about lucene fts plugin: "This plugin is no longer maintained in Dovecot (as of 2.3+) and will be removed in the future." Does anyone know about approximate EOL date for lucene plugin support in Dovecot? -- Pozdrawiam. Jacek Grabowski.

6 8

Dovecot v2.3.17.1 Released
by Aki Tuomi 07 Feb '22

07 Feb '22

We are happy to announce 2.3.17.1 patch release of Dovecot. This contains some fixes for issues found after 2.3.17 release. https://dovecot.org/releases/2.3/dovecot-2.3.17.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.17.1.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy -- - dsync: Add back accidentically removed parameters. - lib-ssl-iostream: Fix assert-crash when OpenSSL returned syscall error without errno. - master: Dovecot failed to start if ssl_ca was too large.

7 8

test-file-cache.c needs #ifdef HAVE_RLIMIT_AS
by Rupert Gallagher 07 Feb '22

07 Feb '22

test-file-cache.c:259:24: error: use of undeclared identifier 'RLIMIT_AS' test_assert(getrlimit(RLIMIT_AS, &rl_cur) == 0); ^ test-file-cache.c:267:24: error: use of undeclared identifier 'RLIMIT_AS' test_assert(setrlimit(RLIMIT_AS, &rl_new) == 0); ^ test-file-cache.c:270:24: error: use of undeclared identifier 'RLIMIT_AS' test_assert(setrlimit(RLIMIT_AS, &rl_cur) == 0); ^ test-file-cache.c:276:24: error: use of undeclared identifier 'RLIMIT_AS' test_assert(setrlimit(RLIMIT_AS, &rl_new) == 0); ^ test-file-cache.c:279:24: error: use of undeclared identifier 'RLIMIT_AS' test_assert(setrlimit(RLIMIT_AS, &rl_cur) == 0); ^

3 9

v2.3.17 quota-dict related sql errors
by Pascal Volk 06 Feb '22

06 Feb '22

Hi there, I've updated Dovecot from v2.3.14 (cee3cbc0d) to v2.3.17 (e2aa53df5b). Right after the update, dovecot begun flooding the mail.log and PostgreSQL's log. My dict sql configuration: ,--[ .../dovecot/dovecot-dict-sql.conf.ext ]-- | map { | pattern = priv/quota/storage | table = userquota | username_field = uid | value_field = bytes | } | map { | pattern = priv/quota/messages | table = userquota | username_field = uid | value_field = messages | } `-- This worked for decades. Since the update dovecot is passing the user's email address, instead the user's UID to the query. And therefor I have lots of errors in the log files: see attached `mail.log' and `postgresql-14-main.log' excerpts. The `userquota' table looks like this: Table "public.userquota" Column | Type | Collation | Nullable | Default ----------+---------+-----------+----------+--------- uid | bigint | | not null | bytes | bigint | | not null | 0 messages | integer | | not null | 0 ... Foreign-key constraints: "fkey_userquota_uid_users" FOREIGN KEY (uid) REFERENCES users(uid) ON DELETE CASCADE (full database structure: https://bitbucket.org/pvo/vmm/src/vmm-0.7.0/pgsql/create_tables.pgsql) Regards, Pascal -- Ubuntu is an ancient African word meaning “I can’t install Debian.” -- unknown

3 4