- dovecot - dovecot.org

Fwd: connection refused, no error anywhere
by Marco Fioretti 22 Jan '25

22 Jan '25

Hi Nick, honestly, I don't know why that port was set to 0, I just inherited the whole server... however, even changing that number to 143 and restarting dovecot makes no difference in the output of netstat I just pasted in another reply.... Il giorno mar 21 gen 2025 alle ore 19:00 Nick Howitt via dovecot < dovecot(a)dovecot.org> ha scritto: > Any reason why the imap-listener port is set to 0 and not 143 or > commented out? > > Have you checked if dovecot is listening on 143? > > > On 21/01/2025 17:50, Marco Fioretti via dovecot wrote: > > Greetings, > > > > I was just tasked with rebuilding from scratch the mail server of an NGO, > > on a brand new Ubuntu 24.04 LTS VPS. > > > > I have copied the whole dovecot configuration to the new server, and now > am > > stuck because: > > > > - dovecot IS running, dovecot service status shows no errors, but: > > > > - if I try to connect with mutt from my desktop I get "connection > refused" > > > > - the ufw firewall does allow imap/imaps connections, and there are no > > errors in its log > > > > - even "telnet localhost 143" fails: > > Trying ::1... > > Connection failed: Connection refused > > Trying 127.0.0.1... > > telnet: Unable to connect to remote host: Connection refused > > > > - I see no related errors in /var/log/mail.log or /var/log/syslog. > > > > > > output of dovecot -n is pasted below, I only changed the actual domain > name > > to "example.com" > > > > TIA for any pointer, I really need to get this server back online as soon > > as possible... > > > > Marco > > > > # 2.3.21 (47349e2482): /etc/dovecot/dovecot.conf > > # Pigeonhole version 0.5.21 (f6cd4b8e) > > doveconf: Warning: NOTE: You can get a new clean config file with: > doveconf > > -Pn > dovecot-new.conf > > doveconf: Warning: Obsolete setting in /etc/dovecot/conf.d/10-ssl.conf:9: > > ssl_dh_parameters_length is no longer needed > > # OS: Linux 6.8.0-51-generic x86_64 Ubuntu 24.04.1 LTS ext4 > > # Hostname: example.com > > auth_debug = yes > > auth_verbose = yes > > auth_verbose_passwords = plain > > mail_location = maildir:/var/mail/mymail_storage/base/ > > mbox_write_locks = fcntl > > passdb { > > args = /etc/imap.v_users > > driver = passwd-file > > } > > passdb { > > driver = pam > > } > > service auth { > > unix_listener /var/spool/postfix/private/auth { > > group = postfix > > mode = 0660 > > user = postfix > > } > > } > > service imap-login { > > inet_listener imap { > > port = 0 > > } > > } > > ssl_cert = </etc/letsencrypt/live/example.com/fullchain.pem > > ssl_cipher_list = ALL > > ssl_key = # hidden, use -P to show it > > ssl_prefer_server_ciphers = yes > > userdb { > > args = /etc/imap.v_users > > driver = passwd-file > > } > > userdb { > > driver = passwd > > } > > verbose_ssl = yes > > _______________________________________________ > > dovecot mailing list --dovecot(a)dovecot.org > > To unsubscribe send an email todovecot-leave(a)dovecot.org > _______________________________________________ > dovecot mailing list -- dovecot(a)dovecot.org > To unsubscribe send an email to dovecot-leave(a)dovecot.org >

1 0

Fwd: connection refused, no error anywhere
by Marco Fioretti 22 Jan '25

22 Jan '25

