How to enable SMTP logs on Exchange edge transport server 2013

Hello all,

Could you clarify which command is useful now to enable SMTP logs on Edge transport 2013

I Tried this one, but nothing happens:

Set-TransportServer Edge01 -ConnectivityLogEnabled $true -ConnectivityLogPath "C:\SMTP Logs"

Thank you in advance

March 16th, 2015 1:18am

The cmdlet you've issued will only log details about the outbound connection activity - take a look here. It won't get you details about individual SMTP messages, which what you're after I believe. Instead, you should be using Protocol Logging which will yield the information required. Note that by contrast to Connectivity Logging - which is configured at server level -, Protocol Logging is enabled at connector level (send/receive). The exact cmdlets are here.
Free Windows Admin Tool Kit Click here and download it now
March 16th, 2015 1:45am

Thank you very much,

so it basically means that I need to use the following command:

Set-MailboxTransportService Mailbox01 -ReceiveProtocolLogPath "C:\SMTP Protocol Logs\Receive.log"

Where Mailbox01 is my Edge transport server. Am I right?

March 16th, 2015 2:07am

I believe it's Set-TransportService that should be used against the Edge server to configure the log path. For enabling the protocol logging to 'Verbose' see the section Use the Shell to enable or disable protocol logging on a Send connector or a Receive connector" of the URL I've pasted above - https://technet.microsoft.com/en-us/library/bb124531%28v=exchg.150%29.aspx.

Free Windows Admin Tool Kit Click here and download it now
March 16th, 2015 2:16am

Ok, So I used Set-ReceiveConnector "Connection from Contoso.com" -ProtocolLoggingLevel Verbose command on Exchange server.  Where exactly do I need to find the logs on which server?

March 16th, 2015 8:23am

Do a Get-TransportService <EdgeServer> | fl ReceiveProtocolLogPath, SendProtocolLogPath.

The receive connector is defined per server, while the send connector is defined org-wide. For the latter, check on the servers marked as source transport agents against the respective send connectors.

Free Windows Admin Tool Kit Click here and download it now
March 16th, 2015 9:44am

After the command I got this:

ReceiveProtocolLogPath :
SendProtocolLogPath    :

So I guess it means there is no path to my edge transport server logs.

Tried the same command and pointed Exchange server instead of Edge transport andd got a path to the log files.

I still don't understand which command is useful to activate the logging


  • Edited by Santarem01 Monday, March 16, 2015 10:08 AM
March 16th, 2015 10:08am

Hi,

According to your description, I understand that you want to enable SMTP log for Edge Server.
If I misunderstand your concern, please do not hesitate to let me know.

Attention: do not perform protocol log on an Edge Transport server that has been subscribed to the Exchange organization by using EdgeSync. Instead, make the changes in the Transport service on the Mailbox server. The changes are then replicated to the Edge Transport server next time EdgeSync synchronization occurs.
We can use Set-SendConnector and Set-ReceiveConnector with ProtocolLoggingLevel parameter to enable or disable protocol log for a send or receive connector, for example:
Set-ReceiveConnector "Connection from Contoso.com" -ProtocolLoggingLevel Verbose
Also, we can modify the path of log location. More details about Protocol logging in Exchange 2013, please refer to:
https://technet.microsoft.com/en-us/library/aa997624(v=exchg.150).aspx

For your reference, the default location of relevant log in Edge Server 2010:
Message tracking log: C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\MessageTracking
Connectivity log: C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\Connectivity
Send protocol log: C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpSend
Receive protocol log: C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpReceive

Thanks

Free Windows Admin Tool Kit Click here and download it now
March 17th, 2015 9:05am

Thank you for the information. Everything is okay now :-)
March 20th, 2015 5:01am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics