- dovecot - dovecot.org

R: Dovecot 2.3 shared namespace issues
by Stefano Cecconello 15 Nov '22

15 Nov '22

Hello, My bad, the OS was ubuntu 20.04 and not 22.04 . After further tinkering\testing, it seems that removing the " acl_ignore_namespace = shared/* " setting did the trick, now we're getting the correct ACL on client side . Without it we can see the folder with the right permissions : Logging as user01 : shared\Sharer01\INBOX : '[NONEXISTENT] Mailbox doesn't exist: shared/test.imapsharer01(a)td01.testdomain.it/INBOX'' shared\Sharer01\subfolder01 ( RW ) : 'shared/test.imapsharer01(a)td01.testdomain.it/subfolder01 test.imapuser01(a)td01.testdomain.it akxeilprwtscd '] shared\Sharer01\subfolder02ro ( RO ) : '[NOPERM] You lack administrator privileges on this mailbox' Logging on Thunderbird and other IMAP clients ( sylpheed\claws ) as user01 : - It list correctly the shared folders as subscribed folders ; - can't view the mail contents of the sharer INBOX, as desired ; - show the total elements of the sharer INBOX, even if the user01 didnt have access ; If the config is correct, this is somehow what we're trying to accomplish, i have some concerns regarding how it is possible to show the total messages of the remote INBOX without having any privileges . Maybe is something related to the index of that INBOX folder that is somewhat read by the accessing user even if IMAP-wise didnt have any ACL \ rights . I still dont understand why enabling the acl_ignore_namespace setting, results in a : - remote INBOX full control, even if it was not defined in any acl ; - subfolders ACL applied correctly Hope that someone can shed a light on it . Thanks Stefano

1 0

Re: bug: ARGON2 hash selection incompatible with LDAP
by Krisztián Szegi 15 Nov '22

15 Nov '22

