If you have managed an Exchange server in the past, you’ve probably been required to set things up to allow printers, applications, and other devices the ability to send email through the Exchange server. Most often, the solution to this request is to configure an Anonymous Open Relay connector. The first article I ever wrote on this blog was on that very subject: http://wp.me/pUCB5-b . If you need to know what a Relay is, go read that blog.
What people don’t always do, though, is consider the question of whether or not they need an anonymous relay in Exchange. I didn’t really cover that subject in my first article, so I’ll cover it here.
When you Need an Open Relay
There are three factors that determine whether an organization needs an Open Relay. Anonymous relay is only required if you meet all three of the factors. Any other combination can be worked around without using anonymous relaying. I’ll explain how later, but for now, here are the three factors you need to meet:
- Printers, Scanners, and Applications don’t support changes to the SMTP port used.
- Printers, Scanners, and Applications don’t support SMTP Authentication.
- Your system needs to send mail to email addresses that don’t exist in your mail environment (That is to say, your system sends mail to email addresses that you don’t manage with your own mail server).
At this point, I feel it important to point out that Anonymous relays are inherently insecure. You can make them more secure by limiting access, but using an anonymous relay will always place a technical solution in the environment that is designed specifically to circumvent normal security measures. In other words, do so at your own informed risk, and only when it’s absolutely required.
The First Factor
If the system you want to send SMTP messages doesn’t allow you to send email over a port other than 25, you will need to have an open relay if the messages the system sends are addressed to email addresses outside your environment. The bold stuff there is an important distinction. The SMTP protocol defines port 25 as the “default” port for mail exchange, and that’s the port that every email server uses to receive email from all other systems, which means that, based on modern security concerns, sending mail to port 25 is only allowed if the recipient of the email you send exists on the mail server. So if you are using the abc.com mail server to send messages to firstname.lastname@example.org, you will need to use a relay server to do it, or the mail will be rejected because relay is (hopefully) not allowed.
The Second Factor
If your system doesn’t allow you to specify a username and password in the SMTP configuration it has, then you will have to send messages Anonymously. For our purposes, an “anonymous” user is a user that hasn’t logged in with a username and password. SMTP servers usually talk to one another Anonymously, so it’s actually common for anonymous SMTP access to be valid and is actually necessary for mail exchange to function, but SMTP servers will, by default, only accept messages that are destined for email addresses that they manage. So if abc.com receives a message destined for email@example.com, it will accept it. However, abc.com will reject messages to firstname.lastname@example.org, *unless* the SMTP session is Authenticated. In other words, if email@example.com wants to send jim @xyz.com a message, he can open an SMTP session with the abc.com mail server, enter his username and password, and send the message. If he does that, the SMTP server will accept the message, then contact the xyz.com mail server and deliver it. The abc.com mail server doesn’t need to have a username and password to do this, because the xyz.com mail server knows who firstname.lastname@example.org is, so it just accepts the message and delivers it to the correct mailbox. So if you are able to set a username and password with the system you need to send mail with, you don’t need anonymous relay.
The Third Factor
Most of the time, applications and devices will only need to send messages to people who have mailboxes in your environment, but there are plenty of occasions where applications or devices that send email out need to be able to send mail to people *outside* the environment. If you don’t need to send to “external recipients” as these users are called, you can use the Direct Send method outlined in the solutions below.
As promised, here are the solutions you can use *other* than anonymous relay to meet the needs of your application if it doesn’t meet *all three* of the deciding factors.
Authenticated Relay (Factor #3 applies)
In Exchange server, there is a default “Receive Connector” that accepts all messages sent by Authenticated users on port 587, so if your system allows you to set a username and password and change the port, you don’t need anonymous relaying. Just configure the system to use your Exchange Hub Transport server (or CAS in 2013) on port 587, and it should work fine, even if your requirements meet the last deciding factor of sending mail to external recipients.
Direct Send (Factor #2 applies and/or #3 doesn’t apply)
If your system needs to send messages to abc.com users using the abc.com mail server, you don’t need to relay or authenticate. Just configure your system to send mail directly to the mail server. The “direct send” method uses SMTP as if it were a mail server talking to another mail server, so it works without additional work. Just note that if you have a spam filter that enforces SPF or blocks messages from addresses in your environment to addresses in your environment, it’s likely these messages will get blocked, so make allowances as needed.
Authenticated Mail on Port 25 (Only factor #1 applies)
If the system doesn’t allow you to change the port number your system uses, but does allow you to authenticate, you can make a small change to Exchange to allow the system to work. This is done by opening the Default Receive connector (AKA – the Default Front End receive connector on Exchange 2013 and later) and adding Exchange Users to the Permission settings on the Security tab as shown with the red X below:
Once this setting is changed, restart the Transport service on the server and you can then perform authenticated relaying on port 25.
If you do find you need to use an anonymous relay, by all means, do so with careful consideration, but always be conscious of the fact that it isn’t always necessary. As always, comments questions on this article and others are always welcome and I’ll do my best to answer as soon as possible.
2 thoughts on “Do I need Anonymous Relay?”
Great article thank you.
Another requirement for anonymous relay is when using a cloud based security platform for incoming Email (where the MX records point to). The cloud based system then relays to an internal Exchange server in an organisation. Anonymous relay is required on the receive connector along with restricting the IP’s to the cloud platform only.
This is better than using a secured IPSEC restriction as it ensures that the relayed mail is not classed as internal (thus Exchange will rate it with SCL).
Relaying isn’t necessary in this situation on the Exchange server (or shouldn’t be). If cloud security systems have a need to relay messages using an on premises server, they should allow you to use authenticated smtp. If they don’t, switch vendors.
Most mail traffic from cloud to on premises servers doesn’t require a receive connector to function other than the default port 25 connector. A separate connector is only necessary if you want to use a different port, which is a waste of effort. Cloud security services should only relay if they are trying to send messages as an on premises user. In that case, it is actually better to use the direct send technique above and allow the message through on premises filtering.
Anonymous relay is enough of a security risk that it should be avoided if possible. If you are using a cloud service that requires anonymous relay in order to function, switch providers if you can and complain loudly about the lack of Auth smtp function if you can’t.