# GnuPG Encrypted outgoing topic notification emails
**URL:** https://meta.discourse.org/t/gnupg-encrypted-outgoing-topic-notification-emails/46745
**Category:** Feature
**Created:** [July 2, 2016, 3:18pm UTC](https://meta.discourse.org/t/gnupg-encrypted-outgoing-topic-notification-emails/46745 "2016-07-02T15:18:54Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@frigidaire\_amer](https://meta.discourse.org/u/frigidaire_amer)
#### Post date: [July 2, 2016, 3:18pm UTC](https://meta.discourse.org/t/gnupg-encrypted-outgoing-topic-notification-emails/46745/1 "2016-07-02T15:18:54Z")
Hello,
We switched our encrypted mailing list to a Discourse forum with no regret. Thanks for the great work!
When we switched to Discourse (obviously forcing https usage), we agreed to disable email notifications to prevent the sending of information without encryption. However, now, we miss email notifications 🙂
Would it be possible to implement GnuPG encryption only for outgoing topic notification emails? Our only threat model is passive eavesdropping.
Someone already started a topic about that (then the topic was closed):
> [@PAID: PGP Encrypted emails](https://meta.discourse.org/t/paid-pgp-encrypted-emails/38977):
>
> I’d like a plugin to: Store a site-wide public/private key pair for signing system emails Store public PGP keys in user profiles Redact the message topic the subject Sign and encrypt all outgoing mail Block sending emails to those who do not have a key on file I’d like this to be Apache 2.0 Licensed, and publicly released. I’d do this myself, but I’ve never written a line of Ruby stuck_out_tongue. If interested, let me know what the cost would be.
(even if I disagree about the signature stuff which add complexity for a low-value)
Do you think a lot of hacks are needed to complete this feature? Or even a ruby newbie could implement it?
Thanks!
---
### Author:  [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [July 3, 2016, 2:09am UTC](https://meta.discourse.org/t/gnupg-encrypted-outgoing-topic-notification-emails/46745/2 "2016-07-03T02:09:13Z")
The topic you reference got closed because it was in the “marketplace”; to keep things manageable, topics get “expired” out of that category periodically.
As far as implementation goes, I doubt this would go into core any time soon (there’s a _lot_ of more important features to add for general use), but I could definitely see it as a useful niche for a plugin. There might be a few hooks that need to be added to core in order for the plugin to catch the e-mails at just the right point in the processing chain and decrypt/encrypt, but I wouldn’t think it’d be out of the reach, technically, of a suitably motivated individual.