How to change DMARC records from none to quarantine for BIMI?

Email marketer from Mailhardener's Blog explains that BIMI helps display your logo in email inboxes, you'll need a DMARC policy set to either quarantine or reject. Make sure to have a valid VMC certificate, which verifies your logo. They emphasize monitoring DMARC reports to prevent deliverability issues.

Email marketer from EmailSecuritySPF Forum shares that switching to a 'quarantine' policy requires careful monitoring. It's important to use a DMARC reporting tool to get visibility into email authentication results. The marketer suggests gradually increasing the enforcement percentage (e.g., start with 10% quarantine) and monitoring the impact on deliverability.

Marketer from Email Geeks shares the process for implementing BIMI or deploying DMARC with an enforcing policy, which involves reviewing DMARC aggregate reports, ensuring all email sources have aligned SPF and DKIM, switching over when aligned, and monitoring reports for problems, along with updating internal SOPs.

Email marketer from Reddit explains that before changing to a 'quarantine' policy, thoroughly analyze DMARC reports to identify all legitimate email sources and ensure they are properly authenticated with SPF or DKIM. Address any authentication failures before implementing the 'quarantine' policy to avoid impacting legitimate email delivery.

Email marketer from OnlyMyEmail Blog states that transitioning to quarantine for DMARC is an important step to take for security. You should first monitor DMARC with a none policy, then gradually change to a quarantine policy over time. They also suggest getting professional help if unsure.

Email marketer from StackOverflow notes that to successfully implement BIMI, a DMARC policy of either 'quarantine' or 'reject' is necessary. However, make sure you have valid SPF and DKIM records set up correctly, and have been monitoring DMARC reports to prevent blocking legitimate emails. They suggest testing thoroughly before fully implementing quarantine.

Email marketer from EmailGeek Forums shares their experience of changing DMARC to quarantine and states the main thing is monitoring your dmarc reports. Without this you will have no idea what you are quarantining or rejecting. They would suggest working with an expert to help you.

Marketer from Email Geeks shares that they moved to p=reject for BIMI and haven't seen any issues, while also providing a link to a BIMI generator resource.

Marketer from Email Geeks suggests using a service to visualize DMARC reports (e.g., dmarcian.com) and emphasizes the importance of not rushing from a p=none policy to an enforcing policy to avoid breaking legitimate mail.

Expert from SpamResource emphasizes the importance of careful monitoring of DMARC reports when transitioning from 'none' to 'quarantine'. They advise starting with a small percentage of quarantine and gradually increasing it as you gain confidence in your email authentication setup. It's also important to remember to check both SPF and DKIM records.

Expert from Word to the Wise highlights that while BIMI requires a DMARC quarantine or reject policy, the transition to a more restrictive policy from 'none' needs to be carefully planned. They suggest that users should use a tool like the WtW DMARC monitoring tool in order to know what sources are sending emails.

Documentation from Bimigroup.org states that to be eligible for BIMI, a domain must have DMARC set up with either a 'quarantine' or 'reject' policy. This ensures that only authenticated emails can display the brand's logo in supporting email clients. The guide also recommends monitoring DMARC reports and gradually increasing the policy enforcement.

Documentation from dmarcian.com advises a phased approach to implementing a DMARC quarantine policy. Start by monitoring DMARC reports with a 'none' policy, then gradually move to 'quarantine', and eventually 'reject'. This allows you to identify and fix any authentication issues before enforcing stricter policies.

Documentation from Google Workspace Admin Help details the steps involved in implementing DMARC including setting the policy. Moving from p=none to p=quarantine is a suggested step to take to protect your domain from phishing and spoofing. The guide highlights the importance of ongoing monitoring using DMARC reports to ensure no legitimate email is being affected by the new DMARC policy.

Documentation from Valimail.com explains that changing the DMARC policy to 'quarantine' instructs recipient mail servers to place messages that fail DMARC checks into the recipient's spam folder. It is a middle-ground option between 'none' (monitor only) and 'reject' (block messages). This transition requires careful monitoring of DMARC reports to ensure legitimate emails are not incorrectly quarantined.