mirror of
https://github.com/internetstandards/toolbox-wiki.git
synced 2024-12-22 17:45:06 +01:00
Updated SPF how to (markdown)
This commit is contained in:
parent
25a8a22d3e
commit
1ebcf22123
@ -7,3 +7,22 @@ SPF is short for "**S**ender **P**olicy **F**ramework" and is described in [RFC
|
||||
# Why use SPF?
|
||||
Our current e-mail infrastructure was originally designed for any mail sending host to use any DNS domain name it wants. The authenticity of the sending mail server cannot be deterimined, which makes it easy for random third parties to make use of a domain name with possibly a malicious intent. This increases the risk of processing e-mail since the intentions of the sender (host) are uncertain. SPF can help the fight against spam and other kinds of unwanted e-mail be offering a way of authenticating the sending mail server.
|
||||
|
||||
# Tips and tricks for implementation
|
||||
to-do
|
||||
|
||||
# Implementing DANE for SMTP on Debian Stretch
|
||||
**Specifics for this setup**
|
||||
* Linux Debian 9.8 (Stretch)
|
||||
* SpamAssassin version 3.4.2 (running on Perl version 5.28.1)
|
||||
* Postfix 3.4.5
|
||||
* BIND 9.10.3-P4-Debian
|
||||
* postfix-policyd-spf-python 2.0.1-1
|
||||
|
||||
**Assumptions**
|
||||
* DNSSEC is used
|
||||
* Mail server is operational
|
||||
|
||||
## Outbound e-mail traffic
|
||||
This part of the how to describes the steps that should be taken with regard to your outbound e-mail traffic. This enables other parties to use SPF for validating the authenticity of e-mail servers sending e-mail on behalf of your domain name.
|
||||
|
||||
### Generating and publishing SPF records
|
||||
|
Loading…
Reference in New Issue
Block a user