Solved

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

Posted on 2014-10-08
5
240 Views
Last Modified: 2014-10-23
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?
0
Comment
Question by:ruhkus
[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
5 Comments
 
LVL 63

Assisted Solution

by:Simon Butler (Sembee)
Simon Butler (Sembee) earned 200 total points
ID: 40369480
Nothing has changed in Exchange 2013.
Create a new connector but make sure the scope settings are correct so that your connector is used.

Simon.
0
 
LVL 25

Expert Comment

by:Mohammed Khawaja
ID: 40369506
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.
0
 
LVL 31

Accepted Solution

by:
Gareth Gudger earned 300 total points
ID: 40369833
Simon is correct. You can set up a Receive Connector like you did in 2007 for anonymous application relay. If you need it to relay externally it does require a little more PowerShell. But nothing has changed since 2007.
0
 

Author Comment

by:ruhkus
ID: 40370551
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.
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40370577
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/
0

Featured Post

Veeam gives away 10 full conference passes

Veeam is a VMworld 2017 US & Europe Platinum Sponsor. Enter the raffle to get the full conference pass. Pass includes the admission to all general and breakout sessions, VMware Hands-On Labs, Solutions Exchange, exclusive giveaways and the great VMworld Customer Appreciation Part

Question has a verified solution.

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

The new Gmail Phishing Scam going around is surprising even the savviest of users with its sophisticated techniques.
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.
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…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses
Course of the Month2 days, 19 hours left to enroll

622 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