内容转换跟踪Content conversion tracing

适用于:Exchange Server 2013Applies to: Exchange Server 2013

内容转换跟踪将捕获发生在 Microsoft Exchange Server 2013 邮箱服务器上入站和出站邮件上邮箱传输服务执行的 MAPI 内容转换中的失败。Content conversion tracing captures failures in the MAPI content conversion that's performed by the Mailbox Transport service on inbound and outbound messages on a Microsoft Exchange Server 2013 Mailbox server.

邮箱服务器上邮箱传输服务负责在邮箱收件人之间发送和发送的邮件的内容转换。The Mailbox Transport service on a Mailbox server is responsible for the content conversion of messages sent to and from mailbox recipients. 具体来说,邮箱传输提交服务将邮箱用户的出站邮件从 MAPI 转换为 MIME。Specifically, the Mailbox Transport Submission service converts outbound messages from mailbox users from MAPI to MIME. 邮箱传输传递服务将邮箱用户的入站邮件从 MIME 转换为 MAPI。The Mailbox Transport Delivery service converts inbound messages for mailbox users from MIME to MAPI. 内容转换跟踪负责捕获这些 MAPI 转换失败。Content conversion tracing is responsible for capturing these MAPI conversion failures.

邮箱服务器上传输服务中的分类程序负责向外部收件人发送的所有邮件的内容转换。The categorizer in the Transport service on a Mailbox server is responsible for the content conversion of all messages sent to external recipients. 内容转换跟踪不会捕获传输服务中的分类程序在转换发送到外部收件人的邮件时遇到的任何内容转换失败。Content conversion tracing doesn't capture any content conversion failures that the categorizer in the Transport service encounters as it converts messages sent to external recipients.

配置内容转换跟踪Configure content conversion tracing

内容转换跟踪由 Exchange 命令行管理程序中 Set-TransportServiceSet-MailboxTransportService cmdlet 中的以下参数控制:Content conversion tracing is controlled by the following parameters in the Set-TransportService and Set-MailboxTransportService cmdlets in the Exchange Management Shell:

  • ContentConversionTracingEnabled: 此参数启用或禁用邮箱服务器上传输服务或邮箱服务器上邮箱传输服务中的内容转换跟踪。ContentConversionTracingEnabled: This parameter enables or disables content conversion tracing in the Transport service on the Mailbox server, or in the Mailbox Transport service on the Mailbox server. 此参数的有效值为 和 $true $falseValid values for this parameter are $true and $false. 默认值为 $falseThe default value is $false. 如果您的 Exchange组织包含多个邮箱服务器,则必须在每个邮箱服务器上启用内容转换跟踪。If your Exchange organization contains multiple Mailbox servers, you must enable content conversion tracing on each Mailbox server.

  • PipelineTracingPath:虽然此参数与管道跟踪相关联,但它还指定内容转换跟踪文件的根位置。PipelineTracingPath: Although this parameter is associated with pipeline tracing, it also specifies the root location of the content conversion tracing files. 传输服务中的默认位置是 %ExchangeInstallPath%TransportRoles\Logs\Hub\PipelineTracingThe default location in the Transport service is %ExchangeInstallPath%TransportRoles\Logs\Hub\PipelineTracing. 邮箱传输服务中的默认位置是 %ExchangeInstallPath%TransportRoles\Logs\Mailbox\PipelineTracing 。该路径必须是计算机的本地Exchange路径。The default location in the Mailbox Transport service is %ExchangeInstallPath%TransportRoles\Logs\Mailbox\PipelineTracing.The path must be local to the Exchange computer.

内容转换在 ContentConversionTracing PipelineTracingPath 参数指定的路径中创建一个名为 的文件夹。Content conversion creates a folder named ContentConversionTracing in the path specified by the PipelineTracingPath parameter. 在 文件夹中 ContentConversionTracing ,内容转换创建两个子文件夹: InboundFailuresOutboundFailuresIn the ContentConversionTracing folder, content conversion creates two subfolders: InboundFailures and OutboundFailures. InboundFailures 文件夹包含入站邮件内容转换失败的信息。The InboundFailures folder contains the information from inbound message content conversion failures. OutboundFailures 文件夹包含出站邮件内容转换失败的信息。The OutboundFailures folder contains the information from outbound message content conversion failures.

