Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win


Exchange 2013 - Forwarding To External SMTP Address Not Working

Posted on 2015-01-07
Medium Priority
Last Modified: 2015-01-19
Exchange 2013 install and trying to get email retained in the users Exchange mailbox *and* get a copy forwarded to an external email address. The external account is not receiving the email. It is hitting the internal Exchange mailbox for the user.

Stepped through the following article, entering this command via EMS:

Set-Mailbox -Identity "test" -DeliverToMailboxAndForward $true -ForwardingSMTPAddress "test@external.com"


My output to the above command shows:

ForwardingSmtpAddress: smtp:test@external.com
DeliverToMailboxAndForward: True


Also reviewed this article which basically states the same PS command to enable this feature:

All looks simple enough, but is not working. Appreciate any assistance -
Question by:hwtech
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
LVL 20

Accepted Solution

Satya Pathak earned 1000 total points
ID: 40535723
LVL 63

Assisted Solution

by:Simon Butler (Sembee)
Simon Butler (Sembee) earned 1000 total points
ID: 40535828
You need to check message tracking to see whether the message is actually being passed out or not.
The way that Exchange does automatically forwarding means that it is actually possible the messages get blocked by the remote server. The messages appear to be spoofed by Exchange, so if the original source of the message and the destination are using anti-spoofing measures, then the email can be rejected.
Message Tracking will tell you if Exchange is sending the email out or not.


Author Comment

ID: 40536425
On the message tracking, I'm not seeing it. If I check the internal acct *test@domain.com* for an email object that, when received on the account, is forwarded to external acct *test@external.com* using:

Get-MessageTrackingLog -Sender test@domain.com -Recipients test@external.com

.....I don't see the subject email listed in the resultant output.

If I generate a new email from internal *test@domain.com* and send to external *test@domain.com* - I DO see it in the resultant output using the above command.

Still learning my way around EX-2013, but can I assume that the forwarding function is not working?
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40537633
Stepping back a bit...

If you run

get-mailbox -identity user.name | select identity, ForwardingSmtpAddress

Does the forward show?

If you send an email internally to the internal recipient, does it forward to the external recipient?


Author Comment

ID: 40537796
Was incorrect on the MessageTrackingLog command format noted earlier:

Get-MessageTrackingLog -Sender test@domain.com -Recipients test@external.com

The section highlighted in bold, was the internal Exchange user acct mailbox that was to do the forwarding (thinking this was the acct doing the actual forwarding to the external acct) - WRONG.

Changed that section of the command to the *originating* email acct that initiated the email  (my business account that I was doing all this testing with) - the remainder of the command syntax staying the same - I then get intelligible output to this issue.

There's a sequence of EventID's, with the last EventID of "DROP" - I've not gotten to the point of deciphering each of these ID's and their meaning, but I'm guessing DROP was doing exactly that, as the email was never received on the forwarded acct destination.

Per the linked articles in SatyaPathak, I wasn't clear if a mail-enabled contact required to be setup or not for each of these forwarding accts.  So I began with just this command which got me working:

set-remotedomain Default -AutoForwardEnabled $true

What I'm not clear on is if enabling this *remotedomain* has in any way compromised the security on this Exchange server.  Will need to do some reading.
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40537950
"set-remotedomain Default -AutoForwardEnabled $true"

There is no need to run that command.

It would allow anyone in your environment to configure a rule to automatically forward an email to an external recipient. Not only is that a security risk, but also puts your server at risk of an email loop.


Author Comment

ID: 40538541
Appreciate that bit of info. I'll need to on/off that setting and test forwarding function operations. That's what got me working initially, at least that's what it appears.

Author Closing Comment

ID: 40557660
Sorry for delay in followup. Closing as haven't had a chance yet for followup on this issue. Appreciate the assistance.

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

On September 18, Experts Exchange launched the first installment of the Help Bell, a new feature for Premium Members, Team Accounts, and Qualified Experts. The Help Bell will serve as an additional tool to help teams increase question visibility.
If something goes wrong with Exchange, your IT resources are in trouble.All Exchange server migration processes are not designed to be identical and though migrating email from on-premises Exchange mailbox to Cloud’s Office 365 is relatively simple…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…
Suggested Courses

604 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question