Exchange 2013 eventid Fail source routing

Mohamed Bahloul 1 Reputation point
2021-09-21T13:35:40.453+00:00

Hello,

i have Exchange 2013 with DAG implementation and forti-mail handling external domain , I'm facing an issue with some internal users to receive messages from external and internal domain the following :-

the single message failed to a single users between all users that are all internal .. source was routing.

second from monitoring mailboxes always failing, please advice to check and fix it

thanks in advance..

134004-rt.jpg

135450-133975-rt2.jpg

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,373 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Joyce Shen - MSFT 16,646 Reputation points
    2021-09-28T03:15:03.247+00:00

    Hi @Mohamed Bahloul

    According to my research, I found this article: Oct 13 "The SMTP availability of the Receive connector Default was low"
    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    Each mailbox database, there are health mailboxes which are used to send messages for the purpose of monitoring the availability of services and various customer touch points (CTPs) within Exchange. These health mailboxes used to stir up quite a bit of "noise" in the transport logs and journaling services. The System Probe Drop SMTP Agent debuted in CU9 as a way of delivering these monitoring messages bypassing the traditional transport queue. And whatever bypasses transport, bypasses logging and journaling which is great news in the case of these health mailboxes. Unfortuantely, this new SMTP agent does not drop these monitoring emails in a traditional manner, but instead, removes all email recipients. This method of dropping the email to avoid traditional transport queue has had an adverse effect. The emails still get passed down the pipeline (it's just a different Agent handling it), but now the relevant sender/recipient pairs are invalid. This results in the email delivery failing for all of these health mailbox "monitoring emails".

    Long story short - as long as you don't have valid messages with an EventID of FAIL, then this error is safe to ignore.

    Some similar issue discussed here:
    The SMTP availability of the Receive connector
    RecipientStatus Probe Message Accepted and dropped

    If an Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.