文件夹或文件夹中所有文件的最大大小为 InboundFailures 128 MB (OutboundFailures MB) 。The maximum size for all the files in the InboundFailures folder or the OutboundFailures folder is 128 megabytes (MB). 内容转换跟踪不使用循环日志记录来根据文件的年龄或大小删除旧文件。Content conversion tracing doesn't use circular logging to remove old files based on the age or size of the files. 一旦达到文件夹的最大大小,内容转换跟踪就会停止向该文件夹写入信息。As soon as the maximum size for a folder is reached, content conversion tracing stops writing information to the folder. 如果要确保不超出最大文件夹大小限制,可以创建定期将内容转换跟踪文件移动到其他位置的计划任务。If you want to make sure that the maximum folder size limits aren't exceeded, you can create a scheduled task that periodically moves the content conversion tracing files to a different location.

在内容转换跟踪中需要对文件夹和子文件夹具有以下权限:The permissions required on the folders and subfolders used in content conversion tracing are as follows:

  • 管理员:完全控制Administrators: Full Control

  • 网络服务:完全控制Network Service: Full Control

  • 系统:完全控制System: Full Control

警告

内容转换跟踪将复制电子邮件的完整内容。Content conversion tracing copies the complete contents of email messages. 为了避免泄露机密信息,您需要对内容转换跟踪文件的位置设置适当的安全权限。To avoid the unwanted disclosure of confidential information, you need to set appropriate security permissions on the location of the content conversion tracing files.

内容转换跟踪工作原理How content conversion tracing works

当入站邮件的内容转换失败时,会向邮件发件人 (状态代码为 5.6.0) DSN 邮件的传递状态通知。When the content conversion of an inbound message fails, a delivery status notification (DSN) that has the status code 5.6.0 is sent to the message sender. 如果启用内容转换跟踪,则生成 5.6.0 DSN 邮件时将记录失败信息。If content conversion tracing is enabled, the failure information is recorded at the time that the 5.6.0 DSN message is generated. 每个内容转换错误都会生成两个单独的文件。Each content conversion error generates two separate files.

将入站邮件从 MIME 转换为 MAPI 时发生的内容转换错误会在 InboundFailures 文件夹中生成以下两个文件:A content conversion error that occurs when an inbound message is converted from MIME to MAPI generates the following two files in the InboundFailures folder:

  • <GUID> .eml: 此文件包含文本格式的失败邮件。<GUID>.eml: This file contains the failed message in text format.

  • <GUID>.txt: 此文件包含异常描述、转换结果、转换选项以及邮箱传输服务对全部邮件施加的邮件大小限制。<GUID>.txt: This file contains the exception description, conversion results, conversion options, and message size limits imposed on all messages by the Mailbox Transport service.

将出站邮件从 MAPI 转换为 MIME 时发生的内容转换错误会在 OutboundFailures 文件夹中生成以下两个文件:A content conversion error that occurs when an outbound message is converted from MAPI to MIME generates the following two files in the OutboundFailures folder:

  • <GUID> .msg: 此文件包含以 Microsoft 邮件格式Outlook失败的邮件。<GUID>.msg: This file contains the failed message in the Microsoft Outlook message format.

  • <GUID>.txt: 此文件包含异常描述、转换结果、转换选项以及存储驱动程序对全部邮件施加的邮件大小限制。<GUID>.txt: This file contains the exception description, conversion results, conversion options, and message size limits imposed on all messages by the store driver.

占位符 <GUID> 在两个文件名中均相同。The placeholder <GUID> is the same in both file names. 每个内容转换错误都会生成一个不同的 GUID,用于对应邮件和文本文件的文件名中。Each content conversion error generates a different GUID that's used in the file names of the corresponding message and text files. 文件名中使用的 GUID 示例为 038b930e-61fd-4bfd-b9b4-0374c18b73f7An example of a GUID that's used in the file names is 038b930e-61fd-4bfd-b9b4-0374c18b73f7.

内容转换跟踪的注意事项Considerations for content conversion tracing

您可以将内容转换跟踪保持启用状态,以主动监视。You can leave content conversion tracing enabled for proactive monitoring. 或者,您可以启用内容转换跟踪来排除特定故障事件的故障。Or, you can enable content conversion tracing to troubleshoot a specific failure event. 通常,可以通过要求 5.6.0 DSN 邮件的收件人重新发送原始邮件来重现入站内容转换失败。You can usually reproduce inbound content conversion failures by asking the recipient of the 5.6.0 DSN message to resend the original message.

