mirror of
https://github.com/internetstandards/toolbox-wiki.git
synced 2024-11-22 02:51:36 +01:00
Updated SPF how to (markdown)
This commit is contained in:
parent
77e639d027
commit
386270be51
@ -11,6 +11,7 @@ Our current e-mail infrastructure was originally designed for any mail sending h
|
|||||||
* The sender address shown to the user ("RFC5322.From") is not used when authenticating. SPF uses the invisible "RFC5321.MailFrom" header. Combining SPF with DMARC removes this disadvantage.
|
* The sender address shown to the user ("RFC5322.From") is not used when authenticating. SPF uses the invisible "RFC5321.MailFrom" header. Combining SPF with DMARC removes this disadvantage.
|
||||||
* E-mail forwarding is not supported, since the e-mail is often forwarded by another e-mail server.
|
* E-mail forwarding is not supported, since the e-mail is often forwarded by another e-mail server.
|
||||||
* SPF does not work between domains that use the same e-mail server.
|
* SPF does not work between domains that use the same e-mail server.
|
||||||
|
* Parked domains should be explicitly configured to not use e-mail. For SPF this is done with an empty policy and a hard fail: "v=spf1 –all".
|
||||||
|
|
||||||
# Outbound e-mail traffic (DNS records)
|
# Outbound e-mail traffic (DNS records)
|
||||||
SPF for outbound e-mail traffic is limited to publishing an SPF policy as a TXT-record in a domain name's DNS zone. This enables other parties to use SPF for validating the authenticity of e-mail servers sending e-mail on behalf of your domain name.
|
SPF for outbound e-mail traffic is limited to publishing an SPF policy as a TXT-record in a domain name's DNS zone. This enables other parties to use SPF for validating the authenticity of e-mail servers sending e-mail on behalf of your domain name.
|
||||||
|
Loading…
Reference in New Issue
Block a user