Understanding Email Forwarding in Exchange & Microsoft 365: ForwardingSmtpAddress vs. ForwardingAddress

Email forwarding is a fundamental capability within Exchange and Microsoft 365 environments, yet the distinction between ForwardingSmtpAddress and ForwardingAddress often causes confusion. Let's clarify these two parameters and how they govern email redirection.

Understanding the Core Parameters

1. ForwardingSmtpAddress: Directing Emails Externally

The ForwardingSmtpAddress parameter is your go-to for sending emails to recipients outside your organization. Think of personal email accounts like Gmail, Yahoo, or any other external domain. Since these are external addresses, they don't require the same internal validation as recipients within your own network.

  • Use Case: Imagine a contractor, Jane, who needs all emails sent to her company address to automatically land in her personal Gmail inbox (jane.doe@gmail.com). Setting her mailbox's ForwardingSmtpAddress to this external address achieves this seamlessly.

2. ForwardingAddress: Keeping Email Redirection Internal

In contrast, the ForwardingAddress parameter is strictly for forwarding emails to recipients within your organization. These internal recipients are validated and can be identified using various internal identifiers like their alias, distinguished name, or GUID.

  • Use Case: Consider a scenario where Mark is leaving the company, but his manager, Sarah, needs to monitor his incoming mail. You would configure Mark's mailbox with the ForwardingAddress set to Sarah's internal mailbox (sarah@company.com).

Controlling Delivery Behavior: DeliverToMailboxAndForward

The DeliverToMailboxAndForward parameter offers crucial control over whether the original mailbox retains a copy of the forwarded email.

  • Setting DeliverToMailboxAndForward to $true means the email is delivered to the original recipient's mailbox and forwarded to the specified forwarding address.

  • Setting it to $false means the email is only forwarded to the designated address and does not appear in the original recipient's inbox.

  • Use Case Example: If Mark's mailbox is set to forward emails to Sarah, and DeliverToMailboxAndForward is $true, emails will appear in both Mark's inbox and Sarah's. If it's $false, only Sarah will receive the emails.

The Precedence Rule: Internal Over External

A critical behavior to understand is that when both ForwardingSmtpAddress and ForwardingAddress are configured on a mailbox, ForwardingAddress takes precedence. The system prioritizes internal forwarding over external forwarding.

  • Scenario: If Jane's mailbox is configured with both her external Gmail address (ForwardingSmtpAddress) and Sarah's internal address (ForwardingAddress), any email sent to Jane's mailbox will only be forwarded to Sarah. The external forwarding to Gmail will be ignored.

Configuring Email Forwarding

You have several methods for configuring email forwarding in Exchange and Microsoft 365:

  • Outlook on the Web (OWA): Typically used for setting ForwardingSmtpAddress for individual users. You can usually find this under Settings > Mail > Forwarding.
  • Exchange Admin Center (EAC): Provides granular control. Within a mailbox's properties under the Email Forwarding tab, you can configure both ForwardingAddress (for internal) and ForwardingSmtpAddress (for external).
  • Microsoft 365 Admin Center: When setting up email forwarding through the user interface here, it generally configures the ForwardingSmtpAddress.

Why This Distinction Matters

A solid understanding of these parameters is vital for efficient administration and troubleshooting:

  • Transport Rules Interaction: Be aware that when ForwardingSmtpAddress is set via EAC, certain transport rules might not process messages as expected. For instance, rules based on the X-MS-Exchange-ForwardingLoop header might fail because this header is often added after transport rules have evaluated the message.
  • Tenant Migration Scenarios: During a tenant-to-tenant migration, leveraging ForwardingSmtpAddress with the Set-Mailbox PowerShell cmdlet on the old mailbox can ensure a copy of incoming mail continues to be delivered to the new mailbox during the transition period.
  • Remote Domain Settings: The functionality of ForwardingSmtpAddress is subject to the AutoForwardEnabled setting configured on the relevant Remote Domain. If auto-forwarding is disabled for a remote domain, external forwarding to that domain via ForwardingSmtpAddress will not work.

By understanding these key parameters and their behaviors, you can effectively manage email forwarding within your Exchange and Microsoft 365 environment, ensuring mail is routed correctly and predictably.

Comments

Post a Comment

Popular posts from this blog

Microsoft 365 Office Update Channels: A Complete Guide

Selecting the appropriate update channel for Microsoft 365 Office applications is crucial for balancing feature availability, system stability, and organizational requirements. Microsoft offers multiple update channels, each catering to different business needs—from early access to new features to long-term stability with minimal disruptions. Microsoft 365 Office Update Channels Overview 1. Beta Channel (Code: BetaChannel) Description:  Offers the earliest access to upcoming features, updates, and bug fixes. Best For:  Users who want to preview and test the latest innovations and provide feedback to Microsoft. Formerly Known As:  Insider, Insider Fast, Monthly. 2. Current Channel (Preview) (Code: CurrentPreview) Description:  Receives feature updates about a month before they reach the Current Channel, with reduced risk compared to the Beta Channel. Best For:  Organizations that want early access to updates...
Read more

Unveiling Primary Mailbox Statistics

Keep your Microsoft Exchange environment running smoothly with these simple PowerShell commands. Primary Mailbox Insights Want to know how much space primary mailboxes are using? This single command gives you a clear picture of storage status, item count, and total size: PowerShell Command Get-Mailbox -ResultSize Unlimited | Get-MailboxStatistics | Select DisplayName, StorageLimitStatus , @{ Name = " TotalItemSize (MB) "; Expression = { [math]::Round(($_.TotalItemSize.ToString().Split("(")[1].Split(" ")[0].Replace(",", "") / 1MB), 2) }}, ItemCount | Sort " TotalItemSize (MB) " -Descending | Export-CSV " C:\temp\All Mailboxes.csv " -NoTypeInformation This command does all the heavy lifting: It fetches all user mailboxes fast. It gathers essential stats like size and item count. It converts sizes to MB for easy reading. It sorts mailboxes from largest to sma...
Read more

Manage DL Members in OWA Without Allowing DL Creation – A Practical Solution

Today, I'd like to share a real-world workaround that solves a common issue in Microsoft 365: giving users the ability to manage Distribution List (DL) members through Outlook on the Web (OWA) without giving them permission to create or delete DLs. This is a frequent request for organizations focused on strict governance and efficient delegation. The Challenge A client recently encountered a problem where a user was unable to manage Distribution Group (DG) members via OWA. After some investigation, we discovered that the MyDistributionGroups role was not included in their role assignment policy. While enabling this role would solve the immediate issue, it comes with a significant drawback: it also grants the user the ability to create and delete DLs. For organizations with strict governance policies or those that prefer centralized DL creation, this isn't an ideal scenario. The Goal Our objective was clear: Allow users to manage existing Dist...
Read more