Exchange Server 中的 Dsn 和 NdrDSNs and NDRs in Exchange Server

如果在传递邮件时出现问题,Exchange 会向邮件发件人发送 NDR,指出存在问题。When there's a problem delivering a message, Exchange sends an NDR to the message sender that indicates there was a problem. Ndr 包含一个指示邮件未送达原因的代码,以及可帮助您传递邮件的可能解决方案。NDRs include a code that indicates why the message wasn't delivered, and possible solutions to help get the message delivered.

Ndr 中包含的信息旨在便于阅读和帮助用户和管理员。The information that's included in NDRs is designed to be easy to read and helpful for both users and administrators. 在某些情况下,发件人可以识别和修复自己的问题(例如,当收件人的电子邮件地址中有拼写错误时)。In some cases, senders can identify and fix their own problems (for example, when there's a typo in the recipient's email address). 在其他情况下,管理员可能需要修复 Exchange 环境中的问题,或将目标域中的管理员通知给其邮件环境中的问题。In other cases, an administrator may need to fix an issue in the Exchange environment, or notify the administrators in the destination domain about problems in their messaging environment.

有关与 Exchange Server 中的 Ndr 相关的过程,请参阅Exchange server 中的 dsn 和 ndr 的过程For procedures related to NDRs in Exchange Server, see Procedures for DSNs and NDRs in Exchange Server.

如果您需要 Office 365 或 Exchange Online 中有关 NDR 的帮助,请参阅在 Office 365 中以电子邮件的方式发送未送达报告If you need help with NDRs in Office 365 or Exchange Online, see Email non-delivery reports in Office 365.

Ndr 中的信息Information in NDRs

以下是 NDR 的一个示例:This is an example of an NDR:

显示管理员部分的用户和诊断信息的 NDR