---------- Forwarded message --------- Da: Marco Fioretti <marco.fioretti(a)gmail.com> Date: mar 21 gen 2025 alle ore 19:27 Subject: Re: connection refused, no error anywhere To: Marc <Marc(a)f1-outsourcing.eu> Hi Marc, this is the output of netstat -tanp (I only removed the line showing the details of my ssh connection): Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 516/systemd-resolve tcp 0 0 127.0.0.54:53 0.0.0.0:* LISTEN 516/systemd-resolve tcp 0 0 127.0.0.1:10023 0.0.0.0:* LISTEN 28575/postgrey --in tcp6 0 0 :::80 :::* LISTEN 26990/apache2 tcp6 0 0 ::1:10023 :::* LISTEN 28575/postgrey --in and indeed it there is no tracce of dovecot there, but what should I do then? "service dovecot status" says the service IS active... Thanks! Il giorno mar 21 gen 2025 alle ore 19:00 Marc <Marc(a)f1-outsourcing.eu> ha scritto: > You are sure dovecot is running on the ports (netstat -tanp). You are sure > this firewall is ok? Maybe flush it, just to be sure. > > > Greetings, > > > > I was just tasked with rebuilding from scratch the mail server of an > > NGO, > > on a brand new Ubuntu 24.04 LTS VPS. > > > > I have copied the whole dovecot configuration to the new server, and now > > am > > stuck because: > > > > - dovecot IS running, dovecot service status shows no errors, but: > > > > - if I try to connect with mutt from my desktop I get "connection > > refused" > > > > - the ufw firewall does allow imap/imaps connections, and there are no > > errors in its log > > > > - even "telnet localhost 143" fails: > > Trying ::1... > > Connection failed: Connection refused > > Trying 127.0.0.1... > > telnet: Unable to connect to remote host: Connection refused > > > > - I see no related errors in /var/log/mail.log or /var/log/syslog. > > > > > > output of dovecot -n is pasted below, I only changed the actual domain > > name > > to "example.com" > > > > TIA for any pointer, I really need to get this server back online as > > soon > > as possible... > > > > Marco > > > > # 2.3.21 (47349e2482): /etc/dovecot/dovecot.conf > > # Pigeonhole version 0.5.21 (f6cd4b8e) > > doveconf: Warning: NOTE: You can get a new clean config file with: > > doveconf > > -Pn > dovecot-new.conf > > doveconf: Warning: Obsolete setting in /etc/dovecot/conf.d/10- > > ssl.conf:9: > > ssl_dh_parameters_length is no longer needed > > # OS: Linux 6.8.0-51-generic x86_64 Ubuntu 24.04.1 LTS ext4 > > # Hostname: example.com > > auth_debug = yes > > auth_verbose = yes > > auth_verbose_passwords = plain > > mail_location = maildir:/var/mail/mymail_storage/base/ > > mbox_write_locks = fcntl > > passdb { > > args = /etc/imap.v_users > > driver = passwd-file > > } > > passdb { > > driver = pam > > } > > service auth { > > unix_listener /var/spool/postfix/private/auth { > > group = postfix > > mode = 0660 > > user = postfix > > } > > } > > service imap-login { > > inet_listener imap { > > port = 0 > > } > > } > > ssl_cert = </etc/letsencrypt/live/example.com/fullchain.pem > > ssl_cipher_list = ALL > > ssl_key = # hidden, use -P to show it > > ssl_prefer_server_ciphers = yes > > userdb { > > args = /etc/imap.v_users > > driver = passwd-file > > } > > userdb { > > driver = passwd > > } > > verbose_ssl = yes >

1 0

connection refused, no error anywhere
by Marco Fioretti 21 Jan '25

21 Jan '25

Greetings, I was just tasked with rebuilding from scratch the mail server of an NGO, on a brand new Ubuntu 24.04 LTS VPS. I have copied the whole dovecot configuration to the new server, and now am stuck because: - dovecot IS running, dovecot service status shows no errors, but: - if I try to connect with mutt from my desktop I get "connection refused" - the ufw firewall does allow imap/imaps connections, and there are no errors in its log - even "telnet localhost 143" fails: Trying ::1... Connection failed: Connection refused Trying 127.0.0.1... telnet: Unable to connect to remote host: Connection refused - I see no related errors in /var/log/mail.log or /var/log/syslog. output of dovecot -n is pasted below, I only changed the actual domain name to "example.com" TIA for any pointer, I really need to get this server back online as soon as possible... Marco # 2.3.21 (47349e2482): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.21 (f6cd4b8e) doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -Pn > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/conf.d/10-ssl.conf:9: ssl_dh_parameters_length is no longer needed # OS: Linux 6.8.0-51-generic x86_64 Ubuntu 24.04.1 LTS ext4 # Hostname: example.com auth_debug = yes auth_verbose = yes auth_verbose_passwords = plain mail_location = maildir:/var/mail/mymail_storage/base/ mbox_write_locks = fcntl passdb { args = /etc/imap.v_users driver = passwd-file } passdb { driver = pam } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 0 } } ssl_cert = </etc/letsencrypt/live/example.com/fullchain.pem ssl_cipher_list = ALL ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = /etc/imap.v_users driver = passwd-file } userdb { driver = passwd } verbose_ssl = yes

3 2

Mail with single \r, partial fetch, error "Broken virtual size in mailbox"
by Ewald Dieterich 17 Jan '25

17 Jan '25

