If you need to forward mail to an external email address, you cannot simply type the address in Delivery Options. A (mail-enabled) Contact needs to be created in AD first, and Delivery Options modified to point to the Contact.
Exchange Server 2007: In Exchange Server 2007, these tasks remain the same. However, instead of using ADUC to accomplish them, you use the EMC or the shell (aka "EMS"). The new term for a Contact is MailContact.
To create a MailContact using the Exchange Management Console:1. Expand Recipeint Configuration | Mail Contact
2. In the Action pane, click New Mail Contact
3. To create a new Contact object, leave the default (New Contact) selected | click Next
4. Type First name, Last name
5. Click Edit to add the external email address
6. Click New to complete creation of new MailContact
To create a new MailContact using the Exchange Management Shell:
New-MailContact -Name "Foo User" -ExternalEmailAddress "foo@externaldomain.com
Next, we set the recipient's Delivery Options to deliver to the alternate recipient.
To forward mail for a recipient to the MailContact using the Exchange Management Console:1. Expand Recipeint Configuration | Mailbox | select mailbox | properties | Mail Flow Settings tab | Delivery Options
2. Under Forwarding address, select the Forward to checkbox
3. Click Browse to select the MailContact

Figure 1: Modifying Delivery Options to forward email to an alternate recipient
4. Optional: If a copy of the message needs to be delivered to both the external recipient and the original recipient's mailbox, select the Deliver message to both forwarding address and mailbox
5. Click OK to close Delivery Options properties
6. Click OK to close recipient's properties
Using the Exchange Management Shell:
Set-Mailbox "Joe Adams" -ForwardingAddress "foo@externaldomain.com"
To deliver a copy to the mailbox (in addition to the external email address - equivalent of step 4 above):Set-Mailbox "Joe Adams" -ForwardingAddress "foo@externaldomain.com" -DeliverToMailboxAndForward $true
To get a list of mailboxes with forwarding enabled:Get-Mailbox | where {$_.ForwardingAddress -ne $null} | ft name,forwardingaddress
Automatic forwarding and Remote Domains
Remote Domains are a bunch of settings, such as message formats, character sets, and OOFs, for messages sent to particular remote domains. The default Remote Domain setting applies to address space * - that is, all remote domains for which an explicit Remote Domain setting does not exist. 
Figure 2: The Allow automatic forward setting for remote domains impacts client-side automatic forwarding, and is disabled by default.
However, this setting only applies to client-side forwarding. For instance, if a user creates a rule in Microsoft Outlook to automatically forward mail to an external email address, the default setting does not allow it. To enable automatic client-side forwarding of mail to external addresses, select the Allow automatic forward checkbox in a remote domain's properties | Format of original message sent as attachment to journal report tab (Yes, the tab is mislabeled. It is the "Message Formats" tab... :).
Server-side forwarding setup by an administrator is not impacted by this setting.
Labels: Administration, Exchange Server 2007, Exchange Shell, Mailbox

Exchangepedia Blog is read by visitors from all 50 US States and 150 countries world-wide

15 Comments:
Why not just modify the TargetAddress field in Active directory user with smtp:forwardingaddress@domain.com This will send all mail to this user bypassing the mailbox.
Afaik, simply adding the external email address to targetAddress attribute doesn't work. (Need to test further, but this is what the initial tests reveal).
It also doesn't help if you want to deliver to the addressed recipient *and* the alternate recipient (whether internal or external).
Can I use this to forward emails to a server and port number?
Will it show up with the original header information?
- Messages will be forwarded to the external mail host responsible for that domain/email address.
- This has no connection with message routing. Send Connectors determine how messages are routed to an external domain/address space.
- Yes, original headers are preserved.
is there a way to list the forwarding enabled accounts in 03?
similar to "get-mailbox"
Bharat
Would like to know whether there any options available for forwarding a copy of the send mails from a set of users to a monitoring account (Say administrator's email account). We need it to be done as discreet as possible to track the activities of certain sales executives who are believed as manipulating selling prices.
Scripts, third party tools which could be installed at the server side would be a great help for us.
@Anonymous: Which version of Exchange server?
You could use Journaling.
- In Exchange 2003/2000, Journaling is per Mailbox Database. You will end up journaling all mailboxes on the Database.
Overview of Exchange Server 2003 Journaling
- In Exchange 2007, you can journal selectively.
Overview of Journaling
How to Create a New Journal Rule
If you're on Exchange Server 2007, you can use Transport Rules to send a copy of messages to the desired recipient.
Overview of Transport Rules
On either version, you can assign Full Access permissions and access the mailbox using OWA or Microsoft Outlook.
HOW TO: Grant Full Mailbox Access permission
Well done!
How can I forward e-mail to more then two recepient?
@Anonymous from March 18: You can forward to a Distribution Group, and add the external recipients to the Distribution Group.
Note, to add external recipients to a Distribution Group, you need to create them as Contacts first.
Thanks Bharat, I am able to forward e-mail to more than two recipients.
MS Exhange Transport services is in STARTING status, any idea what might cause this exception. I restarted the server couple of times.
Hello, I have followed the instructions but still cannot get it to work.
I have selected the option to deliver message to both forwarding address and mailbox. When I send a test mail it arrives fine at the mailbox but doesn't get forwarded. Then, a minute or so later, a NDR shows up at the mailbox. It gives me the following error "#550 5.7.1 Unable to relay"
I have been scouring the net for a solution but haven't found anything. Do you guys have any thoughts?
(It's Exchange 2007 and we have a 2-server org with one internal and one front end)
Cheers
I followed the above but I'm getting NDR's with "#550 5.7.1 Unable to relay "
Any ideas? I'm using Exchange 2007 btw...
very nice article
Post a Comment
Links to this post:
Create a Link
<< Home