Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 228
  • Last Modified:

Exchange 2013 - Forwarding To External SMTP Address Not Working

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"

http://technet.microsoft.com/en-us/library/dd351134%28v=exchg.150%29.aspx
=====

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:
http://www.techieshelp.com/exchange-2013-forward-email-to-external-contact/

All looks simple enough, but is not working. Appreciate any assistance -
0
hwtech
Asked:
hwtech
  • 4
  • 3
2 Solutions
 
Simon Butler (Sembee)ConsultantCommented:
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.

Simon.
0
 
hwtechAuthor Commented:
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?
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Simon Butler (Sembee)ConsultantCommented:
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?

Simon.
0
 
hwtechAuthor Commented:
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.
0
 
Simon Butler (Sembee)ConsultantCommented:
"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.

Simon.
0
 
hwtechAuthor Commented:
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.
0
 
hwtechAuthor Commented:
Sorry for delay in followup. Closing as haven't had a chance yet for followup on this issue. Appreciate the assistance.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now