入站内容转换失败最为常见。Inbound content conversion failures are the most common. 入站内容转换错误的一些原因包括:Some of the reasons for inbound content conversion errors include the following:

  • 违反邮件大小限制:这些邮件大小限制由邮箱传输服务施加,以帮助防止 DoS (拒绝) 。Violations of message size limits: These message size limits are imposed by the Mailbox Transport service to help prevent denial of service attacks (DoS). 这些邮件限制在邮件.txt <GUID> 列出。These message limits are listed in the <GUID>.txt file. 这些邮件限制包括:These message limits include the following:

    • MaxMimeTextHeaderLength: 此限制指定可在 MIME 头中使用的最大文本字符数。MaxMimeTextHeaderLength: This limit specifies the maximum number of text characters that can be used in a MIME header. 值为 2000。The value is 2000.

    • MaxMimeSubjectLength: 此限制指定可在主题行中使用的最大文本字符数。MaxMimeSubjectLength: This limit specifies the maximum number of text characters that can be used in the subject line. 值为 255。The value is 255.

    • MSize: 此限制指定最大邮件大小。MSize: This limit specifies the maximum message size. 值为 2147483647 字节。The value is 2147483647 bytes.

    • MaxMimeRecipients: 此限制指定"收件人"、"抄送"和"密件抄送"字段中允许的收件人总数。MaxMimeRecipients: This limit specifies the total number of recipients allowed in the To, Cc, and Bcc fields. 值为 12288。The value is 12288.

    • MaxRecipientPropertyLength: 此限制指定可在收件人描述中使用的最大文本字符数。MaxRecipientPropertyLength: This limit specifies the maximum number of text characters that can be used in a recipient description. 值为 1000。The value is 1000.

    • MaxBodyPartsTotal: 此限制指定可在 MIME 多部分邮件中使用的邮件部分的最大数量。MaxBodyPartsTotal: This limit specifies the maximum number of message parts that can be used in a MIME multipart message. 值为 250。The value is 250.

    • MaxEmbeddedMessageDepth: 此限制指定邮件中可以存在的最大转发邮件数。MaxEmbeddedMessageDepth: This limit specifies the maximum number of forwarded messages that can exist in a message. 值为 30。The value is 30.

      有关在邮件服务器或边缘传输服务器上传输服务中使用的可配置邮件大小限制的详细信息,请参阅邮件大小限制For more information about configurable message size limits used in the Transport service on Mailbox servers or on Edge Transport servers, see Message size limits.

  • 将入站 iCalendar 邮件转换为会议请求失败:RFC 2445 将 iCalendar 定义为日历数据交换的标准。Failure to convert an inbound iCalendar message to a meeting request: RFC 2445 defines iCalendar as a standard for calendar data exchange. 转换失败的特定原因包括:Specific causes of the conversion failure include the following:

    • 发送代理未正确使用 iCalendar。Incorrect use of iCalendar by the sending agent.

    • Outlook 或 Exchange 日历架构不支持 iCalendar 结构。Constructs of iCalendar that can't be supported by the Outlook or Exchange calendar schema.

    iCalendar 的转换失败不会使发件人收到 5.6.0 DSN 邮件。Conversion failures of iCalendar don't result in the sender receiving a 5.6.0 DSN message. 相反,邮件会随包含 iCalendar 邮件正文的附加 .ics 文件一起传递。Instead, the message is delivered with an attached .ics file that contains the iCalendar message body.

  • MIME 邮件格式不正确导致的失败:未经请求的商业电子邮件或垃圾邮件在邮件头中可能有格式错误,如收件人描述中的引号不匹配。Failures caused by badly formatted MIME messages: Unsolicited commercial email or spam messages may have formatting errors in the message header, such as unmatched quotation marks in recipient descriptions. MIME 邮件格式不正确导致的失败次数要小得多,被视为错误。A much smaller number of failures caused by badly formatted MIME messages are considered bugs.

出站内容转换失败比入站失败低得多。Outbound content conversion failures are much less common than inbound failures. 当出站失败时,通常是由代码错误Exchange损坏的邮件内容导致的。When outbound failures occur, they are usually caused by Exchange code bugs or corrupted message content.