I suppose configuring a remote domain and disabling NDRs to may work, but I don’t know what impact that may have on Managed Availability. The main purpose of this article at the moment is to shed some light on the matter for those of you out there who begin to notice these types of messages or log entries on your own servers.Īs far as I can see there is no remediation for this issue. Whether this can be used for nefarious purposes is unknown to me at this stage.īut in addition to that, it is not very polite to use someone else’s domain name in your product’s code, and may irritate the SEDO server admins if the volume of SMTP connection attempts from Exchange 2013 servers grows too large. At the moment the worst issue I can see is that it reveals the email addresses of your health mailboxes. In other words, my server is attempting SMTP connections to the IP address of the SEDO parking server.Īgain, I don’t see any specific, proven risk at this stage for any Exchange 2013 servers. “A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 82.98.86.172:25” I’ve seen them as well in my test lab, and I’ve also observed entries in my servers’ Frontend Transport protocol logs such as: So far everyone that has shown me an example of the issue is seeing NDRs being sent to that email address. They’ll continue to operate just fine, and Managed Availability will likely work as it is designed to work.īut what you may begin to notice, as several Exchange 2013 customers are asking me about lately, is a number of messages leaving your organization sent to the address. This in itself is not harmful to your Exchange 2013 servers.
0 kommentar(er)
