Shulou(Shulou.com)06/02 Report--

The sending and receiving of Exchange mail are carried out through the Exchange transport server, and a series of actions are carried out in the transport service. In daily management, if a lot of Transport Agent are enabled on Exchange, it is very troublesome to find out the reason why a message is blocked or deleted when troubleshooting. The usual practice is to look at the transport agent log on Exchange. Some traces can be found in the agent log, but sometimes the specific reason can not be found. Before I was dealing with a problem, I asked to find out why the mail that received part of the domain name was marked as spam. I could not find the reason by looking at the transport agent log, because the log through each agent in the transport agent log is now recorded as the agent policy is False, it is best to disable Transport Agent one by one, and it is best to find the corresponding transport agent.

OK, now here's a faster way to track mail delivery. In Exchange, messages need to be filtered or filtered by a delivery agent before they can be delivered. Exchange provides a feature, pipeline tracing, that can be used to track the flow of messages sent by a specific sender on the transport service. Enabling pipeline tracing generates a snapshot of messages at various stages of the transport service to a specific file for administrator analysis. (for more information, please refer to https://technet.microsoft.com/zh-cn/library/bb125018(v=exchg.150).aspx)

The following list describes the mail snapshot files created:

Files such as Original.eml contain the original, unmodified content of the e-mail message before it encounters any SMTP events or transport agents.

Files such as Routingnnnn.eml contain content when e-mail encounters transport SMTP events and transport agents registered on those events during the classified portion of the transport service. The placeholder nnnn represents an integer value that begins with 0001. This value is incremented for each SMTP event and the transport agents registered on those events in the order in which these events and agents act on the message. The Mailbox Transport delivery service does not generate these Routing snapshot files.

Files such as SmtpReceivennnn.eml contain content when an e-mail message encounters OnEndofData and OnEndOfHeaders SMTP events and transport agents registered on those events during the SMTP receive portion of the transport service or mailbox transport delivery service. The placeholder nnnn represents an integer value that begins with 0001. This value is incremented for each SMTP event and the transport agents registered on those events in the order in which these events and agents act on the message.

Before enabling the pipeline tracing feature, we need to understand which scenarios it applies to; we can't just turn it on, because it consumes the server's resources and takes up a certain amount of disk space. If you have the following circumstances, you can consider temporarily enabling pipeline tracing, and you should close it immediately after fetching the data.

1) when excluding the message, you need to analyze which transport agent has operated on the message.

2) when a custom transport agent is enabled or created, you need to verify that the transport agent is in effect as intended.

The following describes how to enable the pipeline tracing feature.

First, enable the pipeline tracing function

1. Use the following command to view the current pipeline tracing configuration of the current Exchange server, so as to record the default configuration of the server and facilitate the restoration of the default configuration later.

Get-TransportService | fl name,*pip*

Get-MailboxTransportService | fl name,*pip*

2. Enable the PipelineTracing function of the transport service, and make the log directory and the specific sender at the same time.

Get-TransportService | Set-TransportService-PipelineTracingEnabled $true-PipelineTracingPath "c:\ dump\"-PipelineTracingSenderAddress test@contoso.com

3. Enable the PipelineTracing function of mailbox transfer service, and make log directory and specific sender at the same time.

Get-MailboxTransportService | Set-MailboxTransportService-PipelineTracingEnabled $true-PipelineTracingPath "c:\ dump"-PipelineTracingSenderAddress test@contoso.com

4. After PipelineTracing is enabled, there is no need to restart the transport service to take effect. Let's test it next. Snapshot data has been produced in the corresponding directory.

5. View the data in the corresponding file.

6. You can see the snapshot data collected.

II. Disable pipeline tracing function

Get-TransportService | Set-TransportService-PipelineTracingEnabled $false

Get-MailboxTransportService | Set-MailboxTransportService-PipelineTracingEnabled $false

The following command restores pipeline tracing to its default settings.

Get-TransportService | Set-TransportService-PipelineTracingEnabled $false-PipelineTracingPath "C:\ Program Files\ Microsoft\ Exchange Server\ V15\ TransportRoles\ Logs\ Hub\ PipelineTracing"-PipelineTracingSenderAddress $null

Get-MailboxTransportService | Set-MailboxTransportService-PipelineTracingEnabled $false-PipelineTracingPath "C:\ Program Files\ Microsoft\ Exchange Server\ V15\ TransportRoles\ Logs\ Mailbox\ PipelineTracing"-PipelineTracingSenderAddress $null

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.