When emails sent from an OVHcloud address land in spam, the most common cause is incomplete domain authentication: a missing or wrong SPF record, DKIM never turned on, or no DMARC at all. Check these three settings in the order below. Most cases can be fixed in the OVHcloud Control Panel, with no special technical skills.
This guide starts from the symptom, checks what the recipient sees, then fixes each item. It applies to OVHcloud email plans (MX Plan, Email Pro, Exchange, Zimbra) on a domain whose DNS zone is managed at OVHcloud.
Why your emails end up in spam
Gmail, Outlook and other mailbox providers do not take an email at its word. They check three things:
- SPF: is the server sending the message authorized by your domain?
- DKIM: does the message carry a valid signature, with the key published in your DNS?
- DMARC: does the domain in the "From" field match the domain verified by SPF or DKIM, and what should happen if it does not?
Google requires at least SPF or DKIM from every sender to Gmail, and all three above 5,000 messages a day. Microsoft applies the same rule to high-volume senders to Outlook.com and Hotmail. A small business is far from those thresholds, but a poorly authenticated domain still looks suspicious to spam filters.
Step 1: read the verdict in a received email
Before touching your DNS, look at what the recipient sees. Send a message from your OVHcloud address to a personal Gmail account, then:
- open the message in Gmail on a computer;
- click the three dots next to "Reply," then Show original;
- read the summary at the top of the page: SPF, DKIM and DMARC each show a verdict,
PASSorFAIL.
Write down the three results. A FAIL, or a missing line, tells you exactly where to start.
Step 2: check and fix SPF
What you should have
For OVHcloud's shared email plans (MX Plan, Email Pro, Hosted Exchange), the value OVHcloud recommends is:
v=spf1 include:mx.ovh.com ~allIf other services send email as your domain (newsletter tool, invoicing software, CRM), add their include: to the same record. A domain must have only one SPF record: two SPF records cause an error, and the check fails for all your email.
Where to change it at OVHcloud
- Go to Web Cloud > Domain names, select the domain, then open the DNS zone tab.
- Click Filter and show the
TXTandSPFtypes to see whether an SPF record already exists. - If there is none: click Add an entry, choose the SPF type, then tick Include OVH email servers. The preview shows the resulting value.
- If there is one: open the ⋮ menu on that line and choose Edit the entry.
OVHcloud says it can take 4 to 24 hours for the change to be fully effective.
Check your domain for free. AttackScout reads your public SPF, DMARC and DKIM records, spots duplicates and the 10-lookup limit, then tells you what to change. Run the free check
Step 3: turn on DKIM
This is the most common gap at OVHcloud: DKIM is not always active by default. Without it, your messages carry no signature, and DMARC can only rely on SPF.
MX Plan
Open MX Plan, select the domain, then the General information tab. A red DKIM badge in the diagnostic area means it is not active: click it, then confirm. OVHcloud's English guide names this button Validate in one place and Enable in another, so click whichever your screen shows.
Email Pro and Exchange
Open Email Pro (or Exchange, in the MICROSOFT section), select the service, then the Associated domains tab. Click the red DKIM badge next to the domain, then confirm.
Zimbra
Open Zimbra Mail, then the Domain tab. In the ⋮ menu next to the domain, choose Diagnostics, then the DKIM tab: it shows the two CNAME records to create or fix.
Timing and check
Activation takes 30 minutes to 24 hours. The badge should then turn green. If your domain is not managed in the same OVHcloud account, OVHcloud gives you two CNAME records to add to the DNS zone yourself before you confirm.
OVHcloud DKIM selectors have plan-specific names (ovhmo… for MX Plan and Zimbra, ovhemp… for Email Pro, ovhex… for Exchange). An outside tool cannot guess them: it needs the exact name, visible in the s= parameter of the signature in a received email.
Step 4: publish a DMARC record
Once SPF and DKIM are in place, add a DMARC record. Start in monitoring mode:
v=DMARC1; p=none; rua=mailto:[email protected]In the DNS zone, click Add an entry and choose the DMARC type: OVHcloud provides a dedicated form, with the _dmarc subdomain and the main settings. The details, including how to move gradually to quarantine, are in our guide on setting up DMARC at OVHcloud.
Step 5: remember your other senders
Your mailbox is not the only thing sending email with your domain. List everything that sends "on your behalf":
- your website's contact form or online store;
- your newsletter tool;
- your invoicing or booking software;
- a Google Workspace or Microsoft 365 mailbox, if you use one with a domain registered at OVHcloud.
Each one must be covered by your SPF record or sign with DKIM for your domain. Otherwise its messages fail DMARC and risk the spam folder. Each service's documentation gives the value to add.
If everything says "PASS" and your emails still go to spam
Authentication is necessary, but not enough. If all three verdicts show PASS, also look at:
- content: an all-caps subject line, a message made of a single image, or shortened links draw the filters' attention;
- recipients: writing to bought or outdated addresses drives up complaints;
- volume: a sudden bulk send from a usually quiet mailbox looks suspicious;
- reputation: if you send a lot to Gmail, Google Postmaster Tools shows your complaint rate (Google requires staying below 0.3% and recommends under 0.1%).
Confirm the fix
Wait a few hours after your last change, then send another test message to Gmail and check Show original again. All three lines should show PASS. You can also check the syntax with our free SPF checker and DMARC checker.
Check your domain for free. In under a minute and without an account, AttackScout checks your domain's email setup, your certificate and your website, then gives you the fix to copy into OVHcloud. Check my domain
Sources
Accessed November 13, 2026, unless stated otherwise.
- OVHcloud documentation, SPF record guide: https://docs.ovhcloud.com/en/guides/web-cloud/domains/dns-zone-spf
- OVHcloud documentation, DKIM record guide: https://docs.ovhcloud.com/en/guides/web-cloud/domains/dns-zone-dkim
- OVHcloud documentation, DMARC record guide: https://docs.ovhcloud.com/en/guides/web-cloud/domains/dns-zone-dmarc
- Google, Email sender guidelines (accessed November 12, 2026): https://support.google.com/mail/answer/81126?hl=en
- Google, Check if a Gmail message is authenticated (accessed November 12, 2026): https://support.google.com/mail/answer/180707?hl=en
- Google, Trace an email with its full header (accessed November 12, 2026): https://support.google.com/mail/answer/29436?hl=en
- Microsoft, Fix NDR error 550 5.7.515 in Outlook.com (accessed November 12, 2026): https://support.microsoft.com/en-us/outlook/fix-ndr-error-550-5-7-515-in-outlook-com
- IETF, RFC 7208 (SPF, 10-lookup limit, single record): https://www.rfc-editor.org/rfc/rfc7208