hmLoadTopic({
hmKeywords:"DKIM,DKIM including in DMARC reports,DMARC,DMARC failure reports,DMARC including DKIM in reports,DMARC logging records,DMARC Public suffix file,DMARC records,DMARC Reporting,Logging,Logging DMARC records,Public suffix file",
hmTitle:"DMARC Settings",
hmDescription:"DMARC Settings DKIM canonicalized headers are included in DMARC failure reports Enable this option if you wish to include DKIM canonicalized headers in DMARC failure reports. T",
hmPrevLink:"security--dmarc_reporting.html",
hmNextLink:"security--message_certification.html",
hmParentLink:"security--dmarc.html",
hmBreadCrumbs:"<a href=\"security_menu.html\">Security Menu<\/a> &gt; Security Manager &gt; Sender Authentication &gt; <a href=\"security--dmarc.html\">DMARC<\/a>",
hmTitlePath:"Security Menu > Security Manager > Sender Authentication > DMARC > DMARC Settings",
hmHeader:"<h1 class=\"p_Heading1\" style=\"page-break-after: avoid;\"><span class=\"f_Heading1\">DMARC Settings<\/span><\/h1>\n\r",
hmBody:"<p class=\"p_BodyText_Center\"><img style=\"margin:0 auto 0 auto;width:32.5625rem;height:26.9375rem;border:none\" src=\".\/images\/sender-authentication_dmarc-settings.png\"\/><\/p>\n\r<p class=\"p_DialogSectionHeading\" style=\"page-break-after: avoid;\"><span class=\"f_DialogSectionHeading\">DMARC Settings<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">DKIM canonicalized headers are included in DMARC failure reports<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Enable this option if you wish to include DKIM <a href=\"security--dkim_options.html\" class=\"topiclink\">canonicalized headers<\/a> in DMARC <a href=\"security--dmarc_reporting.html\" class=\"topiclink\">failure reports<\/a>. This is disabled by default.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">DKIM canonicalized body is included in DMARC failure reports<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Enable this option if you wish to include the DKIM <a href=\"security--dkim_options.html\" class=\"topiclink\">canonicalized body<\/a> in DMARC <a href=\"security--dmarc_reporting.html\" class=\"topiclink\">failure reports<\/a>. This is disabled by default.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Replace Reserved IPs in DMARC reports with &quot;X.X.X.X&quot;<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">By default MDaemon replaces your reserved IP addresses in DMARC reports with &quot;<\/span><span class=\"f_PlainText\">X.X.X.X<\/span><span class=\"f_ControlIndent\">&quot;. Disable this option if you wish to make your reserved IPs visible in DMARC reports. This option does not apply to DKIM canonicalized data.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Refuse to accept messages if \'From\' is incompatible with DMARC<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Enable this option if you wish to refuse messages that are incompatible with DMARC requirements regarding \'From\' header construction. These are messages with multiple \'From\' headers or multiple email addresses in a single \'From\' header. Such messages are currently exempt from DMARC processing. This setting is disabled by default because having multiple addresses in a single \'From\' header is not technically a protocol violation, but enabling the setting would help maximize DMARC protection. This setting is only applied when <a href=\"security--dmarc_verification.html\" class=\"topiclink\">DMARC verification<\/a> is enabled.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Insert &quot;Precedence: bulk&quot; header into DMARC report emails<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">By default MDaemon will insert a bulk mail header into DMARC report emails. Clear this checkbox if you do not wish to insert this header.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Include full DMARC records in log file<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">By default MDaemon logs the full DMARC DNS record it obtains during DMARC DNS queries. Disable this option if you do not with to include the full DMARC record in the log file.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Auto-update public suffix file if older than this many days<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">DMARC requires a public suffix file to reliably determine the proper domains to query for DMARC DNS records. By default MDaemon will automatically update its stored public suffix file whenever it exceeds 15 days old. Change the value of this option if you wish to update the public suffix file more or less often. Disable the option if you do not wish to update it automatically.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Public suffix file URL<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">This is the URL of the public suffix file that MDaemon will download to use for DMARC. By default MDaemon uses the file located at: http:\/\/publicsuffix.org\/list\/effective_tld_names.dat.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Update public suffix file now<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Click this button to manually update the public suffix file, from the <\/span><span class=\"f_ControlIndent\" style=\"font-style: italic;\">Publix suffix file URL<\/span><span class=\"f_ControlIndent\"> specified above.<\/span><\/p>\n\r<p class=\"p_SeeAlso\" style=\"page-break-after: avoid; border-right: none; border-bottom: none; border-left: none;\"><span class=\"f_SeeAlso\">See:<\/span><\/p>\n\r<p class=\"p_SeeAlsoLinks\" style=\"page-break-after: avoid;\"><span class=\"f_SeeAlsoLinks\"><a href=\"security--dmarc.html\" class=\"topiclink\">DMARC<\/a><\/span><\/p>\n\r<p class=\"p_SeeAlsoLinks\" style=\"page-break-after: avoid;\"><span class=\"f_SeeAlsoLinks\"><a href=\"security--dmarc_verification.html\" class=\"topiclink\">DMARC Verification<\/a><\/span><\/p>\n\r<p class=\"p_SeeAlsoLinks\" style=\"page-break-after: avoid;\"><span class=\"f_SeeAlsoLinks\"><a href=\"security--dmarc_reporting.html\" class=\"topiclink\">DMARC Reporting<\/a><\/span><\/p>\n\r<p class=\"p_SeeAlsoLinks\" style=\"page-break-after: avoid;\"><span class=\"f_SeeAlsoLinks\"><a href=\"security--dkim_options.html\" class=\"topiclink\">DKIM Settings<\/a><\/span><\/p>\n\r<p class=\"p_SeeAlsoLinks\" style=\"page-break-after: avoid;\"><span class=\"f_SeeAlsoLinks\">&nbsp;<\/span><\/p>\n\r<p class=\"p_SeeAlsoLinks\" style=\"page-break-after: avoid;\"><span class=\"f_SeeAlsoLinks\">&nbsp;<\/span><\/p>\n\r"
})
