similar to: Setting up the mail-crypt plugin with virtual accounts that have no home directories

Displaying 20 results from an estimated 4000 matches similar to: "Setting up the mail-crypt plugin with virtual accounts that have no home directories"

2023 Mar 04
1
Setting up the mail-crypt plugin with virtual accounts that have no home directories
An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20230304/f769686e/attachment.htm>
2023 Mar 04
1
Setting up the mail-crypt plugin with virtual accounts that have no home directories
An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20230304/a3753b6e/attachment-0001.htm>
2023 Mar 05
1
Setting up the mail-crypt plugin with virtual accounts that have no home directories
An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20230305/f943341b/attachment-0001.htm>
2023 Mar 04
1
Setting up the mail-crypt plugin with virtual accounts that have no home directories
Hi again, I was able to solve both questions. I was overthinking things. A solution to the first question about mail_attribute_dict was simply to use other available variables to point to the virtual user's maildir paths. Like so: /var/mail/%d/%u/dovecot-attributes As for the second question: When I asked it, I was uncertain if dovecot would be able to cope with a hashed password for
2023 Mar 04
1
Setting up the mail-crypt plugin with virtual accounts that have no home directories
Hi, Yeah, I just realized myself that what I did there was probably not the smartest thing to do, as I indeed figured dovecot would probably just use that as a plain text string. ;-) I've now opted to do the following (I'm using PostgreSQL BTW): password_query = SELECT \ email as user, password, \ encode(digest('%w', 'sha256'), 'hex') AS
2023 Mar 05
1
Setting up the mail-crypt plugin with virtual accounts that have no home directories
Hi, Thanks for the notice! But yes, I was aware of this. For future reference though, would you mind telling me how I would go about doing this? I take it I'd first have to re-encrypt the user keys, before changing the account password. So before changing the password for a user in my PostgreSQL database, I would do the following: doveadm mailbox cryptokey password -u 'user at
2019 Dec 08
2
bash script hook lda_mailbox_autocreate for generate mail-crypt user encrypted private key with user password
What it is way most best for causing bash script run (as root) of time mailbox created (lda_mailbox_autocreate)? I use dovecot 2.3.4.1 in Debian 10. And I use of mail-crypt-plugin https://doc.dovecot.org/configuration_manual/mail_crypt_plugin/ I setup mail-crypt for requiring user encrypted EC key (mail_crypt_require_encrypted_user_key = yes). I want for passphrase encrypt EC key using client
2019 Dec 08
2
bash script hook lda_mailbox_autocreate for generate mail-crypt user encrypted private key with user password
> Technically creating and encrypting folder key does not > require decrypting user's private key. All folder keys > are encrypted with user's public key. Problem is for that this is a new user. The new user has no private key. I need for generating that private key. It do not the sense encrypts something using a key public if there is no private key. Both key public and private
2023 Feb 27
1
Auth variables unknown variable -- about to go crazy
Hi everyone, I'm trying to configure my email server to encrypt mails on a per user basis. I have the following in my conf: mail_plugins = $mail_plugins mail_crypt mail_attribute_dict = file:%h/Mail/dovecot-attributes plugin { mail_crypt_curve = secp521r1 mail_crypt_save_version = 2 mail_crypt_require_encrypted_user_key = yes mail_crypt_private_password =
2019 Dec 08
0
bash script hook lda_mailbox_autocreate for generate mail-crypt user encrypted private key with user password
<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> Technically creating and encrypting folder key does not require decrypting user's private key. All folder keys are encrypted with user's public key. </div> <div> <br> </div> <div> Aki </div>
2019 May 31
1
[mail-crypt-plugin] Password Query for Folder Keys questions
So I believe I generated a key successfully with: 'doveadm mailbox cryptokey generate -u user -UR' because I got the output with the check mark and the Public ID string of characters. However I still can't read the CRYPTED emails when logging in with IMAP.. i'm still getting the following error in the mail log: Error: read() failed: read(/var/vmail/[domain .
2019 Aug 22
0
Trying to install Mailcrypt, receive completely blank emails
Hi - perhaps someone can help me. Starting from a good and well-functioning mailserver setup, I have installed MailCrypt as per the instructions (I think) to have the per-user passworded keys setup. dovecot.conf /Added:/ mail_attribute_dict = file:%h/Maildir/dovecot-attributes mail_plugins = $mail_plugins mail_crypt dovecot-sql.conf.ext /commented this/ #password_query = SELECT email as user,
2020 May 14
0
[Dovecot v2.3.9.3] HTTP API Endpoint for mailbox cryptokey operations
Hello everyone, I successfully set up the mail_crypt plugin using folder keys, and require user's key to be encrypted with a password using mail_crypt_require_encrypted_user_key = yes. As I'm trying to streamline the process of creating a user, and want to develop an application in PHP to help me in that process, I'm very interested in the doveadm HTTP API. Although the
2018 May 20
0
Best mail encryption solution for per-user
> On 19 May 2018 at 16:40 mail at sjemm.net wrote: > > > May 18, 2018 10:01 PM, "Aki Tuomi" <aki.tuomi at dovecot.fi> wrote: > >> On 18 May 2018 at 21:44 mail at sjemm.net wrote: > >> > >> May 18, 2018 4:43 PM, "Aki Tuomi" <aki.tuomi at dovecot.fi> wrote: > >> On 18 May 2018 at 17:38 mail at sjemm.net wrote: >
2018 Nov 07
2
Dovecot mail-crypt plugin
After I configuring this, I logged in to the server and check the emails. But they are in plain text. I can even read them from backend. On Wed, Nov 7, 2018 at 1:49 PM Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > On 07 November 2018 at 10:10 Anushka Uditha Bandara <anu.udb at gmail.com> > wrote: > > > > > > I configured an email solution using
2018 Nov 07
2
Dovecot mail-crypt plugin
doveconf -n please > On 07 November 2018 at 10:29 Anushka Uditha Bandara <anu.udb at gmail.com> wrote: > > > The only change which I did is updating the "dovecot.conf" file. I added > below lines. > > mail_plugins = $mail_plugins mail_crypt > mail_attribute_dict = file:%h/Maildir/dovecot-attributes > > plugin { > mail_crypt_curve = <some
2018 Nov 07
2
Dovecot mail-crypt plugin
Can you send output of `doveconf -n` instead, please? =) Aki > On 07 November 2018 at 10:42 Anushka Uditha Bandara <anu.udb at gmail.com> wrote: > > > Please check the attached file. > > On Wed, Nov 7, 2018 at 2:07 PM Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > doveconf -n please > > > > > On 07 November 2018 at 10:29 Anushka
2019 Dec 08
0
bash script hook lda_mailbox_autocreate for generate mail-crypt user encrypted private key with user password
<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> It's a known issue that the password will be set to silly value, most likely 'yes'. </div> <div> <br> </div> <div> You should generate the user key during provisioning with `doveadm cryptokey generate -Uu
2018 Nov 07
2
Dovecot mail-crypt plugin
I configured an email solution using dovecot and postfix and it is working fine. Now I am working for mail encryption. Is it enough to set below configurations on dovecot for mail encryption. Because dovecot wiki is little bit confusing to me. "mail_plugins = $mail_plugins mail_crypt mail_attribute_dict = file:%h/Maildir/dovecot-attributes plugin { mail_crypt_curve = <some curve you
2018 May 23
0
Best mail encryption solution for per-user
On 23.05.2018 09:13, mail at sjemm.net wrote: > May 20, 2018 8:01 PM, mail at sjemm.net wrote: >> May 20, 2018 2:47 PM, "Aki Tuomi" <aki.tuomi at dovecot.fi> wrote: >> >>>> On 19 May 2018 at 16:40 mail at sjemm.net wrote: >>>> >>>> May 18, 2018 10:01 PM, "Aki Tuomi" <aki.tuomi at dovecot.fi> wrote: >>>>