December 2024 - dovecot

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 11 Dec '24

11 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