SBS2011 / Exchange 2010 Receive Connector for server-based app to relay email

Deferring to the pros - I have a single server environment running SBS2011 w/ Exchange 2010.

There is an application that runs on this SBS2011server that uses an internal distribution list to send emails to internal and external email recipients. The email contacts reside on a database internal to the application.

I've stepped through a few articles on how to config a new receive connector, set the appropriate permissions, etc

The last article I tried was from this site, using Option 1:

I created a new connector and named "app relay connector"

Connector settings are:

Network Tab
 - Use the local IP address(s) to receive email from:
      - (my sbs2011 server IP address)
- Receive mail from remote server that have these IP addresses
      - (IP's of the workstations that run this app, run on this network)

Authentication Tab
      - TLS    (checked)
      - Externally Secured   (checked)

Permissions Groups
     - Exchange Servers    (checked)
     - NOTE - I've tried the "anonymous users" but did not work. Currently unchecked

I am getting a "client not authenticated" message. Which, from other steps I've taken in other articles, it's either this message or a "unable to relay" response.

Looking for assistance on how to get this properly configured, to where the application that resides locally on my SBS server can get it's internal email distribution list contacts receiving email.  - thanks
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

imkotteesSenior Messaging EngineerCommented:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
hwtechAuthor Commented:
imkottees - this was one of the articles I've read, in the process of trying to get this to work. Reviewing your article link, the steps outlined appear to me to be identical to the steps I've already taken and noted in my question.

Correct me if I'm wrong and have missed a step listed in your article link - thanks
imkotteesSenior Messaging EngineerCommented:
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Adam BrownSr Solutions ArchitectCommented:
You don't need a receive connector if the application sending mail is located on the server itself and connecting directly to the Exchange services. Receive and Send connectors are used to communicate with other servers, not the server itself. If you can configure the application to connect to the mail server with a valid Mailbox account, you don't really have to do anything. Just make sure the mailbox used to authenticate has permission to send to the Distribution group. If you can't configure the application to use a valid mailbox, however, you just need to make sure the Distribution group is configured to allow communication from non-authenticated users.
hwtechAuthor Commented:
Thanks for the clarification on the requirement to build a connector for a server-side based application, and the need to send email.

I'll need to contact the application vendor to get clarification on how exactly this program works. The application database resides on the server, but how you hook a mailbox into this, I'll have to ask. Will update as I make progress. Thanks
Adam BrownSr Solutions ArchitectCommented:
In the mean time, you should be able to just set up the Distribution groups to not require authentication from users that send to it.
hwtechAuthor Commented:
Wanted to provide a quick update. I've contacted the program vendor who had sent prior info on setting up receive connectors, which didn't work, thus this open thread.

Not to shift blame, but I'm under the impression that he's not exactly sure how the email function within this program works. The "test" workstation we've been sending test emails from, did not have an Outlook client installed on it. We went to another workstation that does have an installed, working Exchange Outlook client on it, but still getting the same "client not authenticated" message when sending from within this program.

I'm to work with the vendor again today, so will update as I have something to update about. Thanks.
hwtechAuthor Commented:
Finally was able to make it back to this issue. I worked with the application vendor on this. He stated that even though the program database resided on the server, the emailing of outside contacts was initiated by the workstation, external to the server Exchange operations. So I provided inaccurate information as to how I understood this to work on my opening comment.

We built a new relay connector, and stepped thru multiple combinations of permissions, etc before this finally worked. We kept getting the client not authenticated, unable to relay. The final working configuration on this was "Authentication tab > Externally Secured (checked)" all others unchecked - "Permission Groups tab > anonymous users - exchange users - exchange servers (checked) " 

But none of the above settings worked when the "network tab - Received mail from remote servers having these IP addresses:" was set to setting. It would not work with this network block setting. It was not until we went in and put the individual workstation IP's to use this feature, i.e., 10.0.0.x. , before this finally worked.

I'm going to go ahead and close this ticket, but if you know of any issues on SBS-2011 Exchange and this network scope setting, I"d like to know for future reference.  But now working, and appreciate the assistance.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.