SMTP connector '{4}' is configured to forward messages addressed to domain '{1}' to smart host '{0}' but the '{5}' property in the metabase for SMTP instance '{3}' on server {2} indicates a different smart host. This SMTP connector may not be able to route messages correctly. Current '{5}' value: {8} (Expected value: {9})
SMTP connector '{3}' in routing group '{1}' uses a domain wildcard convention ({7}). This notation is not supported in Exchange ...
SMTP connector '{4}' is configured to allow messages to be relayed to domain '{1}' but the '{5}' property in the metabase ...
SMTP connector '{4}' is configured to forward messages addressed to domain '{1}' to smart host '{0}' but the '{5}' property ...
SMTP connector '{4}' is configured to forward messages addressed to domain '{1}' to smart host '{0}' but the '{5}' property ...
SMTP connector '{4}' is configured to forward messages addressed to domain '{1}' to smart host '{0}' but the '{5}' property ...
SMTP connector '{4}' is configured to route messages to SMTP domain '{1}', which this Exchange organization is authoritative ...
SMTP connector '{4}' is not configured to allow messages to be relayed to non-authoritative SMTP address space '{1}'. This ...
SMTP connector {3} has delivery restrictions based on distribution group membership and server {2} is a bridgehead server ...
SMTP domain '{1}' is set as a non-authoritative address space in recipient policy '{3}', but the '{5}' property in the metabase ...