I run Dovecot 2.3.21 with the mdbox mailbox format. If I do a certain partial fetch on a mail with a single carriage return \r Dovecot closes the connection and logs the following error: Error: Mailbox INBOX: Deleting corrupted cache record uid=1: UID 1: Broken virtual size in mailbox INBOX: read(/var/spool/dovecot/user/storage/m.1): FETCH BODY[]<18.100> got too little data: 5 vs 6 This happens every time, doveadm force-resync doesn't help. Here's how to reproduce the issue: Deliver a mail with a single carriage return \r (here after the header/body separator, but that's not important): echo -ne "Subject: Test\r\n\r\n\rBody\r\n" | doveadm save -u user Then do a partial fetch from a specific offset: . fetch 1 body[]<18.100> * 1 FETCH (BODY[]<18> {6} ody Connection closed by foreign host. Offset 18 with length 6 should "Body\r\n", that's why the response is 1 byte short ("got too little data: 5 vs 6" in the error message), by why is \r causing this? Other offsets seem to work.

4 5

find mailbox (path) of message
by Marc 13 Jan '25

13 Jan '25

How should I use 'doveadm search -u' to get the mailbox path where the message is stored?

4 4

Bug report on attachment search in dovecot fts plugin
by h.murakami＠lab8.co.jp 10 Jan '25

10 Jan '25

Hi. I am using dovecot's fts plugin and have found a bug-like behavior. I have confirmed that dovecot by itself with fts plugin disabled works fine. dovecot --version 2.3.19.1 (9b53102964) The pattern we found is as follows 1. search with `with attachments` condition from RoundCube linked to dovecot 2. dovecot fts plugin executes the following query to solr but no document is found hdr:application%5c%2f+OR+hdr:multipart%5c%2fm+OR+hdr:multipart%5c%2fsigned+OR+hdr:multipart%5c%2freport 3. roundcube search results also show no items found That's all I have to report. If there is any way to improve the situation, we would like to receive it.

3 2

Re: Problem email client iPhone ios18.2
by Michael Slusarz 09 Jan '25

09 Jan '25

> On 01/08/2025 11:06 AM MST Len Padilla via dovecot <dovecot(a)dovecot.org> wrote: > > Details: > https://github.com/st3fan/dovecot-xaps-daemon > https://github.com/st3fan/dovecot-xaps-plugin Discussion of Apple Push Notifications is kind of irrelevant, since Apple doesn't support this anymore (more accurately: it has been deprecated, and existing users will eventually lose the functionality). See, e.g., https://blog.mxroute.com/important-update-regarding-ios-push-notifications/ michael

2 2

repo.dovecot.org status
by Jasper Spaans 06 Jan '25

06 Jan '25

Hello list, We're using the packages from repo.dovecot.org to run the latest version of dovecot on our systems running ubuntu focal (20.04). We'd like to upgrade these to a more recent ubuntu version[1], but those builds are not available on repo.dovecot.org. Is that repo still supported? If so, what would it take to get builds for ubuntu 22.04 and/or 24.04 on there? I can spend some time on that, but I also have the impression that the build infra (including the scripts) that generate the packages for this repo is not very public. Cheers, Jasper [1] for reasons that are out of scope for this message, using a dockerized build or upgrading to 24.04 (which does come with 2.3.21) is not an option at this moment, so we are currently looking at 22.04. unfortunately that also comes with a dovecot from 2022

2 1

SCRAM-SHA -PLUS variants and Dovecot (Channel Binding)
by * Neustradamus * 04 Jan '25

04 Jan '25

Dear all, In first, I wish you a Happy New Year 2025! In the past, I have requested SCRAM support in Dovecot, etc. I would like to know the situation with -PLUS variants (Channel Binding)? This feature for more security is always missing. RFC 9266: Channel Bindings for TLS 1.3: - https://datatracker.ietf.org/doc/html/rfc9266 Little details, to know easily: - tls-unique for TLS =< 1.2 - tls-server-end-point - tls-exporter for TLS = 1.3 Can you add tls-unique, tls-server-end-point and tls-exporter to be perfect? Stephan Bosch has started but no news since one year: - https://github.com/dovecot/core/compare/main...stephanbosch:dovecot-core:sa… Other links: SASL2 I-D: Extensible Simple Authentication and Security Layer (SASL): - https://datatracker.ietf.org/doc/html/draft-melnikov-sasl2 It is in several XEPs too: - XEP-0388: Extensible SASL Profile: https://xmpp.org/extensions/xep-0388.html - XEP-0440: SASL Channel-Binding Type Capability: https://xmpp.org/extensions/xep-0440.html - XEP-0474: SASL SCRAM Downgrade Protection: https://xmpp.org/extensions/xep-0474.html - XEP-0480: SASL Upgrade Tasks: https://xmpp.org/extensions/xep-0480.html Thanks in advance. Regards, Neustradamus

1 0

Possible SSL Related Issue
by bcs＠nanomail.net 02 Jan '25

02 Jan '25

Need some help in resolving the issue described below and would greatly appreciate any assistance. Please let me know if any additional information is required. Thank you. Updated Postfix with signed certificates from self signed and am experiencing several new log entries that I am unable to identify. See history that follows. * Self signed certificate in Postfix with pop3. Has worked this way since original install. Dec 29 00:12:41 mail dovecot: pop3-login: Login: user=<usr1>, method=PLAIN, rip=209.197.77.67, lip=10.0.1.211, mpid=15448, TLS, session=<CuXLvmEqzM/RxU1D> Dec 29 00:12:41 mail dovecot: pop3(usr1): Disconnected: Logged out top=0/0, retr=0/0, del=0/2825, size=204691614 * Updated log entry for signed certificate in Postfix. Original self signed certificate still used in Dovecot. Note new disconnect record with information such as <136791><t3CWAKwqpieu9RkM> before the Disconnected message. Unable to find anything about these codes. Jan 1 16:48:12 mail dovecot: pop3-login: Login: user=<usr1>, method=PLAIN, rip=174.245.25.12, lip=10.0.1.211, mpid=136791, TLS, session=<t3CWAKwqpieu9RkM> Jan 1 16:48:13 mail dovecot: pop3(usr1)<136791><t3CWAKwqpieu9RkM>: Disconnected: Logged out top=0/0, retr=0/0, del=0/2867, size=206803370 * Self signed certificate in Postfix with imap. Dec 29 00:06:30 mail dovecot: imap-login: Login: user=<usr2>, method=PLAIN, rip=10.0.1.101, lip=10.0.1.211, mpid=15104, TLS, session=<bZezqGEqBMMKAAFl> Dec 29 00:06:31 mail dovecot: imap(usr2): Connection closed (SELECT finished 0.177 secs ago) in=102 out=952 * Updated non self signed certificate in Postfix. Original self signed certificate still used in Dovecot. Similar information before Disconnect message. Jan 1 16:55:00 mail dovecot: imap-login: Login: user=<usr2>, method=PLAIN, rip=10.0.1.4, lip=10.0.1.211, mpid=136855, TLS, session=<Z/7hGKwqntEKAAEE> Jan 1 16:55:00 mail dovecot: imap(usr2)<136855><Z/7hGKwqntEKAAEE>: Connection closed (SELECT finished 0.117 secs ago) in=106 out=1012 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Issue persists and appears worse when attempting to access the mail server with the Rainloop web application. Rainloop log messages before signed certificate update appeared as the following: Dec 29 07:09:17 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=20215, TLS, session=<xTGtkGcqKNgKAAHT> Dec 29 07:09:17 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=20216, TLS, session=<azKtkGcqMtgKAAHT> Dec 29 07:09:17 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=20217, TLS, session=<Qz2tkGcqOtgKAAHT> Dec 29 07:09:17 mail dovecot: imap(usr): Logged out in=211 out=2047 Dec 29 07:09:17 mail dovecot: imap(usr): Logged out in=28 out=787 Dec 29 07:09:17 mail dovecot: imap(usr): Logged out in=80 out=1449 Dec 29 07:09:17 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=20218, TLS, session=<0EetkGcqRNgKAAHT> Dec 29 07:09:17 mail dovecot: imap(usr): Logged out in=350 out=1381 Dec 29 07:09:17 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=20220, TLS, session=<U8+vkGcqVNgKAAHT> Dec 29 07:09:17 mail dovecot: imap(usr): Logged out in=713 out=66680 Dec 29 07:09:24 mail dovecot: imap(usr): Connection closed (SELECT finished 0.176 secs ago) in=110 out=970 But now contain the same type of <141032><n0r2ZbAqLLMKAAHT> entries before Logged out and seems to be completing significantly more logins and logouts. Note the web interface is working. Jan 1 22:02:53 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141032, TLS, session=<n0r2ZbAqLLMKAAHT> Jan 1 22:02:53 mail dovecot: imap(usr)<141032><n0r2ZbAqLLMKAAHT>: Logged out in=11 out=457 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Jan 1 22:02:53 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141034, TLS, session=<4OP7ZbAqOLMKAAHT> Jan 1 22:02:53 mail dovecot: imap(usr)<141034><4OP7ZbAqOLMKAAHT>: Logged out in=80 out=1470 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Jan 1 22:02:54 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141038, TLS, session=<Grz9ZbAqSLMKAAHT> Jan 1 22:02:54 mail dovecot: imap(usr)<141038><Grz9ZbAqSLMKAAHT>: Logged out in=342 out=1473 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Jan 1 22:02:54 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141039, TLS, session=<+Mf9ZbAqVLMKAAHT> Jan 1 22:02:54 mail dovecot: imap(usr)<141039><+Mf9ZbAqVLMKAAHT>: Logged out in=693 out=37481 deleted=0 expunged=0 trashed=0 hdr_count=20 hdr_bytes=20978 body_count=0 body_bytes=0 Jan 1 22:02:59 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141041, TLS, session=<MxRKZrAq6IcKAAHT> Jan 1 22:02:59 mail dovecot: imap(usr)<141041><MxRKZrAq6IcKAAHT>: Logged out in=28 out=881 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Jan 1 22:03:07 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141043, TLS, session=<SsLKZrAq7ocKAAHT> Jan 1 22:03:07 mail dovecot: imap(usr)<141043><SsLKZrAq7ocKAAHT>: Logged out in=525 out=10554 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=3522 body_count=1 body_bytes=4807 Jan 1 22:03:08 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141045, TLS, session=<b2/bZrAq/IcKAAHT> Jan 1 22:03:08 mail dovecot: imap(usr)<141045><b2/bZrAq/IcKAAHT>: Logged out in=523 out=15895 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=947 body_count=1 body_bytes=13215 Jan 1 22:03:09 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141047, TLS, session=<P3XrZrAqsJYKAAHT> Jan 1 22:03:09 mail dovecot: imap(usr)<141047><P3XrZrAqsJYKAAHT>: Logged out in=523 out=8719 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=779 body_count=1 body_bytes=6300 Jan 1 22:03:10 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141049, TLS, session=<JmD7ZrAqwJYKAAHT> Jan 1 22:03:10 mail dovecot: imap(usr)<141049><JmD7ZrAqwJYKAAHT>: Logged out in=523 out=13125 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=780 body_count=1 body_bytes=10700 Jan 1 22:03:11 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141051, TLS, session=<kkoLZ7Aq0JYKAAHT> Jan 1 22:03:11 mail dovecot: imap(usr)<141051><kkoLZ7Aq0JYKAAHT>: Logged out in=523 out=8022 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=800 body_count=1 body_bytes=5582 Jan 1 22:03:12 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141055, TLS, session=<7ywbZ7Aq4JYKAAHT> Jan 1 22:03:12 mail dovecot: imap(usr)<141055><7ywbZ7Aq4JYKAAHT>: Logged out in=523 out=13955 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=1113 body_count=1 body_bytes=11104 Jan 1 22:03:13 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141057, TLS, session=<JAMrZ7Aq6JYKAAHT> Jan 1 22:03:13 mail dovecot: imap(usr)<141057><JAMrZ7Aq6JYKAAHT>: Logged out in=523 out=14232 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=774 body_count=1 body_bytes=11814 Jan 1 22:03:14 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141059, TLS, session=<lvE6Z7Aq9JYKAAHT> Jan 1 22:03:14 mail dovecot: imap(usr)<141059><lvE6Z7Aq9JYKAAHT>: Logged out in=523 out=6987 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=749 body_count=1 body_bytes=4599 Jan 1 22:03:15 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141061, TLS, session=<6NdKZ7AqBJcKAAHT> Jan 1 22:03:15 mail dovecot: imap(usr)<141061><6NdKZ7AqBJcKAAHT>: Logged out in=523 out=7126 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=812 body_count=1 body_bytes=4676 Jan 1 22:03:16 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141063, TLS, session=<ebpaZ7AqCJcKAAHT> Jan 1 22:03:16 mail dovecot: imap(usr)<141063><ebpaZ7AqCJcKAAHT>: Logged out in=523 out=26116 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=861 body_count=1 body_bytes=23498 Jan 1 22:03:17 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141065, TLS, session=<2aRqZ7AqDJcKAAHT> Jan 1 22:03:17 mail dovecot: imap(usr)<141065><2aRqZ7AqDJcKAAHT>: Logged out in=523 out=8776 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=775 body_count=1 body_bytes=6374 Jan 1 22:03:18 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141067, TLS, session=<b4d6Z7AqAOIKAAHT> Jan 1 22:03:18 mail dovecot: imap(usr)<141067><b4d6Z7AqAOIKAAHT>: Logged out in=523 out=9875 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=749 body_count=1 body_bytes=7498 Jan 1 22:03:20 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141069, TLS, session=<a3GKZ7AqCuIKAAHT> Jan 1 22:03:20 mail dovecot: imap(usr)<141069><a3GKZ7AqCuIKAAHT>: Logged out in=523 out=61311 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=1153 body_count=1 body_bytes=58591 Jan 1 22:03:21 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141071, TLS, session=<AHuaZ7AqDuIKAAHT> Jan 1 22:03:21 mail dovecot: imap(usr)<141071><AHuaZ7AqDuIKAAHT>: Logged out in=523 out=9458 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=1150 body_count=1 body_bytes=6745 Jan 1 22:03:22 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141073, TLS, session=<X2WqZ7AqGuIKAAHT> Jan 1 22:03:22 mail dovecot: imap(usr)<141073><X2WqZ7AqGuIKAAHT>: Logged out in=523 out=11885 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=772 body_count=1 body_bytes=9482 Jan 1 22:03:23 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141075, TLS, session=<eEu6Z7AqKOIKAAHT> Jan 1 22:03:23 mail dovecot: imap(usr)<141075><eEu6Z7AqKOIKAAHT>: Logged out in=523 out=8665 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=777 body_count=1 body_bytes=6326 Jan 1 22:03:24 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141077, TLS, session=</i3KZ7AqOOIKAAHT> Jan 1 22:03:24 mail dovecot: imap(usr)<141077></i3KZ7AqOOIKAAHT>: Logged out in=523 out=42692 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=778 body_count=1 body_bytes=40360 Jan 1 22:03:25 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141079, TLS, session=<NCDaZ7AqOuIKAAHT> Jan 1 22:03:25 mail dovecot: imap(usr)<141079><NCDaZ7AqOuIKAAHT>: Logged out in=523 out=19469 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=1641 body_count=1 body_bytes=16070 Jan 1 22:03:26 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141081, TLS, session=<QAfqZ7AqPuIKAAHT> Jan 1 22:03:26 mail dovecot: imap(usr)<141081><QAfqZ7AqPuIKAAHT>: Logged out in=523 out=9596 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=858 body_count=1 body_bytes=7098 Jan 1 22:03:29 mail dovecot: imap-login: Login: user=<usr>, method=PLAIN, rip=10.0.1.211, lip=10.0.1.211, mpid=141083, TLS, session=<AgEYaLAqgLUKAAHT> Jan 1 22:03:29 mail dovecot: imap(usr)<141083><AgEYaLAqgLUKAAHT>: Logged out in=523 out=11342 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=1188 body_count=1 body_bytes=8581 Jan 1 22:10:40 mail dovecot: imap(usr)<141310><rUXLgbAqGq8KAAE8>: Connection closed (SELECT finished 0.074 secs ago) in=101 out=966 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0

2 1

Hard-coded upper limit for sieve_max_redirects ?
by Maciej Polewczynski 02 Jan '25

02 Jan '25

Hello, After upgrading Dovecot from version 2.3.4 to 2.3.19 i noticed errors for some users having sieve redirects. Before upgrade all worked fine. In sieve plugin i have two limits: sieve_max_actions = 500 sieve_max_redirects = 150 If user have up to 100 redirects all works fine but if there are 101 or more none of them works and there is error: dovecot: lmtp(test2.mbox) Error: sieve: msgid=<***l>: redirect action: failed to check for duplicate forward to <101th.email.address> It seams that there is another limit but cant find where. When checked "dovecot -n|grep 100" there was only "default_process_limit". Increasing this changed nothing. Still the same error. File ".dovecot.sieve.log" in user home dir don't have any additional information. There is only: redirect action: failed to check for duplicate forward: internal error occurred: refer to server log for more information. Do you have any ideas how to fix it? -- Best regards, Maciej Polewczyński Do or do not. There is no try.

3 4

Moving all mail from one user to another
by Peter Reinhold 29 Dec '24

29 Dec '24

Hi all I have a user that has changed domain, and I am looking to move all her mail from her old account into her new one, but I am really unsure about how to go about it I would think that I am should use https://doc.dovecot.org/main/core/man/doveadm-move.1.html to do it, but the example supplied and all discussion about that tool I can find online is only about moving a users mail across folders on their account, and not the entire accounts content to another account. Has anyone tried to do something like this? -- Peter Reinhold

3 2

993 SSL 143 No encryption
by Dino Edwards 26 Dec '24

26 Dec '24

Hello, I have a dovecot server that listens on both 143 and 993 using SSL. I'm trying to get the 143 port to be unencrypted while 993 to remain encrypted. Is there any way to accomplish this? Thanks

2 3

vacation auto reply mail line endings CR LF
by tobias.niethammer＠projektb.net 21 Dec '24

21 Dec '24

Hi all, I tried to setup dovecot 2.3.21.1 (d492236fa0) (dovecot-pigeonhole-0.5.21.1) with the sieve vacation function. I'm getting here a bit into trouble. if I sent an e-mail to an receipient dovecot does via dma and the local mailserver an mail reply but the mail does only have the header inside. After a bit research my conclusion is that the reply mail which gets generated has line endings CR LF. I have to remove this manualy and set it to \LF to get the mail correcly transfered. I Setup the sieve rule with roundcube. I tried to manualy change the .dovecot.sieve file endings and comipled with sievec .dovecot.sieve .dovecot.svbin the binary again, with no change in the behavior. I guess i missed somewhere an variable to fix this issue? here the sieve file: #################################################### require ["vacation"];^M # rule:[Urlaub]^M if true^M {^M vacation :addresses "test02(a)projektb-mail.net" :subject "test Urlaub" text:^M test 1 test 2 test 3^M .^M ;^M }^M #################################################### thank you for your Support Tobias

4 5

Sekt
by Michael Grimm 20 Dec '24

20 Dec '24

.

1 1

COPY vs MOVE
by Scott Q. 19 Dec '24

19 Dec '24

Anyone that knows a bit about the dovecot internals. is move in any way faster than copy / set deleted flag / expunge ? Thanks! Scott

1 0

failed: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown: SSL alert number 46, session=
by Marc 19 Dec '24

19 Dec '24

What is the best way to get rid of this message? I think clients start generating after ssl crt update.

3 8

ACL propagation with acl_defaults_from_inbox
by Francois Lesueur 19 Dec '24

19 Dec '24

Hello, When dovecot is configured with "acl_defaults_from_inbox = yes", ACL propagation when creating folders seems a bit strange to us. The current behavior is : - INBOX has some ACLs defined in its dovecot-acl file - This ACL is the default for subfolders without a dovecot-acl file inside ("acl_defaults_from_inbox = yes") - When creating a folder, a dovecot-acl file is created inside this folder with a copy of the contents of the dovecot-acl from the INBOX The behavior we expected was : - INBOX has some ACLs defined in its dovecot-acl file - This ACL is the default for subfolders without a dovecot-acl file inside - When creating a folder directly under INBOX, a dovecot-acl file should not be created, as the default from INBOX is already enforced. For subfolders, defaults from INBOX should not be propagated either in the dovecot-acl files. Although dovecot-acl files in subfolders allow to have exceptions, most usage of "acl_defaults_from_inbox = yes" is probably to have mailbox-wide ACLs. In the current behavior, when someone removes an ACL from the INBOX, it will still be present in subfolders, which is error-prone in a setup where users expect that their INBOX ACL is enforced throughout their mailbox. I think that avoiding propagating INBOX ACL when creating a new folder in the case where "acl_defaults_from_inbox" is activated would be more intuitive. Am I missing something ? Cheers, Francois

1 0

Recursive doveadm acl add for shared mailbox
by r.barclay＠habmalnefrage.de 17 Dec '24

17 Dec '24

Hello, I have a shared mailbox (e.g. "info(a)example.org") and want to give a new user (e.g. "john.doe(a)example.org") access. I can use: doveadm acl add -u info(a)example.org INBOX user=john.doe(a)example.org create delete expunge insert lookup post read write write-deleted write-seen Unfortunately, the shared mailbox contains several nested folders. And the new user needs to access these, too. So I probably had to use doveadm acl add -u info(a)example.org .INBOX.SubfolderXY user=john.doe(a)example.org create delete expunge insert lookup post read write write-deleted write-seen ... for each and every subfolder. Is there a way to give permissions recursively? INBOX and all (sub-)subfolders? And, by the way, do I have to use doveadm acl recalc -u info(a)example.org OR doveadm acl recalc -u john.doe(a)example.org after that? At the moment I always do both. Thank you! Reg

3 3

Is there anyway for mail logger plugins to log RETR event??
by Chi Min Wang 17 Dec '24

17 Dec '24

Hello Everyone: The dovecot mail_logger_plugins did support delete/undelete/expunge/mailbox_delete/mailbox_rename event log,is it possible to add RETR event log?? Thanks!!

1 0

dovecot configuration question userdb driver
by Stanislav 17 Dec '24

17 Dec '24

Greetings, I have a mail server for a few folks, basically my family. My current Dovecot configuration is the following, which works like a charm: ========== passdb { driver = sql args = /usr/local/etc/dovecot/dovecot-sql.conf.ext } userdb { driver = static args = uid=981 gid=981 home=/var/mail/virtual/%d/%n/home } ========== I've decided to deploy Solr to be able to search faster. Now, when I try to execute "doveadm index -A inbox" I get an error "Error: auth-master: userdb list: User listing returned failure" because I'm using the static userdb. My question is, how do I implement the listing users feature while using "static driver" or a similar approach? I really want to keep using the template "/var/mail/virtual/%d/%n/home" instead of defining a custom path for each user. So I came up with this idea to replace "static" with "sql" driver for "userdb" since there's "iterate_query" I can use to achieve my goal, tho I have to define "user_query", so I can do something like: ======= SELECT '/var/mail/virtual/%d/%n/home' AS maildir, 981 AS uid, 981 AS gid FROM mailbox WHERE username='%u' and active='1'; ======= However, this is a useless waste of resources since I'm not really querying anything, and I'm not even sure if there's template support (e.g., %d/%n) in there. Appreciate any help Best

2 3

Error: Couldn't open INBOX: Permission denied
by dovecot＠crighton.me.uk 15 Dec '24

15 Dec '24

I'm trying to get Dovecot working on Rocky 9.5. In 10-mail.conf I have: mail_privileged_group = mail mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u In /var/spool: drwxr-x---. 3 mail mail 64 Dec 13 16:29 mail In /var/spool/mail: -rw-rw----. 1 peter mail 500 Dec 13 16:29 peter When I try to login using Telnet I get the following in /var/log/maillog: Dec 13 17:03:23 Backup dovecot[690594]: pop3-login: Login: user=<peter>, method=PLAIN, rip=172.21.10.5, lip=172.21.10.5, mpid=690664, secured, session=<8Or5zikp7uCsFQoF> Dec 13 17:03:23 Backup dovecot[690594]: pop3(peter)<690664><>: Error: Couldn't open INBOX: Permission denied Dec 13 17:03:23 Backup dovecot[690594]: pop3(peter)<690664><>: Disconnected: Couldn't open INBOX: Permission denied top=0/0, retr=0/0, del=0/0, size=0 (There is a random data between <> - I've deleted it as I'm not sure if it is sensitive. I'm certain I'm typing the password correctly in Telnet and I think the first of the three lines from the log indicate that I successfully connected. But why do I get Permission denied when Dovecot tries to open the INBOX? As far as I can see I've set them right (as per the permissions pasted above).

5 8

Rebuild uuidlist?
by Gandalf Corvotempesta 14 Dec '24

14 Dec '24

Guys i did a mess. A bad script made by me, changed (a lot) of filenames in the maildir, in example almost all email filenames were changed. I think I have to rebuild the UID <> filename mapping because dovecot is still trying to read the old file that doesn't exists anymore (it has a new name) Any suggestions? I think this would lead to a full-download of all messages client side, right ?

1 0

Mail gone when recreating a folder in a second IMAP session
by Ewald Dieterich 13 Dec '24

13 Dec '24

I'm running Dovecot 2.3.21 with the mdbox mailbox format. I lose mails (with an asterisk, see below) when I'm doing the following in 2 IMAP sessions: Session 1: Create a folder, save a mail and select it: . create folder . append folder {1} . select folder * 1 EXISTS * OK [UIDVALIDITY 1734013510] UIDs valid Session 2: Delete the folder, create it again, save a mail in it, check the number of messages and the uidvalidity:. . delete folder . create folder . append folder {1} . status folder (messages uidvalidity) * STATUS folder (MESSAGES 1 UIDVALIDITY 1734013511) Everything is as expected until here, the uidvalidity was increased by 1, which makes sense. Session 1: Just do a noop . noop * BYE IMAP session state is inconsistent, please relogin. Dovecot notices that something is wrong and closes the connection. This error is logged: Error: Mailbox folder: Corrupted transaction log file /var/spool/dovecot/user/mailboxes/folder/dbox-Mails/dovecot.index.log seq 2: indexid changed: 1734011270 -> 1734011403 (sync_offset=0) Session 2: Check the folder again: . status folder (messages uidvalidity) * STATUS folder (MESSAGES 0 UIDVALIDITY 1734013512) The mail is gone, uidvalidity was again increased by 1, so this is a new folder. I think the problem is that the folder's transaction log is deleted in session 1 in mail_transaction_log_file_open() when Dovecot notices discrepancies in what it expects: if (ret == 0) { /* corrupted */ if (index->readonly) { /* don't delete */ } else { i_unlink_if_exists(file->filepath); } *reason_r = "File is corrupted"; return 0; } This basically recreates the folder, so now it's empty. Here's the asterisk: I know that technically the mail isn't lost because it's still in the storage file and can be recovered. But it's still ugly. And when I copy a mail from another folder instead of appending it, I can't recover it for the folder because the information that the mail was copied is definitely lost. Can this be fixed in Dovecot?

3 4

sieve enotify mixes message body and subject
by Cajus Korn 12 Dec '24

12 Dec '24

Dear Community, I found that the following lines of a sieve filter require ["enotify"]; # rule:[enotify] if true { notify :importance "2" :message "New Message received." "mailto:xyz@somedomain.com"; } results in getting the following reply: [...] X-Sieve: Pigeonhole Sieve 0.5.21.1 (49005e73) Message-ID: <dovecot-sieve-1733953974-73072-0(a)ironman.cajus.name> Date: Wed, 11 Dec 2024 22:52:54 +0100 Subject: New Message received. From: Postmaster <postmaster(a)ironman.cajus.name> To: xyz(a)somedomain.com Auto-Submitted: auto-notified; owner-email="contacta(a)ironman.cajus.name" Precedence: bulk X-Priority: 3 (Normal) Importance: Normal MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Notification of new message. Shouldn't the message "New Message received." be in the mail body and "Notification of new message." be in the subject? So body and subject got mixed up. Until now I do not know how to debug this further. Any ideas? kind regards Cajus

1 0