Quantcast
Channel: Exchange Server 2013 - Mail Flow and Secure Messaging forum
Viewing all articles
Browse latest Browse all 2249

Transport rule blocking message - having trouble tracking down the issue

$
0
0

Hi all,

          Exchange 2013 single server environment.

There are a few transport rules in this environment, one of them blocks sending to an "all staff" DL by all but selected senders, including one external "mass-mail" type provider that is used for newsletters etc.

The external provider sends from different hosts, but they always have their company name in the sending domain name - due to this, I have added an exception of "The sender address includes <company name>"

This has been working for approx. 6 months - but recently started bouncing mails - and im struggling to work out why.

The message tracking log shows a sender which should match the criteria, the event data shows the action of reject message...

EventData               : {[AMA, SUM|v=0|action=|error=|atch=0], [AMA, EV|engine=M|v=0|sig=1.219.1551.0|name=|file=],
                          [TRA, ETR|ruleId=2d247558-5b44-40cf-8c7a-d33dbfc7b291|st=12/05/2016 7:49:09
                          AM|action=RejectMessage|action=Halt|sev=1|mode=Enforce], [CompCost, |AMA=0|ETR=0],

When I turn on pipelinetracing with

Get-TransportService | Set-TransportService -PipelineTracingSenderAddress <senderaddress as it appears in  message tracking>

Get-TransportService | Set-TransportService -PipelineTracingEnabled $true

send another test message

The directory that Get-TransportService | fl *pipeline* specifies doesn't even exist.

is there another way of troubleshooting this that I have missed? and any suggestions on why pipelinetracing doesn't seem to be working ?


Viewing all articles
Browse latest Browse all 2249

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>