This article was previously published under Q192583
This article has been archived. It is offered "as is" and will no longer be updated.
When the Internet Mail Service receives an inbound Internet messagefrom a custom recipient whose alias is ambiguous, the Internet Mail Servicefails to deliver the message. This can occur when the inbound Internet MailService server has the following registry value enabled:
The message is then archived on the Internet Mail Service server. Thefollowing event logs are generated:
NOTE: The file name will be different in each scenario and for eachmessage.
Event: 12004 Source: MSExchangeIS Description: Error 80004005-F0000000 occurred while processing message <>. The archive filename is '3SW32JRP'. Event: 4117 Source: MSExchangeIMC Description: An error was returned from the messaging software the Internet Mail Service uses to process messages on the Microsoft Exchange Server. As a result, the message in spool file 3SW32JRP failed to be delivered. The message has been moved to the IMCDATA\IN\ARCHIVE directory.
When two sites have an identical custom recipient, directory replicationbetween the sites creates duplicate entries in the global address list. Forexample, if firstname.lastname@example.org exists in site X email@example.com exists in site Y, upon site replication between thesites, the global address list will have two identical entries, resultingin ambiguous names.
When the Internet Mail Service submits the message to the Microsoftinformation store, and the ResolveP2 registry key is enabled, a directorylookup on the sender is submitted to the directory service. The directoryservice finds duplicate entries, and this creates an ambiguous conditionbecause there is more than one address that meets the criteria. This errorthen is mapped as E_FAIL, resulting in the above error logs, and message isarchived in the archive directory.
To resolve this problem, obtain the latest service pack for Exchange Serverversion 5.5. For more information, please see the following article in theMicrosoft Knowledge Base:
191014XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack
The English version of this fix should have the following file attributesor later:
Component: Information Store
File Name Version ----------------------- Gapi32.dll 5.5.2398.0 Store.exe 5.5.2398.0 Mdbmsg.dll 5.5.2398.0
Microsoft has confirmed this to be a problem in Microsoft Exchange Serverversion 5.5.