Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Your domain's DMARC policy can be configured with different Policy Selectors, sometimes referred to as "Tags", Various tags are used to instruct remote email servers handle email from your domain name. You can start off by instructing remote email servers to ignore emails that fail DMARC authentication and proceed with their normal handling of email. Later, you can move a more strict policy which will instruct remote mail servers to quarantine emails that fail DMARC authentication and to move that email into the recipients junk mail or spam folder. Finally, you can instruct remote email recipient servers to completely reject a percentage or all emails that you have not implicitly authorized to send email on behalf of your domain's email addresses. The reject option being the most strict of all policies, caution should be used before moving to  a reject policy. 

DMARC None or Ignore

"p=none"

In DMARC, there is no official "p=ignore" policy. 

"p=none"

To adhere to the current DMARC1 specification, The correct syntax to use is "p=none".

The "p=none" This policy instructs receiving mail servers to take no action based on the DMARC evaluation results. Meaning This means that the DMARC policy is set to monitor and report mode only; it tells recipient mail servers to neither quarantine or reject emails that fail DMARC authentication. Instead, domain owners may receive aggregate (RUA) and forensic (RUF) reports about DMARC authentication results if the "rua" and "ruf" tags are selected in the domain's DMARC policy.

The recipient mail servers should are requested to go ahead and proceed with their usual mail-handling procedures. The recipient server may place the email in the inbox or junk mail folder, or any other folder depending on how the recipient's mail server is configured to deal with email, in general. This "p=none" is typically what you would set your DMARC policy to when first starting out. This allows you to make sure that email is being handled "as usual" before adding any restrictive DMARC instructions to your domain. 

...