Sorry, I wanted to post from this alias, but From-Address isn't saved with my drafts :) I failed to recognize during my patchwork that the verification function is the same for ARGON2I and -ID: both call `verify_argon2`, which in turn calls `libsodium's crypto_pwhash_str_verify`. In the new light this, there is no "harm" in my patch: - If backend gives back "{ARGON2}...", dovecot verifies with the same call anyway, regardless of what subtype it actually is, i.e.: {ARGON2I} will work too. - If dovecot generates the hash, the prefix will be the one set by the config's default hash, so for backwards comp., "{ARGON2ID}" could be used if someone wants that. Dovecot will succeed in verifying {ARGON2} generated by itself as well. "Aki Tuomi" aki.tuomi(a)open-xchange.com – 15 November 2022 13:55 > > On 15/11/2022 14:45 EET Krisztián Szegi <oni-dono(a)mszk.eu> wrote: > > > > > > Good day to all, > > > > this is my first post to the mailing list! > > > > I'd like to report that non-binding auth to (Open)LDAP doesn't work if the latter hashes passwords with ARGON2. > > > > Although dovecot (I am using http://2.3.19.1) does support ARGON2 with libsodium, but it doesn't recoginize hashes beginning "{ARGON2}$argon2id$" stored (and hashed, using ppolicy module's hashCleartext) by OpenLDAP. > > > > Now, I understand that ARGON2I, -D, and -ID are not compatible, but the ACTUAL algorithm is there between the two $. > > Furthermore, I think dovecot is in the minority here, I haven't met any software that specifies the ARGON2 subtype between {}. > > BTW, I haven't met any software that hashes passwords with ARGON2, but not with the ARGON2ID subtype (where libsodium is available, which also seems to be the standard here), as THAT is the recommended one anyway. > > > > I patched the rpm in OpenSUSE repo to alias {ARGON2} to {ARGON2ID}: > > https://build.opensuse.org/package/view_file/home:Samonitari:branches:openS… > > > > Could we get something like this (but maybe more correct) into the official source? > > Maybe a config switch to alias it runtime? > > > > Thanks for the attention: > > Krisztián > > Hi! > > Thanks for your report. I think it makes sense, we'll see what we can do about this. > > Aki > >

1 0

Dovecot 2.3 shared namespace issues
by Stefano Cecconello 15 Nov '22

15 Nov '22

Hello, We're trying to configure the shared mailbox feature\namespace on a dovecot 2.3 installation . OS : Ubuntu 22.04 x64 Dovecot : 2:2.3.19.1-2+ubuntu20.04 Our test enviroment is based on a dovecot frontend ( director + proxy ) and a dovecot backend ( auth and storage ), later we will think about increasing the number of backends and frontends ( if we got it right, as we plan to use multiple backends, we should use imapc in order to bind the sharer and the accessing user to the same backend ) . On dovecot backend we've configured the new shared namespace, as stated in the documentation ( https://doc.dovecot.org/configuration_manual/shared_mailboxes/shared_mailbox es/#user-shared-mailboxes ) : -- Dovecot conf -------------------- # Maildir's location is under home dir, which is returned by userdb. mail_location = maildir:~/Maildir:VOLATILEDIR=/tmp_lock/%2.256Nu/%u # Quota, mail_log plugins enabled everywhere mail_plugins = quota notify acl fts fts_lucene mail_log mailbox_alias virtual # Default namespace namespace { hidden = no inbox = yes location = prefix = separator = / type = private mailbox Sent { special_use = \Sent auto = create } mailbox Trash { special_use = \Trash auto = create } mailbox Drafts { special_use = \Drafts auto = create } mailbox SPAM { special_use = \Junk auto = create } } # namespace used by virtual search namespace { prefix = VrtSearch. separator = / location = virtual:/etc/dovecot-common-backend/virtual:INDEX=~/virtual hidden = yes subscriptions = no inbox = no list = no } # IMAP SHARING FEATURE service dict { unix_listener dict { mode = 0600 user = vpopmail group = vchkpw } } plugin { acl = vfile acl_ignore_namespace = shared/* acl_shared_dict = proxy::acl-mysql } dict { acl-mysql = mysql:/etc/dovecot-common-backend/dovecot-dict-sql.conf.ext } # namespace used for IMAP sharing feature namespace { type = shared separator = / prefix = shared/%%u/ location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u list = children subscriptions = no } -- Dovecot dict sql -------------------- # IMAP SHARING FEATURE connect = host=x.x.x.x dbname=xxxxxx user=xxxxxx password=xxxxxx map { pattern = shared/shared-boxes/user/$to/$from table = imap_user_shares value_field = dummy fields { from_user = $from to_user = $to } } map { pattern = shared/shared-boxes/anyone/$from table = imap_anyone_shares value_field = dummy fields { from_user = $from } } -- Dict DB contents -------------------- mysql> select * from imap_user_shares; +------------------------------------------+-------------------------------- --------+-------+ | from_user | to_user | dummy | +------------------------------------------+-------------------------------- --------+-------+ | test.imapsharer01(a)td01.testdomain.it | test.imapuser01(a)td01.testdomain.it | 1 | +------------------------------------------+-------------------------------- --------+-------+ For our tests, we've : - created two users test.imapsharer01(a)td01.testdomain.it test.imapuser01(a)td01.testdomain.it - Created two INBOX subfolders on the sharer01 user, giving user01 those permissions : subfolder01 giving to user01 Full control subfolder02ro giving to user01 list and read - logging as user01 with thunderbird, we see the shared namespace tree : shared test.imapsharer01(a)td01.testdomain.it subfolder01 subfolder02 we're able to see the contents of each folder, even the INBOX . Checking the folder properties, thunderbird reports that the user01 has full control on the INBOX of shared01 . If we try to check the ACL via python script ( imaplib.gestacl ) or via doveadm, we can see that the sharer01 INBOX has no rights for user01 . But via thunderbird ( or other email clients ) we can delete emails . ACL - sharer01 accessing its folder ('OK', [b'INBOX test.imapsharer01(a)td01.testdomain.it lrwstipekxacd']) ('OK', [b'subfolder01 test.imapuser01(a)td01.testdomain.it akxeilprwtscd test.imapsharer01(a)td01.testdomain.it lrwstipekxacd']) ('OK', [b'subfolder02ro test.imapuser01(a)td01.testdomain.it lr test.imapsharer01(a)td01.testdomain.it lrwstipekxacd']) ACL - user01 accessing sharer01 folders ('OK', [b'shared/test.imapsharer01(a)td01.testdomain.it/INBOX']) ('OK', [b'shared/test.imapsharer01(a)td01.testdomain.it/subfolder01 test.imapuser01(a)td01.testdomain.it akxeilprwtscd']) ('OK', [b'shared/test.imapsharer01(a)td01.testdomain.it/subfolder02ro test.imapuser01(a)td01.testdomain.it lr']) Testing with doveadm shows the correct ACL : # doveadm -c /etc/dovecot-backend01/dovecot.conf acl debug -u test.imapuser01(a)td01.testdomain.it shared/test.imapsharer01(a)td01.testdomain.it/INBOX doveadm(test.imapuser01(a)td01.testdomain.it): Info: Mailbox 'INBOX' is in namespace 'shared/test.imapsharer01(a)td01.testdomain.it/' doveadm(test.imapuser01(a)td01.testdomain.it): Info: Mailbox path: /home/vpopmail/domains/td01.testdomain.it/dccm4584.imapsharer01/Maildir doveadm(test.imapuser01(a)td01.testdomain.it): Info: All message flags are shared across users in mailbox doveadm(test.imapuser01(a)td01.testdomain.it): Info: User test.imapuser01(a)td01.testdomain.it has no rights for mailbox doveadm(test.imapuser01(a)td01.testdomain.it): Error: User test.imapuser01(a)td01.testdomain.it is missing 'lookup' right doveadm(test.imapuser01(a)td01.testdomain.it): Info: Mailbox shared/test.imapsharer01(a)td01.testdomain.it/INBOX is NOT visible in LIST # doveadm -c /etc/dovecot-backend01/dovecot.conf acl debug -u test.imapuser01(a)td01.testdomain.it shared/test.imapsharer01(a)td01.testdomain.it/subfolder01 doveadm(test.imapuser01(a)td01.testdomain.it): Info: Mailbox 'subfolder01' is in namespace 'shared/test.imapsharer01(a)td01.testdomain.it/' doveadm(test.imapuser01(a)td01.testdomain.it): Info: Mailbox path: /home/vpopmail/domains/td01.testdomain.it/dccm4584.imapsharer01/Maildir/.sub folder01 doveadm(test.imapuser01(a)td01.testdomain.it): Info: All message flags are shared across users in mailbox doveadm(test.imapuser01(a)td01.testdomain.it): Info: User test.imapuser01(a)td01.testdomain.it has rights: lookup read write write-seen write-deleted insert post expunge create delete admin doveadm(test.imapuser01(a)td01.testdomain.it): Info: Mailbox found from dovecot-acl-list doveadm(test.imapuser01(a)td01.testdomain.it): Info: User test.imapsharer01(a)td01.testdomain.it found from ACL shared dict doveadm(test.imapuser01(a)td01.testdomain.it): Info: Mailbox shared/test.imapsharer01(a)td01.testdomain.it/subfolder01 is visible in LIST # doveadm -c /etc/dovecot-backend01/dovecot.conf acl debug -u test.imapuser01(a)td01.testdomain.it shared/test.imapsharer01(a)td01.testdomain.it/subfolder02ro doveadm(test.imapuser01(a)td01.testdomain.it): Info: Mailbox 'subfolder02ro' is in namespace 'shared/test.imapsharer01(a)td01.testdomain.it/' doveadm(test.imapuser01(a)td01.testdomain.it): Info: Mailbox path: /home/vpopmail/domains/td01.testdomain.it/dccm4584.imapsharer01/Maildir/.sub folder02ro doveadm(test.imapuser01(a)td01.testdomain.it): Info: All message flags are shared across users in mailbox doveadm(test.imapuser01(a)td01.testdomain.it): Info: User test.imapuser01(a)td01.testdomain.it has rights: lookup read doveadm(test.imapuser01(a)td01.testdomain.it): Info: Mailbox found from dovecot-acl-list doveadm(test.imapuser01(a)td01.testdomain.it): Info: User test.imapsharer01(a)td01.testdomain.it found from ACL shared dict doveadm(test.imapuser01(a)td01.testdomain.it): Info: Mailbox shared/test.imapsharer01(a)td01.testdomain.it/subfolder02ro is visible in LIST in the debug log we can see the delete operation : Nov 15 10:53:25 imap(357716 test.imapuser01@td01.testdomain.it):Debug: Mailbox Trash: Mailbox opened Nov 15 10:53:25 imap(357716 test.imapuser01@td01.testdomain.it):Debug: acl vfile: file /home/vpopmail/domains/td01.testdomain.it/dccm4584.imapuser01/Maildir/.Trash /dovecot-acl not found Nov 15 10:53:25 imap(357716 test.imapuser01@td01.testdomain.it):Debug: Mailbox shared/test.imapsharer01(a)td01.testdomain.it: Mailbox opened Nov 15 10:53:25 imap(357716 test.imapuser01@td01.testdomain.it):Debug: Mailbox Trash: Adding field flags to cache for the first time (uid=0) Nov 15 10:53:25 imap(357716 test.imapuser01@td01.testdomain.it):Debug: Mailbox Trash: saving UID 0: Opened mail because: header Message-ID (Cache file is unusable) Nov 15 10:53:25 imap(357716 test.imapuser01@td01.testdomain.it):Debug: Mailbox Trash: Adding field hdr.Message-ID to cache for the first time (uid=0) Nov 15 10:53:25 imap(357716 test.imapuser01@td01.testdomain.it):Debug: Mailbox shared/test.imapsharer01(a)td01.testdomain.it: UID 1: Expunge requested Nov 15 10:53:25 imap(357716 test.imapuser01@td01.testdomain.it):Debug: Mailbox Trash: Purging (new file_seq=1668506005): creating cache Nov 15 10:53:25 imap(357716 test.imapuser01@td01.testdomain.it):Debug: Mailbox Trash: Purging finished, file_seq changed 0 -> 1668506005, size=0 -> 412, max_uid=0 Nov 15 10:53:25 imap(357716 test.imapuser01@td01.testdomain.it):Info: copy from shared/test.imapsharer01(a)td01.testdomain.it: box=Trash, uid=1, msgid=<mnid2m.1.24789225.57389.0.1127444.c495198613._(a)nl.aruba.it> Nov 15 10:53:25 imap(357716 test.imapuser01@td01.testdomain.it):Info: expunge: box=shared/test.imapsharer01(a)td01.testdomain.it, uid=1, msgid=<mnid2m.1.24789225.57389.0.1127444.c495198613._(a)nl.aruba.it> Nov 15 10:53:26 imap(357716 test.imapuser01@td01.testdomain.it):Debug: Mailbox shared/test.imapsharer01(a)td01.testdomain.it: UID 1: Mail expunged After we delete a message, we cannot find it on the Trash folders ( user01 or sharer01 ) . Are we missing something ? Thanks Stefano

1 0

Questions around mailcrypt and LDAP
by Andre Rodier 15 Nov '22

15 Nov '22

Hello, all. I read carefully the messages about mailcrypt on the mailing list, especially this response from Aki: > It's best suited for securing external storage such as NFS or object storage. > There are possibilities to encrypt the key using user's password, but this > takes careful planning. The keys can also come from userdb , e.g. LDAP. I am able to extend the LDAP schema of my OpenLDAP server to store a key into LDAP attribute for each user. In this case, would it be enough for Dovecot to encrypt the messages when they arrive ? Maybe I misunderstand the documentation. Even when using user keys protected by a password, the Dovecot LMTP process should be able to encrypt the emails with user’s public key, without a password, no ? Ideally, I would like to store user's emails encrypted, so each users cannot access other user's emails. I don't need folder sharing. Thanks for your advice. Kind regards, André Rodier

2 2

Dovecot not offering TLSv1.2 after a few minutes
by Markus Wienhöfer 14 Nov '22

14 Nov '22

I have a very strange problem with one of our Dovecot servers (2.2.33.2) on Ubuntu 18.04. The current configuration allows for TLSv1 to TLSv1.3 connections. I can verify those using testssl.sh, the tests will succeed (although correctly mentioning, that TLSv1 and TLSv1.1 should be disabled). Running the tests again after about 5 minutes, the results are different. TLSv1.2 now shows "not offered and downgraded to a weaker protocol". Has anybody experienced a similar problem before? Best regards Markus

2 1

Dovecot 2.3.19.1: BUG: Mailbox renaming algorithm got into a potentially infinite loop, aborting
by Ralf Becker 14 Nov '22

14 Nov '22

I found this from 2019 on the list: https://www.mail-archive.com/dovecot@dovecot.org/msg78898.html Timo mentioned it's tracked internally as DOP-1501, but I could find nothing about it being fixed on the (public) list. Any news about that and is the workaround of deleting dovecot.mailbox.log* and dovecot.list.index* still the recommendation, when running into this bug. Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

2 2

Submission: track authenticated_user
by itanguy＠univ-brest.fr 10 Nov '22

10 Nov '22

Hello, We would like to use Dovecot Submission to have less queues to maintain. The relayhost (Postfix) after Dovecot routes mail by sender_map, so authenticated user, not the "mail from" because . For what we've seen, we can't use receive header to retrieve this authenticated_user. Example of header : Received: from mailhost ([0.0.0.0]) by submission.host with ESMTPSA id submission-id (envelope-from<myadress(a)example.com>) for<myadress(a)example.com>; Thu, 9 Nov 2022 08:27:41 +0000 So we've thought to use X-client, but reading the doc seems that's not the a good way : /https://doc.dovecot.org/settings/core// - submission_relay_trusted If enabled, the relay server is trusted. Determines whether we try to send (Postfix-specific) XCLIENT data to the relay server (only if enabled). But, XCLIENT for Submission seems to not transfer LOGIN : /https://doc.dovecot.org/settings/core/ / XCLIENT command can be used to override: Session ID Client IP and port (|%{rip}|,|%{rport}|) HELO - Overrides what the client sent earlier in the EHLO command LOGIN - Currently unused PROTO - Currently unused |forward_*| fields can be sent to auth process’s passdb lookup The trust is always checked against the connecting IP address. Except if HAProxy is used, then the original client IP address is used. Do you know another way to inform the relayhost of submission of the authenticated_user? Thanks Ismaël TANGUY

2 1

SSL error
by Ruben Safir 10 Nov '22

10 Nov '22

Hello I am getting this error and I have no idea why. openssh is upto date client bash-5.1$ fetchmail --ssl -p POP3 -uruben mail2.boroparkmd.com Enter password for ruben(a)mail2.boroparkmd.com: fetchmail: Server certificate verification error: self signed certificate fetchmail: Missing trust anchor certificate: /C=US/ST=NY/L=Brooklyn/O=Dovecot/OU=mail servuces/CN=*.boroparkmd.com/emailAddress=ruben@mrbrklyn.com fetchmail: This could mean that the root CA's signing certificate is not in the trusted CA certificate location, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page. See README.SSL for details. fetchmail: OpenSSL reported: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed fetchmail: mail2.boroparkmd.com: SSL connection failed. fetchmail: socket error while fetching from ruben(a)mail2.boroparkmd.com fetchmail: Query status=2 (SOCKET) Server: Nov 9 09:36:13 mail2 dovecot[25838]: pop3-login: Disconnected: Connection closed: SSL_accept() failed: error:0A000412:SSL routines::sslv3 alert bad certificate: SSL alert number 42 (no auth attempts in 1 secs): user=<>, rip=96.57.23.83, lip=96.57.23.84, TLS handshaking: SSL_accept() failed: error:0A000412:SSL routines::sslv3 alert bad certificate: SSL alert number 42, session=<MBsPlArtPtxgORdT> -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and extermination camps, but incompatible with living as a free human being. -RI Safir 2013

4 6

Help with configuration?
by Ellie McNeill 10 Nov '22

10 Nov '22

Hi, I'm running my own mail server on Debian 11 with exim and Dovecot 2.3.13. I have it working, but I'm seeking advice on further customising my setup. I'm using the Maildir++ format with some personal folders. I use IMAP to retrieve mail and Dovecot's submission server to send mail. 1. I want to have incoming emails automatically placed in certain folders instead of 'Inbox' based on certain criteria. For example, I want all emails from PayPal to go into the 'PayPal' folder and all emails from the Debian mailing list to go into the 'Debian' folder. Can dovecot do this for me and what is the best approach? 2. When I delete an email using my user client, it is only 'marked' as deleted (Thunderbird places a scored line through it, and a 'T' is added to the filename in the Maildir). How can I get dovecot to automatically move mail marked 'deleted' to the Trash folder each time? I also want further delete operations on any mail in the 'Trash' folder to be permanently deleted. 3. I want to hide my client IP address from the headers when submitting mail to Dovecot's submissiond, but I can't seem to find any way to disable this. I would prefer that recipients only see the server IP address, but not the IP address of the mail client which submitted it. Regards, Ellie PS - When signing up for the mailing list, there was no selection ability on the question "Would you like to get replies to your mails only to the list, ie. add a Reply-To header?"

5 5

Re: SSL error
by Joseph Tam 10 Nov '22

10 Nov '22

Ruben Safir <ruben(a)mrbrklyn.com> wrote: > > This got nothing to with LE or own CA. Bottom line is, you need to > > add your own CA to the cert tore (ideally) > > what is a cert tore? Someone has probably already replied to this, but it's a typo: the OP wanted to say "store". The certificate you created was used to sign itself ("self signed") and thus, asserts its own validity. If you need *other* people to trust your SSL service, you should sign your certificate using a third party authority (e.g. LetsEncrypt) to sign it. Most internet users will have these third party signing authority's certificates in their certificate store to validate your service certificate. If this is for your own personal use (i.e. you don't care about trust since you know it's your own certificate), you have to add your self-signed certificate into *your* system's certificate authority store so that your mail reader does not complain about an untrusted certificate. Clear? Joseph Tam <jtam.home(a)gmail.com>

1 0