Solved

Exchange 2013 Receiver frustrations

Posted on 2014-10-20
1
1,983 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
[X]
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
1 Comment
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 40392499
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

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

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

Read this checklist to learn more about the 15 things you should never include in an email signature.
This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
In this video we show how to create an email address policy 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…
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…

724 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