This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
computing:spfdkim [2019/08/12 17:55] – oemb1905 | computing:spfdkim [2019/12/30 02:14] – oemb1905 | ||
---|---|---|---|
Line 9: | Line 9: | ||
#hacking # | #hacking # | ||
- | This tutorial is a bit simpler than the last one. | + | I finally got tired of my email triggering recipients SPAM filters, and worse, I was sometimes flagged by other tech colleagues' |
v=spf1 a mx include: | v=spf1 a mx include: | ||
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] |
- | --- //[[oemb1905@jonathanhaack.com|oemb1905]] 2019/08/12 17:34// | + | 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:// | ||
+ | |||
+ | --- //[[jonathan@haacksnetworking.com|oemb1905]] 2019/12/30 02:13// | ||