首先，我应该说，我很了解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 在应用程序日志中有很多错误，但没有什么突然显现的。 但是再一次，我真的不知道我在找什么。
任何帮助将不胜感激。
编辑：这是从下面的第一个build议的结果：
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!) --------------------------------------------------------------------------------
看起来像他们自己的邮件服务器不可用，事情正在回落到他们的替代MX地址，这些地址未正确configuration为接收该域的邮件。
试试http://www.zmailer.org/mxverify上的免费mxverify工具，并input域名查看几个脚本化testing及其详细结果。 这是这种东西的一个很好的工具。
我同意AdamV，邮件服务器，sbssrv.jfzassoc.com不接受连接，所以邮件是去dnseasy服务器（通过MX优先），他们没有为您的域设置。
由于连接到sbssrv.jfzassoc.com失败，让我们从那里开始。 你可以ping服务器？ 你可以validation它正在运行？ 所有的Exchange服务都在运行吗？ 为sbssvr列出的地址是一个公共地址，从networking内部，你可以打内部地址？ 如果是的话，这指向一个路由问题。
问题原来是办公室里的路由器（掉电，浪涌等）被重置为默认值，并且得到一个新的IP地址来启动。 我将客户端主机上子域的路由更改为新的IP地址，并在路由器设置中重新创build了所有必要的端口转发。 一旦IP更改通过我的DNS服务器，一切都开始工作了。
我需要知道旧IP地址是否是静态的（应该是这个地址的），并且需要在路由器上重新configuration，而我可以在晚上晚些时候做到这一点，一旦我知道肯定。
感谢BillN和AdamV的帮助！ 🙂