-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Microsoft 365 SMTP could not authenticate in SuiteCRM #9371
Comments
Hey, I haven't used Office365 myself, I'm afraid, but I have had a look around for those error messages. Perhaps some of the steps here can assist?: This thread mentions enabling/using App Passwords for Office365: This thread here mentions modifying the Security options for Legacy Auth/Azure: This thread mentions enabling "Authenticated SMTP" in your Office 365 Admin panel: Does anything above lead you to a solution? |
Not directly an issue with SuiteCRM, your O365 tenant has SMTP auth disabled. You can either get it enabled or use a 3rd party SMTP service such as Sendgrid, Amazon SES etc as many of them support SMTP plain text auth. We have a similar ticket for Gsuite deprecation of SMTP plain auth #8791.
|
Tengo el mismo problema con gmail and O365 |
I have the same problem with gmail and o365 |
solved with google when creating an application password https://support.google.com/accounts/answer/185833?hl=es but not with office because it no longer allows creating an application password now it asks to create MFA authentication |
Issue
Office365 SMTP settings cannot authenticate in SuiteCRM.
When I try to configure the default outgoing mail server for sending email notifications using Microsoft 365 smtp.office365, port 587, SuiteCRM gives me SMTP Error: Could not authenticate.
Here is the log
Expected Behavior
I want to be able to configure SuiteCRM outbound email using the Office 365 SMTP settings:
server: smtp.office365.com
port: 587 (SSL/TLS)
Actual Behavior
Every time I try to send a test email, I get this error:
SMTP Error: Could not authenticate
Possible Fix
Have no idea.
Steps to Reproduce
Context
As a lot of corporate clients use O365, it is critical to have the issue resolved.
Your Environment
The text was updated successfully, but these errors were encountered: