From 69ae4ff31924e2817119e856b3b06e66ca120dac Mon Sep 17 00:00:00 2001 From: Arun Date: Fri, 26 May 2023 17:54:07 +0530 Subject: [PATCH] Update dkim_dmarc_spf.md (#3367) --- docs/content/config/best-practices/dkim_dmarc_spf.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/config/best-practices/dkim_dmarc_spf.md b/docs/content/config/best-practices/dkim_dmarc_spf.md index 3fece48b..8ab00f48 100644 --- a/docs/content/config/best-practices/dkim_dmarc_spf.md +++ b/docs/content/config/best-practices/dkim_dmarc_spf.md @@ -262,7 +262,7 @@ The only thing you need to do in order to enable DMARC on a "DNS-level" is to ad Typically something like this should be good to start with: ```txt -_dmarc.example.com. IN TXT "v=DMARC1; p=none; sp=none; fo=0; adkim=4; aspf=r; pct=100; rf=afrf; ri=86400; rua=mailto:dmarc.report@example.com; ruf=mailto:dmarc.report@example.com" +_dmarc.example.com. IN TXT "v=DMARC1; p=none; sp=none; fo=0; adkim=r; aspf=r; pct=100; rf=afrf; ri=86400; rua=mailto:dmarc.report@example.com; ruf=mailto:dmarc.report@example.com" ``` Or a bit more strict policies (_mind `p=quarantine` and `sp=quarantine`_):