Solved

Hub Transport "Transport Rule" not working

Posted on 2009-04-09
2
7,016 Views
Last Modified: 2012-05-06
I have created a Transport Rule to block all messages from the outside to users in a group but when I send meail to the test user in the group I still get the message. Any ideas as to why this would be?
Rule Info:
Restricted Internet Mail
Rule Comments:

Apply rule to messages
from users Outside the organization
   and when any of the recipients in the To or Cc fields is a member of SG-Restricted Internet Email
send Delivery not authorized, message refused to sender with 5.7.1

0
Comment
Question by:jwhitepnv
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
2 Comments
 

Author Comment

by:jwhitepnv
ID: 24109956
Shell Command that was run:

Summary: 1 item(s). 1 succeeded, 0 failed.
Elapsed time: 00:00:00


Restricted Internet Mail
Completed

Warning:
The command completed successfully but no settings of 'Restricted Internet Mail' have been modified.


set-TransportRule -Name 'Restricted Internet Mail' -Comments '' -conditions 'Microsoft.Exchange.MessagingPolicies.Rules.Tasks.FromScopePredicate','Microsoft.Exchange.MessagingPolicies.Rules.Tasks.AnyOfToCcHeaderMemberOfPredicate' -Actions 'Microsoft.Exchange.MessagingPolicies.Rules.Tasks.RejectMessageAction' -Exceptions  -Identity 'Restricted Internet Mail'

0
 

Accepted Solution

by:
jwhitepnv earned 0 total points
ID: 24112304
I figured this out. There is a delay in the Hub Tranport server updating the rules. It only updates every 4 Hours unless you start or stop the Hub Transport.

Per Microsoft TechNet article:.  http://technet.microsoft.com/en-us/library/bb124703.aspx

Each Hub Transport server maintains a recipient cache that is used to look up recipient and distribution list information. The recipient cache reduces the number of requests that each Hub Transport server must make to an Active Directory domain controller. The recipient cache updates every four hours. You can't modify the recipient cache update interval. Therefore, changes to transport rule recipients, such as the addition or removal of distribution list members, may not be applied to transport rules until the recipient cache is updated. To force an immediate update of the recipient cache, you must stop and start the Microsoft Exchange Transport service. You must do this for each Hub Transport server where you want to forcibly update the recipient cache.


1

Featured Post

Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
This video discusses moving either the default database or any database to a new volume.

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question