Where does Exchange Server 2016, Exchange Server 2019, or Exchange Server Subscription Edition (SE) store its Receive Connector and Send Connector SMTP protocol logs (RECVyyyymmdd-n.log and SENDyyyymmdd-n.log), and how do you filter thousands of interleaved SMTP sessions to isolate a single failed email or TLS handshake?
In this complete reference guide, we list the exact default folder paths for every Exchange transport service (Front End Transport, Hub Transport, Mailbox Transport Delivery/Submission, and Edge Transport), explain each CSV field in the log file, and provide a ready-to-run PowerShell script to reconstruct full SMTP conversations by session-id or remote IP address.
Architecture: How SMTP Protocol Logs Map to Exchange Transport Services
\SmtpReceive\RECV*.log(External & Client SMTP)\SmtpSend\SEND*.log(Proxy to Hub Transport)- Enabled by default on
Default Frontend
\SmtpReceive\RECV*.log(Port 2525 internal)\SmtpSend\SEND*.log(Internet & Hybrid Send Connectors)- Key folder for outbound TLS / 550 errors
\SmtpReceive\Delivery\SmtpSend\Submission\SmtpSend\Delivery(Side-effect messages)
Default SMTP Protocol Log Locations in Exchange 2016, 2019 & SE
By default, %ExchangeInstallPath% resolves to C:\Program Files\Microsoft\Exchange Server\V15\ across Exchange Server 2016, Exchange Server 2019, and Exchange Server Subscription Edition (SE).
| Transport Service | Connector Direction | Default Protocol Log Directory Path |
|---|---|---|
| Front End Transport Service (Inbound Port 25/587) | Receive Connectors | %ExchangeInstallPath%TransportRoles\Logs\FrontEnd\ProtocolLog\SmtpReceive |
| Front End Transport Service | Send Connectors | %ExchangeInstallPath%TransportRoles\Logs\FrontEnd\ProtocolLog\SmtpSend |
| Transport Service (Hub) (Outbound Send Connectors & Port 2525) | Receive Connectors | %ExchangeInstallPath%TransportRoles\Logs\Hub\ProtocolLog\SmtpReceive |
| Transport Service (Hub) | Send Connectors | %ExchangeInstallPath%TransportRoles\Logs\Hub\ProtocolLog\SmtpSend |
| Mailbox Transport Delivery Service | Receive Connectors | %ExchangeInstallPath%TransportRoles\Logs\Mailbox\ProtocolLog\SmtpReceive\Delivery |
| Mailbox Transport Submission Service | Send Connectors | %ExchangeInstallPath%TransportRoles\Logs\Mailbox\ProtocolLog\SmtpSend\Submission |
| Mailbox Transport (Side-Effect Messages) | Send Connectors | %ExchangeInstallPath%TransportRoles\Logs\Mailbox\ProtocolLog\SmtpSend\Delivery |
| Edge Transport Server | Receive Connectors | %ExchangeInstallPath%TransportRoles\Logs\Edge\ProtocolLog\SmtpReceive |
| Edge Transport Server | Send Connectors | %ExchangeInstallPath%TransportRoles\Logs\Edge\ProtocolLog\SmtpSend |
Where is my Outbound Send Connector log? Organization Send Connectors (such as your outbound Internet Send Connector orOutbound to Office 365Hybrid Send Connector) execute inside the Transport (Hub) service, so their logs are always located under%ExchangeInstallPath%TransportRoles\Logs\Hub\ProtocolLog\SmtpSend.
Conversely, external inbound mail arriving on TCP port 25 hits the Front End Transport service first, so look in%ExchangeInstallPath%TransportRoles\Logs\FrontEnd\ProtocolLog\SmtpReceive.
Log File Naming Convention & CSV Header Structure
- Send Connector Log Files:
SENDyyyymmdd-nnnn.log(e.g.,SEND20261110-1.log) - Receive Connector Log Files:
RECVyyyymmdd-nnnn.log(e.g.,RECV20261110-1.log)
Each protocol log file starts with 5 metadata header lines before the comma-separated records:
#Software:Microsoft Exchange Server#Version:15.01.nnnn.nnn(Exchange 2016) or15.02.nnnn.nnn(Exchange 2019 / Exchange Server SE)#Log-Type:SMTP Receive Protocol LogorSMTP Send Protocol Log#Date:ISO 8601 UTC timestamp (yyyy-mm-ddThh:mm:ss.fffZ) when the log file was created#Fields:date-time,connector-id,session-id,sequence-number,local-endpoint,remote-endpoint,event,data,context

