ImapHandler Errors: How to setup Inbound Email for office365? v7.12.5

Bungle · 9 January 2023 23:39

Hi,
I have ‘Email Settings’ and ‘Outbound Email’ working correctly using the smtp.office365.com server with TLS. However ‘Inbound Email’ will not work ( i have the imap module installed and imap enabled on office365, with my domain added ).

If i don’t click ‘use SSL’ in the Admin>Inbound Email settings page, i get the following error:-

TLS/SSL failure for outlook.office365.com: SSL negotiation failed*
Please check your settings and try again.*

But if i select SSL, i get the error:-

Login or Password Incorrect

The settings page will not let me save the SSL as true and gives the error:

No optimums were saved with your inbound email account, Please review the settings


[1][DEBUG] ---------------STARTING FINDOPTIMUMS LOOP----------------
[1][DEBUG] 1: I-E testing string: {outlook.office365.com:993/service=imap/ssl/tls/validate-cert/secure}INBOX
[1][ERROR] ImapHandler trying to set a non valid resource az stream.
[1][ERROR] ImapHandler trying to use a non valid resource stream.
[1][WARN] An Imap error detected: "IMAP open error"
[1][ERROR] ImapHandler trying to use a non valid resource stream.
[1][ERROR] ImapHandler trying to use a non valid resource stream.
[1][ERROR] ImapHandler trying to set a non valid resource az stream.
[1][ERROR] ImapHandler trying to use a non valid resource stream.
[1][WARN] An Imap error detected: "IMAP open error"
[1][ERROR] ImapHandler trying to use a non valid resource stream.
[1][ERROR] ImapHandler trying to use a non valid resource stream.
[1][ERROR] ImapHandler trying to set a non valid resource az stream.
[1][ERROR] ImapHandler trying to use a non valid resource stream.
[1][WARN] An Imap error detected: "IMAP open error"
[1][ERROR] ImapHandler trying to use a non valid resource stream.
[1][ERROR] ImapHandler trying to use a non valid resource stream.
[1][WARN] An Imap error detected: "Can't open mailbox {outlook.office365.com:993\/service=imap\/ssl\/tls\/validate-cert\/secure}INBOX: invalid remote specification"
[1][DEBUG] 1: I-E failed using [{outlook.office365.com:993/service=imap/ssl/tls/validate-cert/secure}INBOX] - error: Can't open mailbox {outlook.office365.com:993/service=imap/ssl/tls/validate-cert/secure}INBOX: invalid remote specification
[1][ERROR] ImapHandler trying to use a non valid resource stream.
[1][DEBUG] 1: I-E clearing error and alert stacks.
[1][WARN] An Imap error detected: "Can't open mailbox {outlook.office365.com:993\/service=imap\/ssl\/tls\/validate-cert\/secure}INBOX: invalid remote specification"
[1][WARN] An Imap error detected: "Can't open mailbox {outlook.office365.com:993\/service=imap\/ssl\/tls\/validate-cert\/secure}INBOX: invalid remote specification"
[1][WARN] An Imap error detected: "Can't open mailbox {outlook.office365.com:993\/service=imap\/ssl\/tls\/validate-cert\/secure}INBOX: invalid remote specification"
[1][DEBUG] 2: I-E testing string: {outlook.office365.com:993/service=imap/ssl/tls/validate-cert}INBOX

What does ImapHandler trying to set a non valid resource az stream. mean?
Presumably suitecrm works ok with office365? I know that i have had issues with other applications due to MFA settings, but they are currently disabled.

pgr · 10 January 2023 12:50

Microsoft changed requirements recently. There have been many recent threads about this. SuiteCRM v7.13 is the version that fixes Microsoft email accounts.

Bungle · 10 January 2023 17:10

Thanks pgr,

I’m going around in circles here.

Having struggled with a number of issues, i finally migrated to 8.2, but still had problems with subpanels. I decided to roll back and ensure i had a fully functioning 7.12.5 before migrating, hoping i could finally make the switch

As cicciobello pointed out in this post , there isn’t a supported upgrade path from 7.13 to 8.2. So how are people making the move?

Would the email requirements be fixed in 8.2 if i had 7.12.5 in the legacy folder?

pgr · 11 January 2023 10:12

I expect this will eventually exist, I don’t see why not.

If you’re looking for stability and solving problems, I would stay on the v7 branch for now. My advice for v8 is quite simple: do try it and test it, but don’t make any assumptions. Test every single functionality you need thoroughly.

The convenience of moving to v8 really depends on which parts of the CRM you use, and to what extent those have been developed in v8, not on assumptions like “I have email problems and I hope these are solved in v8”.

Bungle · 11 January 2023 13:11

thanks pgr,
I was trying to test the migration to 8.2 to see how the customisations would work out with my data - rather than try on the demo version.

In the process i got completely muddled in backups and version control etc.

have managed to get everything working again on 7.13, except for setting up the ms email connector, so will work on just getting that resolved.

Bungle · 12 January 2023 11:21

seem to have the same problem on a new install of 7.13 , but cant figure what I’m doing wrong?

Admin>Email settings works ok - test email sent and recieved.

Admin>Outbound Email works only when i enter the password just before clicking test - otherwise an authentication error is thrown - Password is actually being saved to the database though.

