Transport rule to mark message as private?
I have been asked to mark all messages from a particular sender as private when they arrive in our system. This is so that the admin assistant who has access to the recipient's mailbox can't see them. Is this possible?
create a transport rule
1) from people <add user sending email address here>
action
Set header with value
Click header change to "Sensitivity"
Click value change to "Private"
I configured and tested messages before rule sent private and after rule not set private showed up as private.
Ah, well done Darren!. I learn something new everyday.
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.
Similar Messages
-
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 2013Making 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. -
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.
BabuHi 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 -
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 LingerfeltHi 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 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
FarhadHi,
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 rule with custom dsn
Hi
Our environment: Exchange Server 2013 CU6 - DAG
I created a custom dsn: New-systemMessage -dsnCode 5.7.15 -Internal $False -Language en -Text "Custom text"
Then I created a transport rule which reject mails to a test user with enhanced status code 5.7.15.
The Mail is rejected with the status code 5.7.15, but without the custom message. I configured it on Exchange 2010 and it worked. In the meantime we made a transition to Exchange 2013. I don't know how long it doesn't work, I just figured it out because
I had to configure another one and that one doesn't work as well.
Even if I configure a new transport rule which rejects mails to a test user with "Reject the message with the explanation", and as explanation I put in "Sorry" the mail gets rejected with status code 5.7.1 but no text,
Any suggestions?
Regards
PeterHi Amy
Thanks for answering.
I know the link, that was the first reference I contacted.
The dsn message is configured correctly, because it worked. By the way, the parameter -DSNCode doesn't exist with Get-SystemMessage, but only Get-SystemMessage lists all my the custom system messages.
I tried exactly the same in my lab with Exchange 2013 CU6 but no DAG, and I have the same issue.
I created the system message:
New-SystemMessage -DsnCode 5.7.15 -Language en -Text "This is a test." -Internal $true
I created a Transport rule to reject messages to a specified mailbox with enhanced Status code 5.7.15. About 20 minutes later I sent an email to this mailbox and the mail is rejected with the status code 5.7.15, but the text I created with this System message
is missing:
Delivery has failed to these recipients or groups:
[email protected] ([email protected])
Delivery not authorized, message refused
Diagnostic information for administrators:
Generating Server: srvex01.company.com
[email protected]
Remote Server returned '550 5.7.15 TRANSPORT.RULES.RejectMessage; the message was rejected by organization policy'
What am I doing wrong? I did it exactly according to the TechNet article, and I have the same problem on two different Exchange organizations.
Regards
Peter -
How can I make a rule to mark all messages sent to Mail Trash as Read?
How can I make a rule to mark all messages sent to Mail Trash as Read?
When I look at some emails on my phone, I can see from the title that I don't need to read the email so I delete it without opening it. When I go to my Macbook Pro and open mail, the number of unread messages in my Trash shows next to the name. It drives me nuts. Can I just set a rule to mark all messages sent to trash as read? If that isn't possible, I'd take just making the number not show beside the Trash folder.Just in the case that I actually do need to go back to them for some reason. I have some OCD tendencies which is also why the number beside the folder drives me nuts.
-
Is there any way to mark messages forwarded by a rule with that little "forwarded" arrow?
Normally, after forwarding an email, a little arrows appears next to the message reminding me that the message was forwarded. However, when I set up a rule to forward messages, those little "forwarded" arrows don't show up. Why is this?
Is there any way to automatically mark a message as forwarded?I have considered adding a flag as you suggested, but one of the things I really like about the "forwarded" arrow is that, when clicked, it shows me the forwarded message and to whom it was forwarded.
I've also noticed that the same rule, when I select "Apply Rule", does in fact mark those as forwarded with the arrow, but when I click those arrows, it can't find the message. And then, just like before, any new messages that I receive don't get marked. Just seems odd to me. Wish I didn't have to use the flag workaround. -
Rule to mark sent messages read
As some other people have noted in the forums, since I've upgraded to Leopard all my sent messages are getting marked as Unread for some reason I gave up trying to understand and/or fix.
So I was thinking of creating a rule to mark all sent messages as Read.
How could I accomplish that?don't know if this would work but you could try in mail>preferences>rules: "date sent" "is less than" and choose "1", then perform the following... "mark as read".
rules are applied to incoming messages so that new rule would not automatically apply to your sent mailbox. you would have to go to your sent mailbox once in a while, then select the emails you would like the rule to be applied to, then go to the menu message>apply rules.
if you have more than one rule and do not want other rules applied to these sent messages, then before applying the rule, you would have to go to mail>preferences>rules and mark as inactive the other rules, leaving only the above one as active.
a bit tedious workaround i admit and maybe other users may have a more elegant solution.
hope this helps -
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 2007Based 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. -
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 : UnchangedHi 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 -
I have a weird request I have never thought I would get. I have a VIP user that wants to receive no calendar invites / meeting invites from:
- anyone outside of our organization (ie: from the internet)
- only certain users from INSIDE our organization
Can I accomplish this either though a transport rule and/or an Outlook rule? I am on Exchange 2007 currently, and Outlook 2007 currently. Soon to have both on 2013 versions, migrating soon, but if possible, I need to implement this in our current environment.
Thanks in advanceHello,
Based on your description, I understand that the VIP user don't want to receive meeting requests from anyone outside of your organization and certain users from inside your organization. If so, we can't create transport rule in exchange 2007.
I recommend you upgrade your exchange server 2007 to exchange 2013. If you use exchange 2013, you can create this transport rule like : under condition, the sender is this person (distribution
group, you can add certain users from inside your organization to a distribution group) ; the recipient is this person (the VIP user);
the message properties include the message type(Calendaring); under actions, block the message reject the message and include an explanation/ reject the message with the enhanced status code of /delete the message without notifying anyone.
You need to create the second transport rule: you only need to change the first condition: the sender is located outside the organization, and other conditions and actions are the same as the first transport rule.
If you have any feedback on our support, please click
here
Cara Chen
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?
NLSHi 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 -
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
PaulHi 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 -
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 StefanusHi ,
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
Maybe you are looking for
-
All of the sudden everytime i open photoshop it says "adobe photoshop cc 2014 has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available." and it never says an
-
I have purchased actual ringtones from the ITunes store. They were working fine on my Iphone 3 before, but I got a new laptop and the new version of ITunes, and now even though they are listed as ring tones on my ITunes, they will not transfer to my
-
Mixing XDCAM and HDV?? Outputting to SD DVD...
Hi Earlier this year we shot a documentary on a Sony PDW-F350L HD XDCam (great camera, stunning footage - 35Mbps). Working in FCP has been fine. We're doing a follow up and budget and logistics dictate that we sadly can't use 350s again (where we're
-
hi all i tried to get oss2jack working to redirect the sound from TeamSpeak to the Jack Audio Server. But the installation failed, because of the fusd-kor package. could someone pls rebuild fusd-kor? http://aur.archlinux.org/packages.php?O - _Search=
-
Integration Web Service Support?
Does the new Integration 7.0 BPM have web service/SOAP support? In particular, I would like to start my workflow from a web service call, or be able to call web services directly from tasks in my workflow. Can this be done? Please advise, Dave