Description
Domain-based Message Authentication, Reporting & Conformance (DMARC) plays a pivotal role in helping to prevent email spoofing and phishing by verifying the authenticity of the sender’s domain. DMARC also fosters trust among email recipients, ensuring that messages originate from verified sources.
A DMARC policy allows a sender to indicate that their messages are protected by SPF and/or DKIM. It tells a receiver what to do if neither of those authentication methods passes – such as quarantine or reject the message.
There are multiple DMARC enforcement capabilities to customize the behavior of CloudFilter to meet your customer’s security needs. By default, a secure DMARC posture is configured with best practice defaults.
Default settings for DMARC policy enforcement are preconfigured on the Filtering tab at the Reseller, Customer, Domain, and User sections of the Mailprotector Console.
Email patterns vary between organizations and industries. Mailprotector's default settings work very well in most cases, and adjustments for outlying situations should be done carefully. For additional information visit: DMARC Policy Enforcement defined.
Default Settings
DMARC Policy Enforcement
|
Bounce messages that fail DMARC with a reject action |
Enabled |
|
DMARC failure with reject action |
400 |
|
DMARC failure with quarantine action |
200 |
|
DMARC failure with no action |
100 |
|
DMARC authenticated |
0 |
|
DMARC policy not available |
0 |
|
Bad DMARC policy |
0 |
Below is a screenshot showing the default settings for DMARC policy enforcement.
Please contact the Partner Success team with questions.
Comments