If you notice that your email health check didn’t go through, it likely means we never received your test email.
This can happen for a variety of reasons — ranging from incorrect sending settings to delivery issues on your email provider’s side.
In this guide, we’ll walk you through the most common causes and how to troubleshoot them step by step, so you can ensure your test gets delivered and your sending setup is properly validated.
One of the most common reasons for a failed email health check is that your mail provider prevented the test email from being sent. This often happens silently, especially in corporate or tightly controlled email environments.
Here’s how to check:
1.Look for a bounce message:
Check the mailbox of the sender you used for the test. If the message was blocked or failed to deliver, you should see a bounce-back message from your provider. Look specifically for any bounce directed to [email protected] — this will help identify the root cause. If you see such bounce
You may see this error code:
'550 5.7.708 Service unavailable. Access denied, traffic not accepted from this IP. For more information, please go to http://go.microsoft.com/fwlink/?LinkId=526653 AS(7230)
Such a bounce can happen when you have a trial or a 3-month-old Office tenant and try to use email automation tools
Please contact MS support and request permission to send emails via a third-party tool to resolve the issue.
2.Check the admin panel or email logs:
If you have access to your mail provider’s admin console (like Microsoft 365 or Google Workspace), go to the email logs or message trace section.
Look for the test message — it might show up as blocked or stuck in the outbound quarantine zone.
If it's quarantined, review the reason and release the message if needed.
You may also need to whitelist the health check address or adjust your outbound policies to allow test messages through.
After the issue is resolved, do not hesitate to re-launch the test:
Feel free to contact us for any further assistance!