Transport Rule for recipients

I need to setup the following transport rule, Exchange 2010, and I can't get it to work.
If recipient domain is xyz.com, and other recipient domains exist in the email, then I need to send a disclaimer xyz.com recipients as well as the other recipients at different domains such as abc.com. I can get the disclaimer only to append to emails
going to xyz.com and not going to abc.com
Thanks

Hi Mike,
According to your descripton, I found that we want to append disclaimer to recipients which in xyz.com domain, even if the To or Cc fields contain abc.com domain or additional domains' recipients. Right? If I have any misunderstanding, please
correct me.
I suggest create a Transport Rule. Steps as below:
1. EMC
2. Organizatio Configuration -> Hub Transport -> Transport Rules -> New Transport Rule...
3. Name: xyzDisclaimer
    Comment: Appending to disclaimer to xyz.com ONLY
    Select the "Enable Rule" checkbox
    Next
4. Select condition(s): when a recipient's address contains specific words
    Editing: when a recipient's address contains 'xyz.com'
5. Select actions: append disclaimer test and fallback to action if unalbe to apply.
    Editing: 'append' 'text' and fallback to 'wrap\ignore\reject' if unable to apply.
6. Next -> Next -> Finish
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Similar Messages

Create Transport rule for restrict message size and send a rejected message CC: to Administrator

I want to create a Exchange Transport rule for message size restriction (10 MB) when message size is exceed to 10 MB it rejected by the Exchange server and
also rejected message CC: to Administrator. I also create it but unable to configure rejected message CC: to Administrator. Thanks.
Babu

Hi Babu,
I have some tests in my environment using Exchange 2013, you can create a transport rule such as follows to achieve your goal.
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Exchange 2010 - Error setting a new transport rule for email disclaimer

Hi
Trying to setup some additional email disclaimer rules on Hub transport under Org Config on exchange 2010. We allready have a few and they work ok, however we are trying to replace this woth some alternate ones and are getting the error
The length of the property is too long. the maximum length is 8192 and the length of the value provided is 8522.
Most of this length comes from the html code we are inserting into the disclaimer. I've reduced it by about as much as i can but it's still too large. Does anybody have any suggestions or know if it;s possible to increase the 8192 sixze limit ?
Regards
Roger

Hi Roger,
For AD replication packet the ideal size is 8K. Or the above error may occur due to build/design issues.
You can eliminate this size related issue by splitting the large rule into multiple rules. This size limit is Per Rule and does not add up for all rules.

Transport Rules for manager

Hi
I would like to create a simple rule
when a user sends a message with the subject "Project Summary" I want his manager to be added to the CC.
the manager is set for all users of the organization
thanks
Tamir Levy

That was super fast! thanks!
one last thing
do you know what will happen if the user does not have manager defined?
Tamir Levy

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

Microsoft Exchange Transport Rule

Hi All,
This is my case :
My environment need transport rule requirement like this post solution,
https://social.technet.microsoft.com/forums/exchange/en-US/dcf74b3c-063f-42ed-bed2-37b6e882445b/transport-rule-for-automatic-reply-to-sender
But in my environment using Exchange 2010 SP3, there is no "send bounce message to sender with enhanced status code" option.
Can you tell me why this happen?
Is it another option to replace "send bounce message to sender with enhanced status code" in Exchange 2010 SP3?
Hope that you can help me.
Thanks for your attention.
Best Regards,
Henry Stefanus

Hi ,
Please use the option .
"Send rejection message to the sender with enhanced status code"
Please feel free to reply me if you have any queries.
Thanks & Regards S.Nithyanandham

Exchange transport rule to redirect to a different domain?

This is an odd question. Is there any way to use a Transport Rule to redirect a message from one domain to another? Like if you were to send to: [email protected] , I would like to redirect it to [email protected] That possible??

