Internally hosted, SMTP broke, when upgrading from 10.x to 11.x

[donmontalvo]

Just wanted to see if anyone else had an SMTP issue upgrading an internally hosted Jamf Pro server from 10.x to 11.x? If so, how did you resolve it? We have two internally hosted Jamf Pro server environments, in the 10.x environment SMTP works fine, however in the 11.x upgraded environment it stopped working. We have a ticket open, but wanted to check here too.

[obi-k]

Looks like you might be joining the party. Were you using port 25 for SMTP?

https://community.jamf.com/t5/jamf-pro/guide-how-to-configure-jamf-pro-smtp-with-m365/m-p/264099#M24...

[donmontalvo]

Port 25 is used on both our Jamf Pro servers. The SMTP issue is only impacting the Jamf Pro that was upgraded from 10.50.0 to 11.3.2. SMTP continues to work fine on the Jamf Pro server that has not been upgraded yet (still on 10.50.0).

I understand Jamf Cloud doesn't allow communication over Port 25. We are internally hosted, so Port 25 is allowed and supported for internally hosted SMTP traffic.

[donmontalvo · Accepted solution]

This issue was resolved, as it turned out our SMTP configuration was not set up correctly. We only recently noticed since we don't normally send emails from our DEV environment. Once we updated the configuration, it works fine.