Still no update I assume?
DisNews 24.10 - Update on our 2024 goals | Disroot.org they slowly do it and open alpha is sometime soon
2 Likes
I already submitted my public key since the DisNews 24.10 has been announced and yep, it works. All new incoming emails is now encrypted. The Sent folder still not encrypted when sending emails but they are working on it.
1 Like
how does it compare to delta.chat?
Is there anything you had to do in particular, I registered my public key at https://keys.lacre.io but it doesn’t appear to be working.
What ? There is nothing to do with https://keys.lacre.io.
Sorry but do you read the DisNews 24.10 link that I have mentioned above ? The instructions is written clearly:
So if you want to be the early bird and like to live on the edge, please drop us a line. We will be happy to answer all your questions and doubts (muppeth has been using lacre on his main email account already :P). You can also attach your public keys in the email (send it to support@ or info@).
What you need to do is sent an email to support@disroot.org or info@disroot.org about lacre.
1 Like
Ah I see, thanks for the extra info!
You’re welcome. However it is a community, the admins also busy IRL so don’t expect too much to get a quick response.
But most of admins and users is active on xmpp xmpp:disroot@chat.disroot.org?join so they will notice if someone need help with Disroot services 
2 Likes
Lacre is in open beta now https://disroot.org/en/blog/disnews-24.11
3 Likes
I donated $20 and made the switch over to disroot after the Proton CEO’s unsolicited and questionable comments.
It didn’t help that I was using hydroxide as an unofficial proton bridge which led to sync issues and I could only get it working on one device. I wasn’t using PGP for emails and I wasn’t emailing other proton users, so I believe the transition will create less friction for my emails in general.
Currently trying to set up the folder/spam filters for a more automated experience
Edit: Had to tweak their managesieve through Claude. Appears their default implentation is a little off. With that out of the way, I’m digging the unlimited folders for free and integration w/ Kmail/Kontact 
1 Like
A question for anyone who has gotten their GPG key added and has the new Lacre encryption working:
Have you had a chance to test if the encryption also works for emails that are routed through a forwarding service (like a SimpleLogin or AnonAddy alias)?
I’m curious if Lacre is able to correctly identify the final recipient on a forwarded email to apply the GPG key. Any insight you have from your testing would be very helpful.
Thanks!
Lacre encrypts any email sent to the email address you’ve assigned the PGP key to. For example, if I use DuckDuckGo email aliases and set the destination email to myusername@disroot.org (which I enrolled the PGP key to), all emails from the aliasing service will be encrypted with that PGP key.
It’s not mailbox-wide, so if you have a custom domain or other aliases on your account, those won’t be encrypted. Only the aliases you’ve assigned a PGP key to will be encrypted.
1 Like
That makes sense for incoming mail, thank you for clarifying.
My concern, however, is with the Sent folder. According to the ToS:
All emails, unless encrypted by the user (with GnuPG/PGP, for example) are stored unencrypted on our servers
This implies that all our sent items are stored in plain text. So even with Lacre, there might still be a risk that the provider could read our sent mail. It seems the only way to protect sent items is to still encrypt them ourselves before hitting send.
What are everyone’s thoughts on this?
There is always a possibility with that, even with mailbox.org it is encrypted by their sieve filter. It’s unlikely they keep an unencrypted copy.
Correct me if I am wrong
“If you are User A and you send a message from a third-party client like Thunderbird to User B without using PGP encryption within Thunderbird, the copy of that message stored in your “Sent” folder on Mailbox.org’s servers will be unencrypted”
To solve this Disroot has listed down some solution ideas: #176 - Encrypt Sent Items with User's Public PGP Key for Zero-Access Storage - Disroot/gpg-lacre - Disroot Forgejo: Brace yourself, merge conflicts ahead.
1 Like