Skip to main content

Automated reports not being delivered despite successful email DNS validation

  • Oct 28, 2026 1:44 PM UTC
  • 1 reply
  • 11 views

Hi all,

We’re trying to set up automated reports as part of our onboarding process however are experiencing some issues.  

We’ve configured our email domain through Mimecast and added the required SPF, MX, and DKIM DNS records. The DNS configuration test reports: “The Email DNS configuration has been validated successfully.” 

Despite everything having been set up our end and the background job indicating that each task has been completed, the automated reports generated from our custom-built reports are still not being delivered to the email addresses specified in the report settings. Instead, we keep getting email delivery failures stating that the MX records are invalid.

Has anyone encountered this issue before or found a way to troubleshoot it?

Many thanks.

1 reply

Noah
Docebian
  • Noah
  • Docebian
  • Oct 30, 2026 8:49 PM UTC

Hi Nina, The “MX records are invalid” wording is a useful clue, so we can start there. Could you share the full bounce message, including headers? Curious which domain it says has the invalid MX, and which server generated the rejection. (If there is sensitive information, might be best to use a support case! but happy to dig in here as well if it’s not sensitive information) 

If it’s the recipient’s domain: double-check the recipient addresses in the report settings for typos, and look up that domain’s MX publicly (e.g. MXToolbox). If the domain only resolves inside your network, Docebo won’t be able to deliver to it.

If it’s your sender domain: look up its public MX and compare it to the MX value shown in Docebo under Domain management > Email sender domains. A common cause is using a domain whose MX already points to Mimecast for your inbound mail, which conflicts with the MX Docebo’s built-in email service needs. If that’s the case, the usual fixes are a dedicated subdomain for platform email (e.g. learning.yourcompany.com) or, if you have the Custom SMTP app, relaying through Mimecast instead.

If the records all match and it still fails, I’d suggest opening a Support case with the bounce and the test time, and ask them to confirm what response Docebo received from the next mail server.

Happy to dig in further once you have the bounce details!

Noah

Terms & ConditionsAccessibility statement