3 ms·
I thought let's encrypt was only for domain names and not for email encryption. I'm a beginner in self hosted email. I'm using spf and dkim, ip is not blacklis
by ino 10y ago
I thought let's encrypt was only for domain names and not for email encryption. I'm a beginner in self hosted email.
I'm using spf and dkim, ip is not blacklisted, and the domain I'm sending from has a let's encrypt cert, but my emails still go to gmail spam. (Outlook also, but yahoo goes to the inbox)
Now that I'm thinking, the emails are sent using postfix through the fqdn (subdomain.example.com) which is not served by http and hasn't hot a cert.
If this is the case should sending the emails through example.com or add a cert to host.example.com work?
Or is there another mechanism to use let's encrypt certs for email?
- peller 10y agoOne of the things that tripped me up at first was the postfix settings. smtpd_* options are for receiving mail, and smtp_* (no d) are for sending. So you need smtp_tls_cert_file = /etc/letsencrypt/live/$domain/fullchain.pem smtp_tls_key_file = /etc/letsencrypt/live/$domain/privkey.pem smtp_tls_security_level = may # or encrypt, to force TLS Also, yes, if I understand you correctly your cert should include subdomain.example.com even if the web-facing content there doesn't use HTTPS.