question

MohamedBahloul-7862 avatar image
0 Votes"
MohamedBahloul-7862 asked joyceshen-MSFT commented

Exchange 2013 eventid Fail source routing

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


office-exchange-server-mailflow
rt.jpg (36.8 KiB)
rt2.jpg (47.8 KiB)
133975-rt2.jpg (43.4 KiB)
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @MohamedBahloul-7862

I'm a bit confused about your description, do you mean only several messages(both internal and external) failed to send a specific user(s) in your organization? Please correct me if I have any misunderstanding about your question. Can the specific user successfully receive any messgaes directly sent to himself?

And the information you provided above is not complete, we are not able to get more information about why the mail is fail.
I would suggest to export the result running Get-MessageTrackingLog which will record all detailed information, for example:

 get-messagetrackinglog -EventID "FAIL" -Start "09/22/2021 09:00:00" -End "09/22/2021 17:00:00" | export-csv c:\result\fail.csv -notype

For the Health Mailbox, use the same method to get more information as well, we could also consider recreating the health mailboxes. Here is an article gives detailed information: Exchange 2013/2016 Monitoring Mailboxes


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.


0 Votes 0 ·

Hello @joyceshen-MSFT

Thanks you for your response,

yes I confirm , it happened some times between internal users and external to internal but randomly occurred many of them reason of delivery issue is Routing , I ran the required cmdlet

please check it here

https://drive.google.com/file/d/1y-4UBLqGJZ6nLsM0jW5QaHH76fuhE8ks/view?usp=sharing

thanks.

M Bahloul.

0 Votes 0 ·

Hi @MohamedBahloul-7862

Is there any update about your question?

0 Votes 0 ·

1 Answer

joyceshen-MSFT avatar image
0 Votes"
joyceshen-MSFT answered joyceshen-MSFT commented

Hi @MohamedBahloul-7862

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.


· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @MohamedBahloul-7862

Have you checked the information above? Any update so far?

0 Votes 0 ·