Diagnostic-Code: SMTP; 是什么意思?第573章 是什么意思?

发布于 2024-12-09 07:12:17 字数 3856 浏览 0 评论 0原文

我正在使用 sendmail 从 Rails 应用程序发送邮件。但是,向特定用户域发送邮件时似乎发生了错误。 /var/mail/*** 的错误如下:

Date: Tue, 11 Oct 2011 16:33:46 GMT
From: Mail Delivery Subsystem <MAILER-DAEMON@*****>
Message-Id: <201110111633.p9BGXkpR010310@******>
To: <****@*****>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
        boundary="p9BGXkpR010310.1318350826/******"
Subject: Returned mail: see transcript for details
Auto-Submitted: auto-generated (failure)
This is a MIME-encapsulated message

--p9BGXkpR010310.1318350826/*******

The original message was received at Tue, 11 Oct 2011 16:33:42 GMT
from localhost [127.0.0.1]

   ----- The following addresses had permanent fatal errors -----
<****@{domain}.com>
    (reason: 573 ********@****** failed to route the address)
<*****@{domain}.com>
    (reason: 573 *******@****** failed to route the address)
<*****@{domain}.com>
    (reason: 573 *******@******* failed to route the address)

   ----- Transcript of session follows -----
... while talking to *********.com.1.0001.arsmtp.com.:
>>> MAIL From:<*******@*******> SIZE=1273
<<< 573 ********@********* failed to route the address
554 5.0.0 Service unavailable

--p9BGXkpR010310.1318350826/*******
Content-Type: message/delivery-status

Reporting-MTA: dns; StreetSense
Received-From-MTA: DNS; localhost
Arrival-Date: Tue, 11 Oct 2011 16:33:42 GMT

Final-Recipient: RFC822; ****@*******.com
Action: failed
Status: 5.0.0
Diagnostic-Code: SMTP; 573 *******@******* failed to route the address
Last-Attempt-Date: Tue, 11 Oct 2011 16:33:46 GMT

Final-Recipient: RFC822; *******@********.com
Action: failed
Status: 5.0.0
Diagnostic-Code: SMTP; 573 *******@******** failed to route the address
Last-Attempt-Date: Tue, 11 Oct 2011 16:33:46 GMT

Final-Recipient: RFC822; ******@*********.com
Action: failed
Status: 5.0.0
Diagnostic-Code: SMTP; 573 *****@******** failed to route the address
Last-Attempt-Date: Tue, 11 Oct 2011 16:33:46 GMT

退回的邮件全部来自同一个域,并且邮件正在成功发送到其他域。当我查找 SMTP 573 诊断代码时,我收到此“573 内部服务器错误,IP 地址相关。”。但我不知道这意味着什么。谁能帮助我吗?

更新

从@guenter的回答中,我得到了这些命令,我​​运行它并得到以下输出:

# dig streetsense.com MX

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5 <<>> xxxxx.com MX
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61139
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;xxxxx.com.     IN  MX

;; ANSWER SECTION:
xxxxx.com.  3600    IN  MX  10 xxxxx.com.1.0001.arsmtp.com.
xxxxxx.com. 3600    IN  MX  20 xxxxx.com.2.0001.arsmtp.com.

;; AUTHORITY SECTION:
xxxxx.com.  155394  IN  NS  ns04.ntiva.net.
xxxxx.com.  155394  IN  NS  ns01.ntiva.net.
xxxxx.com.  155394  IN  NS  ns02.ntiva.net.
xxxxx.com.  155394  IN  NS  ns03.ntiva.net.

;; ADDITIONAL SECTION:
ns01.ntiva.net.     147 IN  A   xxx.xx.xx.xxx
ns02.ntiva.net.     147 IN  A   xxx.xx.xx.xxx
ns03.ntiva.net.     147 IN  A   xxx.xx.xx.xxx
ns04.ntiva.net.     147 IN  A   xxx.xx.xx.xxx

;; Query time: 45 msec
;; SERVER: xxx.xxx.x.x#xx(xxx.xxx.x.x)
;; WHEN: Tue Oct 11 18:08:23 2011
;; MSG SIZE  rcvd: 262

ping 似乎也正常工作:

# ping xxxxxxx.com
PING xxxxxxxx.com (xxx.xx.xx.xx) xx(xx) bytes of data.
64 bytes from linux06.ntiva.com (xxx.xx.xx.xx): icmp_seq=1 ttl=53 time=29.0 ms
64 bytes from linux06.ntiva.com (xxx.xx.xx.xx): icmp_seq=2 ttl=53 time=27.4 ms
64 bytes from linux06.ntiva.com (xxx.xx.xx.xx): icmp_seq=3 ttl=53 time=27.4 ms
64 bytes from linux06.ntiva.com (xxx.xx.xx.xx): icmp_seq=4 ttl=53 time=27.4 ms

编辑

我的服务器的主机名似乎也与引起问题的域名相同

# hostname
xxxxxxx

这与域名 xxxxxxx.com 相同。这会导致问题吗?

I am using sendmail to send mail from my Rails application. But, there seems to be a error happening while sending mails to a specific user domain. The error from /var/mail/*** is as follows:

Date: Tue, 11 Oct 2011 16:33:46 GMT
From: Mail Delivery Subsystem <MAILER-DAEMON@*****>
Message-Id: <201110111633.p9BGXkpR010310@******>
To: <****@*****>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
        boundary="p9BGXkpR010310.1318350826/******"
Subject: Returned mail: see transcript for details
Auto-Submitted: auto-generated (failure)
This is a MIME-encapsulated message

--p9BGXkpR010310.1318350826/*******

The original message was received at Tue, 11 Oct 2011 16:33:42 GMT
from localhost [127.0.0.1]

   ----- The following addresses had permanent fatal errors -----
<****@{domain}.com>
    (reason: 573 ********@****** failed to route the address)
<*****@{domain}.com>
    (reason: 573 *******@****** failed to route the address)
<*****@{domain}.com>
    (reason: 573 *******@******* failed to route the address)

   ----- Transcript of session follows -----
... while talking to *********.com.1.0001.arsmtp.com.:
>>> MAIL From:<*******@*******> SIZE=1273
<<< 573 ********@********* failed to route the address
554 5.0.0 Service unavailable

--p9BGXkpR010310.1318350826/*******
Content-Type: message/delivery-status

Reporting-MTA: dns; StreetSense
Received-From-MTA: DNS; localhost
Arrival-Date: Tue, 11 Oct 2011 16:33:42 GMT

Final-Recipient: RFC822; ****@*******.com
Action: failed
Status: 5.0.0
Diagnostic-Code: SMTP; 573 *******@******* failed to route the address
Last-Attempt-Date: Tue, 11 Oct 2011 16:33:46 GMT

Final-Recipient: RFC822; *******@********.com
Action: failed
Status: 5.0.0
Diagnostic-Code: SMTP; 573 *******@******** failed to route the address
Last-Attempt-Date: Tue, 11 Oct 2011 16:33:46 GMT

Final-Recipient: RFC822; ******@*********.com
Action: failed
Status: 5.0.0
Diagnostic-Code: SMTP; 573 *****@******** failed to route the address
Last-Attempt-Date: Tue, 11 Oct 2011 16:33:46 GMT

The bounced back emails are all from the same domain, and mails are being successfully sent to other domains. When I looked for SMTP 573 diagnostic codes, I got this "573 Internal server error, IP address related.". But I dont know what it means. Can anyone help me?

Update

From @guenter's answer, I got these commands and I run it and got the following outputs:

# dig streetsense.com MX

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5 <<>> xxxxx.com MX
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61139
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;xxxxx.com.     IN  MX

;; ANSWER SECTION:
xxxxx.com.  3600    IN  MX  10 xxxxx.com.1.0001.arsmtp.com.
xxxxxx.com. 3600    IN  MX  20 xxxxx.com.2.0001.arsmtp.com.

;; AUTHORITY SECTION:
xxxxx.com.  155394  IN  NS  ns04.ntiva.net.
xxxxx.com.  155394  IN  NS  ns01.ntiva.net.
xxxxx.com.  155394  IN  NS  ns02.ntiva.net.
xxxxx.com.  155394  IN  NS  ns03.ntiva.net.

;; ADDITIONAL SECTION:
ns01.ntiva.net.     147 IN  A   xxx.xx.xx.xxx
ns02.ntiva.net.     147 IN  A   xxx.xx.xx.xxx
ns03.ntiva.net.     147 IN  A   xxx.xx.xx.xxx
ns04.ntiva.net.     147 IN  A   xxx.xx.xx.xxx

;; Query time: 45 msec
;; SERVER: xxx.xxx.x.x#xx(xxx.xxx.x.x)
;; WHEN: Tue Oct 11 18:08:23 2011
;; MSG SIZE  rcvd: 262

ping also seem to be working:

# ping xxxxxxx.com
PING xxxxxxxx.com (xxx.xx.xx.xx) xx(xx) bytes of data.
64 bytes from linux06.ntiva.com (xxx.xx.xx.xx): icmp_seq=1 ttl=53 time=29.0 ms
64 bytes from linux06.ntiva.com (xxx.xx.xx.xx): icmp_seq=2 ttl=53 time=27.4 ms
64 bytes from linux06.ntiva.com (xxx.xx.xx.xx): icmp_seq=3 ttl=53 time=27.4 ms
64 bytes from linux06.ntiva.com (xxx.xx.xx.xx): icmp_seq=4 ttl=53 time=27.4 ms

Edit

also my hostname of my server seems to be same as the domain name causing issue

# hostname
xxxxxxx

This is same as the domain xxxxxxx.com. Can this cause the issue?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

走过海棠暮 2024-12-16 07:12:17

无法路由地址是这里的关键。

您的 sendmail 似乎不知道如何路由该地址。您需要在这里进行一些邮件调试。第一步可能是检查 DNS 中该域的 MX 记录 - dig example.com MX

如果没有 MX 记录,那就是问题所在。如果存在 MX 记录,您可以尝试 ping 该主机。

failed to route the address is the key here.

Seems that your sendmail doesn't know how to route that address. You need some mail-debugging here. First step could be to check the DNS for MX-records for this domain - dig example.com MX.

If there is no MX record, that is the problem. If there are MX record(s), you might try to ping that hosts.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文