We had a consultant perform an upgrade from Exchange 2003 to Exchange 2007 some months ago. Several days ago we attempted to install Exchange 2007 SP1 and received the following error "The E-mail Address Policy object must have exactly one primary e-mail address with the prefix "FAXMAKER". (we have the Faxmaker software installed and it is working) Installation of the Service Pack failed and was halted. Upon investigation of the E-Mail Address Policies in the Exchange 2007 Management Console I see that both the Default Policyand the Company Policy show 'False' in the Applied column. When I tried to edit them I received this error: "Unable to edit the specified E-mail address policy. E-mail address policies created with legacy versions of Exchange must be upgraded using the 'Set-EmailAddressPolicy' task, with the Exchange 2007 Recipient Filter specified." I then read and attempted to use the method to upgrade our E-Mail Address Policies outlined in http://msexchangeteam.com/archive/2007/01/11/432158.aspx When I tried to run the cmdlet "Set-EmailAddressPolicy "Default Policy" -IncludedRecipients AllRecipients " as outlined in the article I was met with a similar error "The E-Mail Address Policy object must have exactly one primary e-mail address with the prefix "FAXMAKER". Exchange 2003 System Manager along with Exchange 2003 was removed by the consultant that performed our upgrade so I am unable to edit either of the E-Mail address Policies. Although we are receiving our mail and Exchange 2007 is operating correctly, I really need to resolve this issue and install SP1. Any guidance from the community is appreciated. Thank you!

I think you'll need to go into ADSIEdit territory and remove the information from there. The policy should have been upgraded before Exchange 2003 was removed IMO. It might be worth logging a Microsoft PSS call on this one so that they can guide you - better to be safe than sorry here.

I had this same issue. The client was no longer using FaxMaker so I removed the entry for FAXmaker from the list of E-Mail Addresses in the policy. I used Exchange 2003 System Manager to do this. Maybe you could reinstall System Manager and use that to edit the policy? -Dustin

I was able to install the Exchange 2003 Management Console on a workstation. I removed the Faxmakerentry. I then ran the cmdletSet-EmailAddressPolicy "Default Policy" -IncludedRecipients AllRecipients " with success. When I tried to edit and Apply the Default E-mail Policy in the Exchange 2007 Management Console I received this error: Summary: 2 item(s). 0 succeeded, 1 failed. Elapsed time: 00:00:00 Edit Default PolicyFailed Error:The E-mail address policy object "Default Policy" is invalid because it contains invalid E-mail address templates: 'MS:LGROUP/WGPO', 'CCMAIL: at LGROUP'. To view details of the error, see the application event log in the Windows Event Viewer on the Microsoft Exchange Server computer. Exchange Management Shell command attempted:set-EmailAddressPolicy -Instance 'Default Policy' Elapsed Time: 00:00:00 Apply Default PolicyCancelled The Event viewer detail is: Event Type:ErrorEvent Source:MSExchangeSAEvent Category:General Event ID:2035Date:12/13/2007Time:1:16:35 PMUser:N/AComputer:LG-EXCH-01Description:The e-mail address description object in the Microsoft Exchange directory for the 'CCMAIL' address type on 'AMD64' machines is missing. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. I have not attempted to change the other E-mail address Policy our company uses yet.

Actually the answer is quite simple.. you have to use adsiedit .. but .. be extremely carefull because you could render your exchange environment useless .. !!!! go to Configuration [DC Machinename]- CN=Configuration,DC=domain,DC=local - CN=Services - CN=Microsoft Exchange - Organization name (could be "CN=First Organization") - CN=Recipient Policies double click on the recipinet policy that enhibits the fault and goto to the following entry: disabledGatewayProxy, remove the namespace you noticed when trying to edit the policy through the system manager .. after you removed the entry it all should work fine without problems .. grtx Johan