asked on

Exchange 2013 - best way to configure internal software/scanners/etc. to send e-mails

In Exchange 2007, we were able to set up a receive connector with anonymous authentication that allowed internal software and hardware (printers, scanners, event notification processes) to send e-mails. It is my understanding that with Exchange 2013, creating a similar receive connector using port 25 may end up breaking Exchange. I tried to configure it to work with the default options in Exchange for port 25 but that didn't work either.

One option seems to be to use another port, but some of these simpler services will only work with port 25.

What is the best way to configure Exchange for these services to properly work?

SOLUTION

Simon Butler (Sembee)

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Mohammed Khawaja

What I recommend doing is setup SMTP services on an IIS server and create a remote domain for your Exchange. Setup IP based relay for your devices and this way you could always change the SMTP configuration or relay list without worrying about breaking anything in Exchange.

ASKER CERTIFIED SOLUTION

Gareth Gudger

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ruhkus

ASKER

Thanks. My question comes due to posts such as this one - link

As far as I can tell, I should just need to specify it as a front-end transport receive connector and not hub transport (since multi-role server) and it should work fine, but I wanted to make sure.

Gareth Gudger

Yes. It needs to be a FrontEnd.

I would follow this article from Paul Cunningham. This is the way I always follow.
http://exchangeserverpro.com/exchange-2013-configure-smtp-relay-connector/