Hi,
As far as I know, there is no feature which can redirect all messages from one domain to another in Exchange 2010 at the same time.
However, we can build distribution group and add users, then apply transport rule for the distribution group.
Alternatively, maybe some script can help you. And you’re welcomed to confirm it on our script center forum:
http://social.technet.microsoft.com/Forums/scriptcenter/en-US/home?category=scripting
Thanks,
Angela Shi
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

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 MessageSizeOver for exchange 2010

Hi
I have an exchange 2010 SP3 RU 3 environment with edge transport server implemented. I want to Have Transport rules to limit message size going outside/coming inside on edge transport.
I recently found a solution with -messagesizeover switch for new-trasportrule command in exchange 2013. Unfortunately its unavailable in exchange 2010.
I am wondering if there is a workaround or update for exchange 2010 to add this functionality.
Thanks in advance
Farhad

Hi,
On Exchange 2010, there is no MessageSizeOver parameter when you create a transport rule. But you can limit the sending and receiving message size of the whole Exchange organization using the following cmdlet.
Set-TransportConfig -MaxReceiveSize xxx -MaxSendSize xxx
If you want to limit the sending and receiving messages size for a specific mailbox, you can use the cmdlet below.
Set-Mailbox xxx –MaxSendSize xxx –MaxReceiveSize xxx
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Transport Problem - for KEDR Derivation rule

We are trying to create derivation rule through transaction KEDR without any values. After creating derivation rule, it is creating workbench transport request eventhough K9RE* table is client dependent.
We have different transport routes/groups for customizing and workbench. SAP Layer is assinged to workbench transport group with one another Z* layer.
When we are trying to create request it is creating workbench transport request eventhough it is client dependent. It is using KEG0 package which is assinged to SAP layer.
Workbench transport are not going to all clients and we have to move request manually to other clients.
What should we do for changing this behaviour?
Thanks,
Miral.

With detailed explanation:
I thing previous post with was not detailed enough. Please see below.
We have created two different transport group for differentiating
customizing and workbench transport request.
ZECD layer is assigned to /CUST/ group where as ZWBK and SAP layer is
assinged to /WRKB/ group.
We are moving all client independent transports (assigned to /WRKB/
group) to only 1 client in other systems.
While creating derivation rule through transaction KEDR, it is not
allowing us to assing /CUST/ group eventhough config is client dependent.
It is using package KEG0 which is assinged to SAP layer and SAP layer isassinged to /WRKB/ group in our configuration.
The Derivation rule config is client dependent eventhough it is creatingworkbench request. We would like to know why it is creating workbench
request instead of customizing request.
Thanks,
Miral.

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

Setting a Transport Rule to reply with a Custom DSN for a Disabled User and disconnected mailbox

Here is what I am trying to accomplish. A user leaves the company. We disable there exchange email and that in turn disabled the account in AD. We want a custom NDR to say "This employee is no longer and employee blah blah" We dont get rid of email
boxes but we disable them.
Here is what I done. Created custom NDR and then created a transport rule to read if the message is sent to [email protected] reply back with this NDR code. It works fine if I disable the user from AD and not exchange. Once I "disconnect" the mailbox
it no longer works. I get the default NDR that says this email cant be found. I don't want that one. I want my custom NDR. I don't want to modify the 5.1.1 message either. Is there away around this?

Hi Nellyjo,
In your case, when you disable the user from AD and Exchange, in fact the message is blocked before reaching transport rule, recipient filtering is blocking this email. If you still want to achieve your goal by transport rule, you need to create a mailbox
or contact to make your transport rule work.
What's more, you also can modify original DSN for external and internal senders to meet your requirement.
For more information, here is a similar thread for your reference.
Setting a Transport Rule to reply with a Custom DSN for a Disabled User
http://social.technet.microsoft.com/Forums/en-US/b1a4dd86-1e0e-43a9-b340-a80352e5c323/setting-a-transport-rule-to-reply-with-a-custom-dsn-for-a-disabled-user?forum=exchange2010
Hope it helps.
If you need further assistance, please feel free to let me know.
Best regards,
Amy
Amy Wang
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

Transport Rule for recipients

Similar Messages

Maybe you are looking for