***退回错误信息
From: System Administrator
Sent: Wednesday, April 11, 2007 9:28 AM
To: cclayton@gsig.com
Subject: Undeliverable: RE: 47025 Optic samples.
Your message did not reach some or all of the intended recipients.
Subject: RE: 47025 Optic samples.
Sent: 2007-4-11 9:27
The following recipient(s) could not be reached: cclayton@gsig.com on 2007-4-11 9:28
The message cannot be delivered due to a configuration error on the server. Please contact your Administrator.
<mail.aaa.com #5.3.0 smtp;553 5.3.0 <cclayton@gsig.com>... User unknown>
mail.global.frontbridge.com internet address = 65.55.251.22
>作者: liu 时间: 2007-4-13 10:27 标题: 回复 #1 Look4Dream 的帖子 cclayton@gsig.com>... User unknown 需要确定用户是否存在作者: Look4Dream 时间: 2007-4-18 07:51 标题: 回复 #2 liu 的帖子 用户存在,我已经说明了,只是有的时候会出现这个问题,今天好像又没有问题了,不知道什么意思,到底是哪里的问题呢?哪位大虾知道,给个说明。作者: fairy1331 时间: 2007-4-18 10:43
Numeric Code: 5.3.0
First Available: Exchange Server 2003
Possible Causes: Exchange Server 2003 has a feature that permits Exchange 2003 to operate without the Message Transfer Agent (MTA). If a message was sent incorrectly by using the MTA route, this delivery status notification is returned to the sender.
Note Although Exchange 2003 can operate without the MTA, Microsoft does not recommend or support this configuration.
To turn on this feature and to prevent the messages from queuing to the MTA, follow these steps:
1. Disable the MTA service.
2. Set the DWORD value to 0 in the following registry subkeys for every information store database and public folder store:
HKLM\System\CurrentControlSet\Services\MsExchangeIS\<Server Name>\<PrivMDB_GUID>\Gateway In Threads
HKLM\System\CurrentControlSet\Services\MsExchangeIS\<Server Name>\<PrivMDB_GUID>\Gateway Out Threads
When you do this, you are making store resources that are associated with MTA delivery available.
3. Restart the information store.
Troubleshooting: Check your routing topology. Use the WinRoute tool to make sure that the routes are correctly replicated between servers and routing groups.
FYR作者: atong999888 时间: 2007-4-18 22:44
user unknow我想应该是对方服务器的问题, 可能是后来对方管理员把问题解决了.