exchange 2010 auto response not sending to external domains

Posted on 2015-01-20
Last Modified: 2015-01-20
I'm attempting to set up an auto-responder address on a domain.  The purpose is just to test the email round-tripping.

The email account has been created and a rule created for this mailbox that replies with a template to any emails received.

When I send an email to the echo@ account from another mailbox on the domain, it works fine.
When I send an email to the echo@ account from another mailbox on an external domain, it does not work.

I have the rule respond & then move the email to a folder.  So I can see that the emails from the external domain ARE being received by the echo@ mailbox.

I've tested just sending a new email to an external domain account and that does not work either.  The recipient never gets the email, and the echo@ account never gets any error message or failed delivery notification.  Other users on the domain CAN send outbound to external domain accounts.  Just not echo@


Question by:cef_soothsayer
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

Author Comment

ID: 40559782
I've tested both the auto-responder from, and sending directly to several external email accounts.... gmail etc.  The Echo@ account cant seem to talk to the outside world.
LVL 33

Accepted Solution

Exchange_Geek earned 500 total points
ID: 40559791
That is because your auto reply has been STOPPED at Organization level.

Perform a quick check, using powershell

Get-RemoteDomain * | FL AutoReplyEnabled

If you find it as False, that'll validate what I wrote as my first analysis. Feel free to change it to TRUE using the following command in powershell

Set-RemoteDomain * -AutoReplyEnabled $True

-Tushar Shah

Author Comment

ID: 40559797

I just found half the problem.  There is an external 3rd party relay for outbound spam filtering.  The echo@ account wasn't configured to pass that. (found the details in the send connector).

So now echo@ can send emails.  But the auto-responder is still not working to external addresses.

Create Professional Looking Email Signatures

Create "Professional HTML Email Signatures" with ease.
7 Day Money Back Guarantee if not 100% Satisfied.
Affordable - Try it out for 7 Days Totally Risk Free.
Installers provided for over 45 Email clients.
Both Windows & MAC Supported.
Highly Recommended!

LVL 33

Expert Comment

ID: 40559811
Good find.

Now, were you able to detect IF auto reply is disabled/enabled at Organization level on Exchange?

-Tushar Shah

Author Comment

ID: 40559827
>> Now, were you able to detect IF auto reply is disabled/enabled at Organization level on Exchange?

Well, I already checked the Exchange Management Console, under Organization Configuration / Hub Transport / Remote Domains / Default / Properties / Message Format.  And the "Allow Automatic Replies" is checked enabled.

Anywhere else I should check?
LVL 33

Expert Comment

ID: 40559837
Run a random search

Get-RemoteDomain | FL Name,AutoReply*

Let's check what you got in there.

-Tushar Shah

Author Comment

ID: 40559838
Nevermind!   It is working!  Just took forever to receive the response at gmail.  When I tested it at another pop account (that I've been parallel testing with all along), it now works fine & fast.

thanks for all your help.  I'll mark your answer as the solution so you get credit.  The actual solution was the 3rd party relay service blocking unauthorized senders. (not white-listed)


Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

This article describes how to import an Outlook PST file to Office 365 using a third party product to avoid Microsoft's Azure command line tool, saving you time.
Unified and professional email signatures help maintain a consistent company brand image to the outside world. This article shows how to create an email signature in Exchange Server 2010 using a transport rule and how to overcome native limitations …
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
how to add IIS SMTP to handle application/Scanner relays into office 365.

737 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