邮件退信错误 #550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##
2012-01-11 09:15
666 查看
A week ago, one of our customers had a corrupt email account . Now they are using MS Exchange 2010, but they migrated to this solution a couple of months ago from MS Exchange 2003.
To fix the corrupted mailbox issue, we recommended them to export the valid emails, to delete the corrupted account, to recreate it and to import all the saved emails. Everything work as expected but soon some of their employees started to receive non delivery reports when trying to communicate with that person.
The reports look like:
The e-mail address you entered couldn't be found. Please check the recipient's e-mail address and try to resend the message. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: SERVER.contoso.com
IMCEAEX-_O=CONTOSO_OU=First+20Administrative+20Group_cn=Recipients_cn=mihaeladumitrache@contoso.com
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##
This is an issue that I’ve seen before. The obvious reason for this is the fact that outlook client caches the emails recipients and when you try to send an email to such a recipient, the email client uses the cached LegacyExchangeDN instead the one from the Organization GAL.
Since it was a migrated account from Exchange 2003 to Exchange 2010, the old LegacyExchangeDN attribute was different from the one generated for the new account.
The new one looks like: /o=Contoso/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=username and the old one looks like: /o=Contoso/ou=first administrative group/cn=recipients/cn=username
A friend of mine (Brad Simionescu) that is working for that client came with an interesting idea:
- Remove the old disconnected mailbox
- Force the domain replication
- Using ADSI editor, replace the new LegacyExchangeDN with the old one
- Force the domain replication again
- Rebuild the Exchange address books
If somebody already downloaded the address book with the new LegacyExchangeDN, you have to follow http://support.microsoft.com/kb/287623 article to delete the new cached info and to download again the address book.
To fix the corrupted mailbox issue, we recommended them to export the valid emails, to delete the corrupted account, to recreate it and to import all the saved emails. Everything work as expected but soon some of their employees started to receive non delivery reports when trying to communicate with that person.
The reports look like:
The e-mail address you entered couldn't be found. Please check the recipient's e-mail address and try to resend the message. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: SERVER.contoso.com
IMCEAEX-_O=CONTOSO_OU=First+20Administrative+20Group_cn=Recipients_cn=mihaeladumitrache@contoso.com
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##
This is an issue that I’ve seen before. The obvious reason for this is the fact that outlook client caches the emails recipients and when you try to send an email to such a recipient, the email client uses the cached LegacyExchangeDN instead the one from the Organization GAL.
Since it was a migrated account from Exchange 2003 to Exchange 2010, the old LegacyExchangeDN attribute was different from the one generated for the new account.
The new one looks like: /o=Contoso/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=username and the old one looks like: /o=Contoso/ou=first administrative group/cn=recipients/cn=username
A friend of mine (Brad Simionescu) that is working for that client came with an interesting idea:
- Remove the old disconnected mailbox
- Force the domain replication
- Using ADSI editor, replace the new LegacyExchangeDN with the old one
- Force the domain replication again
- Rebuild the Exchange address books
If somebody already downloaded the address book with the new LegacyExchangeDN, you have to follow http://support.microsoft.com/kb/287623 article to delete the new cached info and to download again the address book.
相关文章推荐
- 解决Exchange 2007 SP1环境下向部分邮箱发送邮件提示未送达“#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##”问题
- 550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found
- Roundcube 无法删除邮件错误解决方法>服务器错误UID COPY: The folder could not be found.
- java.lang.ClassNotFoundException: javax.el.ELResolver错误解决办法
- Eclipse 出现Some sites could not be found. See the error log for more detail.错误 解决方法
- 解析错误报告 'libxml/tree.h' file not found
- 错误记录系列一Parameter 'xxxx' not found. Available parameters are [0, 1, param1, param2]] with root cause
- 使用JSON报的一个错误java.lang.ClassNotFoundException
- iOS 编译含C++代码出现ld: symbol(s) not found for architecture i386错误之解决
- centOS下msyql启动错误-Multiple MySQL running but PID file could not be found
- JSTL表达式错误PropertyNotFoundException: Property 'title' not found on type java.lang.String
- java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver 错误的解决办法
- Genymotion启动时出现错误virtualization engine not found
- yum安装软件包错误 HTTP Error 404 - Not Found Trying other mirror.
- 错误:HttpServlet was not found on the Java
- 错误:Property 'XXX' not found on type java.lang.String解决方法
- java反射读取字符创建类是出现 java.lang.ClassNotFoundException 错误
- iText创建pdf文件里,解决ClassNotFoundException错误
- tomcat启动错误:Native library was not found on the java.library.path
- Maven deploy时报Fatal error compiling: tools.jar not found错误的问题处理