Thanks for asking this question! With the way that our service operates, this is not something that we are able to provide at this time.
For more information if anyone cares to hear it, the reason is that delivery will almost always succeed from the server that you are sending to, but this does not indicate it’s true path with our service. When you send out from our server, so long as our server accepts it, the email is immediately (and successfully) delivered to one of two outbound filter servers. These filters servers then send the email out to one of two load balancers. The load balancer that receives it chooses one of a great number of outbound relays to send the email to. From there, the email can take two paths:
- Direct to recipient.
- To a backup relay range.
If #1, path over, email delivered. If #2, it can again take two paths:
- Direct to recipient.
- To MailChannels.
Once again if it goes to #2, it can take two more paths:
- Direct to recipient.
- Bounced to sender.
This complexity is designed to ensure the highest availability and quality delivery outbound email, and is actually the part of the product that I am most proud of. No one currently performs this level of work on outbound email within our price range, it is truly my favorite thing about MXroute. However, some things are not able to recognize the complexity. If we offered DSN you would likely see it as accepted but by our filters, and that would not indicate whether or not it actually arrived at it’s true destination.