Mail Control - Transport Rule Predicate "RecipientAddressContainsWords"

"RecipientAddressContainsWords" uses a Words type predicate property. Below is the explanation of the usage and limitation of the Words type property:
The Words property accepts one string or an array of strings. It's used in all predicates that inspect different parts of a message for specific words or strings.
In Exchange 2010, only instances of the word without a prefix or suffix are matched. For example, if you specify the word "contoso", the rule will fire only if an exact match is found. The following variations where the word appears as a suffix,
a prefix, or between other characters (other than the space character) aren't considered an exact match:
Acontoso
Contosoa
Acontosob
The property isn't case-sensitive. The asterisk (*) is treated as a literal character, and not used as a wildcard character.
This makes me believe that you cannot block domains (or whitelist domains) by using domain.com in the array (or @domain.com), because it will never be an exact match. There will never be spaces on either side of the string.
Is this correct? Is there a better method (predicate) to block or whitelist domains?

Hi Cross,
According to my knowledge, you don’t have to worry about the words type.
For example, if you want to delete the messages from a domain, you could create a Transport Rule like this:
Conditions:
The sender address includes 'Contoso.com'
Actions:
Delete the message without notifying anyone
By the same token, you could create Transport Rules to block or whitelist domains.
There is a related article for your reference:
How to create a simple Whitelist-Blacklist with Exchange 2010 Transport rules (Exchange 2010)
http://plexhosted.com/billing/knowledgebase/229/How-to-create-a-simple-Whitelist-Blacklist-with-Exchange-2010-Transport-rules-Exchange-2010.html
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or
suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
If you have any further questions, please let me know.
Best regards,
Eric

