Setting up Discourse with ProtonMail account


#1

Hello, I’m trying to setup Discourse with a ProtonMail admin email address. Apparently ProtonMail doesn’t support SMTP so I wondered if there’s a workaround.

Has anyone had experience with this?

It’s for this step:

Hostname for your Discourse? [discourse.example.com]:
Email address for admin account? [me@example.com]:
SMTP server address? [smtp.example.com]:
SMTP user name? [postmaster@discourse.example.com]:
SMTP port [587]:
SMTP password? []:

Thanks!


(Jay Pfaffman) #2

Sure! Just develop a plugin to support proton mail.

It would be easier to use one of the recommended email services, though.


(DjCyry) #3

Why not mailgun for example ?


(Wiliam Joaquim) #4

I use elastic mail, it has very attractive free plans


#5

Thanks for the suggestions. I’m not currently able to develop a plugin (or pay to have one developed) so I’ll keep that in mind for future, thanks Jay.

I’d prefer to use ProtonMail because of the level of privacy it offers - which is important to my clients.

Would it be possible to use an admin email that clients wouldn’t see? I’m presuming the automated emails would always come from the admin email…


(Jay Pfaffman) #6

If you send an email with an address people can’t see, it will be classified as spam.

It doesn’t have to be the same as your hostname, but it’ll need to be a valid domain with spf and dkim records.

Perhaps it would help if you said more about your privacy needs.


(maiki) #7

From What is a “Sending Limit”?:

ProtonMail is not designed for bulk/spam emailing.

Keep your sending below (please note, these limits are suggestions. Your user reputation (as outlined above) is variable and will determine your unique sending limits):

Free Plan: 50 messages*/hour and 150 messages*/day
Plus Plan: 300 messages*/hour and 1000 messages*/day
Visionary Plan: User’s discretion

ProtonMail is currently not designed for high volume sending such as marketing blasts and transactional emails.

So even if you could use ProtonMail’s non-existent API, your “clients” would quickly break your send limit.

Email isn’t the only leaky pipe you need to patch if you are trying to create an anonymous Discourse experience. But you’ve saved some time, as that is not currently possible. :slight_smile: