Posted on 10-04-2016 12:34 PM
I am trying to setup out JSS to relay messages out to Office 365. All of our mailboxes are in the cloud.I have it setup to use smtp.office365.com on port 587 with SSL. Anyone else set this up and have any info. I keep getting an error when sending a test email.
Posted on 10-04-2016 11:57 PM
We have this running with our JSS at the moment.
The only difference we have is using TLS instead of SSL
I'd suggest giving that a go. Good luck!
Posted on 01-04-2017 12:13 PM
Did you ever get this working? We have the same issue. Tried @daz_wallace 's suggestion but that didn't work.
Posted on 01-04-2017 12:49 PM
We figured it out - you need to use TLS and the UPN in the username field for it to work.
Posted on 02-24-2018 10:34 AM
Posted on 03-25-2020 01:46 PM
How do you setup smtp setting for Office 365 with no on prem smtp server?
Posted on 09-02-2020 10:02 AM
not working for me tried all encryption settings combined with UPN
Posted on 01-26-2021 10:18 AM
try the following (although this will be an issue when MSFT deprecates BasicAuth)
Server and Port: smtp.outlok.com : 587
Requires Authentication: Enable + Add UID/PASS
Posted on 01-26-2021 12:34 PM
Yeah any news from Jamf to support the new modern auth with SMTP?
Posted on 10-26-2021 07:20 AM
we are in october 2021. still cannot use the smtp with our azure modern auth. smtp basicauth is disable on azure.
anyone has found a solution ?
Posted on 11-03-2021 01:11 PM
Same boat. Can't get SMTP to work with O365
Posted on 03-29-2022 09:46 AM
I finally found a workaround for this.
How to set up a multifunction device or application to send email using Microsoft 365 or Office 365 ...
Posted on 05-23-2022 02:08 PM
I have the same problem, and have a consultant assisting us with our setup who does not know why it's not working.
Set this up with an account that is NOT enabled for MFA, with the SMTP authentication enabled.
Using port 587 with TLSv1.2 (tried the others also).
UPN for the username
Tried the workaround posted by jsmith_pbs.
Still not working.
Posted on 12-27-2022 10:59 PM
I am also stuck in the same situation... will you suggest me if, you got the way out
Posted on 01-03-2023 12:00 PM
Posted on 05-24-2022 05:53 AM
Just to re-confirm what I am using (successfully):
Connection Timeout: 5s
Requires Authentication: <username> <password>
Posted on 05-24-2022 10:40 AM
Thanks for the feedback!
I tried that, still failing.
And every combination possible of the above
Verified the password on the account, verified that it is NOT enabled for MFA, verified that the account is enabled and can log in, and that SMTP authentication is enabled on the account.
I also created a connector in Exchange online, with all the IP addresses Jamf lists as sending IPs
Also verified that there are no conditional access policies that would be blocking.
Still no joy.
Might be a lost cause, but I've opened a support case with Jamf about this.
We've been working with a consultant to help us get up to speed on Jamf for Mac management, and he can't figure it out either.
Posted on 01-06-2023 06:30 PM
Like most other orgs basic auth in O365 should be disabled which would break this setup that @markdmatthews shared. Jamf still needs to update their product to support modern auth or other method with O365.
Posted on 01-09-2023 05:43 AM
Agreed on Basic Auth and that Jamf needs to provide an SMTP server for Jamf Pro Cloud, but the account as setup...
The account is member of a group which allows connection to O365 without MFA from outside of Organization and is given exception for basic auth for SMTP protocol using a configured policy.
Posted on 01-10-2023 08:30 AM