DNS Records not authenticating and DMARC mismatch with Proton mail

Hi I am having problems with the Brevo Code, DKIM and DMARC records.

First - I’ve added the Brevo Code and DKIM records but Brevo still has an ‹ x › with value mismatch. I’ve double checked with my domain host and the txt records are there and values are correct? (Added a week ago)

Second - Proton mail also requires DMARC records that have different values to Brevo (v=DMARC1; p=quarantine) and I discovered that I can’t add two different DMARC records.

Any help appreciated.

Hi @Garden , thanks for posting on this community!

About your first question: can please write to the support team (contact@brevo.com) and tell them which domain you’re using? They’ll be able to investigate.

Second question:

  • mail specifications (not linked to Brevo, but general mail specifications) require to have one DMARC record only
  • it is not compulsory to use the DMARC record we’re proposing by default. As you long as you have one, it’s ok. The choice is entirely yours, so you can choose to use p=quarantine on your domain if you wish, it’s a setting on your domain side

Does this help?

Hi. I am having similar issues. My emails are being handled by Proton mail. I have a very high profile site getting ready to launch and I need high levels of security protecting the email account from impersonation or spamming. According to Proton Mail the domain is Verified and has MX, SPF, DKIM, and DMARC all in place and working.

These have all been personally added to my DNS registrar by myself and were propagated within minutes. Can you tell me what I need to do to get Brevo to recognise my domain as a legitimate sender address?

Thank you.

Hi @Robert_Luxford , thanks for posting on this community, and adding your feedback.

I don’t know myself; I would advise to write to our support team, and when you have their reply, post it here to help the other community members. Thanks!

Have done and shall do. Thanks for responding.

I had not yet reached the « add a domain » part of the process. Fortunately support was able to assist with my error. All good to go now.

1 Like

Great, thanks for the update!