Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the hueman domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/CloudIngenium.com/htdocs/wp-includes/functions.php on line 6114
Why is my Exchange 2013 Server generating a lot of emails from MailDeliveryProbe@MailDeliveryProbe.com and inboundproxy@inboundproxy.com? – Knowledge eXchange

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

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

At first I was very worried about this. My servers were sending out some 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 port scans detected and other attacks coming from an IP in China so I had considered myself hacked and compromised when I saw a lot of emails being generated from the email addresses MailDeliveryProbe@MailDeliveryProbe.com and inboundproxy@inboundproxy.com. Below is an example of what the Exchange logs had to show:

HARED… SMTP     inboundproxy@inboundproxy.com     {HealthMailbox7ca21706590a4541… Inbound proxy probe

So, I was worried. I tried searching all over the 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 SenderID so that the emails originating from inboundproxy@inboundproxy.com would be turn down.

I reached out to 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. Microsoft Exchange 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”.

 

Enhanced by Zemanta

You may also like...

1 Response

  1. June 24, 2013

    […] majority of the messages in my test lab are from “inboundproxy@inboundproxy.com”. From this source: “The email address inboundproxy@inboundproxy.com is used to do health check for resources from […]

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.