Windows 7 / Getting Started

---

POP

POP configuration is almost exactly the same as IMAP configuration. By default, the POP protocol is neither enabled nor running on Exchange Server 2010. To enable the service, run the following PowerShell command:

Set-Service MSExchangePOP3 -StartupType Automatic

However, before you start the service, you may want to review the logon authentication method required. The default method requires TLS to be enabled (that is, POP over TLS). While many modern POP clients support this, if you simply want to test, you can change that to basic authentication. The PowerShell command for that looks like this:

Set-PopSettings -LoginType PlainTextLogin

And finally, to enable POP logging, you execute the following PowerShell command:

Set-PopSettings -ProtocolLogEnabled $true

You are now ready to start the IMAP service:

Start-Service MSExchangePOP3

With the exception of setting the ProtocolLogEnabled value to $true, all these items can also be done in the appropriate GUI.

POP log files are CSV format log files in plaintext. They are located in C:\Program Files\Microsoft\Exchange Server\V14\Logging\Pop3.

In comparison to the contents of the POP log file from prior versions of Exchange, the presence of the Session-id and Sequence-number fields are noteworthy. The session-id value is guaranteed to be unique, and the sequence-number value identifies the order of commands. They are important when you have many users using the service at the same time, as the input and output from the sessions are interleaved in the log files and can be quite confusing.

Transport

By far in Exchange Server 2010, the most logging choices revolve around SMTP logging on the Transport server. However, most of this logging cannot be configured using the Transport server properties dialog. What can be configured for logging on the Transport server.

PowerShell provides a much richer set of logging options:

[PS] C:\>get-transportserver | fl *Log*

ConnectivityLogEnabled 			: True
ConnectivityLogMaxAge 			: 30.00:00:00
ConnectivityLogMaxDirectorySize 	: 250 MB (262,144,000 bytes)
ConnectivityLogMaxFileSize 		: 10 MB (10,485,760 bytes)
ConnectivityLogPath 			: C:\Program Files\Microsoft\Exchange
				  	  Server\V14\TransportRoles\Logs\Connectivity

MessageTrackingLogEnabled 		: True
MessageTrackingLogSubjectLoggingEnabled	: True
MessageTrackingLogMaxAge 		: 30.00:00:00
MessageTrackingLogMaxDirectorySize 	: 1000 MB (1,048,576,000 bytes)
MessageTrackingLogMaxFileSize 		: 10 MB (10,485,760 bytes)
MessageTrackingLogPath 			: C:\Program Files\Microsoft\Exchange
					  Server\V14\TransportRoles\Logs\MessageTracking

ActiveUserStatisticsLogMaxAge 		: 30.00:00:00
ActiveUserStatisticsLogMaxDirectorySize	: 250 MB (262,144,000 bytes)
ActiveUserStatisticsLogMaxFileSize 	: 10 MB (10,485,760 bytes)
ActiveUserStatisticsLogPath 		: C:\Program Files\Microsoft\Exchange
					  Server\V14\TransportRoles\Logs\ActiveUsersStats

ServerStatisticsLogMaxAge 		: 30.00:00:00
ServerStatisticsLogMaxDirectorySize 	: 250 MB (262,144,000 bytes)
ServerStatisticsLogMaxFileSize 		: 10 MB (10,485,760 bytes)
ServerStatisticsLogPath 		: C:\Program Files\Microsoft\Exchange
					  Server\V14\TransportRoles\Logs\ServerStats

IntraOrgConnectorProtocolLoggingLevel 	: None
ReceiveProtocolLogMaxAge 		: 30.00:00:00
ReceiveProtocolLogMaxDirectorySize 	: 250 MB (262,144,000 bytes)
ReceiveProtocolLogMaxFileSize 		: 10 MB (10,485,760 bytes)
ReceiveProtocolLogPath 			: C:\Program Files\Microsoft\Exchange
					  Server\V14\TransportRoles\Logs\Pro
					  tocolLog\SmtpReceive

RoutingTableLogMaxAge 			: 7.00:00:00
RoutingTableLogMaxDirectorySize 	: 50 MB (52,428,800 bytes)
RoutingTableLogPath 			: C:\Program Files\Microsoft\Exchange
					  Server\V14\TransportRoles\Logs\Routing

SendProtocolLogMaxAge 			: 30.00:00:00
SendProtocolLogMaxDirectorySize 	: 250 MB (262,144,000 bytes)
SendProtocolLogMaxFileSize 		: 10 MB (10,485,760 bytes)
SendProtocolLogPath 			: C:\Program Files\Microsoft\Exchange
					  Server\V14\TransportRoles\Logs\ProtocolLog\SmtpSend

HttpProtocolLogEnabled 			: False
HttpProtocolLogFilePath 		:
HttpProtocolLogMaxAge 			: 7.00:00:00
HttpProtocolLogMaxDirectorySize 	: 250 MB (262,144,000 bytes)
HttpProtocolLogMaxFileSize 		: 10 MB (10,485,760 bytes)
HttpProtocolLogLoggingLevel 		: None

TransportSyncLogEnabled 		: False
TransportSyncLogFilePath 		:
TransportSyncLogLoggingLevel 		: None
TransportSyncLogMaxAge 			: 7.00:00:00
TransportSyncLogMaxDirectorySize 	: 10 GB (10,737,418,240 bytes)
TransportSyncLogMaxFileSize 		: 10 MB (10,485,760 bytes)

TransportSyncHubHealthLogEnabled 	: False
TransportSyncHubHealthLogFilePath 	:
TransportSyncHubHealthLogMaxAge 	: 14.00:00:00
TransportSyncHubHealthLogMaxDirectorySize : 10 GB (10,737,418,240 bytes)
TransportSyncHubHealthLogMaxFileSize 	: 10 MB (10,485,760 bytes)

