SMTP server configuration: Difference between revisions
Jump to navigation
Jump to search
m (Woozle moved page Email server configuration to SMTP server configuration without leaving a redirect: more specific) |
No edit summary |
||
| Line 10: | Line 10: | ||
SPF is relatively simple, I think? Last I remember, there's a web tool to help build the necessary TXT records... but I think those domains may already be configured. Will check that. | SPF is relatively simple, I think? Last I remember, there's a web tool to help build the necessary TXT records... but I think those domains may already be configured. Will check that. | ||
==DKIM (DomainKeys Identified Mail)== | ==DKIM (DomainKeys Identified Mail)== | ||
This has two parts: | |||
* public key in domain's DNS record | |||
* public key attached to email somehow (shouldn't that be "email signed by private key"? | |||
==DMARC (Domain-based Message Authentication, Reporting and Conformance)== | ==DMARC (Domain-based Message Authentication, Reporting and Conformance)== | ||
Revision as of 14:58, 11 August 2022
This page is, for now, notes towards trying to configure our outgoing email servers so that at least GMail won't bounce notifications from apps like phpBB. The primary return-address domains I want to configure are:
- hypertwins.org
- woozalia.com
- wooz.dev
There seem to be several necessary anti-spam protocols: SPF, DKIM, and DMARC.
For clues, I can look at the configuration of toot.cat -- I'm pretty sure we configured it with all three.
SPF (Sender Policy Framework)
SPF is relatively simple, I think? Last I remember, there's a web tool to help build the necessary TXT records... but I think those domains may already be configured. Will check that.
DKIM (DomainKeys Identified Mail)
This has two parts:
- public key in domain's DNS record
- public key attached to email somehow (shouldn't that be "email signed by private key"?