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"){


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){
$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

$ExternalRecNum = $ExternalRecNum + 1
$ExternalRecSize = $ExternalRecSize + $_.TotalBytes/1024
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)

Popular posts from this blog

Downloading a shared file from Onedrive for business using Powershell

I thought I'd quickly share this script I came up with to download a file that was shared using One Drive for Business (which is SharePoint under the covers) with Powershell. The following script takes a OneDrive for business URL which would look like This script is pretty simple it uses the SharePoint CSOM (Client side object Model) which it loads in the first line. It uses the URI object to separate the host and relative URL which the CSOM requires and also the SharePointOnlineCredentials object to handle the Office365 SharePoint online authentication. The following script is a function that take the OneDrive URL, Credentials for Office365 and path you want to download the file to and downloads the file. eg to run the script you would use something like ./spdownload.ps1 '

Export calendar Items to a CSV file using EWS and Powershell

Somebody asked about this last week and while I have a lot of EWS scripts that do access the Calendar I didn't have a simple example that just exported a list of the Calendar events with relevant information to a CSV file so here it is. I've talked on this one before in this howto  but when you query the calendar folder using EWS you need to use a CalendarView which will expand any recurring appointments in a calendar. There are some limits when you use a calendarview in that you can only return a maximum of 2 years of appointments at a time and paging will limit the max number of items to 1000 per call. So if you have a calendar with a very large number of appointments you need to break your query into small date time blocks. In this example script I'm just grabbing the next 7 days of appointments if you want to query a longer period you need to adjust the following lines (keeping in mind what I just mentioned) #Define Date to Query $StartDate = (Get-Date) $EndDate

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 . 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
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.