starred/SuiteCRM-SuiteCRM

Fork 0

mirror of https://github.com/SuiteCRM/SuiteCRM.git synced 2026-03-02 19:16:58 -05:00

Outbound/Inbound Mail: Office365 SMTP Error: Could not authenticate. v7.13 #4924

New issue

Open

opened 2026-02-20 16:26:20 -05:00 by deekerman · 17 comments

deekerman commented

2026-02-20 16:26:20 -05:00

Owner

Originally created by @bunglex on GitHub (Jan 13, 2023).

Issue

Can't set 'Outbound Email' or create 'Personal Outbound Email Account because authentication fails.

Expected Behavior

After setting up 'External OAuth Provider' and 'External OAuth Connector' and successfully retrieving an Access and Refresh Token, you should able to configure 'Outbound Email Settings' and setup a 'Personal Outbound Email Account', and also create inbound email account.

In the detail page for Personal Outbound Email Account , the 'send test email' should send test email when the correct settings are used.

Actual Behavior

In the detail page for Personal Outbound Email Account , the 'send test email' fails and returns an SMTP log that states

Authentication unsuccessful, the user credentials were incorrect.
SMTP Error: Could not authenticate.

SuiteCRm logs :

[FATAL] Using imap handler class: Imap2Handler
[FATAL] An Imap error detected: "IMAP open error: Can not authenticate to IMAP server: A0001 NO AUTHENTICATE failed."
[FATAL] An Imap error detected: "IMAP open error | debug data"
[FATAL] An Imap error detected: "ImapHandler:open: {outlook.office365.com:993\/service=imap\/ssl\/tls\/validate-cert\/secure}INBOX"
[FATAL] An Imap error detected: "ImapHandler:open: Info"
[FATAL] An Imap error detected: "ImapHandler:open: password is empty: no"
[FATAL] An Imap error detected: "ImapHandler:open: 512"
[FATAL] An Imap error detected: "IMAP open error | debug data end "
[FATAL] ImapHandler trying to use a non valid resource stream.
[FATAL] An Imap error detected: "IMAP open error:Can not authenticate to IMAP server: A0001 NO AUTHENTICATE failed."
[FATAL] ImapHandler trying to use a non valid resource stream.
[FATAL] ImapHandler trying to use a non valid resource stream.
[FATAL] An Imap error detected: "IMAP open error: Can not authenticate to IMAP server: A0001 NO AUTHENTICATE failed."
[FATAL] An Imap error detected: "IMAP open error | debug data"
[FATAL] An Imap error detected: "ImapHandler:open: {outlook.office365.com:993\/service=imap\/ssl\/tls\/validate-cert\/secure}INBOX"
[FATAL] An Imap error detected: "ImapHandler:open: Info"
[FATAL] An Imap error detected: "ImapHandler:open: password is empty: no"
[FATAL] An Imap error detected: "ImapHandler:open: 512"
[FATAL] An Imap error detected: "IMAP open error | debug data end "
[FATAL] ImapHandler trying to use a non valid resource stream.
[FATAL] An Imap error detected: "IMAP open error:Can not authenticate to IMAP server: A0001 NO AUTHENTICATE failed."
[FATAL] ImapHandler trying to use a non valid resource stream.
[FATAL] ImapHandler trying to use a non valid resource stream.
[FATAL] An Imap error detected: "IMAP open error: Can not authenticate to IMAP server: A0001 NO AUTHENTICATE failed."
[FATAL] An Imap error detected: "IMAP open error | debug data"
[FATAL] An Imap error detected: "ImapHandler:open: {outlook.office365.com:993\/service=imap\/ssl\/tls\/validate-cert\/secure}INBOX"
[FATAL] An Imap error detected: "ImapHandler:open: Info"
[FATAL] An Imap error detected: "ImapHandler:open: password is empty: no"
[FATAL] An Imap error detected: "ImapHandler:open: 512"
[FATAL] An Imap error detected: "IMAP open error | debug data end "
[FATAL] ImapHandler trying to use a non valid resource stream.
[FATAL] An Imap error detected: "IMAP open error:Can not authenticate to IMAP server: A0001 NO AUTHENTICATE failed."
[FATAL] ImapHandler trying to use a non valid resource stream.
[FATAL] ImapHandler trying to use a non valid resource stream.
[FATAL] An Imap error detected: "Can not authenticate to IMAP server: A0001 NO AUTHENTICATE failed."

However, if you re-enter the password 'after' opening the page, the test succeeds and the email is sent correctly.
forum post here

Possible Fix

unknown

Steps to Reproduce