NDR 中的信息分为两部分:The information in an NDR is separated into two sections:

  1. "用户信息" 部分:此部分首先显示,并尝试解释(非技术术语)邮件传递失败的原因以及成功传递邮件的可能步骤。User information section: This section appears first and attempts to explain (in non-technical terms) why delivery of the message failed, and possible steps to successfully deliver the message.

    • 此部分中显示的文本由生成 NDR 的 Exchange 服务器插入。The text that's displayed in this section is inserted by the Exchange server that generated the NDR.

    • 如果适用,拒绝邮件的服务器的完全限定域名(FQDN)将包含在 "用户信息" 部分(例如 mbx01.contoso.com)中。When applicable, the fully qualified domain name (FQDN) of the server that rejected the message is included in the user information section (for example mbx01.contoso.com).

    • 如果多个收件人的传递失败,则列出每个收件人的电子邮件地址和原因。。If delivery failed for multiple recipients, the email address and reason for failure is listed for each recipient is listed..

  2. "管理员的诊断信息" 部分:本节提供更深入的技术信息,可帮助管理员解决导致传递失败的问题。Diagnostic information for administrators section: This section provides deeper technical information to help administrators troubleshoot the issues that caused the delivery failure.

    本节中的一项关键信息是增强状态代码(例如,4.4.7)。A key piece of information in this section is the enhanced status code (for example, 4.4.7).

    • 增强状态代码由生成 NDR 的服务器返回(无法传递邮件的源服务器或拒绝邮件的目标服务器)。The enhanced status code is returned by the server that generated the NDR (the source server that couldn't deliver the message, or the destination server that rejected the message).

    • 增强状态代码确定在 "用户信息" 部分中显示的文本(Exchange 不会改变代码值)。The enhanced status code determines the text that's displayed in the user information section (the code value isn't altered by Exchange).

    您可以使用 Exchange 命令行管理程序中的get-systemmessage cmdlet 来修改在给定的增强状态代码(包括不同语言的不同文本)的 "用户信息" 部分中显示的文本。You can use the New-SystemMessage cmdlet in the Exchange Management Shell to modify the text that appears in user information section for a given enhanced status code (including different text in different languages). 通过创建自定义说明,可以为环境提供特定内容(如技术支持人员的联系信息),也可以为 Intranet 提供自助服务支持的链接。By creating custom explanations, you can provide specific content for your environment, such as contact information for your help desk, or links to your Intranet for self-service support. 有关详细信息,请参阅Exchange Server 中的 dsn 和 Ndr 过程For more information, see Procedures for DSNs and NDRs in Exchange Server.

    • 本主题中的常见 "增强状态代码" 部分介绍了数字的含义、您可能遇到的代码以及修复阻止邮件传递的基本问题的建议。The Common enhanced status codes section in this topic explains what the numbers mean, the codes that you're likely to encounter, and suggestions to fix the underlying problem that prevented the message from being delivered.

    本节中也提供了以下信息:The following information is also available in this section:

    • 生成服务器:创建 NDR 的邮件服务器。Generating server: The messaging server that created the NDR. 如果发件人的电子邮件地址下方未列出远程服务器,则生成服务器也是拒绝原始电子邮件的服务器。If a remote server isn't listed below the sender's email address, the generating server is also the server that rejected the original email message. 如果邮件传递在 Exchange 组织中的发件人和收件人之间失败,则同一服务器通常会拒绝原始邮件并生成 NDR。If message delivery fails between senders and recipients in the Exchange organization, the same server typically rejects the original message and generates the NDR.

    • 被拒绝的收件人:原始邮件中无法传递的收件人的电子邮件地址。The rejected recipients: The recipient's email address in the original message that couldn't be delivered. 如果多个收件人的传递失败,则列出每个收件人的电子邮件地址。If delivery fails for multiple recipients, the email address of each recipient is listed. 此字段还包含每个电子邮件地址的以下子字段:This field also contains the following sub-fields for each email address:

    • 远程服务器:在 SMTP 传输过程中拒绝原始邮件的服务器的 FQDN (发送邮件正文后传递失败,但在服务器确认接收邮件之前)。Remote server: The FQDN of the server that rejected the original message during SMTP transmission (delivery failed after the message body was sent, but before the server acknowledged receiving the message). 以下情况不显示此字段:This field isn't present when:

    • 拒绝邮件的服务器也生成 NDR。The server that rejected the message also generated the NDR. 这对于同一个 Exchange 组织中的发件人和收件人之间的传递失败很常见。This is typical for delivery failures between senders and recipients in the same Exchange organization.

    • 远程服务器已确认接收原始邮件,但由于其他原因(例如,内容限制),邮件被拒绝。The remote server acknowledged receiving the original message, but the message was rejected for other reasons (for example, content restrictions).

    • 增强状态代码Enhanced status code

    • SMTP 响应:由拒绝原始邮件的邮件服务器返回的 us-ascii 文本字符串。SMTP response: The US-ASCII text string that's returned by the messaging server that rejected the original message. 这通常是增强状态代码的简短说明。This is typically a short explanation of the enhanced status code. 此字符串不是由 Exchange 重写的。This string is not rewritten by Exchange.

    • 原始邮件头:此区域包含已拒绝邮件的邮件头。Original message headers: This area contains the message header of the rejected message. 这些标头字段可提供有用的诊断信息(例如,邮件路由路径中的服务器跃点,或 "收件人" 字段是否与已拒绝收件人的电子邮件地址相匹配)。These header fields can provide useful diagnostic information (for example, server hops in the message routing path, or whether the To field matches the email address of the rejected recipient).

常见的增强状态代码Common enhanced status codes

增强状态代码在 RFC 3463 中定义,并使用语法_ <类>Enhanced status codes are defined in RFC 3463, and use the syntax <class>. <主题><subject>. 详细信息>: <<detail>_:

  • 类:4表示临时传递错误。 **** _ <><class>_: 4 indicates a temporary delivery error. 5表示永久性传递错误。5 indicates a permanent delivery error.

  • 主题: RFC 将如下所示的值分类: _ <><subject>_: The RFC categorizes the values like this:

    • 1:寻址1: Addressing

    • 2:邮箱(收件人)2: Mailbox (the recipient)

    • 3:邮件系统(目标邮件系统)3: Mail system (the destination mail system)

    • 4:网络和路由4: Network and routing

    • 5:邮件传递协议5: Mail delivery protocol

    • 7:安全或策略7: Security or policy

  • 详细信息>:一个1到3位数字,用于进一步对错误进行< 分类。<detail>: A 1 to 3 digit number that further classifies the error.

