Skip to main content

Extract mailboxes that are forwarding email outside of your domain with PowerShell

 

While instructing a PowerShell class at the Federal Reserve Bank in Philadelphia, I took an opportunity to take a real PowerShell need and incorporate it into class.  The need was to discover any user accounts that had rules in Outlook that forward emails outside of the organization.  Below is the resulting script.

 

 

# This code is intended to run on the Exchange server in the

# Exchange Management Shell.  It is also intended to be a

# module or Dot sourced into the session.

# Enable the line of code below to Import the Exchange cmdlets.

# Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010

 

<#

.SYNOPSIS

Retrieves mailboxes that have forwarding rules outside of your email system.

.DESCRIPTION

Retrieves mailboxes that have forwarding rules outside of your email system and presents you with the mailbox owner and the forwarded address .PARAMETER EmailDomain The name of your email domain.  Any forward rules that do not match this domain will be reported.

.EXAMPLE

Find-ForwardedEmails FRB.org

 

Mailbox                                                     External Address

-------                                                     ----------------

Adatum.com/Marketing/Paul West

{"myaccount@somewhere.com" [SMTP:myaccount@somewhere.com]} Adatum.com/Marketing/Paul West {"Pual@yahoo.com" [SMTP:Pual@yahoo.com]} Adatum.com/Executives/Scott MacDonald {"Scott@hotmail.com" [SMTP:Scott@hotmail.com]} Adatum.com/Users/Jason A. Yoder {"Jason@Gmail.com" [SMTP:Jason@Gmail.com]}

 

.NOTES

This function is provided without support or warranty.

Always examine any PowerShell code that you download and understand it before using it.

#>

 

Function Find-ForwardedEmails

{

    Param (

        [CmdletBinding()]

        [Parameter(Mandatory=$True)][string]$EmailDomain

    )

    Try

    {

        Write-Host "Collecting Mailbox Data, please wait" -ForegroundColor Green

        $MailboxList = Get-Mailbox -ea Stop

    }

    Catch

    {

        Write-Host "Error in Mailbox" -ForegroundColor red -BackgroundColor black

 

    }

    Finally

    {

        Write-Host "Completed collecting mailbox data." -ForegroundColor Green

        Write-host "Total mailboxes processed: "($MailboxList).count

    }

 

    # Collect Rule information from the mailboxes

    Try

    {

        Write-Host "Collecting Rulw Data, please wait" -ForegroundColor Green

        $RuleList = $MailBoxList |

        Get-InboxRule -ea SilentlyContinue |

        Where-Object {$_.ForwardTo -notLike "*$EmailDomain*"}

    }

    Catch

    {

       Write-Host "Error in Rules" -ForegroundColor red -BackgroundColor black

    }

    Finally

    {

        Write-Host "Completed collecting rules data." -ForegroundColor Green

        Write-host "Total rules processed: "($RuleList).count

    }

 

    # Output the data to the pipeline.

    ForEach ($Rule in $RuleList)

    {

        $Obj = New-Object PSObject

        $Obj | Add-Member -MemberType NoteProperty -Name "Mailbox"

-Value $Rule.MailBoxOwnerID

        $Obj | Add-Member -MemberType NoteProperty -Name "External Address" -Value $Rule.ForwardTo

 

        # Send the data to the pipeline.

        Write-Output $Obj

 

    }

} # End Function: Find ForwardedEmails

 

Comments

Ballekes said…
Hi,

Nice, thanks!

We have a mixed environment, Exchange and Lotus Domino... does anyone know if this would be possible on Domino?

You can use "tell amgr schedule" in the Domino console to retrieve enabled agents running on mailboxes but what about mail rules that forward messages to external addresses?

Grts.
Grts,

I'm glad that you liked the post. The client that I was working with at the time was migrating from Domino to Exchange 2010. I have not had the opportunity to look for a PowerShell module for Domino. The above code is part of the Exchange 2010 module.

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.