Hello,
I use OVH’s Hosted Exchange email and my ODOO provider asks me to add DNS records in ODOO, but after adding them I still don’t have access to outgoing mail.
Could it be a conflict with the DNS for OVH’s Exchange email?
Here they are:
Hi @OlivierH18
The records you added in the OVH DNS zone are for Mailgun, but the Odoo interface is asking you for exactly the same records and marks them as unverified. It's not a conflict; the records are already set, but Odoo doesn't see them as valid.
Check the TTL, you set it to 0. A TTL of 0 seconds is extremely low and, although technically valid, some external verification systems may have trouble reading them immediately.
Make sure the SPF record is correct. In Odoo, the value it asks for is v=spf1 include:mailgun.org ~all. The record you have entered is exactly that. The problem isn't the content, but the external verification. If Odoo doesn't verify it, try waiting a couple of hours and then, from the Odoo interface, click “Re-verify” or wait for the automatic verification to run again.
Another detail, the DKIM record for pdk2 has a destination that seems to contain a typo. The Odoo interface shows pdk2._domainkey.62b2a.dkim10.eu.mgsnd.org, but in image 1 the destination is pdk2._domainkey.62b2a.dkim10.eu.msgsend.org. Check that the value in the OVH DNS zone is exactly what Odoo requests. If it doesn't match, change the CNAME of pdk2 to point to the correct value.
Finally, check the Automatic sender security box. In Odoo, if you have “Automatic sender security” enabled, Odoo will ask you for the CNAMEs. Since you added the records manually, make sure the Custom DNS option is enabled in Odoo.
I think your issue is propagation time and that the external verification hasn't completed.
Let me know, cheers.
Sergio Turpín
Is this character a capital O or a zero?
In any case neither is valid at msgsend.org
dig pdk1._domainkey.62b2a.dkim1o.eu.msgsend.org txt
status: NXDOMAIN
dig pdk1._domainkey.62b2a.dkim10.eu.msgsend.org txt
status: NXDOMAIN