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

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes.  While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted.  When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places.  First off in the Active Directory Administrative Center.  This is what caused the initial confusion.  Take a look.  This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3.  Test3 is a valid, functioning user account.  Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...