Skip to main content

Content Filtering System Whitelist GUI for Exchange 2007

If you’re using the built-in Content Filtering in Exchange 2007 on a Hub or Edge server you may want to take advantage of System white lists. But if you have used the Set-ContentFilterSetting cmdlet you may have noticed this isn't the most user friendly cmdlet. If you’re maintaining these lists on a regular basis you may really start to dislike the lack of a GUI well I certainly do so I built a pretty simple GUI to make managing the BypassedSenders and BypassedSenderDomains a more enjoyable experience.

It’s pretty simple code first it uses Get-ContentFilterSetting to get the current setting of both of these properties and then displays then in a DatagridView. You can then add more entries or change existing entries by editing the flexGrid then when you hit the update button it will run back through the datagrid values and then creates a collection which is then used to update the ByPassedSenders or ByPassedSenderDomains properties.

I've put a download of the script here the script look like

[System.Reflection.Assembly]::LoadWithPartialName("System.Drawing")
[System.Reflection.Assembly]::LoadWithPartialName("System.windows.forms")

function UpdateBypassSenders(){
$newcombCollection = @()
foreach($Item in $dgDataGrid.Rows){
if ($item.Cells[0].Value -ne $null){
if ($item.Cells[0].Value -ne ""){
$newcombCollection += $item.Cells[0].Value
}
}
}
Set-ContentFilterConfig -BypassedSenders $newcombCollection
$fsTable.Clear()
$contentFilterConfig = get-ContentFilterConfig
foreach ($ent in $contentFilterConfig.BypassedSenders){
$fsTable.Rows.add($ent.ToString())
}
$dgDataGrid.DataSource = $fsTable
}

function UpdateBypassSenderDomains(){
$newcombCollection = @()
foreach($Item in $dgDataGrid1.Rows){
if ($item.Cells[0].Value -ne $null){
if ($item.Cells[0].Value -ne ""){
$newcombCollection += $item.Cells[0].Value
}
}
}
Set-ContentFilterConfig -BypassedSenderDomains $newcombCollection
$fsTable1.Clear()
$contentFilterConfig = get-ContentFilterConfig
foreach ($ent in $contentFilterConfig.BypassedSenderDomains){
$fsTable1.Rows.add($ent.ToString())
}
$dgDataGrid1.DataSource = $fsTable1
}

$form = new-object System.Windows.Forms.form

$contentFilterConfig = get-ContentFilterConfig
$Dataset = New-Object System.Data.DataSet
$fsTable = New-Object System.Data.DataTable
$fsTable.TableName = "BypasssedSender"
$fsTable.Columns.Add("WhitelistEntry")
$BypassSenderArray = $contentFilterConfig.BypassedSenders.ToString().Split(',')

foreach ($ent in $contentFilterConfig.BypassedSenders){
$fsTable.Rows.add($ent.ToString())
}

$fsTable1 = New-Object System.Data.DataTable
$fsTable1.TableName = "BypassedSenderDomains"
$fsTable1.Columns.Add("WhitelistEntry")

foreach ($ent in $contentFilterConfig.BypassedSenderDomains){
$fsTable1.Rows.add($ent.ToString())
}

$dgDataGrid = new-object System.windows.forms.DataGridView
$dgDataGrid.Location = new-object System.Drawing.Size(20,50)
$dgDataGrid.size = new-object System.Drawing.Size(250,450)
$dgDataGrid.AutoSizeRowsMode = "AllHeaders"
$form.Controls.Add($dgDataGrid)
$dgDataGrid.DataSource = $fsTable

$dgDataGrid1 = new-object System.windows.forms.DataGridView
$dgDataGrid1.Location = new-object System.Drawing.Size(320,50)
$dgDataGrid1.size = new-object System.Drawing.Size(250,450)
$dgDataGrid1.AutoSizeRowsMode = "AllHeaders"
$form.Controls.Add($dgDataGrid1)
$dgDataGrid1.DataSource = $fsTable1




# Add Update Button

$exButton = new-object System.Windows.Forms.Button
$exButton.Location = new-object System.Drawing.Size(20,530)
$exButton.Size = new-object System.Drawing.Size(150,20)
$exButton.Text = "Update - Senders"
$exButton.Add_Click({UpdateBypassSenders})
$form.Controls.Add($exButton)

# Add Update Button

$exButton1 = new-object System.Windows.Forms.Button
$exButton1.Location = new-object System.Drawing.Size(320,530)
$exButton1.Size = new-object System.Drawing.Size(150,20)
$exButton1.Text = "Update - Domains"
$exButton1.Add_Click({UpdateBypassSenderDomains})
$form.Controls.Add($exButton1)

$Gbox = new-object System.Windows.Forms.GroupBox
$Gbox.Location = new-object System.Drawing.Size(10,15)
$Gbox.Size = new-object System.Drawing.Size(270,550)
$Gbox.Text = "By-Passed Senders"
$form.Controls.Add($Gbox)

$Gbox1 = new-object System.Windows.Forms.GroupBox
$Gbox1.Location = new-object System.Drawing.Size(310,15)
$Gbox1.Size = new-object System.Drawing.Size(270,550)
$Gbox1.Text = "By-Passed Sender Domains"
$form.Controls.Add($Gbox1)

$form.Text = "Exchange 2007 WhiteList Form"
$form.size = new-object System.Drawing.Size(600,600)
$form.autoscroll = $true
$form.Add_Shown({$form.Activate()})
$form.ShowDialog()

Popular posts from this blog

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

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 https://mydom-my.sharepoint.com/personal/gscales_domain_com/Documents/Email%20attachments/filename.txt 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 ' https://mydom-my.sharepoint.com/personal/gscales_domain_com/Documents/Email%20attachments/filena

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