{4}: The max hop count was exceeded for the message. This code may occur if a loop situation exists between a sending server and a receiving server that are not in the same organization. In this scenario, the message bounces back and forth until the hop count is exceeded. The max hop count property is set for each virtual server, and you can manually override this setting (the default setting is 15 for Exchange 2000 Server and 30 for Exchange Server 2003). Additionally, look for any situations that could cause loops between servers.
The managed folder mailbox policy '{0}' for the mailbox '{1}' cannot be retrieved because it is linked to more than one managed ...
The managed folder mailbox policy '{0}' is invalid because it is linked to more than one default managed folder of the same ...
The managed folders, content settings, and policies that you create are applied to users' mailboxes only when the Managed ...
The MAPI interface for Active Directory is disabled on server {2}. Microsoft Office Outlook clients will not be able to contact ...
The max hop count was exceeded for the message. This code may occur if a loop situation exists between a sending server and ...
The Max number of retries to load resolver configuration data on startup has been reached. The Microsoft Exchange Transport ...
The MaxDSNSize registry value has not been set on server {2}. Implementing this option can increase overall performance and ...
The MaxDumpsterSizePerStorageGroup, MaxDumpsterTime, MaxReceiveSize, and MaxRecipientEnvelopeLimit properties are not used ...
The MaxFieldLength HTTP parameter on server {2} has not been set to 32768. In large environments the absence of this value ...