IT Answers » Recipient Policies

Outlook error message – recipient list too large

NED2COMUNIC8 — Wed, 28 Sep 2011 13:33:26 +0000

New Answer by TomLiotta

Exchange 2003 Recipient Policy

Harry123 — Thu, 04 Nov 2010 23:47:26 +0000

We have an exchange 2003 server, configured to accept messages from multiple smtp domain names. The domain are defined in the Recipient Policy folder in ESM. so far so good. We have a number of users with a smtp email domain address which is not defined in the Recipient policy domain list, these users are receiving email without any issues.

My question is I understood that in order to receive a message to specific smtp domain, it must be defined in the RUS list. Why is this server accepting messages for domains not listed in the Recipient Policy folder?

Can’t Delete Old Recipient Policies in Ex2003

SkipCourt — Thu, 29 May 2008 17:04:09 +0000

We just had our first need to add an additional recipient policy to assign a secondary smtp address to a specific group of users. The policy was added successfully and if you preview the ldap filter, the results are correct. The problem is now one of Priority. Back in our 5.5 days we had a regional setup, which carried over at first to our 2000 Org. We then consolidated all servers into a single admin and routing group and no longer had a need for the “regional” recipient policies. Unfortunately, we find that we can’t delete them mow or change their priority. Attempting to delete returns the message: “This Recipient Policy cannot be deleted”. I assumed it was because it had a Priority of “Highest”, but when I attempted to chnage the priority I got the message: There is no such object on the server. Facility LDPA Provider, ID no: 80072030, Exchnage System Manager.

Thought I might be able to find and delete the objects via adsiedit, but could not locate them under Exchange System Objects or anywhere else for that matter.

Soooooo, does anyone have any suggestions or know of any tools or utilities that will let me get these recipient polcy objects removed??

Microsoft Exchange 2003, Recipient Policy, mailbox management.

ITKE — Tue, 13 May 2008 14:58:13 +0000

A question submitted on SearchExchange.com

I created a policy that deletes or is supposed to delete all emails older than 240 days. Followed the MS kb article to a T in setting up the rule. The mailbox manager goes out finds emails, deletes them, and reports having done so. Checking mailboxes it will have deleted items. The problem is it does not work int he deleted items folder. We have some deleted items folders that contain emails from 2003. Have applied the policy several times and it just does not delete emails that meet the criteria in the deleted items folder. How can I get the policy to work correctly on the deleted items folder?

Exchange 2003/2007 Recipient Policy Problem

EastCoastGuy — Wed, 12 Mar 2008 21:02:26 +0000

After introducing Exchange 2007 into our 2003 environment we discovered one of our recipient policies was a problem b/c it was created in Exchange 5.5. The recommended solution from MS was to recreate the policy in Exchange 2003 which we did.

This created a problem. Once we did what MS said we noticed the default policy (Lowest) was now being applied to everyone. For us this means every user gets 1000 domains added to them. Our desire is to only have the highest recipient policy that has “ourdomain.com” as the only applied policy.

Our structure is pretty basic.

If you are in our top level OU you get the highest priority policy (the one with only one domain). The other policy is the default policy. We strictly use the default policy as a place to tell Exchange that we accept mail for our 1000 domains.

The MS level 1 guy is struggling with this and asking for more money.