Skip to content

Commit 9eefd82

Browse files
authored
Merge pull request #57 from sk3pp3r/master
Update SPF records
2 parents 1f86ae9 + 8928c79 commit 9eefd82

File tree

1 file changed

+20
-2
lines changed

1 file changed

+20
-2
lines changed

README.md

Lines changed: 20 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4583,9 +4583,27 @@ python -c "import random,string,crypt; randomsalt = ''.join(random.sample(string
45834583
###### Network Questions (27)
45844584
45854585
<details>
4586-
<summary><b>Create SPF records for your site to help control spam. ***</b></summary><br>
4586+
<summary><b>Create SPF records for your site to help control spam.</b></summary><br>
4587+
4588+
* Start with the SPF version, this part defines the record as SPF. An SPF record should always start with the version number v=spf1 (version 1) this tag defines the record as SPF. There used to be a second version of SPF (called: SenderID), but this was discontinued.
4589+
4590+
* After including the v=spf1 SPF version tag you should follow with all IP addresses that are authorized to send email on your behalf. For example: <code>v=spf1 ip4:34.243.61.237 ip6:2a05:d018:e3:8c00:bb71:dea8:8b83:851e</code>
4591+
4592+
* Next, you can include an include tag for every third-party organization that is used to send email on your behalf e.g. <code>include:thirdpartydomain.com.</code> This tag indicates that this particular third party is authorized to send email on behalf of your domain. You need to consult with the third party to learn which domain to use as a value for the ‘include’ statement.
4593+
4594+
* Once you have implemented all IP addresses and include tags you should end your record with an <code>~all</code> or <code>-all</code> tag. The all tag is an important part of the SPF record as it indicates what policy should be applied when ISPs detect a server which is not listed in your SPF record. If an unauthorized server does send email on behalf of your domain, action is taken according to the policy that has been published (e.g. reject the email or mark it as spam). What is the difference between these tags? You need to instruct how strict servers need to treat the emails. The <code>~all</code> tag indicates a soft fail and the <code>-all</code> indicates a hardfail. The all tag has the following basic markers:<br><br>
4595+
`-all` – servers that aren’t listed in the SPF record are not authorized to send email (not compliant emails will be rejected)<br>
4596+
`~all` – if the email is received from a server that isn’t listed, the email will be marked as a soft fail (emails will be accepted but marked)<br>
4597+
`+all` - we strongly recommend not to use this option, this tag allows any server to send email from your domain<br>
4598+
4599+
* After defining your SPF record your record might look something like this:
4600+
<code>v=spf1 ip4:34.243.61.237 ip6:2a05:d018:e3:8c00:bb71:dea8:8b83:851e include:thirdpartydomain.com -all</code>
4601+
4602+
Useful resources:
4603+
4604+
- [SPF Record Checker](https://www.dmarcanalyzer.com/spf/checker/)
4605+
- [SPF Syntax](https://www.spf-record.com/syntax)
45874606
4588-
To be completed.
45894607
45904608
</details>
45914609

0 commit comments

Comments
 (0)