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.

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 2013 - The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the configured threshold

    Noticed at about noon that no emails had been received all day. Began to investigate and found that the MS Exchange Transport service had been set to deny email submission because it was using too much memory on the server (91%). 
    The error message makes me think that we may have been getting used by malware or something similar.“The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the
    configured threshold.” 
    There are also several warning messages that list particular IP addresses and say that a connection from that IP was denied because there were already the maximum number of connections (20). 
    From what I can tell, all of the IP addresses are from Taiwan. 
    The time period for which some emails may be missing is from close of business yesterday ( 4/3/2014) through about 12:45 today (4/4/2014). 
    From the time I spent reading and trying to figure out the error, I think we may need to readjust our throttling policies to prevent this from happening. 
    The exchange server is currently running at 90%+ CPU and 50%+ memory usage the majority of the time, and I’m not sure how to fix it.
    Also, I cannot get into EMS I get a access denied message from the destination computer. (Exchange server) I want to get into there to change the throttling policy back to default, since we disabled it.
    The Error reads:
    The WinRM client cannot process the request. The WinRM client tried to use Kerberos authentication mechanism, but the destination computer <Exchange> returned an 'access denied' error. Change the configuration to allow Kerberos authentication
    mechanism to be used or specify one of the authentication mechanism supported by the server. (How do I do this?) To use Kerberos, specify the local computer name as the remote destination. (I'm trying to use EMS while logged into the local Exchange server)
    Also verify that the client computer and the destination computer are joined to a domain. (Exchange is on our domain, and the computer trying to connect is the same computer) To use basic, specify the local computer name as the remote destination, specify
    Basic authentication and provide user mane and password. Possible authentication mechanisms reported by server.
    At line:1 char:1
    + New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed
    I assumed control of this exchange system already in place and I do not have much experience with exchange 2013 or server 2012. I do know 2008, but that doesn't help very much in this situation.
    Recent changes to the system:
    About three days ago we switch our sessions policy to allow many more connections, and I believe this caused the issue. This is what I changed it to:
    Made the registry DWORD (32-bit) "Maximum Allowed Sessions Per User" and modified the value to 1000. Location of registry change @ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
    I just changed it to 10 from the 1000. I'm hoping this solves this. So far no.
    Also, I am not the best in the shell or command line interfaces. Any help would be wonderful!

    Hi,
    Yes, could be hardware performance issue. Try recycle the Transport process and see if the issue persists.
    Thanks,
    Simon Wu
    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

  • 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.

  • 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 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 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
    Peter

    Hi 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

  • Exchange 2010 BCC Transport Rule skipped- Logging required

    Hi,
    we have some transport rules created on Exchange 2010 SP2 U4 that for each message sent to a specific mailbox the message is bcc'ed to some internal users. The rules work all fine, but we have a case were in some occasions a transport rule is not getting
    applied and the message is not delivered to the bcc users but only to the initial recipient mailbox. The transport rule in question has Priority "0" and we have no conflicting trasnport rules
    Message tracking log is not so helpful since it just shows that the message delivered successfully, whereas in the case that the rule is being applied message tracking shows the message being deferred to the other recipients as well.
    Unfortunately we were not able to reproduce the issue since it occurs in an ad-hoc basis therefore enabling pipeline tracing  will not be of much help.
    Please advise, what logging shall we enable on what level to be able to identify the cause and the location of the logs generated in each case (Event Viewer or C:\Program Files\Microsoft\Exchange Server\V14\Logging or C:\Program Files\Microsoft\Exchange
    Server\V14\TransportRoles\Logs).
    Thank you very much in advance.

    Hi,
    If you want to ensure that the transport agent is doing its job within a message, we can enable
    Pipeline tracing feature which allows us to create an exact snapshot of a whole message before and after it encounters each transport agent. Each step of the process is kept in a directory for troubleshooting reasons.
    Before you enable pipeline tracing, you need to specify the sender's email address you want to monitor. Pipeline tracing is designed to log messages sent from a specific email address. Then we can use the following command to enable it:
    Set-TransportServer Server1 -PipelineTracingEnabled $True -PipelineTracingSenderAddress "<>" -PipelineTracingPath <LocalFilePath>
    For more information about pipeline tracing, please refer to:
    http://technet.microsoft.com/en-us/library/bb125018(v=exchg.141).aspx
    Understanding Transport Agents (Part 2)
    http://www.msexchange.org/articles-tutorials/exchange-server-2007/planning-architecture/understanding-transport-agents-part2.html
    Hope it helps.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2010 HTML Signature via Transport Rule

    We had a request to create a custom signature for our organization. I have this working via a transport rule in Exchange 2010. It works great for messages coming from a client such as Outlook or OWA.. but when a message originates from an Iphone or Android Device it does not work.
    Is it possible to make the iPhone send its email as HTML by default? Or has anyone ran into this and found a solution.
    Thanks

    I can't find a clean answer for you.
    You might use the Set-TransportRule cmdlet and one of the exception clauses to look for something in the header.  I looked at an ActiveSync-generated header from my Droid (I don't have an iPhone to try this out on) and I see this:
    Message-ID: [email protected]
    The clause:
    -ExceptIfHeaderMatchesPatterns "Message-ID:\s(\S|\s)*email.android.com"
    should exclude messages sent from Droids.  Of course, I can't say that it'll exclude all of them so you'll have to experiment and use trial and error.
    http://technet.microsoft.com/en-us/library/bb123534(v=exchg.150).aspx
    http://technet.microsoft.com/en-us/library/aa997187(v=exchg.141).aspx
    You may need to experiment with the rule because I haven't tested it.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2013 Transport Rules and Exchange 2007 Decommissioning

    Hello,
    I recently migrated from Exchange 2010 to Exchange 2013, I do have a few traces of Exchange 2007 in the Active Directory that I would like to completely remove. The Exchange 2007 server failed earlier and wasn't decommissioned properly. I read a few articles
    on how to completely remove it from AD, I am still concerned to make the changes in "ADSI Edit". 
    Here is the error message I receive when creating transport rules in Exchange 2013:
    "You are about to create a rule in an organization where Hub Transport servers running Exchange Server 2007
    exist. To ensure the rule is applied consistently across all Hub Transport servers in the organization, you must create an equivalent rule from the Exchange Management Console on an Exchange 2007 server."
    I also noticed that the version of the rules remain Version: 14.0.0.0 for any new rules that I am creating in Exchange 2013.
    I would really appreciate if someone can provide their views and the best practices to remove the traces of Exchange 2007 in AD.

    Hi Sathish,
    How about the result after using ADSI Edit ?
    Best regards,
    Niko Cheng
    TechNet Community Support

  • Transport rule exchange 2010 not sending reply gets stuck in Queue

    I am trying to set up a transport rule in exchange 2010 that will auto reply to a email address that is no longer valid. One of our exec passed away and they want a reply setup to send an automatic message. I read somewhere that the auto reply may not be
    the right way to go about this so I was trying to setup a transport rule. I used the wizard to make the rule for conditions 1 all outside email addresses 2 sent to the internal email address specified. Actions 3 Send rejections message to sender with enhanced
    status code
    Created the message in the rule and gave it a status code 5.7.228 no exceptions and created the rule
    Went to an outside email account and sent to the internal users account. It was reported that it was delivered from our mail filter I verified that it did not get delivered to the user then a few min later the reply appears in the queue viewer on exchange
    a few min later it is gone I figured it worked but when I checked it did not get delivered to the outside email address or seen going through the mail filter. I'm missing something I know its right there somewhere just looking to long and I cant see it.
    This is baffling me as to what happened? What account is it sent from? The user, administrator or do I need to create a postmaster account for it to work? I am a one man shop and it get kind of baffling some times
    Thanks in advance for any help I will keep looking for the answer
    John R
    John R

    Hi John,
    From your description, I would like to verify the following things for troubleshooting:
    1. Please verify if users can send messages to external email addresses.
    2. Please check if internal users can receive the rejection messages.
    Best regards,
    Amy Wang
    TechNet Community Support
    Yes users can send to external address and internal users receive NDR rejection messages
    The system has been in production for 2 years. I'm just trying to find the best way to setup a auto reply for users that are no longer with us or have moved on.
    Thanks for your help
    John R

  • HELP - Exchange Server 2007 Transport Rule Issue

    Hi all,
    sorry if here is not the place to put my question but I did not find another forum, so if anyone can help me I appreciate.
    - I have an Exchange Server 2007 SP3 environment with 1 MBX Server and 3 CAS/HUB Servers.
    - I have created a Transport Rule that said:
    "all emails that have @test.com in BCC field are dropped off except one group can send" .
    The issue is the rule doesn´t work.
    Anyone can help me, please?
    Thanks in advance.
    Luiz

    The Exchange previous versions forums are here: 
    http://social.technet.microsoft.com/Forums/en-US/category/exchangeserverlegacy
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • 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

Maybe you are looking for