Similar Messages

  • Moderation via Transport Rule and multiple Arbitration mailboxes

    Hello,
    when using moderation using a Transport Rule (Transport Rule Action "forward the message to addresses for moderation") it is possible to moderate messages sent to recipients outside the exchange organization (Transport
    Rule Predicate "Sent to Users Outside The Organization"). This all works perfect so far using a single arbitration mailbox.
    Now I would like to add additional arbitration mailboxes for load balancing purposes. As far as I understand, different arbitration mailboxes can configured on the recipients objects which are moderated using the set-<MailEnabledObject> -ArbitrationMailbox
    'XYZ'
    Now, for the described case above where the recipients are external (internet) and not available within the directory, is there a way to use multiple Arbitration mailboxes anyway and if yes, how ?
    Any feedback welcome. Thanks in advance

    Hi,
    Thank you for your post.
    This is a quick note to let you know that we are performing research on this issue.
    Niko Cheng
    TechNet Community Support

  • Transport rule doesn't work (trying to prepend a subject when mail comes to a second domain).

    This is an SBS2011 and accepts mail for two mail domains (successfully), but I am trying to phase out one of the two domains.
    I cannot find a better way to do it, but I have simply created this rule:
    priority 0
    when a recipient's address contains '@<olddomain>.gr'
    prepend message subject with '[GR!] '
    It doesn't do anything.
    It's not a matter of restarting services or waiting for some kind of replication. This rule is created (and is enabled yes) more than a month.
    Any ideas?
    EDIT: In Message Tracker, I find a test message has the following entry just after receiving from remote mail server:
    "The e-mail address for recipient "<myself>@<olddomain>.gr" was updated to the e-mail address "<myself>@M<newdomain>.com". The message is in the process of being delivered.
    ...then I have the successful delivery, without transport rule kicking in.
    So is the problem related to the recipient having BOTH email addresses set? Then why system replaces the old with the default? Probably this is why the rule doesn't kick (as it doesn't match any more).
    Is there a way to prevent this replacement, since I want the recipients to still get reached by the mail?
    NLS

    Hi NLS,
    I would like to verify if you apply the rule for your primary email address.
    You can try to use the following cmdlet to achieve your goal.
    New-TransportRule -Name 'New Rule' -Comments 'Comment' -HeaderContainsMessageHeader 'Received' -HeaderContainsWords 'olddomain.com'-FromAddressContainsWords
    '[email protected]' -PrependSubject "OLDDOMAIN"
    Hope it helps.
    If you need further assistance, please feel free to let me know.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • Custom DSN message nor custom rejection message is appearing when Transport Rule Blocks incoming e-mail.

    Good Afternoon,
          My Customer is running Exchange 2013 CU5 that has a transport rule that is supposed to reject any email from a particular user as that user is no longer with the company. The transport rule rejects the message, BUT, it does
    not show the Custom DSN. It shows the default message:
    Delivery has failed to these recipients or groups:
    [email protected] Your message wasn't delivered because the recipient's email provider rejected it.
    Diagnostic information for administrators:
    Generating server: EXMBX01.DOMAIN.LOCAL
    [email protected] Remote Server returned '< #5.7.169 smtp;550 5.7.169 TRANSPORT.RULES.RejectMessage; the message was rejected by organization policy>'
    I have looked up the transport rule in Exchange:
    Get-TransportRule "User Reject" | fl *Reject*,Description
    RejectMessageEnhancedStatusCode   : 5.7.169
    RejectMessageReasonText           : This E-MAIL Address is no longer in service. Please Contact
                                        [email protected] for assistance
    SmtpRejectMessageRejectText       :
    SmtpRejectMessageRejectStatusCode :
    Description                                  : If the message:
    Is sent to '[email protected]'
    and Is received from 'Outside the organization'
    Take the following actions:
    Set audit severity level to 'High'
    and reject the message and include the explanation 'This E-MAIL
    Address is no longer in service. Please Contact
    [email protected] for assistance' with the status code: '5.7.169'
    I tried setting up to separate external DSN messages and tried both with the same results:
    Get-SystemMessage | ft -a -wr
    Identity            Text
    en\External\5.7.69  This E-MAIL Address is no longer in service. Please Contact [email protected] for assistance.
    en\External\5.7.169 This E-MAIL Address is no longer in service. Please Contact [email protected] for assistance.
    I tried to change the SmtpRejectMessageRejectText on both Exchange servers and got the following error:
    Set-TransportRule -Identity "User Reject" -SMTPRejectMessageRejectText "This E-MAIL Addre
    ss is no longer in service. Please Contact [email protected] for assistance"
    A specified parameter isn't valid on a server with the Hub Transport role installed.
        + CategoryInfo          : InvalidArgument: (SmtpRejectMessageRejectText:String) [Set-TransportRule], ArgumentExcep
       tion
        + FullyQualifiedErrorId : [Server=EXMBX01,RequestId=b2a61aba-179b-4867-85b8-cc47eba62701,TimeStamp=6/27/2014
        7:19:32 PM] [FailureCategory=Cmdlet-ArgumentException] 8BBE1900,Microsoft.Exchange.MessagingPolicies.Rules.Tasks.
      SetTransportRule
        + PSComputerName        : exmbx01.domain.local
    I really am having issues finding and answer. Any assistance would be greatful!
    Thanks,
    Lance Lingerfelt

    Hi Lance,
    Thanks for your update.
    According to the error that you pasted, "A specified parameter isn't valid on a server with the Hub Transport role installed.", it seems you have no proper permission to use some specific parameters.
    Even if there are many parameters in the Technet article
    http://technet.microsoft.com/en-us/library/bb125138(v=exchg.150).aspx , you may not have access to some parameters if they're not included in the permissions assigned to you. You need Organization Management and Records Management permissions, see
    the following links:
    http://technet.microsoft.com/en-us/library/dd633492(v=exchg.150).aspx
    http://technet.microsoft.com/en-us/library/dd335087(v=exchg.150).aspx
    http://technet.microsoft.com/en-us/library/dd638205(v=exchg.150).aspx
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Mail transport rule to block email with recipients in 2 different domains

    Is it possible to set up a mail transport rule (Exchange 2007) to block or put on hold emails that are sent to recipients in more than one domain?
    Eg if the recipients /cc/bcc are 
    [email protected];[email protected] 
    then the email is held for approval before sending
    Can this be limited to only process from certain sending addresses?
    If it can't be done in 2007 can it be done in a later version or can it be done in a non microsoft product eg Postfix 
    This topic first appeared in the Spiceworks Community

    Hi,
    From your description, you want to prohibit retired users from sending emails to
    [email protected] If I have misunderstood your concern, please let me know.
    In your case, these retired users are hosted on Exchange Online, this is Exchange 2013 forum. I would like to tell you how to achieve it on Exchange 2013.
    I recommend you verify it on Office 365 forum. For your convenience:
    https://community.office365.com/en-us/f/158.aspx
    What's more, I would like to clarify the following thing:
    If you prohibit A from sending email to B, B send an email to A and C, when A reply all this email, C still can receive this email, only A can't receive it.
    Hope my clarification is helpful.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • Transport rules work partially(for 1 of 2 mail addresses)

    I have an exchange 2010 setup.
    I want to catch all mails that are send from 1 specific address and send a copy to 2 mailboxes.
    First I tried to create the rule,but it didn't work.
    Next,
    I have created a transport rule, added 2 mail addresses(primary and secondary) for from( people) and forward the mail to a specific mailbox.
    When I send an e-mail from my secondary address the rule works(yeah), when the e-mails from the primary are received, the rule does work(d'oh).
    When I added the rules, I restarted the transport role to be sure everything is loaded.
    I already enabled pipelinetracing for the primary e-mail address, but can't get any wiser of it.
    some debug output
    [PS] C:\Windows\system32>Get-TransportAgent
    Identity                                          
    Enabled         Priority
    Transport Rule Agent                               True           
    1
    ScanMail SMTP Receive Agent                        False           2
    ScanMail Routing Agent                             False          
    3
    Text Messaging Routing Agent                       True            4
    Text Messaging Delivery Agent                      True            5
    [PS] C:\Windows\system32>Get-TransportPipeline
    Event                                             
    TransportAgents
    OnConnectEvent                                     {}
    OnHeloCommand                                      {}
    OnEhloCommand                                      {}
    OnAuthCommand                                      {}
    OnEndOfAuthentication                              {}
    OnMailCommand                                      {}
    OnRcptCommand                                      {}
    OnDataCommand                                      {}
    OnEndOfHeaders                                     {}
    OnEndOfData                                        {}
    OnHelpCommand                                      {}
    OnNoopCommand                                      {}
    OnReject                                          
    OnRsetCommand                                      {}
    OnDisconnectEvent                                  {}
    OnSubmittedMessage                                 {Text Messaging Routing Agent}
    OnResolvedMessage                                  {}
    OnRoutedMessage                                    {Transport Rule Agent}
    OnCategorizedMessage                               {}
    Hope I can get a solution for this.

    Hi Yelti,
    Thank you for your post.
    There are two sentences confused us, we want to confirm
     your requirement in order to give better solution.
    1. I want to catch all mails that are send from 1 specific address and send a copy to 2 mailboxes.
    2. I have created a transport rule, added 2 mail addresses(primary and secondary) for from( people) and forward the mail to a specific mailbox.
    Waiting your reply.
    Best regard,
    Jim

  • Creation of transport rule to send all external mails through a particular server for a specific user..

    HI,
    In our Organisation We have a question, is there any possibility to create a transport rule for sending all external mails through a particular server by a specific user.
    in our organisation we have exchange 2007 one mailbox server and two hub transport servers...and we are using symantic gate way..

    Hi,
    Based on my knowledge, we can use the following transport rule to make that except with one user, other users cannot send outbound external emails:
    And I’m afraid that there is no Exchange feature to make one specific HUB server rout all external emails.
    Because if a Send connector is configured to send messages to an external domain, any Hub Transport server in the organization will route a message for that domain to a source server for that connector to be relayed to the destination domain.
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Transport Rule - Mail Tip Per Domain

    I need to setup a transport rule to do the following:
    If mail sent from a group of users, lets call it Group1
    Apply a policy tip that blocks the message and allows override
    Except if the message is sent to a member of Group1.
    Sounds simple, right? But, I can't find a rule setup that gives me what I need.
    Any help would be appreciated!!

    Hi,
    From your description, I recommend you create the following transport rule to achieve your goal.
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Using Mail Transport Rules and the Exchange AWS API

    I am looking to programmatically Enable and Disable hub transport rules from VS.NET and was hoping these functions would be available via the REST API. However, I can't find any references, which indicates that perhaps they don't exist. 
    The rules I want to access can be used from PowerShell "Enable-TransportRule" and "Disable-TransportRule" and I can use them fine from Powershell.
    So, my first question is, are these rules available from the Exchange EWS API? They need to be triggered when users perform certain events within the application.
    If not, I am guessing I will be able to automate these cmdlets into a C# application or ASP.NET/C# application. Is this a correct assumption?
    Thanks.
    Jonathan.

    No you can't set Transport rules from EWS, EWS is a mailbox access API and setting Transport Rule would be considered an Administrative Task so you need to use and Admin API which for Exchange is still the Exchange Management Shell. You can automate
    the EMS cmdlet with Managed code (eg you could front end them with your own rest service) using Remote Powershell the best place to start would be
    http://msdn.microsoft.com/en-us/library/office/jj943721(v=exchg.150).aspx
    Cheers
    Glen

  • Inconsistent Results from Transport Rule to reset SCL

    I have a client who has multiple sites. Their exchange server receives "scan to email" emails from a Canon C2020 Digital Multifunction on a different site. To stop the Exchange 2013 Spam filter blocking the emails, I set up a Transport Rule.
    The rule has the following properties
    If the Sender Address matches [email protected]
    Set the SCL to 3
    Generate an incident report and email to the system admin, and inlcude the original email
    Is the 3rd of 3 rules (the prior 2 add Disclaimers to outgoing emails depending on who the sender is)
    Simple enough right.
    Wrong - some staff scan to email repeatedly and the scan arrives ok in their inbox.  Others, it simply will not let the email thru, and instead places the email into the Spam Mailbox.  I open the blocked email, click on Send Again and
    it arrives for the user.
    Is the Transport Rule functionality buggy or prone to odd behaviour.  I have sat and read through the Rule so many times it is tattooed onto my retina.
    The Email addresses for all users are created by an Email address policy so all are a consistent format = Firstname + Surname 1st Initial@contoso .com.
    There have been times where I have wondered if the rules are case sensitive when assessing the email addresses.
    Any thoughts to put me out of my misery, please show me where I have done wrong....
    Get-TransportRule returns
    [PS] C:\Windows\system32>Get-TransportRule "[Cust-sos-IN] Reset SCL on Scanner emails" | Format-List
    RunspaceId                                   : 7f9c4f6e-7d35-409e-acf9-cbb272720b8c
    Priority                                     : 2
    DlpPolicy                                    :
    DlpPolicyId                                  : 00000000-0000-0000-0000-000000000000
    Comments                                     :
    ManuallyModified                             : False
    ActivationDate                               :
    ExpiryDate                                   :
    Description                                  : If the message:
    Is sent to '[email protected]' or
    '[email protected]' or
    '[email protected]' or
    '[email protected]' or
    '[email protected]' or
    '[email protected]' or
    '[email protected]'or...
    and Includes these patterns in the From address:
    '[email protected]'
    Take the following actions:
    Set the spam confidence level (SCL) to '3'
    and Send the incident report to [email protected], Include
    original mail
    RuleVersion                                  : 15.0.2.0
    Conditions                                   : {SentTo, FromAddressMatches}
    Exceptions                                   :
    Actions                                      : {SetSCL, GenerateIncidentReport}
    State                                        : Enabled
    Mode                                         : Enforce
    RuleSubType                                  : None
    UseLegacyRegex                               : False
    From                                         :
    FromMemberOf                                 :
    FromScope                                    :
    SentTo                                       :
    {[email protected],
    [email protected],
    [email protected],
    [email protected],
    [email protected],
    [email protected],
    [email protected],
    [email protected], [email protected],
    [email protected],
    [email protected], [email protected],
    [email protected],
    [email protected], [email protected],
    [email protected]...}
    SentToMemberOf                               :
    SentToScope                                  :
    BetweenMemberOf1                             :
    BetweenMemberOf2                             :
    ManagerAddresses                             :
    ManagerForEvaluatedUser                      :
    SenderManagementRelationship                 :
    ADComparisonAttribute                        :
    ADComparisonOperator                         :
    SenderADAttributeContainsWords               :
    SenderADAttributeMatchesPatterns             :
    RecipientADAttributeContainsWords            :
    RecipientADAttributeMatchesPatterns          :
    AnyOfToHeader                                :
    AnyOfToHeaderMemberOf                        :
    AnyOfCcHeader                                :
    AnyOfCcHeaderMemberOf                        :
    AnyOfToCcHeader                              :
    AnyOfToCcHeaderMemberOf                      :
    HasClassification                            :
    HasNoClassification                          : False
    SubjectContainsWords                         :
    SubjectOrBodyContainsWords                   :
    HeaderContainsMessageHeader                  :
    HeaderContainsWords                          :
    FromAddressContainsWords                     :
    SubjectMatchesPatterns                       :
    SubjectOrBodyMatchesPatterns                 :
    HeaderMatchesMessageHeader                   :
    HeaderMatchesPatterns                        :
    FromAddressMatchesPatterns                   :
    {[email protected]}
    AttachmentNameMatchesPatterns                :
    AttachmentExtensionMatchesWords              :
    HasSenderOverride                            : False
    MessageContainsDataClassifications           :
    SenderIpRanges                               :
    SCLOver                                      :
    AttachmentSizeOver                           :
    MessageSizeOver                              :
    WithImportance                               :
    MessageTypeMatches                           :
    RecipientAddressContainsWords                :
    RecipientAddressMatchesPatterns              :
    SenderInRecipientList                        :
    RecipientInSenderList                        :
    AttachmentContainsWords                      :
    AttachmentMatchesPatterns                    :
    AttachmentIsUnsupported                      : False
    AttachmentProcessingLimitExceeded            : False
    AttachmentHasExecutableContent               : False
    AnyOfRecipientAddressContainsWords           :
    AnyOfRecipientAddressMatchesPatterns         :
    ExceptIfFrom                                 :
    ExceptIfFromMemberOf                         :
    ExceptIfFromScope                            :
    ExceptIfSentTo                               :
    ExceptIfSentToMemberOf                       :
    ExceptIfSentToScope                          :
    ExceptIfBetweenMemberOf1                     :
    ExceptIfBetweenMemberOf2                     :
    ExceptIfManagerAddresses                     :
    ExceptIfManagerForEvaluatedUser              :
    ExceptIfSenderManagementRelationship         :
    ExceptIfADComparisonAttribute                :
    ExceptIfADComparisonOperator                 :
    ExceptIfSenderADAttributeContainsWords       :
    ExceptIfSenderADAttributeMatchesPatterns     :
    ExceptIfRecipientADAttributeContainsWords    :
    ExceptIfRecipientADAttributeMatchesPatterns  :
    ExceptIfAnyOfToHeader                        :
    ExceptIfAnyOfToHeaderMemberOf                :
    ExceptIfAnyOfCcHeader                        :
    ExceptIfAnyOfCcHeaderMemberOf                :
    ExceptIfAnyOfToCcHeader                      :
    ExceptIfAnyOfToCcHeaderMemberOf              :
    ExceptIfHasClassification                    :
    ExceptIfHasNoClassification                  : False
    ExceptIfSubjectContainsWords                 :
    ExceptIfSubjectOrBodyContainsWords           :
    ExceptIfHeaderContainsMessageHeader          :
    ExceptIfHeaderContainsWords                  :
    ExceptIfFromAddressContainsWords             :
    ExceptIfSubjectMatchesPatterns               :
    ExceptIfSubjectOrBodyMatchesPatterns         :
    ExceptIfHeaderMatchesMessageHeader           :
    ExceptIfHeaderMatchesPatterns                :
    ExceptIfFromAddressMatchesPatterns           :
    ExceptIfAttachmentNameMatchesPatterns        :
    ExceptIfAttachmentExtensionMatchesWords      :
    ExceptIfSCLOver                              :
    ExceptIfAttachmentSizeOver                   :
    ExceptIfMessageSizeOver                      :
    ExceptIfWithImportance                       :
    ExceptIfMessageTypeMatches                   :
    ExceptIfRecipientAddressContainsWords        :
    ExceptIfRecipientAddressMatchesPatterns      :
    ExceptIfSenderInRecipientList                :
    ExceptIfRecipientInSenderList                :
    ExceptIfAttachmentContainsWords              :
    ExceptIfAttachmentMatchesPatterns            :
    ExceptIfAttachmentIsUnsupported              : False
    ExceptIfAttachmentProcessingLimitExceeded    : False
    ExceptIfAttachmentHasExecutableContent       : False
    ExceptIfAnyOfRecipientAddressContainsWords   :
    ExceptIfAnyOfRecipientAddressMatchesPatterns :
    ExceptIfHasSenderOverride                    : False
    ExceptIfMessageContainsDataClassifications   :
    ExceptIfSenderIpRanges                       :
    PrependSubject                               :
    SetAuditSeverity                             :
    ApplyClassification                          :
    ApplyHtmlDisclaimerLocation                  :
    ApplyHtmlDisclaimerText                      :
    ApplyHtmlDisclaimerFallbackAction            :
    ApplyRightsProtectionTemplate                :
    SetSCL                                       : 3
    SetHeaderName                                :
    SetHeaderValue                               :
    RemoveHeader                                 :
    AddToRecipients                              :
    CopyTo                                       :
    BlindCopyTo                                  :
    AddManagerAsRecipientType                    :
    ModerateMessageByUser                        :
    ModerateMessageByManager                     : False
    RedirectMessageTo                            :
    RejectMessageEnhancedStatusCode              :
    RejectMessageReasonText                      :
    DeleteMessage                                : False
    Disconnect                                   : False
    Quarantine                                   : False
    SmtpRejectMessageRejectText                  :
    SmtpRejectMessageRejectStatusCode            :
    LogEventText                                 :
    StopRuleProcessing                           : False
    SenderNotificationType                       :
    GenerateIncidentReport                       :
    [email protected]
    IncidentReportOriginalMail                   : IncludeOriginalMail
    RouteMessageOutboundConnector                :
    RouteMessageOutboundRequireTls               : False
    Identity                                     : [Cust-sos-IN] Reset SCL on Scanner
    emails
    DistinguishedName                            : CN=[Cust-sos-IN] Reset SCL on Scanner
    emails,CN=TransportVersioned,CN=Rules,CN=Transport
    Settings,CN=Contoso,CN=Microsoft
    Exchange,CN=Services,CN=Configuration,DC=CONTOSO,DC=LOCAL
    Guid                                         : 5d1dbc9b-3718-4874-9552-296e8b98d874
    ImmutableId                                  : 5d1dbc9b-3718-4874-9552-296e8b98d874
    OrganizationId                               :
    Name                                         : [Cust-sos-IN]
    Reset SCL on Scanner emails
    IsValid                                      : True
    WhenChanged                                  : 17/03/2015 2:37:06 PM
    ExchangeVersion                              : 0.1 (8.0.535.0)
    ObjectState                                  : Unchanged

    Hi MBKITMGR,
    Agree with Zammit, you should use the BypassedSenders parameter to specifies the SMTP address values of senders.
    After that, the Content Filter agent doesn't process any content filtering for messages received from the addresses listed on this parameter.
    Best regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Niko Cheng
    TechNet Community Support

  • Where to check/enable for log keeping track of transport rule actions?

    I have implemented some transport rules to "journal" all emails from specific clients as per this
    thread. 
    So there are 4 transport rules to capture all those email:
    1. email from Clients (incoming / FROM)
    1.1 from users outside the organization.
    1.2 sent to member of AD Group
    1.3 sent to users inside the organization.
    1.4 where the from address contains "domain of our clients list"
    1.5 BBC to capture mailbox
    2. email to Clients (outgoing/ TO)
    2.1 from member of AD Group
    2.2 from users inside the org
    2.3 sent to users outside the organization.
    2.4 where the to address contains "domain of our clients list"
    2.5 BBC to capture mailbox
    3. email to Clients (outgoing/ CC)
    3.1 from member of AD Group
    3.2 from users inside the org
    3.3 sent to users outside the organization.
    3.4 where the cc address contains "domain of our clients list"
    3.5 BBC to capture mailbox
    4. email to Clients (outgoing/ BCC)
    4.1 from member of AD Group
    4.2 from users inside the org
    4.3 sent to users outside the organization.
    4.4 where the bcc address contains "domain of our clients list"
    4.5 BBC to capture mailbox
    The symptoms are that while I am seeing by selecting random emails that everything seem to run fine (rule filtering from transport does get incoming and outgoing messages to that “capture” mailbox) and I tested this fine with some test emails
    in different domains.
    Somehow I am no getting the results I want. With business sending some test sets I should be finding in that mailbox, I do not find everything. Some of the email that apparently would logically be captured are not. Is business lying about the test sets they
    send? I don’t think so and the fact is that I seem to be missing emails.
    Anyhow my questions to you are the following:
    1.    Do you know of any logging done by the transport server to check on matches of the filters?
    2.    I am using outside and inside condition in the rules. Are they what I think they are?
    I hope you can help. I think I am doing this right, but I cannot verify the process 100%. Some logs or additional information would help. Or perhaps I am not using the conditions properly.
    Thank you in advance.
    and BTW the environment is Exchange 2007

    Based on my research, there is no specific log to match the filters. During the mail flow, only SMTP log and Message Tracking log can record the message information.
    You can check the two logs if needed. For more information, please refer to the following steps.
    Enable Message tracking log
    1. Open the Exchange Management Console. 
    2. In the console tree, expand Server Configuration, and select Hub Transport.
    3. In the action pane, click the Properties link that is directly under the server name.
    4. In the Properties page, click the Log Settings tab.
    5. In the Message tracking log section, Select Enable message tracking log to enable message tracking.
    6. Click Apply to save changes and remain in the Properties page, or click OK to save changes and exit the Properties page.
    Enable SMTP Log
    1. In the console tree, expand Organization Configuration, and select Hub Transport.
    2. In the action pane, click on Sender Connectors and right click on send connector and then click on properties.
    3. Select “Verbose” under “Protocol logging level” and then click ok.
    Then, you can find the logs from the following location.
    Collect Message Tracking Log
    On the Exchange server, go to directory “c:\program files\Microsoft\exchange server\TransportRoles\Logs\Message Tracking”
    Collect SMTP log
    Open the folder on the Hub Server,: C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpSend.
    Thanks.
    Novak
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Transport Rule does not appear to be working

    hi,
    I have an exchange 2013 environment.  i have a requirement to intercept inbound emails from external senders addressed to [email protected] and forward it to a single recipient.
    we have an internal distribution list already using [email protected] that has 30 members. 
    I have setup the following rule
    apply this rule if: the recipient is [email protected]  and the sender is:outside of the organization
    Do the following:redirect the message to [email protected]
    Priority 0
    Audit : not specified
    mode: enforce
    when i send a test email from externally all 30 people still recieve the mail.   i have tried restarting the transport service.  Can anyone please help me as i am struggling to see what might be wrong.
    thanks
    Paul

    Hi paul ,
    From your description i came to understand that the E-mails from the external senders addressed to the distribution group [email protected] should have to be redirected to [email protected]
    As per my knowledge ,There are two ways to achieve your scenario one is via transport rule and another one is via DL restriction .
    via transport rule
    1.If you wanted to check  whether the transport rule is applied to that message or not you should have to do the message tracking first .
    2.Then you have to enable the pipeline tracing log for the particular recipient in our exchange organisation . With the help of  that logs you can able to identify what are all the transport rules has applied to the messages received by the that recipient
    Note: Pipeline tracing is only for troubleshooting purpose , once you have completed your troubleshooting please turn it off .
    Via DL restriction :
    On that particular DL If you go to the option delivery management you can able to set the restrictions .
    only senders inside my organization - This is the option where you can restrict who can able send an email to this DL and it would be some of the internal recipients or all the internal recipients .
    Senders inside and outside of my organization - This is the option where you can restrict who can able send an email to this DL and it would be some of the internal recipients or all the internal recipients or some of the external recipients
    or all the external recipients .
    you should have to create a contact in case if you wanted to provide mail sending permission to this DL only for some external recipients 
    Please reply me if you have any queries .
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

  • Exchange transport rule so a message classification

    I can create the RMS template in the RMS management utility on the RMS server, put the templates in a shared location and enable RMS by specifying a template location in a Group Policy.
                   The result is that
    users will see the message classifications in Outlook
    … but when I try to create a transport rule based on the template, the templates are not available in ECP in the dropdown for message classification (the ones you see in the example below are there b/c I added them via Exchange
    powershell.
    The other way to add message classifications is to create them in PowerShell on the mail server.  When created this way the Message classifications show up when creating a new rule (as seen above) but
    the end users don’t see them in Outlook. 
    One source says to make a registry change on the user’s computers:
    Next, copy the XML file to a location on the client or networked location which is readable by Users. On the client, make the
    following registry changes:
    [HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\Policy]
    "AdminClassificationPath"="c:\\Classifications.xml"
    "EnableClassifications"=dword:00000001
    "TrustClassifications"=dword:00000001
    After trying both a network share and a local file, the Classifications still don’t show up in Outlook.
    So the only way to get them to show up in Outlook doesn’t allow you to include them in a transport rule (and thus you’re not able to create a rule that allows forwarding inside the domain only)
    and the way to get them to show up when creating a transport rule doesn’t seem to work as far as getting them to show in Outlook.
    Adding them via PowerShell on the Exchange server actually does get them to show up in OWA the way you would expect, they just won't show in Outlook 2010. 
    I imagine the issue is with the reg entry that points Outlook to the xml
    file….(and I do realize reference given is Offfice 2013)  it’s entirely
    possible that Office 2010 requires a new key in a slightly different place but
    im only seeing references to office 2007 and 2013

    Making message classification visible in Outlook 2010
    On the CAS: New-MessageClassification -Name "Internal Use Only" –DisplayName “Internal Use Email” -RecipientDescription "Internal Only, Don’t forward outside Kdm"
    -SenderDescription "tells recipient not to forward outside company”
    From Program Files\Microsoft\Exchange Server\V14\Scripts  
    - Run .\Export-OutlookClassification.ps1 > c:\Temp\Classifications.XML
    Copy the .XML file to the test client in root of C: (tried other locs also)
    Create new reg key (office 2010)
    [HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\Policy]
    "AdminClassificationPath"="C:\Classifications.xml"
    "EnableClassifications"=dword:00000001
    "TrustClassifications"=dword:00000001
    Reboot client
    Should be able to see the message classification when creating a new email. 
    Why can I see this in my test lab using Outlook 2013 and also see it within OWA but I cannot see the classification within Outlook 2010 (which all my users have)? 
    Have tried on two laptops.  One with MS Office prof. and the other with prof. plus. 
    I am local admin on both.

  • Transport Rule and Journaling rule query

    HI I am using Exchange 2010
    i am using transport rule and journaling agent in my setup.
    i would like to know when both agents applied to an user which agent applied first transport or journaling?
    Ex:
    On server, I have created n Transport Rule policy for an user to to move all incoming mails deleted items for the same user i have created journaling policy to move all incoming mails journaled.
    which one will get apply?
    Thanks

    Hi  chandru CT
    Thank you for your question
    The transport rule will be applied firstly.
    The difference between transport rule and journaling role is that transport rule make the original mail BCC to someone by mail. But  Journaling role make the original mail send to someone by attachment .
    Jim xu

  • Powershell script to add multiple domains to a transport rule

    I have a transport rule in Exchange 2013 that I created in the EAC (mail flow>rules).  it is set so *Apply this rule if.. the sender's domain is..  and then I entered a few domains.
    I want to use a powershell script to enter multiple domains into the senderdomainis parameter using the set-transportrule.  I would like to do this from a csv input file.  The file has  header row of domains and then the domains are listed
    under it.  This is also used successfully in a script that does content and sender id filter additions.
    I tried the following:
    $allowed = import-csv c:\temp\allowed.csv
    $Rule=get-transportrule "safe domain List"
    $Senderdomains =$rule.senderdomainis
    foreach($row in $allowed)
    $Senderdomains +=$row.domain
    #Set-Transportrule "Safe Domain List" -senderdomainis $Senderdomains
    It just adds a long line of all the domains mashed together without separation.
    Any ideas would be helpful.
    Thanks.

    This isn't the most elegant solution, but I was able to accomplish it with this script:
    $allowed = import-csv c:\temp\allowed.csv
    $domains=Get-TransportRule "Safe Domain List" | select -ExpandProperty senderdomainis
    foreach ($a in $allowed)
    $domains += $a.domain
    $domainstoadd = $domains | select -Unique
    Set-TransportRule "Safe Domain List" -SenderDomainIs $domainstoadd
    It's key to note that the column in the CSV file has a heading of "Domain". Basically the script pulls the existing array into a variable so you can add values from the CSV to the array. This creates duplicates,
    so the "Select -Unique" is a quick and easy way to eliminate the duplicates.

Maybe you are looking for