Note: This article was originally published in 2013. Some steps, commands, or software versions may have changed. Check the current Exchange 2013 documentation for the latest information.

If you’re encountering this issue, this troubleshooting guide will help you identify the root cause and apply the appropriate fix. This applies to Exchange 2013 environments.

Why is my Exchange 2013 Server generating a lot of emails from (mailto:MailDeliveryProbe@MailDeliveryProbe.com) and (mailto:inboundproxy@inboundproxy.com)?

At first I was very worried about this. My (http://en.wikipedia.org/wiki/Server_%28computing%29 “Server (computing)”) were sending out some (http://en.wikipedia.org/wiki/Email_spam “Email spam”) (forgot to turn on the Sender ID so a few of Non delivery emails were being sent out, whoops) and there had been some (http://en.wikipedia.org/wiki/Port_scanner “Port scanner”) detected and other attacks coming from an (http://en.wikipedia.org/wiki/Internet_Protocol “Internet Protocol”) in (http://en.wikipedia.org/wiki/China “China”) so I had considered myself hacked and compromised when I saw a lot of emails being generated from the (http://en.wikipedia.org/wiki/Email_address “Email address”) (mailto:MailDeliveryProbe@MailDeliveryProbe.com) and (mailto:inboundproxy@inboundproxy.com). Below is an example of what the Exchange logs had to show:

HARED… (http://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol “Simple Mail Transfer Protocol”) inboundproxy@inboundproxy.com {HealthMailbox7ca21706590a4541… Inbound proxy probe

So, I was worried. I tried searching all over the (http://en.wikipedia.org/wiki/Internet “Internet”) and only a few posts mentioned this issue and most of them were unable to offer an answer and simply suggested purging the Health Mailbox and turning on (http://en.wikipedia.org/wiki/Sender_ID “Sender ID”) so that the emails originating from (mailto:inboundproxy@inboundproxy.com) would be turn down. I reached out to (http://www.microsoft.com “Microsoft”) and found out that these email addresses are used by their Health check systems. So I am able to relax at least about this issue and hopefully other people encountering this will not be caught by surprise like myself. Below is the answer I obtained from Microsoft:

“The email address inboundproxy@inboundproxy.com is used to do health check for resources from Frontend Transport role to Hub Transport and its Exchange 2013 product design behavior and it’s not an issue with exchange server.(http://www.microsoft.com/exchange “Microsoft Exchange Server”) Health Manager Service is responsible for health checking if it is stopped health check will not happen on exchange server”.

 

“ Sorry for the delay. The email address _MailDeliveryProbe@MailDeliveryProbe.com is also used for health check purpose only it will do health with mailbox database resources and you can seeMailDeliveryProbe@MailDeliveryProbe.com entries in Message Tracking Delivery logs only and this is also Exchange 2013 product design behavior and no issues with exchange server._ __ Same Microsoft Exchange Health Manager Service is responsible for this health check ”.

 

(http://img.zemanta.com/zemified_h.png?x-id=1d9f28b8-8e50-4d57-9c44-df9b09d6c699)](http://www.zemanta.com/?px “Enhanced by Zemanta”)

Summary

This guide covered the common causes and solutions for this Exchange 2013 issue. If the problem persists, check the official documentation or system logs for additional diagnostic information.