This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
computing:spfdkim [2019/08/12 17:55] – oemb1905 | computing:spfdkim [2019/08/13 17:13] – oemb1905 | ||
---|---|---|---|
Line 26: | Line 26: | ||
Of course, all of this is simply an exercise at shooting at the dark unless you validate it all. Of course, sending emails to your friends and asking them if it got tagged as SPAM is pretty ineffective, | Of course, all of this is simply an exercise at shooting at the dark unless you validate it all. Of course, sending emails to your friends and asking them if it got tagged as SPAM is pretty ineffective, | ||
- | A big thanks to this hacker for finally providing a sensible tutorial to riff off of: | + | [Update: Added DMARC] |
- | --- // | + | Okay, now that you have both an SPF record and DKIM record you can optionally set up another TXT record for DMARC. This will tell the recipient that there is an SPF/DKIM record in place and who to contact in cases of violation. The destination was parsed as follows: |
+ | |||
+ | v=DMARC1; p=none; pct=100; rua=mailto: | ||
+ | |||
+ | On afraid .org, this looks like: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | A big thanks to this hacker for finally providing a sensible tutorial to riff off of: [[https:// | ||
+ | |||
+ | --- // | ||