- dovecot - dovecot.org

Re: Best mail encryption solution for per-user
by Aki Tuomi 27 May '18

27 May '18

> On 26 May 2018 at 10:36 mail(a)sjemm.net wrote: > > > May 23, 2018 10:10 AM, mail(a)sjemm.net wrote: > > May 23, 2018 9:46 AM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: > > > >> On 23.05.2018 10:15, mail(a)sjemm.net wrote: > >> > >>> May 23, 2018 8:31 AM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: > >> > >> On 23.05.2018 09:13, mail(a)sjemm.net wrote: > >>> May 20, 2018 8:01 PM, mail(a)sjemm.net wrote: > >>> May 20, 2018 2:47 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: > >>> On 19 May 2018 at 16:40 mail(a)sjemm.net wrote: > >>> > >>> May 18, 2018 10:01 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: > >>> On 18 May 2018 at 21:44 mail(a)sjemm.net wrote: > >>> > >>> May 18, 2018 4:43 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: > >>> On 18 May 2018 at 17:38 mail(a)sjemm.net wrote: > >>> > >>> May 18, 2018 4:05 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: > >>> On 18 May 2018 at 16:43 mail(a)sjemm.net wrote: > >>> > >>> Hi Tai74 and Aki, > >>> I followed your conversation with interest on how to setup per user encryption in dovecot. > >>> I have setup my dovecot with the following in a conf file: > >>> > >>> ============== > >>> > >>> mail_attribute_dict = file:%h/Maildir/dovecot-attributes > >>> mail_plugins = $mail_plugins mail_crypt > >>> plugin { > >>> > >>> mail_crypt_curve = secp521r1 > >>> > >>> mail_crypt_save_version = 2 > >>> > >>> } > >>> > >>> ============== > >>> > >>> This works nice, all emails are being encrypted and every user/folder has keys. > >>> But as I understood from your conversation these keys are not protected. And I want them to be > >>> protected by the users password used by imap. > >>> > >>> Those passwords are stored in a mysql DB file. ( I used a guide from workaround [dot] org to set up > >>> the DB and postfix/dovecot) > >>> > >>> but how would i set it so, that the users password from the DB is used to encrypt the keys? > >>> > >>> should i use mail_crypt_private_password = ? > >>> how do i point it to the mysql db then? > >>> im unsure about this > >>> > >>> Do you have any hints on this? > >>> > >>> Kind regards, > >>> Zjemm > >>> > >>> The passwords in your MySQL database are, hopefully, not in plaintext. If you want to secure your > >>> user's keys using user's login password, you must have a TOOL that manages this. > >>> > >>> You can use mail_crypt_private_password = %w in (mysql) passdb fields to provide the user's login > >>> password as private password. You might want to run it thru some hash, so %{sha1:password} might be > >>> a good option. > >>> > >>> You can change the key password using 'doveadm mailbox cryptokey', this needs to be done every time > >>> user changes his password. > >>> > >>> Also note that if you go down this road, and the user forgets his password, you will not be able to > >>> recover the emails without backup copy of the private key. > >>> > >>> Aki > >>> > >>> Hi Aki > >>> > >>> I used the following command: > >>> dovecot pw -s SHA256-CRYPT > >>> > >>> the output on the chosen password looks like: {SHA256-CRYPT}$5$Rokc06a7In4SF3bO$OQpGQWqg........ > >>> > >>> This output is used to store in the password fields in the database. So no plain text passwords no > >>> :) > >>> > >>> You can use mail_crypt_private_password = %w in (mysql) passdb fields to provide the user's login > >>> password as private password. > >>> > >>> can you explain this a bit more for me? > >>> > >>> for now i have in the 10-auth.conf file the following: > >>> ============== > >>> passdb { > >>> driver = sql > >>> > >>> # Path for SQL configuration file, see example-config/dovecot-sql.conf.ext > >>> args = /etc/dovecot/dovecot-sql.conf.ext > >>> } > >>> > >>> and: > >>> > >>> userdb { > >>> driver = static > >>> args = uid=vmail gid=vmail home=/var/vmail/%d/%n > >>> } > >>> ============== > >>> > >>> then i have in dovecot-sql.conf.ext > >>> ============== > >>> driver = mysql > >>> connect = host=x.x.x.x dbname=mailserver user=mailuser password=mailpasswordexample > >>> default_pass_scheme = SHA256-CRYPT > >>> password_query = SELECT email as user, password FROM virtual_users WHERE email='%u'; > >>> ============== > >>> Where do i need to set : mail_crypt_private_password = %w ? > >>> > >>> password as private password. You might want to run it thru some hash, so %{sha1:password} might be > >>> a good option. > >>> > >>> the passwords are allready hashed in the DB using: dovecot pw -s SHA256-CRYPT to genereate the has. > >>> so this step isnt nesesary anymore am i right? > >>> > >>> Thank you for your quick response, very helpfull > >>> > >>> Zjemm > >>> > >>> You misunderstood a bit. The idea is to use the *plaintext* password as the password for the > >>> private key. Otherwise anyone could just decrypt it by looking at your database where the hashed > >>> password is.. > >>> > >>> So: > >>> > >>> password_query = SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM > >>> virtual_users WHERE email='%u' > >>> > >>> Aki > >>> > >>> Hi Aki, > >>> > >>> Thank you very much for your help, i realy appreciate that. > >>> > >>> Ok so if i understand it correctly i'll have to use: > >>> > >>> password_query = SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM > >>> virtual_users WHERE email='%u' > >>> > >>> in my dovecot-sql.conf.ext file > >>> > >>> This query selects the user, the password, and %w > >>> > >>> if i run a little query myself: > >>> MariaDB [mailserver]> SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password > >>> FROM virtual_users; > >>> +------------------+----------------------------------+------------------------------------+ > >>> | user | password | userdb_mail_crypt_private_password | > >>> +------------------+----------------------------------+------------------------------------+ > >>> | john(a)example.org | {SHA256-CRYPT}$5$M/GWzmtjsLroRWI | %w | > >>> +------------------+----------------------------------+------------------------------------+ > >>> > >>> %w is a dovecot variable, and stands for the plaintext password, but the password is not stored as > >>> plaintext in the DB, %w get filled with the actual plaintext password by dovecot upon the user that > >>> is typing in the password when authenticating. > >>> > >>> is this correct? > >>> > >>> yes. > >>> > >>> so then i have the username the hashed password en the plaintext password as a result of the query. > >>> > >>> yes > >>> > >>> now userdb_mail_crypt_private_password = the plaintext password > >>> do i need to reference it somewhere? or is userdb_mail_crypt_private_password autmatically used by > >>> the dovecot mail_crypt plugin to encrypt the keys? or should it be mail_crypt_private_password? > >>> > >>> It gets injected into the mail process as 'mail_crypt_private_password', as if it was set in plugin > >>> {} section. > >>> > >>> if i have this setup working i'm going to write a blog post on this topic to share this knowledge > >>> > >>> Thanks again and have a great weekend. > >>> > >>> Zjemm > >>> > >>> Aki > >>> > >>> Hi Aki, > >>> > >>> Cool i'm testing it right now. > >>> I have set up a new mailserver (life is great with lxc containers :) ) > >>> > >>> postfix and dovecot are working like normal > >>> > >>> next i enable mail_crypt > >>> > >>> i did create a file: /etc/dovecot/conf.d/10-mailcrypt.conf > >>> ========================== > >>> mail_attribute_dict = file:%h/Maildir/dovecot-attributes > >>> > >>> mail_plugins = $mail_plugins mail_crypt > >>> > >>> plugin { > >>> mail_crypt_curve = secp521r1 > >>> mail_crypt_save_version = 2 > >>> } > >>> ========================== > >>> > >>> and then i changed the file: /etc/dovecot/dovecot-sql.conf.ext > >>> > >>> so the query is now the new query: > >>> password_query = SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM > >>> virtual_users WHERE email='%u'; > >>> > >>> then i restarted dovecot and postfix and send a test email to the one and only testuser that is in > >>> there. > >>> > >>> when i open the mailbox with the tool mutt, i can see the new email, and when openening the email > >>> the mutt client drops the connection. > >>> > >>> in the log i can see: > >>> > >>> May 19 13:34:48 mailserver1.example.local dovecot[600]: imap-login: Login: user=<john(a)example.org>, > >>> method=PLAIN, rip=::1, lip=::1, mpid=713, TLS, session=<E3PnIY9sNM4AAAAAAAAAAAAAAAAAAAAB> > >>> May 19 13:34:49 mailserver1.example.local dovecot[600]: imap(john(a)example.org): Error: read() > >>> failed: > >>> read(/var/vmail/example.org/john/Maildir/cur/1526736378.M161472P641.mailser…, > >>> =571:2,) failed: Private key not available: Cannot decrypt key > >>> bfc5bb25b1bf64290eea6dc14b516c6a0a25b64551b6e4f0f8677ba7274887cb: error:03070068:bignum > >>> routines:BN_mpi2bn:encoding error (FETCH BODY[] for mailbox INBOX UID 8) > >>> > >>> i think i missed a step, but witch one? > >>> > >>> the userpassword hasnt been changed (that would be the next step in the testing process) > >>> > >>> should i've use doveadm first to encrypt the key with that userpassword? i thought it would do that > >>> on the fly, because the initial keys where only just created when enabling the mail_crypt plugin > >>> > >>> please let me know your thougts > >>> Zjemm > >>> I noticed you replied directly to me, and not to the list, too... fixed that for you. > >>> > >>> mail_crypt_private_password is used when key is created, but if you have created it before using > >>> password, you'll need to encrypt it before turning the setting on. > >>> > >>> Aki > >>> Hi, Ok i'm sorry about that, thank you for fixing that. i'm a bit new to mailing lists :) > >>> > >>> are you a dovecot devoloper? or a enthusiastic user? > >>> > >>> anyway, i managed to get it working now with all your help :) > >>> > >>> to start fresh i did a: > >>> rm -rf /var/vmail/example.org > >>> > >>> so all email is gone, and i assume all dovecot keys are gone that way. > >>> > >>> Then i tried to set a password first: > >>> > >>> root@mailserver1:/var/vmail# doveadm mailbox cryptokey password -u john(a)example.org -n summersun > >>> result: Changed password for 0 key(s) > >>> > >>> (summersun = the password for this user) > >>> > >>> but then it says there are 0 keys, so then i send the test user an email and try to open the > >>> mailbox, i'll get: > >>> > >>> imap(john(a)example.org): Error: read() failed: > >>> read(/var/vmail/example.org/john/Maildir/cur/1526827992.M149712P883.mailser…, > >>> =561:2,) failed: Private key not available: Cannot decrypt key > >>> 71849013a70b0c631c06112077e7c2fe39b0b2737b4933b219793841209d4e7f: error:03070068:bignum > >>> routines:BN_mpi2bn:encoding error > >>> > >>> but hey, now the key's are created, so i tried to set the password again: > >>> > >>> root@mailserver1:/var/vmail# doveadm mailbox cryptokey password -u john(a)example.org -n summersun > >>> result: dcrypt_key_load_private(787701bd677dd69a26842547a3926cbaa625b0b5a91751f06678c3e9708343d9) > >>> failed: password missing > >>> ========= > >>> > >>> Lets start over again, i did a new: > >>> rm -rf /var/vmail/example.org > >>> > >>> i disabled the mail_crypt_private_password in the sql query and send an email to the test user. > >>> now again new keys are generated. > >>> > >>> then i did set the password via doveadm: > >>> > >>> root@mailserver1:/var/vmail# doveadm mailbox cryptokey password -u john(a)example.org -n summersun > >>> result: Changed password for 1 key(s) > >>> > >>> i enabled the mail_crypt_private_password again in the sql query part and now it works :) > >>> > >>> YESSS!!! > >>> > >>> if i now change the password for the user, i cannot read the email anymore. that is what should > >>> happen. > >>> so now i changed the password for this user also with doveadm: > >>> - doveadm mailbox cryptokey password -u john(a)example.org -n qwerty -o summersun > >>> > >>> and now i'm able to read the emails again. so it all works now as expected. > >>> > >>> i have now only one thing remaining. > >>> > >>> when i want to add a new user, i have to somehow: > >>> - create the new user in the mysql DB > >>> - start with dovecot not using mail_crypt_private_password (so disabled) > >>> - send an initial email to let the users mailbox be created and generate the keys > >>> - set the users password with doveadm > >>> - restart dovecot again with mail_crypt_private_password (so enabled) > >>> > >>> but this would be disruptive to existing users, and i would have to script the whole thing as a > >>> "add-new-user" script to make it usable i guess. > >>> > >>> do you know of a more easy way of acomplishing this? > >>> could i use doveadm for all steps, and get around the mail_crypt_private_password disable part? > >>> > >>> or could i add a column in the mysql db called userdb_mail_crypt_private_password and fill that > >>> column with %w for users that allready exist, and empty for new users. > >>> when being empty, it might not set the mail_crypt_private_password for new users > >>> > >>> or is this the wrong way of thinking? > >>> > >>> let me know your thoughts on this. > >>> > >>> And last but not least, i really want to thank you for all your help. It is a really nice > >>> experience. > >>> Bless you! > >>> > >>> Zjemm > >>> Hi Aki, > >>> > >>> You did fix the posting on the mail archive, i can see our conversation on there, all but the last > >>> email i send to you. > >>> Maybe you did not received the last email? > >>> > >>> would you be willing to take a look at my last question in the email See below: > >>> Thank you very much. > >>> > >>> ================================ > >>> i have now only one thing remaining. > >>> > >>> when i want to add a new user, i have to somehow: > >>> - create the new user in the mysql DB > >>> - start with dovecot not using mail_crypt_private_password (so disabled) > >>> - send an initial email to let the users mailbox be created and generate the keys > >>> - set the users password with doveadm > >>> - restart dovecot again with mail_crypt_private_password (so enabled) > >>> > >>> but this would be disruptive to existing users, and i would have to script the whole thing as a > >>> "add-new-user" script to make it usable i guess. > >>> > >>> do you know of a more easy way of acomplishing this? > >>> could i use doveadm for all steps, and get around the mail_crypt_private_password disable part? > >>> > >>> or could i add a column in the mysql db called userdb_mail_crypt_private_password and fill that > >>> column with %w for users that allready exist, and empty for new users. > >>> when being empty, it might not set the mail_crypt_private_password for new users > >>> > >>> or is this the wrong way of thinking? > >>> > >>> let me know your thoughts on this. > >>> > >>> And last but not least, i really want to thank you for all your help. It is a really nice > >>> experience. > >>> Bless you! > >>> > >>> Zjemm > >> > >> If you have mail_crypt_private_password set *when* keys are generated, > >> dovecot should use that password to encrypt the user key. > >> > >> Aki > >>> Hi Aki, > >>> > >>> well, if there is a new email user setup in the mysql DB, and no email has been send to that new > >>> user. at that point there are no keys. > >>> > >>> So trying to set a password on those key's wont work. see: > >>> root@mailserver1:/var/vmail/example.org# doveadm mailbox cryptokey password -u john2(a)example.org -n > >>> qwerty > >>> result: Changed password for 0 key(s) > >>> > >>> the keys need to be generated first. And that only happens when sending a mail to that new user. > >>> Also, at the point of creating the keys, the mail_crypt_private_password should be disabled > >>> otherwise the keys are generated and also encrypted with no user password, and then im unable to > >>> set a new pasword for that key > >>> > >>> How can i set the password before the keys are generated? > >>> or can i manually generate key's and then set the password? > >>> > >>> so at this point i have to do the following: > >> > >> You can use doveadm mailbox cryptokey generate -u user -U > >> > >> to generate a user key. > >> > >> Aki > >> > >>> - create the new user in the mysql DB > >>> - start with dovecot not using mail_crypt_private_password (so disabled) > >>> - send an initial email to let the users mailbox be created and generate the keys > >>> - set the users password with doveadm > >>> - restart dovecot again with mail_crypt_private_password (so enabled) > >>> can i somehow enable the mail_crypt_private_password per user? > >>> because this mysql query always returns: %w > >>> and thus allways sets: userdb_mail_crypt_private_password > >>> SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM virtual_users; > > > > Hi Aki, > > > > You are correct > > > > doveadm mailbox cryptokey generate -u user -U generates the keys, but i have to first remove: > > '%w' AS userdb_mail_crypt_private_password > > from dovecot configuration and restart dovecot. > > > > if i don't do that, the keys are generated, but also somehow encrypted using: no > > password/empty/something else (i don't know) > > > > here you can see that happening: > > > > root@mailserver1:/var/vmail/example.org# doveadm mailbox cryptokey generate -u john2(a)example.org -U > > Folder Public ID > > ✓ <userkey> 53004acf9886f887ca081c83d7392a5aa3fac4b5a20ce013db91a341fb4644c4 > > root@mailserver1:/var/vmail/example.org# doveadm mailbox cryptokey password -u john2(a)example.org -n > > qwerty > > result: dcrypt_key_load_private(53004acf9886f887ca081c83d7392a5aa3fac4b5a20ce013db91a341fb4644c4) > > failed: password missing > > > > it expects an old password wich is never set in my opinion. > > > > so the last part of this setup would be to figure out a way to disable '%w' AS > > userdb_mail_crypt_private_password for new users without manually removing that part from the query > > and restarting dovecot. As that would mean connection interruption while adding new users > > > > if we could add new users to the DB and somehow not give '%w' AS userdb_mail_crypt_private_password > > for that new user in the query, we can add the password afterward, and then enable '%w' AS > > userdb_mail_crypt_private_password in the query for this user > > > > could we add a column in the user db lets say called: encrypted (yes/no) > > > > and then change the existing query: SELECT email as user, password, '%w' AS > > userdb_mail_crypt_private_password FROM virtual_users; > > > > to firrt check if encryption is set to 'yes', if so retrun: > > SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM virtual_users; > > > > if not return: > > SELECT email as user, password FROM virtual_users; > > > > but then in one mysql query so dovecot can work with it > > > > ? > > > Hi Aki, > > would you be willing to respond to my last question i had send to you last week? > its this one: > ================================== > > doveadm mailbox cryptokey generate -u user -U generates the keys, but i have to first remove: > > '%w' AS userdb_mail_crypt_private_password > > from dovecot configuration and restart dovecot. > > > > if i don't do that, the keys are generated, but also somehow encrypted using: no > > password/empty/something else (i don't know) > > > > here you can see that happening: > > > > root@mailserver1:/var/vmail/example.org# doveadm mailbox cryptokey generate -u john2(a)example.org -U > > Folder Public ID > > ✓ <userkey> 53004acf9886f887ca081c83d7392a5aa3fac4b5a20ce013db91a341fb4644c4 > > root@mailserver1:/var/vmail/example.org# doveadm mailbox cryptokey password -u john2(a)example.org -n > > qwerty > > result: dcrypt_key_load_private(53004acf9886f887ca081c83d7392a5aa3fac4b5a20ce013db91a341fb4644c4) > > failed: password missing > > > > it expects an old password wich is never set in my opinion. > > could this be a bug? or am i doing it wrong? if needed i could send in a bug report? > > or might we need to enable the userdb_mail_crypt_private_password "per user" ? > > > > > so the last part of this setup would be to figure out a way to disable '%w' AS > > userdb_mail_crypt_private_password for new users without manually removing that part from the query > > and restarting dovecot. As that would mean connection interruption while adding new users > > > > if we could add new users to the DB and somehow not give '%w' AS userdb_mail_crypt_private_password > > for that new user in the query, we can add the password afterward, and then enable '%w' AS > > userdb_mail_crypt_private_password in the query for this user > > > > could we add a column in the user db lets say called: encrypted (yes/no) > > > > and then change the existing query: SELECT email as user, password, '%w' AS > > userdb_mail_crypt_private_password FROM virtual_users; > > > > to firrt check if encryption is set to 'yes', if so retrun: > > SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM virtual_users; > > > > if not return: > > SELECT email as user, password FROM virtual_users; > > > > but then in one mysql query so dovecot can work with it > > Please let me know your thougts, after this last thing im done :) > also let me know if i can support this project in some way, im willing to contribute > > Zjemm You can select it as userdb_mail_crypt_save_version=0 to disable encryption (it won't disable decryption). You can use value '2' for enabling encryption. DO NOT USE 1. Also I tried the SQL based thing, and if you had EMPTY mail_crypt_private_password, try these to change the password. If the one that works is the second one, let me know =) doveadm mailbox cryptokey password -u testuser -nnewpass -o "" doveadm mailbox cryptokey password -u testuser -nnewpass -o "yes" Aki

1 0

lda / postfix / dovecot -- bounced messages not working
by Scott Ruckh 25 May '18

25 May '18

I saw another thread about this topic, but I did not understand the solution. . . I recently discovered my bounced messages were not getting delivered. Obviously since I was not getting any messages, I thought everything was fine. Anyway, my maillog has entries similar to below for bounced messages: Mar 29 10:48:09 firewall postfix/pipe[9089]: 19565807: to=<myuser(a)my.domain>, relay=dovecot, delay=0.11, delays=0.02/0.01/0/0.08, dsn=5.3.0, status=bounced (command line usage error. Command output: lda: Fatal: Invalid -f parameter: Missing domain ) In the previous thread discussing this issue it mentioned that this was a dovecot error and possibly due to a dovecot 2.3.0 upgrade. I am running dovecot-2.3.0-1.1 on a CentOS 7 server. The solution from the other thread simply stated that the original poster is instead using lmtp instead of lda, or at least that it was I got from the thread. If using lmtp instead of lda is the correct solution, could I get an example of what configuration changes need to be made to make that happen? Otherwise, has anyone else seen this error and know the solution to make it work. My current dovecot configuration for postfix (master.cf) is using the de-facto standard from many web docs: dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/deliver -f ${sender} -d ${recipient} This is the same configuration that was originally setup and has worked for years; until the bounced message problem was recently discovered. If anyone has seen this error and knows the solution, I would appreciate the help. Thank You. Scott

2 1

last login tracking error
by David Mehler 25 May '18

25 May '18

Hello, I'm running dovecot 2.2 and trying to do last login tracking. I am using a MySQL database. When a user logs in I get this in the log: 2018-04-07 16:55:14 imap(user(a)example.com)<54415><BmevY0hpMN5/AAAB>: Error: last_login_dict: Failed to write value for user user(a)example.com: dict-server returned failure: sql dict: commit failed: Field 'name' doesn't have a default value (reply took 0.018 secs (0.000 in dict wait, 0.009 in other ioloops, 0.001 in locks, async-id reply 0.000 secs ago, started on dict-server 0.006 secs ago, took 0.006 secs)) Here's an excerpt from my dovecot-dict-sql.conf.ext file: map { pattern = shared/last-login/$user table = accounts value_field = last_login value_type = uint fields { username = $user } } The username does have a value. Can anyone see what I've got wrong? Thanks. Dave. doveconf -n 2018-04-07 16:55:14 imap(user(a)example.com)<54415><BmevY0hpMN5/AAAB>: Error: last_login_dict: Failed to write value for user user(a)example.com: dict-server returned failure: sql dict: commit failed: Field 'name' doesn't have a default value (reply took 0.018 secs (0.000 in dict wait, 0.009 in other ioloops, 0.001 in locks, async-id reply 0.000 secs ago, started on dict-server 0.006 secs ago, took 0.006 secs)) # 2.3.1 (8e2f634): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.1 (d9bc6dfe) # OS: FreeBSD 11.1-RELEASE-p4 amd64 # Hostname: localhost auth_cache_size = 24 M auth_cache_ttl = 18 hours auth_default_realm = example.com auth_mechanisms = plain login auth_realms = example.com nickandwill.com dict { acl = mysql:/usr/local/etc/dovecot/dovecot-dict-sql.conf.ext lastlogin = mysql:/usr/local/etc/dovecot/dovecot-dict-sql.conf.ext quota = mysql:/usr/local/etc/dovecot/dovecot-dict-sql.conf.ext } first_valid_gid = 999 first_valid_uid = 999 hostname = mail.example.com imap_idle_notify_interval = 10 mins last_valid_gid = 999 last_valid_uid = 999 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lda_original_recipient_header = X-Original-To listen = 127.0.0.1 66.228.47.34 log_path = /var/log/dovecot/dovecot.log log_timestamp = "%Y-%m-%d %H:%M:%S " mail_access_groups = vmail mail_gid = vmail mail_home = /home/vmail/mailboxes/%d/%n mail_location = maildir:~/mail:LAYOUT=fs mail_plugins = acl mail_log notify quota trash virtual welcome zlib mail_privileged_group = vmail mail_server_admin = mailto:postmaster@example.com mail_uid = vmail mailbox_idle_check_interval = 59 secs 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 spamtest spamtestplus virustest editheader imapflags notify imapsieve vnd.dovecot.imapsieve namespace { location = maildir:/home/vmail/public/:CONTROL=~/mail/public:INDEX=~/mail/public mailbox TestFolder { auto = subscribe comment = Public Folder for message sharing } prefix = Public/ separator = / subscriptions = yes type = public } namespace { hidden = no location = maildir:/home/vmail/shared/office/.Maildir:CONTROL=~/.Maildir/control/office:INDEX=~/.Maildir/index/office prefix = office/ separator = / } namespace inbox { inbox = yes location = mailbox Archives { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Trash { auto = subscribe autoexpunge = 30 days special_use = \Trash } mailbox virtual/All { comment = All my messages special_use = \All } prefix = separator = / type = private } namespace virtual { location = virtual:/usr/local/etc/dovecot/virtual:INDEX=~/virtual:CONTROL=~/virtual prefix = virtual/ separator = / } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile:/usr/local/etc/dovecot/global-acls:cache_secs=300 acl_anyone = allow acl_globals_only = yes acl_shared_dict = proxy::acl fts = lucene fts_autoindex = yes fts_autoindex_max_recent_msgs = 80 fts_index_timeout = 90 fts_lucene = whitespace_chars=@. normalize no_snowball imapsieve_mailbox1_before = file:/home/vmail/sieve/global/learn-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/home/vmail/sieve/global/learn-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * last_login_dict = proxy::lastlogin last_login_key = last-login/%n mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size quota = dict:User quota::proxy::quota quota_exceeded_message = Storage quota for this account has been exceeded, please try again later. quota_grace = 10%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_vsizes = true quota_warning = storage=100%% quota-exceeded 100 %u quota_warning2 = storage=95%% quota-warning 95 %u quota_warning3 = storage=90%% quota-warning 90 %u quota_warning4 = storage=85%% quota-warning 85 %u quota_warning5 = storage=75%% quota-warning 75 %u sieve = ~/.dovecot.sieve sieve_before = /home/vmail/sieve/before.d sieve_default = /home/vmail/sieve/default.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags +spamtest +spamtestplus +virustest +editheader sieve_global_dir = /home/vmail/sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute +vnd.dovecot.environment sieve_max_redirects = 30 sieve_max_script_size = 1M sieve_pipe_bin_dir = /home/vmail/sieve sieve_plugins = sieve_imapsieve sieve_extprograms sieve_spamtest_max_header = X-Spamd-Result: default: [[:alnum:]]+ \[-?[[:digit:]]+\.[[:digit:]]+ / (-?[[:digit:]]+\.[[:digit:]]+)\] sieve_spamtest_status_header = X-Spamd-Result: default: [[:alnum:]]+ \[(-?[[:digit:]]+\.[[:digit:]]+) / -?[[:digit:]]+\.[[:digit:]]+\] sieve_spamtest_status_type = score sieve_user_log = /home/vmail/sieve/sieve_error.log sieve_virustest_status_header = X-Virus-Scan: Found to be (.+)\. sieve_virustest_status_type = text sieve_virustest_text_value1 = clean sieve_virustest_text_value5 = infected trash = /usr/local/etc/dovecot/trash.conf welcome_script = welcome %u postmaster@%d welcome_wait = yes } postmaster_address = postmaster(a)example.com protocols = imap lmtp sieve sendmail_path = /usr/local/sbin/sendmail service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } user = root } service imap-login { inet_listener imap { address = 127.0.0.1 } inet_listener imaps { address = 66.228.47.34 port = 993 ssl = yes } } service imap-postlogin { executable = script-login /usr/local/etc/dovecot/trackauth.sh user = vmail } service imap { executable = imap } service lmtp { executable = lmtp unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } service managesieve-login { inet_listener sieve { address = 127.0.0.1 port = 4190 } } service quota-status { client_limit = 1 executable = quota-status -p postfix unix_listener /var/spool/postfix/private/dovecot-quota { group = postfix mode = 0660 user = postfix } } service quota-warning { executable = script /usr/local/etc/dovecot/quota-warning.sh unix_listener quota-warning { group = vmail mode = 0660 user = vmail } user = vmail } service welcome { executable = script /usr/local/etc/dovecot/welcome.sh unix_listener welcome { user = vmail } user = vmail } ssl = required ssl_cert = </usr/local/etc/ssl/acme/example.com/fullchain.pem ssl_cipher_list = ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256 ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { info_log_path = /var/log/dovecot/dovecot-lmtp.log log_path = /var/log/dovecot/dovecot-lmtp-errors.log mail_plugins = acl mail_log notify quota trash virtual welcome zlib sieve } protocol lda { mail_plugins = acl mail_log notify quota trash virtual welcome zlib sieve } protocol imap { mail_max_userip_connections = 20 mail_plugins = acl mail_log notify quota trash virtual welcome zlib imap_acl imap_quota imap_sieve imap_zlib last_login fts fts_lucene } protocol sieve { info_log_path = /var/log/dovecot/dovecot-sieve.log log_path = /var/log/dovecot/dovecot-sieve-errors.log }

2 1

Bug: subscriptions file
by Rupert Gallagher 24 May '18

24 May '18

Dovecot does not clear the subscription file from non-existent folders.

5 10

question on setting ulimit on debian
by Sophie Loewenthal 24 May '18

24 May '18

Hi, I’ve been trying to increase the number of open files for the dovecot user on Debian 9 and have so far, failed! I’ve tried this: # cat /etc/security/limits.d/limits_dovecot.conf dovecot soft nofile 2048 dovecot hard nofile 8192 # cat /etc/systemd/system/dovecot.service.d/service.conf LimitNOFILE=8192 But to no avail: # prlimit -p 27208|grep -i nofile NOFILE max number of open files 1024 4096 files Lost me :( Any ideas? Thanks,Sophie.

2 2

Dovecot send duplicated certificates when using ssl_alt_cert
by Jean-Daniel Dupas 24 May '18

24 May '18

Hello, I'm running dovecot 2.3.1 (c5a5c0c82) and trying to experiment with using both RSA and ECDSA certificates. My configuration is as follow: ssl_alt_cert = </path/to/my.rsa.key ssl_alt_key = </path/to/my.rsa.key ssl_cert = </path/to/my.ecdsa.pem ssl_key = </path/to/my.ecdsa.key Both certificates are let's encrypt certificate, so both are using the same intermediate CA. The certificate chain are: for rsa: - my certificate - Let's Encrypt Authority X3 - DST Root CA X3 for ecdsa: - my certificate - Let's Encrypt Authority X3 - DST Root CA X3 My problem is that when connecting, dovecot includes 2 copies of Let's Encrypt Authority X3 in the certificate chain. I think this is a bug. When building the chain, dovecot should ignore duplicated certificates and when opening the connection, it should only send intermediates related to the used certificate (either RSA or ECDSA). (and as a side note, when using dovecot -n, dovecot hides the ssl_key (ssl_key = # hidden, use -P to show it) but not the ssl_alt_key. This is probably a bug too). --------------- openssl s_client -showcerts -host imap.example.com -port 993 -servername imap.example.com CONNECTED(00000005) depth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3 verify error:num=20:unable to get local issuer certificate verify return:0 --- Certificate chain 0 s:/CN=imap.example.com i:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 -----BEGIN CERTIFICATE----- MIIHPDCCBiSgAwIBAgISA2e3bP2o1mpdOr9kTDm/R/zuMA0GCSqGSIb3DQEBCwUA … -----END CERTIFICATE----- 1 s:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 i:/O=Digital Signature Trust Co./CN=DST Root CA X3 -----BEGIN CERTIFICATE----- MIIEkjCCA3qgAwIBAgIQCgFBQgAAAVOFc2oLheynCDANBgkqhkiG9w0BAQsFADA/ MSQwIgYDVQQKExtEaWdpdGFsIFNpZ25hdHVyZSBUcnVzdCBDby4xFzAVBgNVBAMT … -----END CERTIFICATE----- 2 s:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 i:/O=Digital Signature Trust Co./CN=DST Root CA X3 -----BEGIN CERTIFICATE----- MIIEkjCCA3qgAwIBAgIQCgFBQgAAAVOFc2oLheynCDANBgkqhkiG9w0BAQsFADA/ MSQwIgYDVQQKExtEaWdpdGFsIFNpZ25hdHVyZSBUcnVzdCBDby4xFzAVBgNVBAMT … -----END CERTIFICATE----- --- Server certificate subject=/CN=imap.example.com issuer=/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 --- No client certificate CA names sent --- SSL handshake has read 5140 bytes and written 468 bytes --- New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384 Server public key is 4096 bit Secure Renegotiation IS supported Compression: NONE Expansion: NONE No ALPN negotiated SSL-Session: Protocol : TLSv1.2 Cipher : ECDHE-RSA-AES256-GCM-SHA384 Session-ID: 591240C021A02B399CCB010F37AF7AD83227DC1770C606F73B3EEA3514AF07FB Session-ID-ctx: Master-Key: 7D5A5BFC1B4B8EECF4F41DC084265AF6D32B82130F381B8DDF685B589D54D9BDEBFC20F1DD80E150CD56850C0D062E9E TLS session ticket lifetime hint: 300 (seconds) TLS session ticket: 0000 - 3a 72 98 05 72 af 3d ed-26 a9 e7 2b 68 6b 0a 25 :r..r.=.&..+hk.% … Start Time: 1526482021 Timeout : 300 (sec) Verify return code: 0 (ok) ---

3 3

Re: lazy_expuge + mdbox
by Matt Bryant 24 May '18

24 May '18

To a degree I agree .. given mdbox doesnt delete until purge .. but then would be nice if purge took a dovecot search rather than just ditch everything with refcount=0 ... in that way could say purge everything thats been marked as delete according to a specified criteria. rgds Matt completly unrelated moved mailserver back home and listed on cyren so atm getting bounced by dovecot.fi .. have requested de-listing > Aki Tuomi <mailto:aki.tuomi@dovecot.fi> > 24 May 2018 at 3:35 pm > > I am not sure if lazy expunge makes much sense with mdbox, at least if > you use the same mdbox storage with it. It might make sense with > separate mdbox/sdbox/something for .EXPUNGED. > > Aki > Matt Bryant <mailto:matt@the-bryants.net> > 24 May 2018 at 11:53 am > So moving on from earlier issue now looking at converting mail inbox to > mdbox and keeping lazy_expunge as mdbox also .. but again seeing some > wierdness so questions .... > > 1) When i purge trash folder I seem to get 2 copies of the message in > .EXPUNGED/Trash folder .. however if I set > lazy_expunge_only_last_instance = yes then dont seem to get ANY copy .. > just nothing. > > 2) If I go into Trash and delete a message ... then it does not get > moved .. I assume that a delete in Trash is not actually an expunge on > TB and hence does get caught by the plugin. > > 3) Since mdbox doesnt delte anything anyway until purged would it be > better not to use lazy-expunge but just have a job that moves any > messages in mdbox_deleted: storage to the hidden .EXPUNGED namespace .. > does doveadm move work with mdbox_deleted ??? > > any help appreciated > > rgds > > Matt

