mail flow rule not work

liuwei@cesm 631 Reputation points
2020-12-02T07:05:54.257+00:00

HI, Expert,

I setu the rule when biger size message hit our mail server, the server will reject to give explanation to sender.

I test it not work.

Could you give advice what I lost?

Brgds
Liu Wei

44266-rs-mail-workflow-not-working.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,440 questions
{count} votes

Accepted answer
  1. Joyce Shen - MSFT 16,646 Reputation points
    2020-12-03T05:52:27.747+00:00

    Hi @liuwei@cesm

    What's your Exchange server and CU version?

    Please provide more information about your issue? Not work means you still receive messages size larger than 5MB or what else?

    Have you checked the rules you created befor which you may selected "Stop processing more rules"

    Select this check box to avoid applying additional rules after this rule processes a message. If the rule with higher priority worked with this option checked, this will lead to other rules not working.

    For more information: Procedures for mail flow rules in Exchange Server


    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 comments No comments

10 additional answers

Sort by: Most helpful
  1. liuwei@cesm 631 Reputation points
    2020-12-29T07:58:46.99+00:00

    HI, Andy,

    From the log. Exchange server did "not delivey'" only. It did not follow "send explanation to sender."

    Brgds
    Liu Wei


  2. liuwei@cesm 631 Reputation points
    2020-12-30T13:12:18.24+00:00

    HI, Andy,

    [PS] C:\Windows\system32>Get-RemoteDomain |FL NDREnabled

    NDREnabled : True

    Brgds
    Liu Wei


  3. liuwei@cesm 631 Reputation points
    2021-01-02T14:23:31.95+00:00

    Hello, Andy,

    Sure. There are two FAIL. I see same result, so I only post. Please the two FAIL recorded:


    ConnectorId :
    Source : ROUTING
    EventId : FAIL
    InternalMessageId : 26667451940871
    MessageId : <ME4P282MB1285DEBC76E5963E5396E0B3A6DD0@ME4P282MB1285.AUSP282.PROD.OUTLOOK.COM>
    NetworkMessageId : e33a3115-fa25-475c-2d25-08d8a8290619
    Recipients : {Internal email address}
    RecipientStatus : {[{LED=550 5.7.1 TRANSPORT.RULES.RejectMessage; the message was rejected by organization
    policy};{MSG=};{FQDN=};{IP=};{LRT=}]}
    TotalBytes : 14497
    RecipientCount : 1
    RelatedRecipientAddress :
    Reference :
    MessageSubject : TESTMYDOG
    Sender : XXXXXX@Karima ben .com
    ReturnPath : XXXXXX@Karima ben .com
    Directionality : Incoming
    TenantId :
    OriginalClientIp :
    MessageInfo :
    MessageLatency :
    MessageLatencyType : None
    EventData : {[ToEntity, Unknown], [FromEntity, Internet], [DeliveryPriority, Normal], [AccountForest,
    XXXX.YYYYY]}
    TransportTrafficType : Email
    SchemaVersion : 15.01.2044.006

    RunspaceId : 3c7f6196-9913-4da7-9460-9ca39f30bf39
    Timestamp : 12/25/2020 1:50:16 PM
    ClientIp :
    ClientHostname : 1036599090-HKEXG01YYYYYY
    ServerIp :
    ServerHostname :
    SourceContext : Transport Rule Agent
    ConnectorId :
    Source : AGENT
    EventId : FAIL
    InternalMessageId : 26723286515735
    MessageId : <ME4P282MB1285280ED0BEC1CA72609C46A6DC0@ME4P282MB1285.AUSP282.PROD.OUTLOOK.COM>
    NetworkMessageId : c1b3ba5c-2e95-4478-7f54-08d8a898f480
    Recipients : {Internal email address}
    RecipientStatus : {[{LED=550 5.7.1 TRANSPORT.RULES.RejectMessage; the message was rejected by organization
    policy};{MSG=};{FQDN=};{IP=};{LRT=}]}
    TotalBytes : 15479
    RecipientCount : 1
    RelatedRecipientAddress :
    Reference :
    MessageSubject : TESTMYDOG
    Sender : XXXXX@Karima ben .com
    ReturnPath : XXXXX@Karima ben .com
    Directionality : Incoming
    TenantId :
    OriginalClientIp :
    MessageInfo : 2020-12-25T05:50:15.594Z;SRV=1036600-HKEXG02.XXXX.YYYYY:TOTAL-FE=0.781|SMR=0.764(SMRPI=0.009(
    SMRPI-FrontendProxyAgent=0.009))|SMS=0.016;SRV=103659909-HKEXG0101.XXXX.YYYYY:TOTAL-HUB=0.316|SMR
    =0.262(SMRDE=0.157|SMRC=0.105(SMRCL=0.103|X-SMRCR=0.105))|CAT-PEN=0.052(CATOS=0.044(CATSM=0.0
    44(CATSM-Unified Group Post Sent Item Routing Agent=0.007|CATSM-Malware
    Agent=0.035))|CATRESL=0.006|CATORES-PEN=0.001(CATRS-PEN=0.001(CATRS-Transport Rule
    Agent-PEN=0.001)))
    MessageLatency :
    MessageLatencyType : None
    EventData : {[E2ELatency, 1.098], [DeliveryPriority, Normal], [AccountForest, XXXX.YYYYY]}
    TransportTrafficType : Email
    SchemaVersion : 15.01.2044.006

    RunspaceId : 3c7f6196-9913-4da7-9460-9ca39f30bf39
    Timestamp : 12/25/2020 1:50:16 PM
    ClientIp :
    ClientHostname : 1036599090-HKEXG01YYYYYY
    ServerIp :
    ServerHostname :
    SourceContext :
    ConnectorId :
    Source : ROUTING
    EventId : FAIL
    InternalMessageId : 26723286515735
    MessageId : <ME4P282MB1285280ED0BEC1CA72609C46A6DC0@ME4P282MB1285.AUSP282.PROD.OUTLOOK.COM>
    NetworkMessageId : c1b3ba5c-2e95-4478-7f54-08d8a898f480
    Recipients : {INternal email address}
    RecipientStatus : {[{LED=550 5.7.1 TRANSPORT.RULES.RejectMessage; the message was rejected by organization
    policy};{MSG=};{FQDN=};{IP=};{LRT=}]}
    TotalBytes : 15479
    RecipientCount : 1
    RelatedRecipientAddress :
    Reference :
    MessageSubject : TESTMYDOG
    Sender : XXXXXX@Karima ben .com
    ReturnPath : XXXXXX@Karima ben .com
    Directionality : Incoming
    TenantId :
    OriginalClientIp :
    MessageInfo :
    MessageLatency :
    MessageLatencyType : None
    EventData : {[ToEntity, Unknown], [FromEntity, Internet], [DeliveryPriority, Normal], [AccountForest,
    XXXX.YYYYY]}
    TransportTrafficType : Email
    SchemaVersion : 15.01.2044.006
    ++++++

    0 comments No comments

  4. liuwei@cesm 631 Reputation points
    2021-01-07T04:49:28.937+00:00

    Sorry, Andy,

    I ask the service provider to give the version. still waiting. From the EAC, I see it possibel on-prem Exchange Server in hybrid mode. But I am not sure.

    I will update the version informtion when get.

    Brgds
    Liu Wei

    0 comments No comments