One or more messages have failed delivery due to DNS response 'non-existent domain'. This will occur if one of the DNS servers in use does not know how to resolve the recipient domain. Check the recipient domain and ensure it is correct. If you believe this response was received in error, the connectivity log should be enabled to determine which DNS server is providing the incorrect response. The connectivity log can be enabled within the Exchange Management Shell by issuing the command "Set-TransportServer -Identity '{2}' -ConnectivityLogEnabled:$TRUE". The log is located in directory {3}
One or more Exchange virtual servers are owned by this node. You must failover each Exchange virtual server to at least one ...
One or more folders in your mailbox is named incorrectly. The name of one or more of your folders includes the character ...
One or more folders specified in folder scope for indexed search is not a mailbox folder. Indexed search is not supported ...
One or more items couldn't be attached because they exceeded the maximum size limit of {0} megabytes (MB) for attachments. ...
One or more messages have failed delivery due to DNS response 'non-existent domain'. This will occur if one of the DNS servers ...
One or more messages have failed delivery due to insufficient permissions on the remote server. If the remote server is in ...
One or more messages in the 'Messages awaiting directory lookup' queue on server {1} are addressed to database '{3}' on server ...
One or more messages in the 'Messages awaiting directory lookup' queue on server {1} are addressed to server {2}. Server ...
One or more messages in the 'Messages awaiting directory lookup' queue on server {1} are addressed to the mailbox store '{3}' ...