2 1

lazy_expuge + mdbox
by Matt Bryant 24 May '18

24 May '18

So moving on from earlier issue now looking at converting mail inbox to mdbox and keeping lazy_expunge as mdbox also .. but again seeing some wierdness so questions .... 1) When i purge trash folder I seem to get 2 copies of the message in .EXPUNGED/Trash folder .. however if I set lazy_expunge_only_last_instance = yes then dont seem to get ANY copy .. just nothing. 2) If I go into Trash and delete a message ... then it does not get moved .. I assume that a delete in Trash is not actually an expunge on TB and hence does get caught by the plugin. 3) Since mdbox doesnt delte anything anyway until purged would it be better not to use lazy-expunge but just have a job that moves any messages in mdbox_deleted: storage to the hidden .EXPUNGED namespace .. does doveadm move work with mdbox_deleted ??? any help appreciated rgds Matt

1 0

Released Pigeonhole v0.4.24 for Dovecot v2.2.36.
by Stephan Bosch 24 May '18

24 May '18

Hello Dovecot users, Here is the Pigeonhole release that goes with the new Dovecot v2.2.36 release. Apart from the changes that were already in the RC, this final release adds one new feature: a plugin for the IMAP FILTER=SIEVE capability. The is a vendor-defined feature that adds the ability to manually invoke Sieve filtering in IMAP. Changelog v0.4.24: + Implement plugin for the a vendor-defined IMAP capability called "FILTER=SIEVE". It adds the ability to manually invoke Sieve filtering in IMAP. More information can be found in doc/plugins/imap_filter_sieve.txt. - Fix assert panics triggered by empty messages that are being forwarded using redirect or vnd.dovecot.report. This does not likely normally occur, but this is seen as a result of certain benign failures in object storage. - Make the length of the subject header for the vacation response configurable and enforce the limit in UTF-8 codepoints rather than bytes. The subject header for a vacation response was statically truncated to 256 bytes, which is too limited for multi-byte UTF-8 characters. - Sieve editheader extension: Fix assertion panic occurring when it is used to manipulate a message header with a very large header field. - Properly abort execution of the sieve_discard script upon error. Before, the LDA Sieve plugin attempted to execute the sieve_discard script when an error occurs. This can lead to the message being lost. - Fix the interaction between quota and the sieve_discard script. When quota was used together with a sieve_discard script, the message delivery did not bounce when the quota was exceeded. The release is available as follows: https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.24.t… https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.24.t… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

Autofile Junk for all users
by ＠lbutlr 23 May '18

23 May '18

How would I get the rule if header :contains "X-spam-flag" "YES" { fileinto "Junk"; } To apply to all users mail at delivery time?

4 4