Exchange Transport Rule - still blocking me

Hey Guys,
I have an issue that I am curious about getting some feedback on. I built a transport rule in a Exchange 2007 SP2 to block email from a specific distribution list to recipients external to our organization.

During the testing, I added myself to the distribution list. It seems to be working, so I removed myself, but now it still thinks that I am in the distribution list.

Does anyone have an explanation for this? I found an section on TechNet that talks about it the Expanded Groups cache storing group membership for 4 hours, but then I noticed that that article was applying to 2013, so I'm not sure if that applies.

Anyway, it's not a big deal because I just disabled the rule for the time being. But, eventually I need to get it enabled and I'd like to know what's going on here. Maybe restarting the transport service will reset it, but I'd rather not have to do that. If it's just a few hours, then that's fine, I can wait it out for changes.

Thanks,
Ben
Jack5BackAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DipakCommented:
Yes, you are right.

Each Hub Transport server maintains a recipient cache that's 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.

http://technet.microsoft.com/en-us/magazine/2007.05.compliance.aspx

http://technet.microsoft.com/en-us/magazine/2007.05.compliance.aspx

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Vijaya Babu SekarAssociate Ops ManagerCommented:
you can restart the service  "Microsoft Transport Service"  it may be replicate will happen immediately


Thanks
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.