下表包含 Ndr 中针对最常见的邮件传递失败返回的增强状态代码。The following tables contain the enhanced status codes that are returned in NDRs for the most common message delivery failures.

备注

有关 Office 365 和混合环境中的增强状态代码的信息,请参阅office 365 中的电子邮件未送达报告For information about enhanced status codes in Office 365 and hybrid environments, see Email non-delivery reports in Office 365.

临时传递失败次数Temporary delivery failures

增强状态代码Enhanced status code 说明Description 可能的原因和解决方案Possible causes and solutions
4.3.14.3.1 Insufficient system resources 可用磁盘空间不足(例如,容纳队列数据库的磁盘不具有所需的可用空间量)。Free disk space is low (for example, the disk that holds the queue database doesn't have the required amount of free space). 有关详细信息,请参阅了解回压力For more information, see Understanding back pressure. 若要将队列数据库移动到不同的磁盘,请参阅更改队列数据库的位置To move the queue database to different disk, see Change the location of the queue database.
可用内存不足(例如,在配置为使用动态内存的虚拟机上安装的 Exchange)。Available memory is low (for example, Exchange installed on a virtual machine that's configured to use dynamic memory). 始终在 Exchange 虚拟机上使用静态内存。Always use static memory on Exchange virtual machines. 有关详细信息,请参阅Exchange 内存要求和建议For more information, see Exchange memory requirements and recommendations.
4.3.24.3.2 Service not available
or
Service not active
您已在侦听端口25的邮箱服务器上的传输(集线器)服务中配置自定义接收连接器。You've configured a custom Receive connector in the Transport (Hub) service on a Mailbox server that listens on port 25. 通常情况下,侦听端口25的自定义接收连接器属于邮箱服务器上的前端传输服务。Typically, custom Receive connectors that listen on port 25 belong in the Front End Transport service on the Mailbox server.
重要说明 Exchange 服务器组件处于非活动状态。Important Exchange server components are inactive. 您可以通过在 Exchange 命令行管理程序中运行以下命令来对Get-ServerComponent -Identity <ServerName>此进行确认:。You can confirm this by running the following command in the Exchange Management Shell: Get-ServerComponent -Identity <ServerName>.
若要重新启动所有非活动组件,请运行Set-ServerComponentState -Identity <ServerName> -Component ServerWideOffline -State Active -Requester Maintenance以下命令:。To restart all inactive components, run the following command: Set-ServerComponentState -Identity <ServerName> -Component ServerWideOffline -State Active -Requester Maintenance.
不兼容的传输代理(尤其是 Exchange 更新之后)。Incompatible transport agents (in particular, after an Exchange update). 在确定传输代理之后,请将其停用或卸载。After you identify the transport agent, disable it or uninstall it. 有关详细信息,请参阅排查传输代理故障For more information, see Troubleshoot transport agents.
4.4.14.4.1 Connection timed out 可能最终会自我纠正的暂时性网络问题。Transient network issues that might eventually correct themselves. Exchange 服务器会定期尝试连接到目标服务器以传递邮件。The Exchange server periodically tries to connect to the destination server to deliver the message. 出现多次故障后,邮件将以永久失败代码的 NDR 返回给发件人。After multiple failures, the message is returned to the sender in an NDR with a permanent failure code.
有关配置队列重试间隔和失败间隔的详细信息,请参阅配置邮件重试间隔、重新提交间隔和过期间隔For more information about configuring the queue retry and failure intervals, see Configure message retry, resubmit, and expiration intervals.
若要手动重试队列,请参阅重试队列To manually retry a queue, see Retry queues.
TCP 端口25上的防火墙或 Internet 服务提供商(ISP)限制。Firewall or Internet service provider (ISP) restrictions on TCP port 25.
4.4.24.4.2 Connection dropped 暂时的网络问题或服务器问题可能会最终纠正自己。Transient network issues or server problems that might eventually correct themselves. 发送服务器将重试邮件传递,并将生成更多的状态报告。The sending server will retry delivery of the message, and will generate further status reports.
已达到连接的邮件大小限制,或源 IP 地址的邮件提交率已超过配置的限制。The message size limit for the connection has been reached, or the message submission rate for the source IP address has exceeded the configured limit. 有关详细信息,请参阅邮件速率限制和限制For more information, see Message rate limits and throttling.
反垃圾邮件、SMTP 代理或防火墙配置问题将阻止来自 Exchange 服务器的电子邮件。Antispam, SMTP proxy, or firewall configuration issues are blocking email from the Exchange server.
4.4.74.4.7 Message delayed
or
Queue expired; Message expired
发送连接器配置问题。Send connector configuration issues. 例如:For example:
•发送连接器配置为在应使用智能主机路由时使用 DNS 路由,反之亦然。• The Send connector is configured to use DNS routing when it should be using smart host routing, or vice-versa. 使用 nslookup 验证是否可从 Exchange 服务器访问目标域。Use nslookup to verify that the destination domain is reachable from the Exchange server.
•发送连接器为 HELO 或 EHLO 请求提供的 FQDN 与您的 MX 记录中的主机名称不匹配(例如,mail.contoso.com)。• The FQDN that the Send connector provides to HELO or EHLO requests doesn't match the host name in your MX record (for example, mail.contoso.com). 某些邮件系统配置为比较这些值,以减少垃圾邮件的工作量。Some messaging systems are configured to compare these value in an effort to reduce spam. 发送连接器上的默认值为空,这意味着使用的是 Exchange server 的 FQDN (例如,exchange01.contoso.com)。The default value on a Send connector is blank, which means the FQDN of the Exchange server is used (for example, exchange01.contoso.com).
目标服务器上未启动邮箱传输传递服务(这将阻止邮件传递到邮箱)。The Mailbox Transport Delivery service isn't started on the destination server (which prevents the delivery of the message to the mailbox).
目标邮件系统中存在传输中性加密格式(TNEF)邮件(也称为 rtf 格式或 Outlook 中的 RTF)的问题。The destination messaging system has issues with Transport Neutral Encryption Format (TNEF) messages (also known as rich text format or RTF in Outlook). 例如,会议请求或包含嵌入到邮件正文中的图像的邮件。For example, meeting requests or messages with images embedded in the message body.
如果目标域使用发件人策略框架(SPF)检查邮件源,则您的域可能存在 SPF 问题(例如,您的 SPF 记录不包括您的域的所有电子邮件源)。If the destination domain uses the Sender Policy Framework (SPF) to check message sources, there may be SPF issues with your domain (for example, your SPF record doesn't include all email sources for your domain).

永久性传递故障Permanent delivery failures

增强状态代码Enhanced status code 说明Description 可能的原因和解决方案。Possible causes and solutions.
5.1.05.1.0 Sender denied 答复旧邮件或作为文件导出的邮件(重要的收件人属性可能已更改)。Replying to old messages, or messages that were exported as files (important recipient attributes might have changed). 验证收件人的电子邮件地址是否正确。Verify that the recipient's email address is correct.
联系人条目中的属性格式不正确或缺失。Malformed or missing attributes in contact entries.
发件人筛选被发件人筛选(直接)或发件人位于用户的阻止发件人列表中,并且将发件人筛选器代理配置为使用安全列表聚合。The sender is blocked by sender filtering (directly, or the sender is on a user's Blocked Senders list, and the Sender Filter agent is configured to use safelist aggregation. 有关详细信息,请参阅发件人筛选安全列表聚合For more information, see Sender filtering and Safelist aggregation.
5.1.15.1.1 RESOLVER.ADR.ExRecipNotFound; not found
or
User unknown
收件人的电子邮件地址不正确(收件人在目标邮件系统中不存在)。The recipient's email address is incorrect (the recipient doesn't exist in the destination messaging system). 验证收件人的电子邮件地址。Verify the recipient's email address.
您重新创建了已删除的邮箱,并且内部用户正在使用自动完成缓存中的旧条目来处理 Outlook 或 Outlook 网页版中的电子邮件(X. 500 值或收件人的LegacyExchangeDN值现在是不同的)。You recreated a deleted mailbox, and internal users are addressing email messages in Outlook or Outlook on the web using old entries in their autocomplete cache (the X.500 values or LegacyExchangeDN values for the recipient are now different). 告诉用户从自动完成缓存中删除条目,然后再次选择收件人。Tell users to delete the entry from their autocomplete cache and select the recipient again.
5.1.35.1.3 STOREDRV.Submit; invalid recipient address 收件人的电子邮件地址不正确(例如,它包含不受支持的字符或格式无效)。The recipient's email address is incorrect (for example, it contains unsupported characters or invalid formatting).
5.1.45.1.4 Recipient address reserved by RFC 2606 接收连接器拒绝包含 RFC 2606 中定义的顶级域的 SMTP 连接(. test、. 示例、. 无效或 localhost),此行为由set-receiveconnectorset-receiveconnector cmdlet 上的_RejectReservedTopLevelRecipientDomains_参数控制。Receive connectors reject SMTP connections that contain the top level domains defined in RFC 2606 (.test, .example, .invalid, or .localhost), This behavior is controlled by the RejectReservedTopLevelRecipientDomains parameter on the New-ReceiveConnector and Set-ReceiveConnector cmdlets.
5.1.55.1.5 Recipient address reserved by RFC 2606 接收连接器拒绝包含 RFC 2606 (example.com、example.net 或 example.org)中定义的第二层域的 SMTP 连接。Receive connectors reject SMTP connections that contain the second level domains defined in RFC 2606 (example.com, example.net, or example.org). 此行为由set-receiveconnectorset-receiveconnector cmdlet 上的_RejectReservedSecondLevelRecipientDomains_参数控制。This behavior is controlled by the RejectReservedSecondLevelRecipientDomains parameter on the New-ReceiveConnector and Set-ReceiveConnector cmdlets.
5.1.65.1.6 Recipient addresses in single label domains not accepted 接收连接器拒绝包含单个标签域的 SMTP 连接(例如,chris@contoso 而不是 chris@contoso.com)此行为由set-receiveconnectorset-receiveconnector cmdlet 上的_RejectSingleLabelRecipientDomains_参数控制。Receive connectors reject SMTP connections that contain single label domains (for example, chris@contoso instead of chris@contoso.com) This behavior is controlled by the RejectSingleLabelRecipientDomains parameter on the New-ReceiveConnector and Set-ReceiveConnector cmdlets.
5.1.75.1.7 Invalid address
or
Unknown sender address
发件人的电子邮件地址有问题。There's a problem with the sender's email address. 验证发件人的电子邮件地址。Verify the sender's email address.
5.1.85.1.8 Access denied, bad outbound sender 发件人超过了邮件速率限制(例如,应用程序服务器配置为通过 Exchange 中继大量邮件。The sender has exceeded a message rate limit (for example, an application server is configured to relay a large number of messages through Exchange. 有关详细信息,请参阅邮件速率限制和限制允许匿名中继在 Exchange 服务器上For more information, see Message rate limits and throttling and Allow anonymous relay on Exchange servers.
5.2.15.2.1 Content Filter agent quarantined this message 邮件被内容筛选功能隔离。The message was quarantined by content filtering. 若要配置内容筛选的例外,请参阅使用 Exchange 命令行管理程序配置内容筛选的收件人和发件人例外To configure exceptions to content filtering, see Use the Exchange Management Shell to configure recipient and sender exceptions for content filtering.
5.2.25.2.2 Mailbox full 收件人的邮箱已超过其存储配额,无法再接收新邮件。The recipient's mailbox has exceeded its storage quota and is no longer able to accept new messages. 有关配置邮箱配额的详细信息,请参阅配置邮箱的存储配额For more information about configuring mailbox quotas, see Configure storage quotas for a mailbox.
5.2.35.2.3 RESOLVER.RST.RecipSizeLimit; message too large for this recipient 邮件太大。The message is too large. 重新发送不带任何附件的邮件,或为收件人配置更大的邮件大小限制。Send the message again without any attachments, or configure a larger message size limit for the recipient. 有关详细信息,请参阅收件人限制For more information, see Recipient limits.
5.3.05.3.0 Too many related errors 邮件被确定为格式不正确,并已移动到病毒邮件队列。The message was determined to be malformed, and was moved to the poison message queue. 有关详细信息,请参阅队列类型For more information, see Types of queues.
5.3.25.3.2 STOREDRV.Deliver: Missing or bad StoreDriver MDB properties 您使用的是 ABP 路由代理,而收件人不是在其通讯簿策略(ABP)中指定的全局地址列表的成员。You're using the ABP Routing agent, and the recipient isn't a member of the global address list that's specified in their address book policy (ABP). 有关详细信息,请参阅使用 Exchange 命令行管理程序在 Exchange Server 中安装和配置通讯簿策略路由代理通讯簿策略For more information, see Use the Exchange Management Shell to install and configure the Address Book Policy Routing Agent and Address book policies in Exchange Server.
5.3.35.3.3 Unrecognized command 用于内部邮件流的接收连接器缺少所需的 Exchange Server 身份验证机制。Receive connectors that are used for internal mail flow are missing the required Exchange Server authentication mechanism. 有关接收连接器上的身份验证的详细信息,请参阅接收连接器身份验证机制For more information about authentication on Receive connectors, see Receive connector authentication mechanisms.
5.3.45.3.4 Message size exceeds fixed maximum message size 邮件太大。The message is too large. 源或目标邮件系统可能会生成此错误。This error can be generated by the source or destination messaging system. 重新发送不带任何附件的邮件,或配置更大的邮件大小限制。Send the message again without any attachments, or configure a larger message size limit. 有关详细信息,请参阅Exchange Server 中的邮件大小限制For more information, see Message size limits in Exchange Server.
5.3.55.3.5 System incorrectly configured 检测到邮件循环。A mail loop was detected. 验证接收连接器上的fqdn属性与组织中的邮件流中使用的另一台服务器、服务或设备的 fqdn 不匹配(默认情况下,接收连接器使用 Exchange 服务器的 fqdn)。Verify that the FQDN property on the Receive connector doesn't match the FQDN of another server, service, or device that's used in mail flow in your organization (by default, the Receive connector uses the FQDN of the Exchange server).
5.4.45.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain Exchange 服务器上存在 DNS 或网络适配器配置问题。There's a DNS or network adapter configuration issue on the Exchange server.
•通过在 Exchange 命令行管理程序中运行以下命令来验证 Exchange 的内部和外部 DNS 查找设置:• Verify the internal and external DNS lookup settings for the Exchange by running these commands in the Exchange Management Shell:
Set-transportservice |格式-列表名称、ExternalDNS*、InternalDNS*Get-TransportService | Format-List Name,ExternalDNS*,InternalDNS*
Set-frontendtransportservice |格式-列表名称、ExternalDNS*、InternalDNS*Get-FrontEndTransportService | Format-List Name,ExternalDNS*,InternalDNS*
您可以使用set-transportserviceset-frontendtransportservice cmdlet 上_的* InternalDNS_和_ExternalDNS* _参数配置这些设置。You can configure these settings by using the InternalDNS* and ExternalDNS* parameters on the Get-TransportService and Get-FrontEndTransportService cmdlets.
默认情况下,这些设置由发送连接器使用( _UseExternalDNSServersEnabled_参数值的默认值为$false)。By default, these settings are used by Send connectors (the default value of the UseExternalDNSServersEnabled parameter value is $false).
•在 Exchange 服务器的操作系统中检查网络适配器的优先级(顺序)。• Check the priority (order) of the network adapters in the operating system of the Exchange server.
5.4.65.4.6 Hop count exceeded - possible mail loop 配置错误导致发生电子邮件循环。A configuration error has caused an email loop. 默认情况下,在电子邮件循环的20次迭代之后,Exchange 将中断循环并生成 NDR。By default, after 20 iterations of an email loop, Exchange interrupts the loop and generates an NDR.
验证收件人和发件人的收件箱规则或收件人邮箱上的转发规则不会导致此问题(邮件生成一封邮件,这将生成另一封邮件,并且该进程将无限期继续)。Verify that Inbox rules for the recipient and sender, or forwarding rules on the recipient 's mailbox aren't causing this (the message generates a message, which generates another message, and the process continues indefinitely).
验证邮箱在 Active Directory 中没有targetAddress属性值(此属性对应于 Exchange 中的邮件用户的_ExternalEmailAddress_参数)。Verify the mailbox doesn't have a targetAddress property value in Active Directory (this property corresponds to the ExternalEmailAddress parameter for mail users in Exchange).
如果删除 Exchange 服务器,或修改与邮件路由邮件流相关的设置,请务必重新启动 Microsoft Exchange 传输服务和 Exchange 前端传输服务。If you remove Exchange servers, or modify settings related to mail routing an mail flow, be sure to restart the Microsoft Exchange Transport and Exchange Frontend Transport services.
5.5.25.5.2 Send hello first SMTP 命令不按顺序发送(例如,服务器先发送 SMTP 命令(如 AUTH 或 MAIL),然后再使用 EHLO 命令标识自己。SMTP commands are sent out of sequence (for example, a server sends an SMTP command like AUTH or MAIL FROM before identifying itself with the EHLO command). 建立与邮件传递服务器的连接后,第一个 SMTP 命令必须始终是 EHLO 或 HELO。After establishing a connection to a messaging server, the first SMTP command must always be EHLO or HELO.
5.5.35.5.3 Too many recipients 邮件的 "收件人"、"抄送" 和 "密件抄送" 行上的收件人总数超过了组织、接收连接器或发件人的单个邮件中允许的收件人总数。The combined total of recipients on the To, Cc, and Bcc lines of the message exceeds the total number of recipients allowed in a single message for the organization, Receive connector, or sender. 有关详细信息,请参阅Exchange Server 中的邮件大小限制For more information, see Message size limits in Exchange Server.
5.7.15.7.1 Unable to relay
or
Client was not authenticated
您有一个尝试通过 Exchange 中继邮件的应用程序服务器或设备。You have an application server or device that's trying to relay messages through Exchange. 有关详细信息,请参阅允许匿名中继在 Exchange 服务器上For more information, see Allow anonymous relay on Exchange servers.
收件人配置为仅接受来自已通过身份验证的邮件(通常为内部发件人)的邮件。The recipient is configured to only accept messages from authenticated (typically, internal) senders. 有关详细信息,请参阅配置邮箱的邮件传递限制For more information, see Configure message delivery restrictions for a mailbox.
5.7.35.7.3 Cannot achieve Exchange Server authentication
or
Not Authorized
防火墙或其他设备阻止了 Exchange Server 身份验证所需的扩展 SMTP 命令(X-EXPS)。A firewall or other device is blocking the Extended SMTP command that's required for Exchange Server authentication (X-EXPS).
内部电子邮件流量通过未配置为使用 Exchange Server 身份验证方法的连接器进行流动。Internal email traffic is flowing through connectors that aren't configured to use the Exchange Server authentication method . 验证任何自定义接收连接器上的远程 IP 地址范围。Verify the remote IP address ranges on any custom Receive connectors.
5.7.9005.7.900
toto
5.7.9995.7.999
Delivery not authorized, message refused 邮件已被邮件流规则(也称为传输规则)拒绝。The message was rejected by a mail flow rule (also known as a transport rule). 当规则配置为拒绝邮件(否则,使用的默认代码为5.7.1)时,此增强状态代码范围可用。This enhanced status code range is available when the rule is configured to reject messages (otherwise, the default code that's used is 5.7.1). 有关详细信息,请参阅Exchange Server 中的邮件流规则操作For more information, see Mail flow rule actions in Exchange Server.