Complete Field Reference in Exchange Protocol Logs
| Field Name | Description |
|---|---|
date-time | UTC timestamp of the SMTP protocol event in ISO 8601 format (yyyy-mm-ddThh:mm:ss.fffZ). |
connector-id | Name/identity of the Receive or Send Connector associated with the SMTP session (e.g., EXCH01\Default Frontend EXCH01). |
session-id | Unique 16-character hexadecimal GUID assigned to a single TCP SMTP connection. All lines belonging to the same conversation share the same session-id. |
sequence-number | Counter starting at 0 and incrementing for each event within the same session-id. |
local-endpoint | Local Exchange Server IP address and TCP port (IP:Port). |
remote-endpoint | Remote peer IP address and TCP port (IP:Port). |
event | Single-character symbol indicating the event type: • + : Connect• - : Disconnect• > : Send (command/response sent by this server)• < : Receive (command/response received from remote server)• ** * : Information (TLS certificate thumbprint, cipher suite, authentication username, or routing context) |
data | The actual SMTP verb or response payload (e.g., EHLO mail.contoso.com, 250 2.1.0 Sender OK, 550 5.7.1 Unable to relay). |
context** | Additional diagnostic context (such as TLS certificate subject/issuer, SetSessionPermissions, or disconnect reason). |
PowerShell Script: Parse Protocol Logs & Reconstruct Full SMTP Sessions
Because an Exchange server handles dozens of concurrent SMTP connections simultaneously, lines from different sessions are interleaved in the .log file. Use this PowerShell function to strip the # header lines, parse the CSV columns cleanly, and reconstruct complete SMTP sessions by sender/recipient, error code, or remote IP address:
function Get-ExchangeSmtpProtocolSession {
param(
[string]$LogDirectory = "$env:ExchangeInstallPath\TransportRoles\Logs\FrontEnd\ProtocolLog\SmtpReceive",
[string]$SearchText = "550 ", # e.g., '550 ', '451 ', 'STARTTLS', or a sender/recipient email
[int]$NewestFiles = 5
)
$Headers = @("DateTime","ConnectorId","SessionId","SequenceNumber","LocalEndpoint","RemoteEndpoint","Event","Data","Context")
$LogFiles = Get-ChildItem -Path $LogDirectory -Filter "*.log" |
Sort-Object LastWriteTime -Descending |
Select-Object -First $NewestFiles
$AllRows = foreach ($File in $LogFiles) {
Get-Content $File.FullName |
Where-Object { $_ -notmatch '^#' -and $_.Trim() -ne '' } |
ConvertFrom-Csv -Header $Headers
}
# Find all unique SessionIds that contain the SearchText in Data or Context
$MatchingSessionIds = $AllRows |
Where-Object { $_.Data -match $SearchText -or $_.Context -match $SearchText -or $_.RemoteEndpoint -match $SearchText } |
Select-Object -ExpandProperty SessionId -Unique
# Return the complete chronological SMTP conversation for every matching SessionId
$AllRows |
Where-Object { $_.SessionId -in $MatchingSessionIds } |
Sort-Object SessionId, { [int]$_.SequenceNumber } |
Select-Object DateTime, SessionId, SequenceNumber, RemoteEndpoint, Event, Data, Context
}
# Example 1: Reconstruct full SMTP conversations for any session that returned a 550 rejection
Get-ExchangeSmtpProtocolSession -SearchText "550 " | Format-Table -AutoSize
# Example 2: Inspect outbound Hub Send Connector TLS negotiation details
Get-ExchangeSmtpProtocolSession `
-LogDirectory "$env:ExchangeInstallPath\TransportRoles\Logs\Hub\ProtocolLog\SmtpSend" `
-SearchText "STARTTLS" | Format-Table -AutoSize