SmarterMail Configured for SMTP Relay on Azure where Port 25 Blocked
Question asked by Marc Rohrer - 2/15/2020 at 9:30 AM

We've been using SmarterMail Free Edition (Build 7242) as an SMTP Relay server for years. We're migrating to Azure, and have found out that Port 25 is blocked. We're trying to configure SmarterMail to use Port 587 instead. However, I haven't figured out how to get the connection to send out the emails to occur on Port 587. Generally, we configure SmarterMail based on our notes, and then let it run for years without having to interact with it. We ran through the configuration, which we then learned of Port 25 was blocked by Azure. We haven't been able to figure out how to use Port 587 to send the email out from SmarterMail.

When the email is generated by the app, it is being sent to Which does make it into the SmarterMail spool.But when SmarterMail goes to send it out, it's always on Port 25. Such as to Google,

I'm hoping there is away to configure the SMTP out for SMTP Relay to use Port 587. Unfortunately, I'm not seeing it right. Any help will be greatly appreciated.


4 Replies

Reply to Thread
Sébastien Riccio Replied
Inter-server SMTP communication (outgoing mail from your server) always occurs on port 25.
I think I read somewhere that you can ask AWS to allow port 25 for your IP.

Google sent me here:

echoDreamz Replied
Sébastien Riccio Replied
You're right. I had AWS in mind and I have no idea why...
Marc Rohrer Replied
Thanks for the information, and what I kind of expected.

Reply to Thread