Log into SuiteCRM as admin
Go to Admin > Outbound Email
Create or select/edit a Personal Outbound Email Account
Exchange Server: outlook.office365.com
Mail SMTP/SLL: TLS
Exchange Server Port: 587
User SMTP Authentication: X
Password: your O365 password
Send Test email

Authentication fails and displays SMTP Log

Enter Password again
Send Test Email

Test passes and email is sent

Context

Can't setup an office365 outbound or inbound email account

Your Environment

SuiteCRM Version used: 7.13
Browser name and version : Chrome Version 109.0.5414.74 (64-bit)):
Environment name and version : Mysql8 PHP 7.4
Operating System and version: Ubuntu 20.04

Originally created by @bunglex on GitHub (Jan 13, 2023). #### Issue   Can't set 'Outbound Email' or create 'Personal Outbound Email Account because authentication fails. #### Expected Behavior  After setting up 'External OAuth Provider' and 'External OAuth Connector' and successfully retrieving an Access and Refresh Token, you should able to configure 'Outbound Email Settings' and setup a 'Personal Outbound Email Account', and also create inbound email account. In the detail page for Personal Outbound Email Account , the 'send test email' should send test email when the correct settings are used. #### Actual Behavior   In the detail page for Personal Outbound Email Account , the 'send test email' fails and returns an SMTP log that states **`Authentication unsuccessful, the user credentials were incorrect.`** **`SMTP Error: Could not authenticate.`** SuiteCRm logs : ``` [FATAL] Using imap handler class: Imap2Handler [FATAL] An Imap error detected: "IMAP open error: Can not authenticate to IMAP server: A0001 NO AUTHENTICATE failed." [FATAL] An Imap error detected: "IMAP open error | debug data" [FATAL] An Imap error detected: "ImapHandler:open: {outlook.office365.com:993\/service=imap\/ssl\/tls\/validate-cert\/secure}INBOX" [FATAL] An Imap error detected: "ImapHandler:open: Info" [FATAL] An Imap error detected: "ImapHandler:open: password is empty: no" [FATAL] An Imap error detected: "ImapHandler:open: 512" [FATAL] An Imap error detected: "IMAP open error | debug data end " [FATAL] ImapHandler trying to use a non valid resource stream. [FATAL] An Imap error detected: "IMAP open error:Can not authenticate to IMAP server: A0001 NO AUTHENTICATE failed." [FATAL] ImapHandler trying to use a non valid resource stream. [FATAL] ImapHandler trying to use a non valid resource stream. [FATAL] An Imap error detected: "IMAP open error: Can not authenticate to IMAP server: A0001 NO AUTHENTICATE failed." [FATAL] An Imap error detected: "IMAP open error | debug data" [FATAL] An Imap error detected: "ImapHandler:open: {outlook.office365.com:993\/service=imap\/ssl\/tls\/validate-cert\/secure}INBOX" [FATAL] An Imap error detected: "ImapHandler:open: Info" [FATAL] An Imap error detected: "ImapHandler:open: password is empty: no" [FATAL] An Imap error detected: "ImapHandler:open: 512" [FATAL] An Imap error detected: "IMAP open error | debug data end " [FATAL] ImapHandler trying to use a non valid resource stream. [FATAL] An Imap error detected: "IMAP open error:Can not authenticate to IMAP server: A0001 NO AUTHENTICATE failed." [FATAL] ImapHandler trying to use a non valid resource stream. [FATAL] ImapHandler trying to use a non valid resource stream. [FATAL] An Imap error detected: "IMAP open error: Can not authenticate to IMAP server: A0001 NO AUTHENTICATE failed." [FATAL] An Imap error detected: "IMAP open error | debug data" [FATAL] An Imap error detected: "ImapHandler:open: {outlook.office365.com:993\/service=imap\/ssl\/tls\/validate-cert\/secure}INBOX" [FATAL] An Imap error detected: "ImapHandler:open: Info" [FATAL] An Imap error detected: "ImapHandler:open: password is empty: no" [FATAL] An Imap error detected: "ImapHandler:open: 512" [FATAL] An Imap error detected: "IMAP open error | debug data end " [FATAL] ImapHandler trying to use a non valid resource stream. [FATAL] An Imap error detected: "IMAP open error:Can not authenticate to IMAP server: A0001 NO AUTHENTICATE failed." [FATAL] ImapHandler trying to use a non valid resource stream. [FATAL] ImapHandler trying to use a non valid resource stream. [FATAL] An Imap error detected: "Can not authenticate to IMAP server: A0001 NO AUTHENTICATE failed." ``` However, if you re-enter the password 'after' opening the page, the test succeeds and the email is sent correctly. [forum post here](https://community.suitecrm.com/t/imaphandler-errors-how-to-setup-inbound-email-for-office365-v7-12-5/87565/6) #### Possible Fix  unknown #### Steps to Reproduce   1. Log into SuiteCRM as admin 2. Go to Admin > Outbound Email 3. Create or select/edit a Personal Outbound Email Account 4. Exchange Server: outlook.office365.com 5. Mail SMTP/SLL: TLS 6. Exchange Server Port: 587 7. User SMTP Authentication: X 8. Password: your O365 password 9. Send Test email Authentication fails and displays SMTP Log 10. Enter Password again 11. Send Test Email Test passes and email is sent #### Context   Can't setup an office365 outbound or inbound email account #### Your Environment  * SuiteCRM Version used: 7.13 * Browser name and version : Chrome Version 109.0.5414.74 (64-bit)): * Environment name and version : Mysql8 PHP 7.4 * Operating System and version: Ubuntu 20.04