[PS] C:\>

We won't cover each of these in detail, but we will cover concepts. First and foremost: all TransportSync* and HttpProtocol* variables and values are reserved for internal Microsoft use. A reasonable guess (and we have no knowledge on the accuracy of this) is that they are used for Microsoft's Exchange Hosting business.

Any *LogMaxAge variable is used to limit how long a log file is retained in a log file directory. It is the maximum amount of time that the log file will reside in the *LogPath directory. When *LogMaxAge is exceeded, Exchange will automatically remove log files that exceed that age.

Any *LogMaxDirectorySize variable is used to limit how large a log file directory can grow. If a log directory grows larger than *LogMaxDirectorySize, then enough older log files are removed to bring the size of the directory beneath the *LogMaxDirectorySize. Oldest log files are removed first.

Any *LogMaxFilesize variable is used to limit the size of an individual log file. If an in-use log file exceeds that value, it is closed and a new log file is opened. Some logging types (such as the routing table) don't include this value because a new log file is opened every time something needs to be logged.

Any *LogPath variable is used to indicate the directory where that particular type of log file is stored.

Finally, any *LogEnabled variable is used to indicate whether or not that particular type of logging is enabled. Certain log files, such as Active User Statistics and Server Statistics, are always generated and cannot be disabled. Other log files, such as connectivity logging and message tracking, are generated by default but can be disabled. However, the Send Protocol and the Receive Protocol log files are not controlled at the Transport server level but at the connector level.

Connectivity Log

The connectivity log shows every connection to the Transport server and some brief information about what happened during that connection.

Message Tracking

A message tracking log tracks every step that a message follows through a specific Exchange server.

Active User Statistics

Each day, a Transport server generates a summary of email for each incoming and each outgoing email address. This summary contains the following fields of information in CSV format:

• DateTime
• UserAddress
• MessageScope
• SenderSmtpMessages
• SenderSmtpBytes
• SenderSmtpRecipientCount
• SenderStoreDriverMessages
• SenderStoreDriverBytes
• SenderStoreDriverRecipientCount
• RecipientStoreDriverMessages
• RecipientStoreDriverBytes
• RecipientSmtpMessages
• RecipientSmtpBytes
• RecipientFailMessages
• RecipientFailBytes
• SenderFailMessages
• SenderFailBytes
• SenderExternalSmtpMessages
• SenderExternalSmtpBytes
• SenderExternalSmtpRecipientCount
• RecipientAggregationMessages
• RecipientAggregationBytes
• SenderGatewayMessages
• SenderGatewayBytes
• RecipientPickupMessages
• RecipientPickupBytes
• SenderAgentMessages
• SenderAgentBytes
• RecipientExpandMessages
• RecipientExpandBytes
• TotalEndToEndMessageLatency
• TotalEndToEndMessageLatencyCount

Server Statistics

Each day a Transport server also generates an overall summary of its activities to a log file, based on its connections to source and destination servers. This summary contains the following fields of information in CSV format:

• DateTime
• ClientHostName
• ServerHostName
• DeliverGatewayMessages
• DeliverGatewayBytes
• DeliverGatewayRecipients
• DeliverAgentMessages
• DeliverAgentBytes
• DeliverAgentRecipients
• DeliverStoreDriverMessages
• DeliverStoreDriverBytes
• DeliverStoreDriverRecipients
• DeliverSmtpIntraOrgMessages
• DeliverSmtpIntraOrgBytes
• DeliverSmtpIntraOrgRecipients
• DeliverSmtpForeignMessages
• DeliverSmtpForeignBytes
• DeliverSmtpForeignRecipients
• ReceiveStoreDriverMessages
• ReceiveStoreDriverBytes
• ReceiveStoreDriverRecipients
• ReceiveSmtpLocalMessages
• ReceiveSmtpLocalBytes
• ReceiveSmtpLocalRecipients
• ReceivePickupMessages
• ReceivePickupBytes
• ReceivePickupRecipients
• ReceiveSmtpIntraOrgMessages
• ReceiveSmtpIntraOrgBytes
• ReceiveSmtpIntraOrgRecipients
• ReceiveSmtpForeignMessages
• ReceiveSmtpForeignBytes
• ReceiveSmtpForeignRecipients
• ReceiveAggregationMessages
• ReceiveAggregationBytes
• ReceiveAggregationRecipients
• ReceiveMailboxRulesMessages
• ReceiveMailboxRulesBytes
• ReceiveMailboxRulesRecipients
• ResubmitDumpsterMessages
• ResubmitDumpsterBytes
• ResubmitRedundancyMessages
• ResubmitRedundancyBytes
• DSNMessages
• DSNBytes
• AgentFailLocalMessages
• AgentFailLocalBytes
• AgentFailForeignMessages
• AgentFailForeignBytes
• RoutingFailLocalMessages
• RoutingFailLocalBytes
• RoutingFailForeignMessages
• RoutingFailForeignBytes
• EndToEndLatencyPercentile100
• EndToEndLatencyPercentile99
• EndToEndLatencyPercentile95
• EndToEndLatencyPercentile90
• EndToEndLatencyPercentile80
• EndToEndLatencyPercentile70
• EndToEndLatencyPercentile60
• EndToEndLatencyPercentile50
• EndToEndLatencyPercentile25
• EndToEndLatencyPercentileCount
• LocalLatencyPercentile100
• LocalLatencyPercentile99
• LocalLatencyPercentile95
• LocalLatencyPercentile90
• LocalLatencyPercentile80
• LocalLatencyPercentile70
• LocalLatencyPercentile60
• LocalLatencyPercentile50
• LocalLatencyPercentile25
• LocalLatencyPercentileCount