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.
Page 1 / 1
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!
Darren
Did you ever get this working? We have the same issue. Tried @daz_wallace 's suggestion but that didn't work.
thanks
Raj
We figured it out - you need to use TLS and the UPN in the username field for it to work.
Well played, it worked for me. Thanks @typeraj
How do you setup smtp setting for Office 365 with no on prem smtp server?
not working for me tried all encryption settings combined with UPN
try the following (although this will be an issue when MSFT deprecates BasicAuth)
Server and Port: smtp.outlok.com : 587
Encryption: TLSv1.2
Requires Authentication: Enable + Add UID/PASS
Yeah any news from Jamf to support the new modern auth with SMTP?
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 ?
Same boat. Can't get SMTP to work with O365
I finally found a workaround for this.
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.
ERROR:Error sending message.
SUGGESTION:Ensure you can connect to the SMTP Server.
Just to re-confirm what I am using (successfully):
Server: smtp.outlook.com
Port: 587
Connection Timeout: 5s
Requires Authentication: <username> <password>
Encryption: TLSv1.2
Just to re-confirm what I am using (successfully):
Server: smtp.outlook.com
Port: 587
Connection Timeout: 5s
Requires Authentication: <username> <password>
Encryption: TLSv1.2
Thanks for the feedback!
I tried that, still failing.
- Tried both smtp.office365.com and smtp.outlook.com
- both ports 25 and 587
- Connection timeout from 5 to 20 seconds
- With and without authentication
- All encryption options
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.
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.
ERROR:Error sending message.
SUGGESTION:Ensure you can connect to the SMTP Server.
I am also stuck in the same situation... will you suggest me if, you got the way out
I am also stuck in the same situation... will you suggest me if, you got the way out
Not yet - opened a case with Jamf support, but they were not able to help
________________________________
"This e-mail and any accompanying attachments are confidential. The information is intended solely for the use of the individual to whom it is addressed. Any review, disclosure, copying, distribution, or use of the email by others is strictly prohibited. If you are not the intended recipient, you must not review, disclose, copy, distribute or use this e-mail; please delete it from your system and notify the sender immediately."
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.
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.
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.
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.
I've tried using an account that is enabled for Basic Authentication for SMTP - didn't make a difference.
________________________________
"This e-mail and any accompanying attachments are confidential. The information is intended solely for the use of the individual to whom it is addressed. Any review, disclosure, copying, distribution, or use of the email by others is strictly prohibited. If you are not the intended recipient, you must not review, disclose, copy, distribute or use this e-mail; please delete it from your system and notify the sender immediately."
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.