deekerman added the

Type: Bug

Priority:Important

Area: Emails:Config

labels

2026-02-20 16:26:20 -05:00

deekerman commented

2026-02-20 16:26:23 -05:00

Author

Owner

@SuiteBot commented on GitHub (Jan 14, 2023):

This issue has been mentioned on SuiteCRM. There might be relevant details there:

https://community.suitecrm.com/t/oauth-connection-for-inbound-emails/87421/5

@SuiteBot commented on GitHub (Jan 14, 2023): This issue has been mentioned on **SuiteCRM**. There might be relevant details there: https://community.suitecrm.com/t/oauth-connection-for-inbound-emails/87421/5

deekerman commented

2026-02-20 16:26:23 -05:00

Author

Owner

@SuiteBot commented on GitHub (Jan 14, 2023):

This issue has been mentioned on SuiteCRM. There might be relevant details there:

https://community.suitecrm.com/t/imaphandler-errors-how-to-setup-inbound-email-for-office365-v7-12-5/87565/8

@SuiteBot commented on GitHub (Jan 14, 2023): This issue has been mentioned on **SuiteCRM**. There might be relevant details there: https://community.suitecrm.com/t/imaphandler-errors-how-to-setup-inbound-email-for-office365-v7-12-5/87565/8

deekerman commented

2026-02-20 16:26:23 -05:00

Author

Owner

@timo-ecm2 commented on GitHub (Jan 16, 2023):

Yes I have a similar issue, only I was specific busy with inbound email account.

@timo-ecm2 commented on GitHub (Jan 16, 2023): Yes I have a similar issue, only I was specific busy with inbound email account.

deekerman commented

2026-02-20 16:26:23 -05:00

Author

Owner

@greentreegroup commented on GitHub (Jan 20, 2023):

we are also having issues connecting m365 to suitecrm when sending emails.

@greentreegroup commented on GitHub (Jan 20, 2023): we are also having issues connecting m365 to suitecrm when sending emails.

deekerman commented

2026-02-20 16:26:23 -05:00

Author

Owner

@timo-ecm2 commented on GitHub (Jan 23, 2023):

What about connecting to a gmail account, happens the same?

@timo-ecm2 commented on GitHub (Jan 23, 2023): What about connecting to a gmail account, happens the same?

deekerman commented

2026-02-20 16:26:23 -05:00

Author

Owner

@bunglex commented on GitHub (Jan 27, 2023):

the password is saved and the email sent correctly when using a gmail account
?

@bunglex commented on GitHub (Jan 27, 2023): the password is saved and the email sent correctly when using a gmail account ?

deekerman commented

2026-02-20 16:26:23 -05:00

Author

Owner

@timo-ecm2 commented on GitHub (Jan 30, 2023):

ok thnx @bunglex for the information. Do you know where I can find a good manual / information for a gmail account

@timo-ecm2 commented on GitHub (Jan 30, 2023): ok thnx @bunglex for the information. Do you know where I can find a good manual / information for a gmail account

deekerman commented

2026-02-20 16:26:23 -05:00

Author

Owner

@Lehnerr commented on GitHub (Apr 14, 2023):

I have the same issue, pls help

@Lehnerr commented on GitHub (Apr 14, 2023): I have the same issue, pls help

deekerman commented

2026-02-20 16:26:23 -05:00

Author

Owner

@pgorod commented on GitHub (Apr 14, 2023):

Does this still occur on the latest 7.13?

@pgorod commented on GitHub (Apr 14, 2023): Does this still occur on the latest 7.13?

deekerman commented

2026-02-20 16:26:23 -05:00

Author

Owner

@Lehnerr commented on GitHub (Apr 14, 2023):

yes 7.13.2

@Lehnerr commented on GitHub (Apr 14, 2023): yes 7.13.2

deekerman commented

2026-02-20 16:26:23 -05:00

Author

Owner

@SuiteBot commented on GitHub (May 10, 2023):

