similar to: mail_crypt crashing randomly during LMTP

On 29. Mar 2020, at 16:07, Timo Sirainen <timo at sirainen.com> wrote: > > On 29. Mar 2020, at 15.15, Andi Krischer <ak at michaelpelzer.de> wrote: >> We have a really strange bug with our dovecot setup. After weeks and month of debugging we?re finally reached the point when we ask you for help. >> >> Our basic setup is quite simple: a single dovecot 2.3.10

On 29. Mar 2020, at 17.07, Timo Sirainen <timo at sirainen.com> wrote: > >> This is what the log says in the moment of crashing: >> dovecot: lmtp(53852): Panic: Module context mail_crypt_user_module missing >> *** backtrace *** (see: https://pastebin.com/YCiFtxmy) > > It shows mailbox_free() in the backtrace, so it's probably crashing in

On 29. Mar 2020, at 15.15, Andi Krischer <ak at michaelpelzer.de> wrote: > We have a really strange bug with our dovecot setup. After weeks and month of debugging we?re finally reached the point when we ask you for help. > > Our basic setup is quite simple: a single dovecot 2.3.10 (0da0eff44) install on Debian 10 with LDAP as user/passdb and sieve, imap_sieve and mail_crypt as

> On 22 March 2019 19:36 Dave via dovecot <dovecot at dovecot.org> wrote: > > > [Dovecot v2.2.33.2] > > I'm testing out mail_crypt on a fresh Dovecot install to get a feel for > how it works, but I'm running into something unexpected. > > The mail_crypt plugin does seem to be working, but NOT on incoming > email.? What I mean is, if I send a test

Hi! Some replies: 1. the problem with mail_crypt_global_public_key, there is a bug that we are fixing where file inputs under plugin { } section do not get aboard. workaround 1: You can base64 encode the PEM key (yes, again), and put it in one line such as plugin { mail_crypt_global_public_key = LS0tLS1C..... } workaround 2: Return the key from userdb, you can use same format. 3. The

Hi, i have a problem. I sent test e-mail. It is in folder "Sent", but it was not delivered (folder "Inbox" is empty). /var/log/dovecot: ......... lda(mail at example.com): Error: User initialization failed: mail_crypt_plugin: mail_crypt_global_public_key: Couldn't parse public key: Unknown key format ......... Try RSA and EC:

[Dovecot v2.2.33.2] I'm testing out mail_crypt on a fresh Dovecot install to get a feel for how it works, but I'm running into something unexpected. The mail_crypt plugin does seem to be working, but NOT on incoming email.? What I mean is, if I send a test email to the server that has Dovecot installed, the message correctly arrives in the user's Maildir folder (I'm using

Dovecot version: 2.2.22 (fe789d2) I generated an EC key from the page https://wiki2.dovecot.org/Plugins/. For reference here's my /etc/dovecot/conf.d/10-mail-crypt.conf file: ---- mail_plugins = $mail_plugins mail_crypt plugin { # mail_crypt_global_private_key = </etc/dovecot/ecprivkey.pem mail_crypt_global_public_key = </etc/dovecot/ecpubkey.pem mail_crypt_save_version =

I've successfully implemented the mail_crypt plugin on v2.2.27 and it's working like a champ, but some of our administrative operations require access to Maildir messages in plaintext. I've found numerous threads detailing help with mail_crypt setup, but none of my research has yielded a method of decrypting the stored messages. Relevant plugin config: mail_crypt_curve =

Hi, guys. Also, currently a problem (with http://wiki2.dovecot.org/Plugins/MailCrypt#EC_key): # dovecot mailbox cryptokey generate -u name at example.com -UR doveadm(name at example.com): Error: mail_crypt_user_get_public_key(name at example.com) failed: mailbox_attribute_get(INBOX, /shared/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/pvt/crypt/active) failed: Mailbox attributes not

On 04.11.2017 20:52, Zbyszek ???kiewski wrote: > Hi, > > I have few questions regarding mail_crypt: > > 1) Is mail_crypt_global_private_key file read upon dovecot start/restart only or it is/can be read in any other time? I have made few tests by starting dovecot and removing master key for decryption - therefore it is not available on the platform - it only reside in memory,

On 06.11.2017 13:20, Zbyszek ???kiewski wrote: > >> Wiadomo?? napisana przez Aki Tuomi <aki.tuomi at dovecot.fi> w dniu 06.11.2017, o godz. 08:44: >> >> On 04.11.2017 20:52, Zbyszek ???kiewski wrote: >>> Hi, >>> >>> I have few questions regarding mail_crypt: >>> >>> 1) Is mail_crypt_global_private_key file read upon dovecot

> On 06/08/2020 13:52 secure.light.0417.road <secure.light.0417.road at protonmail.com> wrote: > > > Ah, right. The hashed password can't be used to encrypt. > > I want to remove possibility to decrypt mails using materials in mail servers in VPS. I've thought about below scenario: > > 1. The client generates asymmetric keys in local. > 2. The client

mail_attribute_dict = file:%h/Maildir/dovecot-attributes > dovecot.conf Apparently so?)) ----- ???????? ????????? ----- > ??: "Evgeniy Korneechev" <ekorneechev at altlinux.org> > ????: "dovecot" <dovecot at dovecot.org> > ????????????: ???????, 17 ?????? 2017 ? 17:32:38 > ????: Re: Plugin "mail_crypt" does not work > Hi, guys. Also,

Hi, I have few questions regarding mail_crypt: 1) Is mail_crypt_global_private_key file read upon dovecot start/restart only or it is/can be read in any other time? I have made few tests by starting dovecot and removing master key for decryption - therefore it is not available on the platform - it only reside in memory, removing one of attack vectors 2) Is there planned any ?rollout? for key

> Wiadomo?? napisana przez Aki Tuomi <aki.tuomi at dovecot.fi> w dniu 06.11.2017, o godz. 08:44: > > On 04.11.2017 20:52, Zbyszek ???kiewski wrote: >> Hi, >> >> I have few questions regarding mail_crypt: >> >> 1) Is mail_crypt_global_private_key file read upon dovecot start/restart only or it is/can be read in any other time? I have made few tests by

Hi, What would be a good backup method for mail stored encrypted with mail_crypt per user(folder). As the administrator does not have the key (the user has) i'm thinking: - the user must backup his/her email via the mail client, but as an admin you want to be able to restore mail when needed on the server itself or on a new server. - the admin creates a backup of the vmail folder per user

> On May 26, 2017 at 5:13 PM "dovecot at avv.solutions" <dovecot at avv.solutions> wrote: > > > Hello Community, > > (sorry to be more busy, hence more running questions in parallel :) ) > > As mentioned in another post, I am testing mail_crypt plugin. > > I was wondering how to really secure the process sothat even the admin > cannot have any

Hello, I am testing mail_crypt plugin with per account encryption and wanted to generate a new keypair for an account but noticed that I now end up with 2 keypairs where one is active and the other inactive as you can see below: $ doveadm mailbox cryptokey list -u email at domain.tld -U Folder Active Public ID yes 7b140b4f3d6d68eed2c59259ac5e6f6a280dc82990292dc415b4100d6c797f67

mail_crypt_private_password cannot be hashed, as it's used to encrypt the key. Aki > On 06/08/2020 10:06 secure.light.0417.road <secure.light.0417.road at protonmail.com> wrote: > > > I've tried to append the field "userdb_mail_crypt_private_password=<same-hashed-password-in-passwd-file>" to the end of each user line in userdb as passwd-file. And use