首先，我应该说我非常了解 Windows，但对 Exchange 却不太了解。
我正在尝试支持运行带有 Exchange 的 SBS2003 服务器的用户。周末，每个向他的任何地址发送邮件的人都会收到如下错误消息：
Delivery to the following recipient failed permanently:
[email protected]
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 554 554 5.7.1 <[email protected]>: Relay access denied (state 14).
----- Original message -----
Received: by 10.114.18.7 with SMTP id 7mr5572745war.127.1275423472120; Tue, 01
Jun 2010 13:17:52 -0700 (PDT)
MIME-Version: 1.0
Sender: [email protected]
Received: by 10.143.10.15 with HTTP; Tue, 1 Jun 2010 13:17:32 -0700 (PDT)
From: My Name <[email protected]>
Date: Tue, 1 Jun 2010 15:17:32 -0500
X-Google-Sender-Auth: XiPrP8Em_6Eb94EH9m84nJVGvCY
Message-ID: <[email protected]>
Subject: TEST
To: Client <[email protected]>
Content-Type: multipart/alternative; boundary=001636b1484ffe72470487fdaa5b
应用程序日志中有很多错误，但没有一个是显而易见的。不过话说回来，我并不知道我在寻找什么。
任何帮助将不胜感激。
编辑：以下是第一个建议的结果：
MX-VERIFY-CGI run for ``[email protected]''
--------------------------------------------------------------------------------
Doing resolver lookup for T=MX domain=``jfzassoc.com''
DNS yields following MX entries
jfzassoc.com (7200s) IN MX 20 sbssrv.jfzassoc.com
jfzassoc.com (7200s) IN MX 30 mx1.dnsmadeeasy.com
jfzassoc.com (7200s) IN MX 40 mx2.dnsmadeeasy.com
jfzassoc.com (7200s) IN MX 50 mx3.dnsmadeeasy.com
--------------------------------------------------------------------------------
Testing MX server: sbssrv.jfzassoc.com
Address lookup did yield following ones:
IPv4 173.15.20.182
Testing server at address: IPv4 173.15.20.182
ERROR: Connect failure reason: Connection timed out
(Still possibly all OK!)
--------------------------------------------------------------------------------
Testing MX server: mx1.dnsmadeeasy.com
Address lookup did yield following ones:
IPv4 66.231.182.63
IPv4 66.231.182.64
IPv4 66.231.182.80
IPv4 66.231.182.35
Testing server at address: IPv4 66.231.182.63
[ CONNECTED! ]
220 mx1cm.dnsmadeeasy.com ESMTP DNS Made Easy Messaging
EHLO vger.kernel.org
250-mx1cm.dnsmadeeasy.com
250-PIPELINING
250-SIZE 31457280
250-VRFY
250-ETRN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
Excellent! It speaks ESMTP!
MAIL FROM:<>
250 2.1.0 Ok
Fine, it accepts NULL return-path as is mandated by RFC 2821 section 6.1
RSET
250 2.0.0 Ok
MAIL FROM:<[email protected]>
250 2.1.0 Ok
RCPT TO:<[email protected]>
554 5.7.1 <[email protected]>: Relay access denied
Something WRONG!! rc=554
Testing server at address: IPv4 66.231.182.64
[ CONNECTED! ]
220 mx1cm.dnsmadeeasy.com ESMTP DNS Made Easy Messaging
EHLO vger.kernel.org
250-mx1cm.dnsmadeeasy.com
250-PIPELINING
250-SIZE 31457280
250-VRFY
250-ETRN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
Excellent! It speaks ESMTP!
MAIL FROM:<>
250 2.1.0 Ok
Fine, it accepts NULL return-path as is mandated by RFC 2821 section 6.1
RSET
250 2.0.0 Ok
MAIL FROM:<[email protected]>
250 2.1.0 Ok
RCPT TO:<[email protected]>
554 5.7.1 <[email protected]>: Relay access denied
Something WRONG!! rc=554
Testing server at address: IPv4 66.231.182.80
[ CONNECTED! ]
220 mx1cm.dnsmadeeasy.com ESMTP DNS Made Easy Messaging
EHLO vger.kernel.org
250-mx1cm.dnsmadeeasy.com
250-PIPELINING
250-SIZE 31457280
250-VRFY
250-ETRN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
Excellent! It speaks ESMTP!
MAIL FROM:<>
250 2.1.0 Ok
Fine, it accepts NULL return-path as is mandated by RFC 2821 section 6.1
RSET
250 2.0.0 Ok
MAIL FROM:<[email protected]>
250 2.1.0 Ok
RCPT TO:<[email protected]>
554 5.7.1 <[email protected]>: Relay access denied
Something WRONG!! rc=554
Testing server at address: IPv4 66.231.182.35
[ CONNECTED! ]
220 mx1cm.dnsmadeeasy.com ESMTP DNS Made Easy Messaging
EHLO vger.kernel.org
250-mx1cm.dnsmadeeasy.com
250-PIPELINING
250-SIZE 31457280
250-VRFY
250-ETRN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
Excellent! It speaks ESMTP!
MAIL FROM:<>
250 2.1.0 Ok
Fine, it accepts NULL return-path as is mandated by RFC 2821 section 6.1
RSET
250 2.0.0 Ok
MAIL FROM:<[email protected]>
250 2.1.0 Ok
RCPT TO:<[email protected]>
554 5.7.1 <[email protected]>: Relay access denied
Something WRONG!! rc=554
--------------------------------------------------------------------------------
Testing MX server: mx2.dnsmadeeasy.com
Address lookup did yield following ones:
IPv4 208.94.147.129
Testing server at address: IPv4 208.94.147.129
[ CONNECTED! ]
220 mx2.dnsmadeeasy.com ESMTP TiggeeSMTP (1.0.2.0002.1)
EHLO vger.kernel.org
250-mx2.dnsmadeeasy.com
250-PIPELINING
250-SIZE 30240000
250-VRFY
250-ETRN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
Excellent! It speaks ESMTP!
MAIL FROM:<>
250 2.1.0 Ok
Fine, it accepts NULL return-path as is mandated by RFC 2821 section 6.1
RSET
250 2.0.0 Ok
MAIL FROM:<[email protected]>
250 2.1.0 Ok
RCPT TO:<[email protected]>
554 5.7.1 <[email protected]>: Relay access denied
Something WRONG!! rc=554
--------------------------------------------------------------------------------
Testing MX server: mx3.dnsmadeeasy.com
Address lookup did yield following ones:
IPv4 67.19.109.170
Testing server at address: IPv4 67.19.109.170
ERROR: Connect failure reason: Connection refused
(Still possibly all OK!)
--------------------------------------------------------------------------------
答案1
看起来他们自己的邮件服务器不可用，并且一切都回到了他们的备用 MX 地址，该地址没有正确配置来接收该域的邮件。
试用免费的 mxverify 工具http://www.zmailer.org/mxverify并输入域名即可查看几个脚本测试及其详细结果。对于这类事情来说，这是一个很棒的工具。
答案2
我同意 AdamV 的观点，邮件服务器 sbssrv.jfzassoc.com 不接受连接，因此邮件将发送到 dnseasy 服务器（通过 MX 优先级），而这些服务器并未为您的域名进行设置。
由于与 sbssrv.jfzassoc.com 的连接失败，让我们从那里开始。您可以 ping 服务器吗？您可以验证它是否正在运行吗？所有 Exchange 服务都在运行吗？列出的 sbssvr 地址是公共地址，从网络内部，您可以访问内部地址吗？如果可以，则表明存在路由问题。
答案3
问题原来是办公室里的路由器不知何故（断电、电涌等）被重置为默认值，并获得了一个新的 IP 地址。我将客户端主机上的子域路由更改为新 IP 地址，并在路由器设置中重新创建所有必要的端口转发。一旦 IP 更改通过我的 DNS 服务器，一切便会重新开始工作。
我需要查明旧的 IP 地址是否是静态的（它应该是），并且需要在路由器上重新配置以代替动态 IP 地址，但我可以在确定后在晚上晚些时候这样做。
感谢 BillN 和 AdamV 的帮助！:)