This issue has been mentioned on SuiteCRM. There might be relevant details there:

https://community.suitecrm.com/t/email-setup-help-and-explanation/88999/2

@SuiteBot commented on GitHub (May 10, 2023): This issue has been mentioned on **SuiteCRM**. There might be relevant details there: https://community.suitecrm.com/t/email-setup-help-and-explanation/88999/2

deekerman commented

2026-02-20 16:26:23 -05:00

Author

Owner

@pstevens71 commented on GitHub (May 24, 2023):

I suspect it might be this issue: there is a fix proposed and it works (I tested it).
https://github.com/salesagility/SuiteCRM/issues/9457

@pstevens71 commented on GitHub (May 24, 2023): I suspect it might be this issue: there is a fix proposed and it works (I tested it). [https://github.com/salesagility/SuiteCRM/issues/9457](url)

deekerman commented

2026-02-20 16:26:23 -05:00

Author

Owner

@chris001 commented on GitHub (May 24, 2023):

@pstevens71 That link leads to a non existent page.... this is the one: https://github.com/salesagility/SuiteCRM/issues/9457

@chris001 commented on GitHub (May 24, 2023): @pstevens71 That link leads to a non existent page.... this is the one: https://github.com/salesagility/SuiteCRM/issues/9457

deekerman commented

2026-02-20 16:26:24 -05:00

Author

Owner

@pstevens71 commented on GitHub (Jun 27, 2023):

The previous #9457 doesn't seem to work for me on 7.13.3. I just cannot seem to authenticate outbound email.
I've tried ins sugarmailer.php to use the debugging to force the correct password and it works no problem. However, I cannot get test to work or after it's saved to work. I checked the DB and there are values in the password. Anyone know the password encryption? Is it MD5?

Also further info.... when using a gmail account with an app password, I can send a test and verify. However, the user cannot send with this account. (yes I have the option selected).

@pstevens71 commented on GitHub (Jun 27, 2023): The previous #9457 doesn't seem to work for me on 7.13.3. I just cannot seem to authenticate outbound email. I've tried ins sugarmailer.php to use the debugging to force the correct password and it works no problem. However, I cannot get test to work or after it's saved to work. I checked the DB and there are values in the password. Anyone know the password encryption? Is it MD5? Also further info.... when using a gmail account with an app password, I can send a test and verify. However, the user cannot send with this account. (yes I have the option selected).

deekerman commented

2026-02-20 16:26:24 -05:00

Author

Owner

@rmunoz10 commented on GitHub (Aug 3, 2024):

v7.14.4 Inbound fails too.

Sat Aug 3 10:37:00 2024 [21013][1][FATAL] ImapHandler trying to use a non valid resource stream.
Sat Aug 3 10:37:00 2024 [21013][1][FATAL] ImapHandler trying to use a non valid resource stream.
Sat Aug 3 10:38:00 2024 [21013][1][FATAL] An Imap error detected: "IMAP open error: Can not authenticate to IMAP server: Empty startup greeting (outlook.office365.com:993)"
Sat Aug 3 10:38:00 2024 [21013][1][FATAL] An Imap error detected: "IMAP open error | debug data"
Sat Aug 3 10:38:00 2024 [21013][1][FATAL] An Imap error detected: "ImapHandler:open: {outlook.office365.com:993/service=imap}INBOX"

@rmunoz10 commented on GitHub (Aug 3, 2024): v7.14.4 Inbound fails too. Sat Aug 3 10:37:00 2024 [21013][1][FATAL] ImapHandler trying to use a non valid resource stream. Sat Aug 3 10:37:00 2024 [21013][1][FATAL] ImapHandler trying to use a non valid resource stream. Sat Aug 3 10:38:00 2024 [21013][1][FATAL] An Imap error detected: "IMAP open error: Can not authenticate to IMAP server: Empty startup greeting (outlook.office365.com:993)" Sat Aug 3 10:38:00 2024 [21013][1][FATAL] An Imap error detected: "IMAP open error | debug data" Sat Aug 3 10:38:00 2024 [21013][1][FATAL] An Imap error detected: "ImapHandler:open: {outlook.office365.com:993\/service=imap}INBOX"

deekerman commented

2026-02-20 16:26:24 -05:00

Author

Owner

@pstevens71 commented on GitHub (Aug 5, 2024):

Hey @rmunoz you can't use IMAP for O365, it's no longer supported. You have to setup Oauth.

@pstevens71 commented on GitHub (Aug 5, 2024): Hey @rmunoz you can't use IMAP for O365, it's no longer supported. You have to setup Oauth.

deekerman commented

2026-02-20 16:26:24 -05:00

Author

Owner

@rmunoz commented on GitHub (Aug 5, 2024):