Exchange 2013 Receive Connector for SMTP Enabled internal devices

Posted on 2013-06-12
Last Modified: 2013-12-04
Hi All,

We are migrating to Exchange 2013 and have hit a problem many on this version have encountered and many not yet resolved.

We have a number of devices that use SMTP to send status reports and scanned docs to our email server.  They have worked fine with Exchange 2010 but 2013 isn't playing the game, and I must be doing something wrong.

In ECP I have created a receive connector
I select Hub Transport as the role
I then select Custom
I leave the adapter bindings at default
I remove the "Remote Network" IP's, and assign the range of our internal ip range
I save this connector then open its properties to set the authentication under Security.  I uncheck all types so that no method of authentication is required.
for permission groups I only select anonymous

Does anyone have a step by step procedure on how to setup an receive connector for devices not capable of authenticating.
Question by:mbkitmgr
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
LVL 10

Expert Comment

by:Senthil Kumar
ID: 39240519
Try creating a receive connector for a single device IP address and check whether it works. Give this receive connector permission to anonymous and  check.

Author Comment

ID: 39246543
Thanks , while I had tried this, I did do it again and Exchange still does not receive the email from simple devices

Author Comment

ID: 39249248
Many thanks to the moderator who rightly so pointed out this should have been included.

Like any organisation, I have a number of devices ranging from routers to switches, printers to multi-function centers, and some applications/scripts that send email via SMTP.

Some devices have no authentication mechanism in their software, while others offer windows credentials, and some support TLS.  I have been doing quite a bit of research on this and some suggestions either don't work, or are ill advised.  On one MS forum the "Moderator" confessed they had no idea how or if it could be done.

So what is the best way, and can it be provided as a step by step method.  I've set them up in the past with since Exchange 5.5, 2000, 2003, 2007, 2010 but cant crack it in 2013.  Judging by the number of hits on topics around this I am not in the minority.

I manage many sites that have the same types of devices making migration to Exchange 2013 a risk - so is it possible at all with Exchange 2013 - or do we exercise our downgrade rights to 2010 so that our major devices like the Multifunction centres can work in the way intended.?

To date I have tested Receive Connectors with the following properties

Custom Connector
tried both Hub and Frontend transport roles
With no Security, Basic Security, TLS Security (for those devices that supported it)
Permission group = anonymous
Remote Network settings = All Internal IP Addresses
Left Adapter bindings as defaults (all avail IPV4)
Automating Your MSP Business

The road to profitability.
Delivering superior services is key to ensuring customer satisfaction and the consequent long-term relationships that enable MSPs to lock in predictable, recurring revenue. What's the best way to deliver superior service? One word: automation.

LVL 14

Expert Comment

ID: 39258009
Set security to anonymous and externally secured. What ip scope do you have for your default connector? As your edge device be it firewall or spam appliance etc will be delivering mail on the same subnet, is the default connector being chosen and this rejecting the mail?

You should reduce the scope of the internal connector to the IPs of the devices and turn on logging of the connectors to get some additional information.
LVL 37

Expert Comment

by:Jian An Lim
ID: 39261033
can you provide your receive connector in exchange 2010 ? (and exchange 2013?)

protocol logging: "verbose"
goto network - make sure receive mail from remote servers have the "right IP"
go to authentication and click "externally secured"
goto permission groups and click "exchange servers"


This should allow any email to sent (if match the IP) from anywhere to everywhere.

Author Comment

ID: 39270743
Ran the command ,

Get-ReceiveConnector "[Cust] - Relay Connector" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "ms-Exch-SMTP-Accept-Any-recipient"

Open in new window

Restarted the transport service and front end transport.
LVL 37

Expert Comment

by:Jian An Lim
ID: 39271163
anyway, your way works as well, but it will require powershell.
the way i use exchange server as permission groups will not require so ..
but works well ...

Accepted Solution

mbkitmgr earned 0 total points
ID: 39338345
The solution was provided by MS Exchange Support.  The vendor for our Digital Copier paid to have have it provided

Author Closing Comment

ID: 39347411
Resolved by Microsoft Support

Featured Post

Migrating Your Company's PCs

To keep pace with competitors, businesses must keep employees productive, and that means providing them with the latest technology. This document provides the tips and tricks you need to help you migrate an outdated PC fleet to new desktops, laptops, and tablets.

Question has a verified solution.

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

This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
If you troubleshoot Outlook for clients, you may want to know a bit more about the OST file before doing your next job. IMAP can cause a lot of drama if removed in the accounts without backing up.
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…
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…

690 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