Solved

Exchange 2013 Receiver frustrations

Posted on 2014-10-20
1
1,717 Views
Last Modified: 2014-10-21
I'm having problems trying to add a receive connector for an application database - iSAMS. Basically an SMTP Relay.

It was working fine in Ex2010/Ex2013 co-existence with the  receiver on the old mail server.

I added it to the new 2013 server so that I could start decommissioning the old 2010 server and the ECP will not allow me to add it.

I choose Hub Transport and a custom rule to allow application relay.

I specify the IP address 10.3.3.23 which is an internal IP address on the 2013 mail server specifically for this relay. This used to be an IP on the old 2010 server. I then specify the 5 internal IP addresses that the email might come from on the application server.

I get the error :

The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL2013\Default Frontend MAIL2013". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.

When I check the settings for this FrontEnd receiver it seems to receive email from anywhere  and specifies all IP addresses that are bound to the adaptor.

The security settings are all ticked apart from Externally secured and the Permission Groups are all ticked except Partners and Exchange Users.

What I don't understand is why doesn't this Front End rule allow this email through? If its because I need to set a hub transport instead of a Front End rule then why does the FrontEnd rule stop me?

How do I overcome this issue?

Many thanks as I'm becoming increasingly frustrated.
0
Comment
Question by:itmtsn
1 Comment
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
Comment Utility
The frontend connector will allow email through, but only for inbound email. Therefore if your application is sending email to internal users it would be fine.
However if you need to send to external recipients, then you will need another connector.

Your mistake was choosing Hub Transport in the wizard. You need to choose Frontend Transport.
That should allow you to create the connector with the specific requirements, on the regular SMTP port.

Simon.
0

Featured Post

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

Join & Write a Comment

Easy CSR creation in Exchange 2007,2010 and 2013
This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
In this video we show how to create a Shared Mailbox 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 Recipients >> Sha…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

763 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

Need Help in Real-Time?

Connect with top rated Experts

9 Experts available now in Live!

Get 1:1 Help Now