Skip to main content

Default Recipient Policy update error shows legacy MS and CCMAIL address policies

After the transition to Exchange 2007 you might find that the update of objects in Active Directory fails when you try to run Update of Default Recipient Policy. You get an error stating the there are legacy Exchange address policies (CCMAIL and MS) in Default Policy and update is not actually run. If you edit Default Policy in Exchange Management Console you see that there are none of MS and CCMAIL entries in your policy.

To resolve this issue you need to edit your policy in Active Directory using ADSIEdit tool and delete disabledGatewayProxy entries of MS and CCMAIL
  • Add ADSIEdit snap-in to MMC console (Support Tools must be installed in order to be able to add ADSIEdit)
  • Connect to Configuration Naming Context
  • Browse to Services --> Microsoft Exchange --> YOURORGANIZATON --> Recipient Policies
  • On the right click Properties of Default Policy
  • Click Show only objects with entries
  • Find disabledGatewayProxy
  • Edit its content
  • Remove:
    • MS:ORGANIZATIONNAME/ORGANIZATIONNAME
    • CCMAIL: at ORGANIZATIONNAME
  • Repeat this step for all the policies in your organization that include these two entries

Popular posts from this blog

Change SMTP port 25 in Exchange 2007, 2010

For some reason you might want to change default SMTP port number 25 Exchange 2007 is using. Exchange 2007 uses RECEIVE AND SEND connectors, one for receiving mails and other for sending mails (obviously ;)
So you need to change ports on those connectors. I will not say those two, because you might be using more than two.
You change Receive connector port by opening the connector properties in Exchange Management Console --> Hub Transport --> RECEIVECONNECTORNAME --> Properties --> Network --> Local IP Addresses (Edit Receive Connector Binding)
Just to clarify what "Local IP Addresses" and "Remote Servers" are (from Exchange 2007 help), because I find it little bit confusing: Use these local IP Addresses to receive mail Use this list to specify the IP addresses and port numbers on which this Receive connector listens for incoming mail. Receive mail from remote servers which have these IP addresses Use this list to specify the remote IP address range fr…

Error "<#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP#" when you send attachment in your mail

Some users were receiving error <#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP# when they sent message with attachment. The problem is when attached document name is longer than 50 characters. Some Firewalls have header size restriction and that limit blocks this messages to be sent. To correct this, change header limit on affected Firewall or shorten the name of the document you are sending (which is probably not good permanent solution).******
Update #1: Default header size limit in Exchange 2007 is 64K.Update #2: It might be the SMTP version problem. Mail is rejected with CONTENT-DISPOSITION error (overly long message header field for CONTENT-DISPOSITION) but not for all SMTP servers (same mail sent through different SMTP servers). If you send mail with attachment that has name longer than 50 characters from Exchange 2007 directly through DNS you may encounter this error, but if you send same mail from Exchange 2007 through smart host (other than Exchange) mail is d…

The attempt to connect to http://yourserver/PowerShell using "Kerberos" authentication failed

The error you get: The attempt to connect to http://yourserver/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found

If you removed Exchange server from the machine and installed it again, you can get following error when you open Exchange Management Console:
The following error occurred while attempting to connect to the specified Exchange server 'yourserver.domain.com':The attempt to connect to http://yourserver.domain.com/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found.
Possible causes are:  -The user name or password specified are invalid.  -Kerberos is used when …