Admin> External OAuth Provider seems to work and is set up as explained here… EXTERNAL OAUTH PROVIDER

Admin> External OAuth Connection also seems to work and i’m retrieving an access token and refresh token when i click authenticate.

Admin> Inbound Email
The listview does not display unless i comment out line 515 in include/ListView/ListViewData.php and when trying to setup a Personal Inbound Email Account, the OAuth connection popup is blank, however i can set it manually by typing into the input box.

However when setting the monitored folders a popup title appears and disappears instantly. I rolled back to php 7.4, and now this popup stays visible ‘Select Subscribed Folders’ but has ‘Login or Password Incorrect’

There is nowhere to enter a password on the Personal Inbound Email page, so i assume the problem is related to the same issue i have with the password on the Admin>Outbound Email settings?

pgr · 13 January 2023 16:14

Sorry, I don’t use Office email accounts myself, I don’t really know much about the specificities of this. And I haven’t tried the new 7.13 version yet.

I suppose you’re getting some bug in the new UI…

Bungle · 14 January 2023 10:49

no probs, and thanks. I’ve added it as an issue on github,

github.com/salesagility/SuiteCRM

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

opened 01:44AM - 14 Jan 23 UTC

bunglex

#### Issue Can't set 'Outbound Email' or create 'Personal Outbound Email Ac…count 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

pstevens · 21 April 2023 17:36

Giving this one a bump here. I’m having the exact same issue. Creating the external oAuth goes well, no problem, but when creating the personal inbound email account I get “Login or Password Incorrect” and not sure how they can be? The login is the email address and there is no password field? I’m assuming it’s using the oAuth key? Does anyone have this working with 0365? Any tips on how to get this working? (13.1 BTW)

kyleb · 20 October 2023 03:20

Hey Paul!

I have a suggested fix for this on SuiteCRM-Core. I was experiencing the same problem. After ensuring IMAP was enabled with office365, and having OATH - I was still getting errors… but it started with “Login or Password Incorrect”.

github.com/salesagility/SuiteCRM-Core

GoDaddy Email Sync Breaks on MIME Header Decoding in SuiteCRM 8.4

opened 06:26PM - 16 Oct 23 UTC

DBRenny

#### Issue We are experiencing an issue with the email synchronization functionality in SuiteCRM. Specifically, the system encounters a fatal error during the process of handling MIME header decoding for email subject, to list, from, and other headers. The error message indicates a problem with the foreach() function, suggesting that the variable being iterated upon is not an array or object as expected. #### Expected Behavior The CRM should seamlessly decode MIME headers and handle email headers, regardless of their encoding, without encountering fatal errors. The process should iterate over the decoded headers and correctly process the email details into a readable format. #### Actual Behavior Instead of successful processing, the system throws a fatal error, particularly pointing to the foreach() line in the handleMimeHeaderDecode method. The error message is: "Invalid argument supplied for foreach()". This issue disrupts the normal flow of email synchronization, preventing emails from being properly imported and read in the CRM. Relevant logs indicate the error originates from the handleMimeHeaderDecode method, but there's no additional information about the state or format of the data being passed to foreach(). [SuiteCRM_10236 sample log.txt](https://github.com/salesagility/SuiteCRM/files/12920000/SuiteCRM_10236.sample.log.txt) #### Possible Fix A potential fix could involve adding robust checks before the foreach() statement to ensure the variable is indeed iterable. If the variable is a JSON string, it might require decoding with json_decode(). Here's a proposed code snippet (GPT helped): It referenced subject, but all header information except time information is not syncing. ``` php Copy code // Check if $subjectDecoded is JSON, and decode it if necessary if (is_string($subjectDecoded)) { $decodedJson = json_decode($subjectDecoded); if (json_last_error() === JSON_ERROR_NONE) { $subjectDecoded = $decodedJson; } else { // Handle error } } // Check if $subjectDecoded is iterable if (is_iterable($subjectDecoded)) { // existing foreach loop } else { // Handle error } ``` #### Steps to Reproduce 1. Set up email synchronization in SuiteCRM. 2. Receive an email with a subject that requires MIME header decoding. 3. Observe the SuiteCRM log or UI for errors during the email import process. 4. Notice the "Invalid argument supplied for foreach()" error pointing to the handleMimeHeaderDecode method. #### Context This is our pilot system, but we need to use as many integrated features as possible. I want to get through these roadblocks to start expanding the scope of users. Outbound email automation still works, and in the meantime my users can use outlook. but this is a major adoptability issue. Inbound email box view: ![image](https://github.com/salesagility/SuiteCRM/assets/100956107/a1cd68ef-125c-4fb5-bed7-7222c00da8d8) Email detail level view: ![image](https://github.com/salesagility/SuiteCRM/assets/100956107/bf944e73-09bf-47a9-8e3e-126633247864) #### Your Environment * SuiteCRM Version used: 8.4 * Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): * Environment name and version: PHP 8.1.24, MariaDB 11.0.3, Godaddy Office 365 (outlook.office365.com) - utilizing an OATH connection * Debian GNU/Linux 11 (bullseye) This is somewhat similar to this issue: [SuiteCRM#9921](https://github.com/salesagility/SuiteCRM-Core/issues/206), but I opened a new one so it could be replicated with my environment.

I’m not sure how well the PR will be received (It is my first ever PR, not just on github).