# Mailfence **URL:** https://discuss.privacyguides.net/t/mailfence/10965 **Category:** Tool Suggestions **Created:** 2022-12-13T13:39:06Z **Posts:** 16 ## Post 1 by @Regime6045 — 2022-12-13T13:39:06Z Any thoughts about Mailfence as an email provider? I couldn’t find anything about it in the Github Discussions so I was wondering if this was rejected for some reason or just nobody has been aware of it? I don’t have any experience with it myself but it claims to offer easy to use PGP-based end-to-end encrypted email similar to Protonmail and [Mailbox.org](http://Mailbox.org) --- ## Post 2 by @dngray — 2022-12-13T14:03:06Z This used to be listed, but was removed due to a lack of encryption at rest [https://github.com/privacytools/privacytools.io/issues/1908#issuecomment-627154266](https://github.com/privacytools/privacytools.io/issues/1908#issuecomment-627154266) I sent them another email asking them on 9th March 2022 and they said that it still was not ready yet. This means unless an email is encrypted by the sender with PGP prior to you receiving it, it won’t be encrypted on receipt. That is the best way, but as a fallback we like to see that all email is encrypted at rest. --- ## Post 3 by @Regime6045 — 2022-12-13T14:59:34Z Thanks, very interesting. Their website makes you think they encrypt everything. --- ## Post 7 by @Rebeca_Abreu — 2025-02-11T11:25:30Z As I’ve checked on their website, Mailfence provides encryption at rest. --- ## Post 8 by @fria — 2025-02-11T18:01:40Z > **[This is how Mailfence provides a secure email service](https://mailfence.com/en/secure-email.jsp)** > > Our goal is to provide maximum protection to our users against all possible threats. Find out how we provide a highly secure email. Appears so, this is great news. It looks like they’re not open source currently and lack an audit so I think we’ll still wait and see for now. --- ## Post 9 by @BlackDog — 2025-02-12T19:17:03Z I couldn’t find anything about encryption at rest on the page linked in the post above. There is however some info on their blog:- [Encryption at Rest: What is It, and How Mailfence Implemented It](https://blog.mailfence.com/encryption-at-rest/) --- ## Post 11 by @Vadim — 2025-11-12T14:54:06Z Apologies if resurrecting an old thread is not the right way to go about things. I know the team wanted to wait and see what happened back in February, but following up it appears the are still not open source and lack an audit. Would it be worthwhile to reach out to the Mailfence team and see if they are willing for an audit to be conducted? The minimum requirements for a email service to be recommended based on the criteria does not require them to be open-source so I believe this service could potentially be considered and added back with an audit. --- ## Post 12 by @redial — 2026-03-17T10:48:21Z Hello everyone, I’d also resurrect this discussion. Imo they fulfil more than the minimum requirements, especially if you consider that support for open access (IMAP, SMTP, etc.) has become the exception rather than the rule. When did an audit become the ultimate decision factor? Sincere question. --- ## Post 13 by @Shampoo — 2026-03-17T13:19:06Z They aren’t open source either. I think that’s the more important part. --- ## Post 14 by @Regime6045 — 2026-03-17T14:40:41Z How does that matter? Whether the server runs open source software is irrelevant, because you can’t see what they’re running anyway. And it is compatible with any email client so you can use an open source client app. --- ## Post 15 by @Shampoo — 2026-03-17T15:01:53Z > [@Regime6045](#): > > And it is compatible with any email client so you can use an open source client app. Go check their site. According to their pricing page and knowledge base IMAP, SMTP, and POP are only available for their most expensive personal plan or their business plans. Apps should be open sourced if you’re required to use them. --- ## Post 16 by @redial — 2026-03-26T08:45:57Z Maybe a team member could chime in the discussion below?