I am trying to use my own send-only server to send emails. I am running this SMTP gateway to use TLS because of which the client I use to send emails requires a certificate. I am using a self-signed certificate which is very easily configurable if I use postfix/ssmtp for sending emails but I am not …

I would like to correct my question. So I really don’t need to add any certs for this to work but still its failing to communicate on TLS. If I am testing it with swaks its working fine. Example command: swaks --to user@example.com --from me@example.com --auth PLAIN --auth-user myusername -tls -s s…

You can directly use the AWS SES SMTP to achieve this why do you want to have a local relay?

@itsbhanusharma AWS ses provides 60k emails per month free and as far as I know these email calls should be requested from ec2 instance to work otherwise they are charged as normal. My discourse instance is hosted on a digital ocean droplet. I could be wrong but this is my understanding and the reas…

So even if Your SES API is receiving emails from a DigitalOcean IP, it would make it chargeable, You may decide to use another service or spin up exim on an ec2 instance to be a bridge between your DO droplet and AWS SES. I don’t think it’ll work but You can try. It should (in theory anyway) be lik…

I have already solved the relaying problem by running a local smtp server in ec2 which eventually forwards the smtp request to ses. The problem is discourse is failing on TLS handshake with this smtp server where as postfix/swaks and similar applications are working just fine.

Solving that should be as simple as using port 25 (without encryption)

Is there a way I can see where this SMTP handshake is handled? Like any library discourse is using in ruby behind the scenes? I don’t want to disable TLS here.

Then use a Valid SSL certificate (even letsencrypt should work fine)

Using valid cert from letsencrypt didn’t help for some reason. Don’t know why. But after setting this in app.yaml, emails are working now. DISCOURSE_SMTP_OPENSSL_VERIFY_MODE: none Someone with more knowledge about SMTP might provide why this is working but I am good for now I guess.

Does this end up being cheaper than simply moving the discourse instance into S3?

Hinzufügen von TLS-Zertifikat zusammen mit SMTP-Konfiguration

Unterstützung Installation

Stephen (Stephen) 10. Mai 2020 um 13:36 11

Ist das am Ende günstiger als das Verschieben der Discourse-Instanz nach S3?

Thema		Antworten	Aufrufe
Problem with SMTP configuration Self-hosting	15	7250	8. Oktober 2023
Can't send email with certificate issue Self-hosting	2	1569	2. April 2019
Can new discourse install not require smtp server certificate validation? Self-hosting	3	855	9. September 2018
Discourse aws EC2 G Suite troubleshoting Support	3	1980	8. Juni 2024
SMTP setup not working with GMail's smtp-relay Self-hosting email	5	1110	5. März 2026

Hinzufügen von TLS-Zertifikat zusammen mit SMTP-Konfiguration

Verwandte Themen