summaryrefslogtreecommitdiff
path: root/content/mail/validate.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/mail/validate.md')
-rw-r--r--content/mail/validate.md29
1 files changed, 20 insertions, 9 deletions
diff --git a/content/mail/validate.md b/content/mail/validate.md
index 2e371b2..8447409 100644
--- a/content/mail/validate.md
+++ b/content/mail/validate.md
@@ -119,10 +119,9 @@ systemctl reload postfix
## Adding the DNS record!
-We are only one step away from having functioning OpenDKIM. We must add
-the DKIM public key to our server\'s DNS settings, so go ahead and open
-up [your registrar\'s site](https://www.epik.com/?affid=we2ro7sa6) or
-wherever your site\'s DNS settings are.
+We are only one step away from having functioning OpenDKIM. We must add the
+DKIM public key to our server\'s DNS settings, so go ahead and open up your
+registrar\'s site or wherever your site\'s DNS settings are.
The public key is found in the file `/etc/postfix/dkim/mail.txt`, but it
will display as multiple lines and multiple quoted strings, which is
@@ -145,9 +144,8 @@ host we put it for is `mail._domainkey`.
{{< img alt="Adding the OpenDKIM TXT entry in DNS settings" src="/pix/dkim-01.png" link="/pix/dkim-01.png" >}}
-On my registrar, Epik, this is how it is input, but on some registrars,
-it may be required to include your domain name as well as
-`mail._domainkey.example.org`.
+On my registrar, this is how it is input, but on some registrars, it may be
+required to include your domain name as well as `mail._domainkey.example.org`.
If you have your own DNS server, add a TXT entry as follows:
@@ -172,7 +170,7 @@ You can permanently change your hostname by changing it in
`/etc/hostname` and rebooting, or you can just run
`hostname example.org` to change it temporarily for testing. Either way,
this will allow us to run the `mail` command as in [the SMTP
-article](smtp.html).
+article](../smtp).
```sh
echo "Hi there.
@@ -211,9 +209,22 @@ an email-authentication standard used to prevent spammers from sending messages
that appear to come from a spoofed domain.
cat /etc/mailname
- echo "v=spf1 mx a:mail.$(cat /etc/mailname) -all"
+ IP4=<your VPS's IPv4 address>
+ IP6=<your VPS's IPv6 address>
+ echo "v=spf1 mx a:mail.$(cat /etc/mailname) ip4:$IP4 ip6:$IP6 -all"
+
+**Note**: previous versions of this guide didn't ask you to specify the `ip4`
+and `ip6` mechanisms. If you don't include them, some email hosts (most
+notoriously gmail) will not accept mail from your server.
+
+The `IP4` and `IP6` values should be the same as what you set your [PTR
+records](../rdns) to.
The output of `cat /etc/mailname` is the Host field. The output of the second command is the TXT value.
Again, you can check [that site](https://appmaildev.com/en/spf)
to make sure your DKIM, DMARC, and SPF entries are valid. That's it!
+
+## Contribution
+
+- SPF mechanisms updated by Martin Chrzanowski \-- [website](https://m-chrzan.xyz), [donate](https://m-chrzan.xyz/donate.html)