With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case.
New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers.

Comments:Anonymous
This problem cleared up for me once I stopped rerouting incoming SMTP mail through the Internet Mail Service.
x
4

Anonymous
This happened when I applied service pack 4 to 5.5 running service park 3. I had to change the file version in IMS to correct it and I haven't been able to correct the problem in the MS Mail Connector.
x
3

EventID.Net
This behavior occurs because Internet Mail Service is connecting to itself in an attempt to deliver the message. See ME260247 for more information.
x
1

EventID.Net
See the links below for suggestions on how to troubleshoot this event. Also, suggested on a newsgroup post: "Turn on the SMTP Protocol Log category of Diagnostics Logging on the IMS. Set the level to "Maximum". Stop and restart the IMS. Wait for the 4115 to show up, then stop the IMS, turn off the SMTP Protocol Log. Now have a look through the log files for the "too many hops" line and work UP the file until you see the RCPT TO header. That'll tell you where the message was going. From there it should be easy to figure out what's happening."
x
2