Skip to main content

Quck SMTP Bandwidth usage script for Exchange 2007

Being able to tell how much bandwidth a particular server has consumed over a period of time is quite handy when your in a pinch and trying to work out where your bandwidth is being consumed. It can also be used in a wider context when trying to work what particular patterns and pressures are happening on particular server. The latter requiring a a more lateral analysis of the data.

Exchange 2007 does a good job of logging message tracking information but these create a chalenge of filtering down this information into what been sent/received and how much bandwidth being used.

The first things this script does is grabs all the message tracking records for a particular time period for a paricular server (based on a cmdline parameter you pass it). It then filters just on Sent and Recieved Email and then uses a hashtable and some other filtering code to count the number of email sent and recieved based on recpients of a message (eg a message sent to 5 external recipients will be count 5 times).

How accurate is this well ..... its approximatly acurate the data is good but some better maths is need to get a really acurate but thats a longer story that would probably put you all to sleep ...

To run the script you need to provide the servername of the server you want to pull the logs from and the number of hours you want to look back eg to look at the last 24 hours on a server call myexserver would be

./lexchv2.ps1 myexserver 24

I've put a download of the script here the code looks like

$dtQueryDT = [system.DateTime]::Now.AddHours(-($args[1]))
$dtQueryDTf = [system.DateTime]::Now


$InternalNum = 0
$InternalSize = 0

$ExternalSentNum = 0
$ExternalSentSize = 0

$ExternalRecNum = 0
$ExternalRecSize = 0

$ServerName = $args[0]

$DomainHash = @{}
$msgIDArray = @{}


get-accepteddomain | ForEach-Object{
if ($_.DomainType -eq "Authoritative"){
$DomainHash.add($_.DomainName.SmtpDomain.ToString().ToLower(),1)
}

}

Get-MessageTrackingLog -Server $ServerName -ResultSize Unlimited -Start $dtQueryDT -End $dtQueryDTf | ForEach-Object{
if ($_.EventID.ToString() -eq "SEND" -bor $_.EventID.ToString() -eq "RECEIVE"){
foreach($recp in $_.recipients){
if($recp.ToString() -ne ""){
$unkey = $recp.ToString() + $_.Sender.ToString() + $_.MessageId.ToString()
if ($msgIDArray.ContainsKey($unkey) -eq $false){
$msgIDArray.Add($unkey,1)
$recparray = $recp.split("@")
$sndArray = $_.Sender.split("@")
if ($_.Sender -ne ""){
if ($DomainHash.ContainsKey($recparray[1])){
if ($DomainHash.ContainsKey($sndArray[1])){
$InternalNum = $InternalNum + 1
$InternalSize = $InternalSize + $_.TotalBytes/1024
}
else{

$ExternalRecNum = $ExternalRecNum + 1
$ExternalRecSize = $ExternalRecSize + $_.TotalBytes/1024
}
}
else{
if ($DomainHash.ContainsKey($sndArray[1])){
$ExternalSentNum = $ExternalSentNum + 1
$ExternalSentSize = $ExternalSentSize + $_.TotalBytes/1024
}
}
}
}

}
}
}

}

"Sent/Recieved Internally Number : " + $InternalNum
"Sent/Recieved Internally Size : " + [math]::round($InternalSize/1024,2)
"Externally Sent Number : " + $ExternalSentNum
"Externally Sent Size : " + [math]::round($ExternalSentSize/1024,2)
"Externally Recieved Number : " + $ExternalRecNum
"Externally Recieved Size : " + [math]::round($ExternalRecSize/1024,2)
Labels:

Popular posts from this blog

Testing and Sending email via SMTP using Opportunistic TLS and oAuth in Office365 with PowerShell

As well as EWS and Remote PowerShell (RPS) other mail protocols POP3, IMAP and SMTP have had OAuth authentication enabled in Exchange Online (Official announcement here ). A while ago I created  this script that used Opportunistic TLS to perform a Telnet style test against a SMTP server using SMTP AUTH. Now that oAuth authentication has been enabled in office365 I've updated this script to be able to use oAuth instead of SMTP Auth to test against Office365. I've also included a function to actually send a Message. Token Acquisition  To Send a Mail using oAuth you first need to get an Access token from Azure AD there are plenty of ways of doing this in PowerShell. You could use a library like MSAL or ADAL (just google your favoured method) or use a library less approach which I've included with this script . Whatever way you do this you need to make sure that your application registration  https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-
Read more

The MailboxConcurrency limit and using Batching in the Microsoft Graph API

If your getting an error such as Application is over its MailboxConcurrency limit while using the Microsoft Graph API this post may help you understand why. Background   The Mailbox  concurrency limit when your using the Graph API is 4 as per https://docs.microsoft.com/en-us/graph/throttling#outlook-service-limits . This is evaluated for each app ID and mailbox combination so this means you can have different apps running under the same credentials and the poor behavior of one won't cause the other to be throttled. If you compared that to EWS you could have up to 27 concurrent connections but they are shared across all apps on a first come first served basis. Batching Batching in the Graph API is a way of combining multiple requests into a single HTTP request. Batching in the Exchange Mail API's EWS and MAPI has been around for a long time and its common, for email Apps to process large numbers of smaller items for a variety of reasons.  Batching in the Graph is limited to a m
Read more

How to test SMTP using Opportunistic TLS with Powershell and grab the public certificate a SMTP server is using

Most email services these day employ Opportunistic TLS when trying to send Messages which means that wherever possible the Messages will be encrypted rather then the plain text legacy of SMTP.  This method was defined in RFC 3207 "SMTP Service Extension for Secure SMTP over Transport Layer Security" and  there's a quite a good explanation of Opportunistic TLS on Wikipedia  https://en.wikipedia.org/wiki/Opportunistic_TLS .  This is used for both Server to Server (eg MTA to MTA) and Client to server (Eg a Message client like Outlook which acts as a MSA) the later being generally Authenticated. Basically it allows you to have a normal plain text SMTP conversation that is then upgraded to TLS using the STARTTLS verb. Not all servers will support this verb so if its not supported then a message is just sent as Plain text. TLS relies on PKI certificates and the administrative issue s that come around certificate management like expired certificates which is why I wrote th
Read more
All sample scripts and source code is provided by for illustrative purposes only. All examples are untested in different environments and therefore, I cannot guarantee or imply reliability, serviceability, or function of these programs.

All code contained herein is provided to you "AS IS" without any warranties of any kind. The implied warranties of non-infringement, merchantability and fitness for a particular purpose are expressly disclaimed.