#3174 new
Stefan Seiz

Can't connect to office365 IMAP anymore

Reported by Stefan Seiz | December 28th, 2022 @ 10:48 AM

Hi,

all of a sudden, i can't log in to my outlook imap account anymore. the error i get is "BAD User is authenticated but not connected". Any idee what could be causing this?

Here's the log from activity viewer:

10:42:12 Running action
10:42:12 Handling request
10:42:12 Ready to run action (type: 1000, retry count: 0)
10:42:12 Clearing connection to outlook.office365.com
10:42:12 Trying to connect to outlook.office365.com on port 993 (CFNetwork) without STARTTLS (required)
10:42:12 Resolved hostname (outlook.office365.com).
10:42:12 Prepare secure connection...
10:42:12 Successful connection.
10:42:12 Initiating secure connection...
10:42:12 Returned (4)...
10:42:12 Protocol version: kTLSProtocol12
10:42:13 S: * OK The Microsoft Exchange IMAP4 service is ready. [RgBSADMAUAAyADgAMQBDAEEAMAAwADQANAAuAEQARQBVAFAAMgA4ADEALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
10:42:13 C: A0 CAPABILITY
10:42:13 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
10:42:13 S: A0 OK CAPABILITY completed.
10:42:13 Retrieving password (keychain or user request)
10:42:13 C: A1 AUTHENTICATE XOAUTH2 ••••••••••
10:42:14 S: A1 OK AUTHENTICATE completed.
10:42:14 C: A2 CAPABILITY
10:42:14 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+
10:42:14 S: A2 OK CAPABILITY completed.
10:42:14 C: A3 ID ("name" "MailMate" "version" "r5918" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")
10:42:14 S: A3 BAD User is authenticated but not connected.
10:42:14 Warning: Detected Exchange IMAP server response state bug. Trying to work around it by interpreting it as a temporary connection issue.
10:42:14 Error code: 1004
10:42:14 Failed action (1000). Reset observed read/write timeouts: 8/8

10:42:14 Handling reply
10:42:14 Running action
10:42:14 Handling request
10:42:14 Trying to disconnect nicely (8)...
10:42:14 C: A4 LOGOUT
10:42:14 S: * BYE Microsoft Exchange Server IMAP4 server signing off.
10:42:14 S: A4 OK LOGOUT completed.
10:42:14 Clearing connection to outlook.office365.com
10:42:15 Ready to run action (type: 1000, retry count: 1)
10:42:15 Clearing connection to outlook.office365.com
10:42:15 Trying to connect to outlook.office365.com on port 993 (CFNetwork) without STARTTLS (required)
10:42:15 Resolved hostname (outlook.office365.com).
10:42:15 Prepare secure connection...
10:42:16 Successful connection.
10:42:16 Initiating secure connection...
10:42:16 Returned (4)...
10:42:16 Protocol version: kTLSProtocol12
10:42:16 S: * OK The Microsoft Exchange IMAP4 service is ready. [RgBSADMAUAAyADgAMQBDAEEAMAAwADcANQAuAEQARQBVAFAAMgA4ADEALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
10:42:16 C: A0 CAPABILITY
10:42:16 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
10:42:16 S: A0 OK CAPABILITY completed.
10:42:16 Retrieving password (keychain or user request)
10:42:16 C: A1 AUTHENTICATE XOAUTH2 ••••••••••
10:42:18 S: A1 OK AUTHENTICATE completed.
10:42:18 C: A2 CAPABILITY
10:42:18 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+
10:42:18 S: A2 OK CAPABILITY completed.
10:42:18 C: A3 ID ("name" "MailMate" "version" "r5918" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")
10:42:18 S: A3 BAD User is authenticated but not connected.
10:42:18 Warning: Detected Exchange IMAP server response state bug. Trying to work around it by interpreting it as a temporary connection issue.
10:42:18 Error code: 1004
10:42:18 Failed action (1000). Reset observed read/write timeouts: 8/8

10:42:18 Handling reply
10:42:18 Running action
10:42:18 Handling request
10:42:18 Trying to disconnect nicely (8)...
10:42:18 C: A4 LOGOUT
10:42:18 S: * BYE Microsoft Exchange Server IMAP4 server signing off.
10:42:18 S: A4 OK LOGOUT completed.
10:42:18 Clearing connection to outlook.office365.com
10:42:20 Ready to run action (type: 1000, retry count: 2)
10:42:20 Clearing connection to outlook.office365.com
10:42:20 Trying to connect to outlook.office365.com on port 993 (CFNetwork) without STARTTLS (required)
10:42:20 Resolved hostname (outlook.office365.com).
10:42:20 Prepare secure connection...
10:42:20 Successful connection.
10:42:20 Initiating secure connection...
10:42:20 Returned (4)...
10:42:20 Protocol version: kTLSProtocol12
10:42:20 S: * OK The Microsoft Exchange IMAP4 service is ready. [RgBSADMAUAAyADgAMQBDAEEAMAAwADgAMAAuAEQARQBVAFAAMgA4ADEALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
10:42:20 C: A0 CAPABILITY
10:42:20 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
10:42:20 S: A0 OK CAPABILITY completed.
10:42:20 Retrieving password (keychain or user request)
10:42:20 C: A1 AUTHENTICATE XOAUTH2 ••••••••••
10:42:22 S: A1 OK AUTHENTICATE completed.
10:42:22 C: A2 CAPABILITY
10:42:22 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+
10:42:22 S: A2 OK CAPABILITY completed.
10:42:22 C: A3 ID ("name" "MailMate" "version" "r5918" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")
10:42:22 S: A3 BAD User is authenticated but not connected.
10:42:22 Warning: Detected Exchange IMAP server response state bug. Trying to work around it by interpreting it as a temporary connection issue.
10:42:22 Error code: 1004
10:42:22 Failed action (1000). Reset observed read/write timeouts: 8/8

10:42:22 Handling reply
10:42:22 Running action
10:42:22 Handling request
10:42:22 Trying to disconnect nicely (8)...
10:42:22 C: A4 LOGOUT
10:42:22 S: * BYE Microsoft Exchange Server IMAP4 server signing off.
10:42:22 S: A4 OK LOGOUT completed.
10:42:22 Clearing connection to outlook.office365.com
10:42:25 Ready to run action (type: 1000, retry count: 3)
10:42:25 Clearing connection to outlook.office365.com
10:42:25 Trying to connect to outlook.office365.com on port 993 (CFNetwork) without STARTTLS (required)
10:42:25 Resolved hostname (outlook.office365.com).
10:42:25 Prepare secure connection...
10:42:25 Successful connection.
10:42:25 Initiating secure connection...
10:42:25 Returned (4)...
10:42:25 Protocol version: kTLSProtocol12
10:42:25 S: * OK The Microsoft Exchange IMAP4 service is ready. [RgBSADAAUAAyADgAMQBDAEEAMAAwADgAOQAuAEQARQBVAFAAMgA4ADEALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
10:42:25 C: A0 CAPABILITY
10:42:25 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
10:42:25 S: A0 OK CAPABILITY completed.
10:42:25 Retrieving password (keychain or user request)
10:42:25 C: A1 AUTHENTICATE XOAUTH2 ••••••••••
10:42:27 S: A1 OK AUTHENTICATE completed.
10:42:27 C: A2 CAPABILITY
10:42:27 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+
10:42:27 S: A2 OK CAPABILITY completed.
10:42:27 C: A3 ID ("name" "MailMate" "version" "r5918" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")
10:42:27 S: A3 BAD User is authenticated but not connected.
10:42:27 Warning: Detected Exchange IMAP server response state bug. Trying to work around it by interpreting it as a temporary connection issue.
10:42:27 Error code: 1004
10:42:27 Failed action (1000). Reset observed read/write timeouts: 8/8

10:42:27 Handling reply
10:42:27 Error: Failed multiple retries (4). Final error code was 1004.
10:42:27 Terminating non-running connection...
10:42:37 Running action
10:42:37 Handling request
10:42:37 Trying to disconnect nicely (8)...
10:42:37 C: A4 LOGOUT
10:42:37 S: * BYE Microsoft Exchange Server IMAP4 server signing off.
10:42:37 S: A4 OK LOGOUT completed.
10:42:37 Clearing connection to outlook.office365.com
10:42:37 Ready to run action (type: 1000, retry count: 0)
10:42:37 Clearing connection to outlook.office365.com
10:42:37 Trying to connect to outlook.office365.com on port 993 (CFNetwork) without STARTTLS (required)
10:42:37 Resolved hostname (outlook.office365.com).
10:42:37 Prepare secure connection...
10:42:37 Successful connection.
10:42:37 Initiating secure connection...
10:42:37 Returned (4)...
10:42:37 Protocol version: kTLSProtocol12
10:42:37 S: * OK The Microsoft Exchange IMAP4 service is ready. [RgBSADAAUAAyADgAMQBDAEEAMAAwADQAMQAuAEQARQBVAFAAMgA4ADEALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
10:42:37 C: A0 CAPABILITY
10:42:37 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
10:42:37 S: A0 OK CAPABILITY completed.
10:42:37 Retrieving password (keychain or user request)
10:42:37 C: A1 AUTHENTICATE XOAUTH2 ••••••••••
10:42:39 S: A1 OK AUTHENTICATE completed.
10:42:39 C: A2 CAPABILITY
10:42:39 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+
10:42:39 S: A2 OK CAPABILITY completed.
10:42:39 C: A3 ID ("name" "MailMate" "version" "r5918" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")
10:42:39 S: A3 BAD User is authenticated but not connected.
10:42:39 Warning: Detected Exchange IMAP server response state bug. Trying to work around it by interpreting it as a temporary connection issue.
10:42:39 Error code: 1004
10:42:39 Failed action (1000). Reset observed read/write timeouts: 8/8

10:42:39 Handling reply
10:42:39 Running action
10:42:39 Handling request
10:42:39 Trying to disconnect nicely (8)...
10:42:39 C: A4 LOGOUT
10:42:39 S: * BYE Microsoft Exchange Server IMAP4 server signing off.
10:42:39 S: A4 OK LOGOUT completed.
10:42:39 Clearing connection to outlook.office365.com
10:42:40 Ready to run action (type: 1000, retry count: 1)
10:42:40 Clearing connection to outlook.office365.com
10:42:40 Trying to connect to outlook.office365.com on port 993 (CFNetwork) without STARTTLS (required)
10:42:40 Resolved hostname (outlook.office365.com).
10:42:40 Prepare secure connection...
10:42:40 Successful connection.
10:42:40 Initiating secure connection...
10:42:40 Returned (4)...
10:42:40 Protocol version: kTLSProtocol12
10:42:40 S: * OK The Microsoft Exchange IMAP4 service is ready. [RgBSADAAUAAyADgAMQBDAEEAMAAwADQANQAuAEQARQBVAFAAMgA4ADEALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
10:42:40 C: A0 CAPABILITY
10:42:40 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
10:42:40 S: A0 OK CAPABILITY completed.
10:42:40 Retrieving password (keychain or user request)
10:42:40 C: A1 AUTHENTICATE XOAUTH2 ••••••••••
10:42:42 S: A1 OK AUTHENTICATE completed.
10:42:42 C: A2 CAPABILITY
10:42:42 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+
10:42:42 S: A2 OK CAPABILITY completed.
10:42:42 C: A3 ID ("name" "MailMate" "version" "r5918" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")
10:42:42 S: A3 BAD User is authenticated but not connected.
10:42:42 Warning: Detected Exchange IMAP server response state bug. Trying to work around it by interpreting it as a temporary connection issue.
10:42:42 Error code: 1004
10:42:42 Failed action (1000). Reset observed read/write timeouts: 8/8

10:42:42 Handling reply
10:42:42 Running action
10:42:42 Handling request
10:42:42 Trying to disconnect nicely (8)...
10:42:42 C: A4 LOGOUT
10:42:42 S: * BYE Microsoft Exchange Server IMAP4 server signing off.
10:42:42 S: A4 OK LOGOUT completed.
10:42:42 Clearing connection to outlook.office365.com
10:42:44 Ready to run action (type: 1000, retry count: 2)
10:42:44 Clearing connection to outlook.office365.com
10:42:44 Trying to connect to outlook.office365.com on port 993 (CFNetwork) without STARTTLS (required)
10:42:44 Resolved hostname (outlook.office365.com).
10:42:44 Prepare secure connection...
10:42:44 Successful connection.
10:42:44 Initiating secure connection...
10:42:44 Returned (4)...
10:42:44 Protocol version: kTLSProtocol12
10:42:44 S: * OK The Microsoft Exchange IMAP4 service is ready. [RgBSADAAUAAyADgAMQBDAEEAMAAwADQAMgAuAEQARQBVAFAAMgA4ADEALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
10:42:44 C: A0 CAPABILITY
10:42:44 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
10:42:44 S: A0 OK CAPABILITY completed.
10:42:44 Retrieving password (keychain or user request)
10:42:44 C: A1 AUTHENTICATE XOAUTH2 ••••••••••
10:42:46 S: A1 OK AUTHENTICATE completed.
10:42:46 C: A2 CAPABILITY
10:42:46 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+
10:42:46 S: A2 OK CAPABILITY completed.
10:42:46 C: A3 ID ("name" "MailMate" "version" "r5918" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")
10:42:46 S: A3 BAD User is authenticated but not connected.
10:42:46 Warning: Detected Exchange IMAP server response state bug. Trying to work around it by interpreting it as a temporary connection issue.
10:42:46 Error code: 1004
10:42:46 Failed action (1000). Reset observed read/write timeouts: 8/8

10:42:46 Handling reply
10:42:46 Running action
10:42:46 Handling request
10:42:46 Trying to disconnect nicely (8)...
10:42:46 C: A4 LOGOUT
10:42:47 S: * BYE Microsoft Exchange Server IMAP4 server signing off.
10:42:47 S: A4 OK LOGOUT completed.
10:42:47 Clearing connection to outlook.office365.com
10:42:50 Ready to run action (type: 1000, retry count: 3)
10:42:50 Clearing connection to outlook.office365.com
10:42:50 Trying to connect to outlook.office365.com on port 993 (CFNetwork) without STARTTLS (required)
10:42:50 Resolved hostname (outlook.office365.com).
10:42:50 Prepare secure connection...
10:42:50 Successful connection.
10:42:50 Initiating secure connection...
10:42:50 Returned (2)...
10:42:50 Protocol version: kTLSProtocol12
10:42:50 S: * OK The Microsoft Exchange IMAP4 service is ready. [RgBSADAAUAAyADgAMQBDAEEAMAAxADMANAAuAEQARQBVAFAAMgA4ADEALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
10:42:50 C: A0 CAPABILITY
10:42:50 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
10:42:50 S: A0 OK CAPABILITY completed.
10:42:50 Retrieving password (keychain or user request)
10:42:50 C: A1 AUTHENTICATE XOAUTH2 ••••••••••
10:42:52 S: A1 OK AUTHENTICATE completed.
10:42:52 C: A2 CAPABILITY
10:42:52 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+
10:42:52 S: A2 OK CAPABILITY completed.
10:42:52 C: A3 ID ("name" "MailMate" "version" "r5918" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")
10:42:52 S: A3 BAD User is authenticated but not connected.
10:42:52 Warning: Detected Exchange IMAP server response state bug. Trying to work around it by interpreting it as a temporary connection issue.
10:42:52 Error code: 1004
10:42:52 Failed action (1000). Reset observed read/write timeouts: 8/8

10:42:52 Handling reply
10:42:52 Error: Failed multiple retries (4). Final error code was 1004.
10:42:52 Terminating non-running connection...
10:43:12 Running action
10:43:12 Handling request
10:43:12 Trying to disconnect nicely (8)...
10:43:12 C: A4 LOGOUT
10:43:12 S: * BYE Microsoft Exchange Server IMAP4 server signing off.
10:43:12 S: A4 OK LOGOUT completed.
10:43:12 Clearing connection to outlook.office365.com
10:43:12 Ready to run action (type: 1000, retry count: 0)
10:43:12 Clearing connection to outlook.office365.com
10:43:12 Trying to connect to outlook.office365.com on port 993 (CFNetwork) without STARTTLS (required)
10:43:12 Resolved hostname (outlook.office365.com).
10:43:12 Prepare secure connection...
10:43:12 Successful connection.
10:43:12 Initiating secure connection...
10:43:12 Returned (4)...
10:43:12 Protocol version: kTLSProtocol12
10:43:12 S: * OK The Microsoft Exchange IMAP4 service is ready. [RgBSADMAUAAyADgAMQBDAEEAMAAwADUAOQAuAEQARQBVAFAAMgA4ADEALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
10:43:12 C: A0 CAPABILITY
10:43:12 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
10:43:12 S: A0 OK CAPABILITY completed.
10:43:12 Retrieving password (keychain or user request)
10:43:12 C: A1 AUTHENTICATE XOAUTH2 ••••••••••
10:43:14 S: A1 OK AUTHENTICATE completed.
10:43:14 C: A2 CAPABILITY
10:43:14 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+
10:43:14 S: A2 OK CAPABILITY completed.
10:43:14 C: A3 ID ("name" "MailMate" "version" "r5918" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")
10:43:14 S: A3 BAD User is authenticated but not connected.
10:43:14 Warning: Detected Exchange IMAP server response state bug. Trying to work around it by interpreting it as a temporary connection issue.
10:43:14 Error code: 1004
10:43:14 Failed action (1000). Reset observed read/write timeouts: 8/8

10:43:14 Handling reply
10:43:14 Running action
10:43:14 Handling request
10:43:14 Trying to disconnect nicely (8)...
10:43:14 C: A4 LOGOUT
10:43:14 S: * BYE Microsoft Exchange Server IMAP4 server signing off.
10:43:14 S: A4 OK LOGOUT completed.
10:43:14 Clearing connection to outlook.office365.com
10:43:15 Ready to run action (type: 1000, retry count: 1)
10:43:15 Clearing connection to outlook.office365.com
10:43:15 Trying to connect to outlook.office365.com on port 993 (CFNetwork) without STARTTLS (required)
10:43:15 Resolved hostname (outlook.office365.com).
10:43:15 Prepare secure connection...
10:43:15 Successful connection.
10:43:15 Initiating secure connection...
10:43:15 Returned (4)...
10:43:15 Protocol version: kTLSProtocol12
10:43:15 S: * OK The Microsoft Exchange IMAP4 service is ready. [RgBSADMAUAAyADgAMQBDAEEAMAAxADAAMgAuAEQARQBVAFAAMgA4ADEALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
10:43:15 C: A0 CAPABILITY
10:43:15 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
10:43:15 S: A0 OK CAPABILITY completed.
10:43:15 Retrieving password (keychain or user request)
10:43:15 C: A1 AUTHENTICATE XOAUTH2 ••••••••••
10:43:18 S: A1 OK AUTHENTICATE completed.
10:43:18 C: A2 CAPABILITY
10:43:18 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+
10:43:18 S: A2 OK CAPABILITY completed.
10:43:18 C: A3 ID ("name" "MailMate" "version" "r5918" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")
10:43:18 S: A3 BAD User is authenticated but not connected.
10:43:18 Warning: Detected Exchange IMAP server response state bug. Trying to work around it by interpreting it as a temporary connection issue.
10:43:18 Error code: 1004
10:43:18 Failed action (1000). Reset observed read/write timeouts: 8/8

10:43:18 Handling reply
10:43:18 Running action
10:43:18 Handling request
10:43:18 Trying to disconnect nicely (8)...
10:43:18 C: A4 LOGOUT
10:43:18 S: * BYE Microsoft Exchange Server IMAP4 server signing off.
10:43:18 S: A4 OK LOGOUT completed.
10:43:18 Clearing connection to outlook.office365.com
10:43:20 Ready to run action (type: 1000, retry count: 2)
10:43:20 Clearing connection to outlook.office365.com
10:43:20 Trying to connect to outlook.office365.com on port 993 (CFNetwork) without STARTTLS (required)
10:43:20 Resolved hostname (outlook.office365.com).
10:43:20 Prepare secure connection...
10:43:20 Successful connection.
10:43:20 Initiating secure connection...
10:43:20 Returned (2)...
10:43:20 Protocol version: kTLSProtocol12
10:43:20 S: * OK The Microsoft Exchange IMAP4 service is ready. [RgBSADMAUAAyADgAMQBDAEEAMAAxADAANAAuAEQARQBVAFAAMgA4ADEALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
10:43:20 C: A0 CAPABILITY
10:43:20 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
10:43:20 S: A0 OK CAPABILITY completed.
10:43:20 Retrieving password (keychain or user request)
10:43:20 C: A1 AUTHENTICATE XOAUTH2 ••••••••••
10:43:22 S: A1 OK AUTHENTICATE completed.
10:43:22 C: A2 CAPABILITY
10:43:22 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+
10:43:22 S: A2 OK CAPABILITY completed.
10:43:22 C: A3 ID ("name" "MailMate" "version" "r5918" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")
10:43:22 S: A3 BAD User is authenticated but not connected.
10:43:22 Warning: Detected Exchange IMAP server response state bug. Trying to work around it by interpreting it as a temporary connection issue.
10:43:22 Error code: 1004
10:43:22 Failed action (1000). Reset observed read/write timeouts: 8/8

10:43:22 Handling reply
10:43:22 Running action
10:43:22 Handling request
10:43:22 Trying to disconnect nicely (8)...
10:43:22 C: A4 LOGOUT
10:43:22 S: * BYE Microsoft Exchange Server IMAP4 server signing off.
10:43:22 S: A4 OK LOGOUT completed.
10:43:22 Clearing connection to outlook.office365.com
10:43:25 Ready to run action (type: 1000, retry count: 3)
10:43:25 Clearing connection to outlook.office365.com
10:43:25 Trying to connect to outlook.office365.com on port 993 (CFNetwork) without STARTTLS (required)
10:43:25 Resolved hostname (outlook.office365.com).
10:43:25 Prepare secure connection...
10:43:25 Successful connection.
10:43:25 Initiating secure connection...
10:43:25 Returned (2)...
10:43:25 Protocol version: kTLSProtocol12
10:43:25 S: * OK The Microsoft Exchange IMAP4 service is ready. [RgBSADMAUAAyADgAMQBDAEEAMAAxADAAMAAuAEQARQBVAFAAMgA4ADEALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
10:43:25 C: A0 CAPABILITY
10:43:25 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
10:43:25 S: A0 OK CAPABILITY completed.
10:43:25 Retrieving password (keychain or user request)
10:43:25 C: A1 AUTHENTICATE XOAUTH2 ••••••••••
10:43:27 S: A1 OK AUTHENTICATE completed.
10:43:27 C: A2 CAPABILITY
10:43:28 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+
10:43:28 S: A2 OK CAPABILITY completed.
10:43:28 C: A3 ID ("name" "MailMate" "version" "r5918" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")
10:43:28 S: A3 BAD User is authenticated but not connected.
10:43:28 Warning: Detected Exchange IMAP server response state bug. Trying to work around it by interpreting it as a temporary connection issue.
10:43:28 Error code: 1004
10:43:28 Failed action (1000). Reset observed read/write timeouts: 8/8

10:43:28 Handling reply
10:43:28 Error: Failed multiple retries (4). Final error code was 1004.
10:43:28 Terminating non-running connection...
10:44:08 Running action
10:44:08 Handling request
10:44:08 Trying to disconnect nicely (8)...
10:44:08 C: A4 LOGOUT
10:44:08 S: * BYE Microsoft Exchange Server IMAP4 server signing off.
10:44:08 S: A4 OK LOGOUT completed.
10:44:08 Clearing connection to outlook.office365.com
10:44:08 Ready to run action (type: 1000, retry count: 0)
10:44:08 Clearing connection to outlook.office365.com
10:44:08 Trying to connect to outlook.office365.com on port 993 (CFNetwork) without STARTTLS (required)
10:44:08 Resolved hostname (outlook.office365.com).
10:44:08 Prepare secure connection...
10:44:08 Successful connection.
10:44:08 Initiating secure connection...
10:44:08 Returned (4)...
10:44:08 Protocol version: kTLSProtocol12
10:44:08 S: * OK The Microsoft Exchange IMAP4 service is ready. [RgBSADMAUAAyADgAMQBDAEEAMAAwADUANQAuAEQARQBVAFAAMgA4ADEALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
10:44:08 C: A0 CAPABILITY
10:44:08 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
10:44:08 S: A0 OK CAPABILITY completed.
10:44:08 Retrieving password (keychain or user request)
10:44:08 C: A1 AUTHENTICATE XOAUTH2 ••••••••••
10:44:10 S: A1 OK AUTHENTICATE completed.
10:44:10 C: A2 CAPABILITY
10:44:10 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+
10:44:10 S: A2 OK CAPABILITY completed.
10:44:10 C: A3 ID ("name" "MailMate" "version" "r5918" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")
10:44:10 S: A3 BAD User is authenticated but not connected.
10:44:10 Warning: Detected Exchange IMAP server response state bug. Trying to work around it by interpreting it as a temporary connection issue.
10:44:10 Error code: 1004
10:44:10 Failed action (1000). Reset observed read/write timeouts: 8/8

10:44:10 Handling reply
10:44:10 Running action
10:44:10 Handling request
10:44:10 Trying to disconnect nicely (8)...
10:44:10 C: A4 LOGOUT
10:44:10 S: * BYE Microsoft Exchange Server IMAP4 server signing off.
10:44:10 S: A4 OK LOGOUT completed.
10:44:10 Clearing connection to outlook.office365.com
10:44:11 Ready to run action (type: 1000, retry count: 1)
10:44:11 Clearing connection to outlook.office365.com
10:44:11 Trying to connect to outlook.office365.com on port 993 (CFNetwork) without STARTTLS (required)
10:44:11 Resolved hostname (outlook.office365.com).
10:44:11 Prepare secure connection...
10:44:11 Successful connection.
10:44:11 Initiating secure connection...
10:44:11 Returned (4)...
10:44:11 Protocol version: kTLSProtocol12
10:44:11 S: * OK The Microsoft Exchange IMAP4 service is ready. [RgBSADMAUAAyADgAMQBDAEEAMAAwADYANAAuAEQARQBVAFAAMgA4ADEALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
10:44:11 C: A0 CAPABILITY
10:44:11 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
10:44:11 S: A0 OK CAPABILITY completed.
10:44:11 Retrieving password (keychain or user request)
10:44:11 C: A1 AUTHENTICATE XOAUTH2 ••••••••••
10:44:13 S: A1 OK AUTHENTICATE completed.
10:44:13 C: A2 CAPABILITY
10:44:13 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+
10:44:13 S: A2 OK CAPABILITY completed.
10:44:13 C: A3 ID ("name" "MailMate" "version" "r5918" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")
10:44:13 S: A3 BAD User is authenticated but not connected.
10:44:13 Warning: Detected Exchange IMAP server response state bug. Trying to work around it by interpreting it as a temporary connection issue.
10:44:13 Error code: 1004
10:44:13 Failed action (1000). Reset observed read/write timeouts: 8/8

10:44:13 Handling reply
10:44:13 Running action
10:44:13 Handling request
10:44:13 Trying to disconnect nicely (8)...
10:44:13 C: A4 LOGOUT
10:44:14 S: * BYE Microsoft Exchange Server IMAP4 server signing off.
10:44:14 S: A4 OK LOGOUT completed.
10:44:14 Clearing connection to outlook.office365.com
10:44:16 Ready to run action (type: 1000, retry count: 2)
10:44:16 Clearing connection to outlook.office365.com
10:44:16 Trying to connect to outlook.office365.com on port 993 (CFNetwork) without STARTTLS (required)
10:44:16 Resolved hostname (outlook.office365.com).
10:44:16 Prepare secure connection...
10:44:16 Successful connection.
10:44:16 Initiating secure connection...
10:44:16 Returned (4)...
10:44:16 Protocol version: kTLSProtocol12
10:44:16 S: * OK The Microsoft Exchange IMAP4 service is ready. [RgBSADMAUAAyADgAMQBDAEEAMAAwADUANQAuAEQARQBVAFAAMgA4ADEALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
10:44:16 C: A0 CAPABILITY
10:44:16 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
10:44:16 S: A0 OK CAPABILITY completed.
10:44:16 Retrieving password (keychain or user request)
10:44:16 C: A1 AUTHENTICATE XOAUTH2 ••••••••••
10:44:17 S: A1 OK AUTHENTICATE completed.
10:44:17 C: A2 CAPABILITY
10:44:17 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+
10:44:17 S: A2 OK CAPABILITY completed.
10:44:17 C: A3 ID ("name" "MailMate" "version" "r5918" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")
10:44:18 S: A3 BAD User is authenticated but not connected.
10:44:18 Warning: Detected Exchange IMAP server response state bug. Trying to work around it by interpreting it as a temporary connection issue.
10:44:18 Error code: 1004
10:44:18 Failed action (1000). Reset observed read/write timeouts: 8/8

10:44:18 Handling reply
10:44:18 Running action
10:44:18 Handling request
10:44:18 Trying to disconnect nicely (8)...
10:44:18 C: A4 LOGOUT
10:44:18 S: * BYE Microsoft Exchange Server IMAP4 server signing off.
10:44:18 S: A4 OK LOGOUT completed.
10:44:18 Clearing connection to outlook.office365.com
10:44:21 Ready to run action (type: 1000, retry count: 3)
10:44:21 Clearing connection to outlook.office365.com
10:44:21 Trying to connect to outlook.office365.com on port 993 (CFNetwork) without STARTTLS (required)
10:44:21 Resolved hostname (outlook.office365.com).
10:44:21 Prepare secure connection...
10:44:21 Successful connection.
10:44:21 Initiating secure connection...
10:44:21 Returned (4)...
10:44:21 Protocol version: kTLSProtocol12
10:44:21 S: * OK The Microsoft Exchange IMAP4 service is ready. [RgBSADMAUAAyADgAMQBDAEEAMAAwADYAMQAuAEQARQBVAFAAMgA4ADEALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
10:44:21 C: A0 CAPABILITY
10:44:21 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
10:44:21 S: A0 OK CAPABILITY completed.
10:44:21 Retrieving password (keychain or user request)
10:44:21 C: A1 AUTHENTICATE XOAUTH2 ••••••••••
10:44:23 S: A1 OK AUTHENTICATE completed.
10:44:23 C: A2 CAPABILITY
10:44:23 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+
10:44:23 S: A2 OK CAPABILITY completed.
10:44:23 C: A3 ID ("name" "MailMate" "version" "r5918" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")
10:44:23 S: A3 BAD User is authenticated but not connected.
10:44:23 Warning: Detected Exchange IMAP server response state bug. Trying to work around it by interpreting it as a temporary connection issue.
10:44:23 Error code: 1004
10:44:23 Failed action (1000). Reset observed read/write timeouts: 8/8

10:44:23 Handling reply
10:44:23 Error: Failed multiple retries (4). Final error code was 1004.
10:44:23 Terminating non-running connection...
10:45:43 Running action
10:45:43 Handling request
10:45:43 Trying to disconnect nicely (8)...
10:45:43 C: A4 LOGOUT
10:45:43 S: * BYE Connection is closed. 13
10:45:43 Error: Reading ended without error.
10:45:43 S: <<< terminated reading >>>
10:45:43 Logout error should not happen (10).
10:45:43 Clearing connection to outlook.office365.com
10:45:43 Ready to run action (type: 1000, retry count: 0)
10:45:43 Clearing connection to outlook.office365.com
10:45:43 Trying to connect to outlook.office365.com on port 993 (CFNetwork) without STARTTLS (required)
10:45:43 Resolved hostname (outlook.office365.com).
10:45:43 Prepare secure connection...
10:45:43 Successful connection.
10:45:43 Initiating secure connection...
10:45:43 Returned (4)...
10:45:43 Protocol version: kTLSProtocol12
10:45:43 S: * OK The Microsoft Exchange IMAP4 service is ready. [TQBNADAAUAAyADgAMABDAEEAMAAwADcANAAuAFMAVwBFAFAAMgA4ADAALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
10:45:43 C: A0 CAPABILITY
10:45:43 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
10:45:43 S: A0 OK CAPABILITY completed.
10:45:43 Retrieving password (keychain or user request)
10:45:43 C: A1 AUTHENTICATE XOAUTH2 ••••••••••
10:45:45 S: A1 OK AUTHENTICATE completed.
10:45:45 C: A2 CAPABILITY
10:45:45 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+
10:45:45 S: A2 OK CAPABILITY completed.
10:45:45 C: A3 ID ("name" "MailMate" "version" "r5918" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")
10:45:46 S: A3 BAD User is authenticated but not connected.
10:45:46 Warning: Detected Exchange IMAP server response state bug. Trying to work around it by interpreting it as a temporary connection issue.
10:45:46 Error code: 1004
10:45:46 Failed action (1000). Reset observed read/write timeouts: 8/8

10:45:46 Handling reply
10:45:46 Running action
10:45:46 Handling request
10:45:46 Trying to disconnect nicely (8)...
10:45:46 C: A4 LOGOUT
10:45:46 S: * BYE Microsoft Exchange Server IMAP4 server signing off.
10:45:46 S: A4 OK LOGOUT completed.
10:45:46 Clearing connection to outlook.office365.com
10:45:47 Ready to run action (type: 1000, retry count: 1)
10:45:47 Clearing connection to outlook.office365.com
10:45:47 Trying to connect to outlook.office365.com on port 993 (CFNetwork) without STARTTLS (required)
10:45:47 Resolved hostname (outlook.office365.com).
10:45:47 Prepare secure connection...
10:45:47 Successful connection.
10:45:47 Initiating secure connection...
10:45:47 Returned (4)...
10:45:47 Protocol version: kTLSProtocol12
10:45:47 S: * OK The Microsoft Exchange IMAP4 service is ready. [TQBNADAAUAAyADgAMABDAEEAMAAwADYAOAAuAFMAVwBFAFAAMgA4ADAALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
10:45:47 C: A0 CAPABILITY
10:45:47 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
10:45:47 S: A0 OK CAPABILITY completed.
10:45:47 Retrieving password (keychain or user request)
10:45:47 C: A1 AUTHENTICATE XOAUTH2 ••••••••••
10:45:49 S: A1 OK AUTHENTICATE completed.
10:45:49 C: A2 CAPABILITY
10:45:49 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+
10:45:49 S: A2 OK CAPABILITY completed.
10:45:49 C: A3 ID ("name" "MailMate" "version" "r5918" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")
10:45:49 S: A3 BAD User is authenticated but not connected.
10:45:49 Warning: Detected Exchange IMAP server response state bug. Trying to work around it by interpreting it as a temporary connection issue.
10:45:49 Error code: 1004
10:45:49 Failed action (1000). Reset observed read/write timeouts: 8/8

10:45:49 Handling reply
10:45:49 Running action
10:45:49 Handling request
10:45:49 Trying to disconnect nicely (8)...
10:45:49 C: A4 LOGOUT
10:45:50 S: * BYE Microsoft Exchange Server IMAP4 server signing off.
10:45:50 S: A4 OK LOGOUT completed.
10:45:50 Clearing connection to outlook.office365.com
10:45:52 Ready to run action (type: 1000, retry count: 2)
10:45:52 Clearing connection to outlook.office365.com
10:45:52 Trying to connect to outlook.office365.com on port 993 (CFNetwork) without STARTTLS (required)
10:45:52 Resolved hostname (outlook.office365.com).
10:45:52 Prepare secure connection...
10:45:52 Successful connection.
10:45:52 Initiating secure connection...
10:45:52 Returned (4)...
10:45:52 Protocol version: kTLSProtocol12
10:45:52 S: * OK The Microsoft Exchange IMAP4 service is ready. [RgBSADMAUAAyADgAMQBDAEEAMAAwADkAMQAuAEQARQBVAFAAMgA4ADEALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
10:45:52 C: A0 CAPABILITY
10:45:52 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
10:45:52 S: A0 OK CAPABILITY completed.
10:45:52 Retrieving password (keychain or user request)
10:45:52 C: A1 AUTHENTICATE XOAUTH2 ••••••••••
10:45:54 S: A1 OK AUTHENTICATE completed.
10:45:54 C: A2 CAPABILITY
10:45:54 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+
10:45:54 S: A2 OK CAPABILITY completed.
10:45:54 C: A3 ID ("name" "MailMate" "version" "r5918" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")
10:45:54 S: A3 BAD User is authenticated but not connected.
10:45:54 Warning: Detected Exchange IMAP server response state bug. Trying to work around it by interpreting it as a temporary connection issue.
10:45:54 Error code: 1004
10:45:54 Failed action (1000). Reset observed read/write timeouts: 8/8

10:45:54 Handling reply
10:45:54 Running action
10:45:54 Handling request
10:45:54 Trying to disconnect nicely (8)...
10:45:54 C: A4 LOGOUT
10:45:54 S: * BYE Microsoft Exchange Server IMAP4 server signing off.
10:45:54 S: A4 OK LOGOUT completed.
10:45:54 Clearing connection to outlook.office365.com
10:45:57 Ready to run action (type: 1000, retry count: 3)
10:45:57 Clearing connection to outlook.office365.com
10:45:57 Trying to connect to outlook.office365.com on port 993 (CFNetwork) without STARTTLS (required)
10:45:57 Resolved hostname (outlook.office365.com).
10:45:57 Prepare secure connection...
10:45:57 Successful connection.
10:45:57 Initiating secure connection...
10:45:58 Returned (2)...
10:45:58 Protocol version: kTLSProtocol12
10:45:58 S: * OK The Microsoft Exchange IMAP4 service is ready. [RgBSADMAUAAyADgAMQBDAEEAMAAwADkANQAuAEQARQBVAFAAMgA4ADEALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
10:45:58 C: A0 CAPABILITY
10:45:58 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
10:45:58 S: A0 OK CAPABILITY completed.
10:45:58 Retrieving password (keychain or user request)
10:45:58 C: A1 AUTHENTICATE XOAUTH2 ••••••••••
10:46:00 S: A1 OK AUTHENTICATE completed.
10:46:00 C: A2 CAPABILITY
10:46:00 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CLIENTNETWORKPRESENCELOCATION BACKENDAUTHENTICATE CHILDREN IDLE NAMESPACE LITERAL+
10:46:00 S: A2 OK CAPABILITY completed.
10:46:00 C: A3 ID ("name" "MailMate" "version" "r5918" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")
10:46:00 S: A3 BAD User is authenticated but not connected.
10:46:00 Warning: Detected Exchange IMAP server response state bug. Trying to work around it by interpreting it as a temporary connection issue.
10:46:00 Error code: 1004
10:46:00 Failed action (1000). Reset observed read/write timeouts: 8/8

10:46:00 Handling reply
10:46:00 Error: Failed multiple retries (4). Final error code was 1004.
10:46:00 Terminating non-running connection...

Comments and changes to this ticket

  • Stefan Seiz

    Stefan Seiz December 28th, 2022 @ 10:51 AM

    FWIW: with the same account, i can successfully send mails via SMTP.

  • Joshua Wang

    Joshua Wang December 28th, 2022 @ 05:24 PM

    I have the same issue with builds 5933, 5913, & 5928 on 2 machines.

  • John Man

    John Man December 28th, 2022 @ 07:30 PM

    I suddenly have this problem too. Mailmate was working fine with Office 365 this morning and then during the morning (I think) it suddenly stopped working. I have not changed any settings nor changed any software.

    Accessing my Office 365 mailbox using my iPhone's Mail app works. Mailmate does not work.

    I tried creating an Office 365 one time password and using that instead with the "openssl" command I found in another post on this tracker but it still doesn't work. Full log below. The end says:

    ". OK CAPABILITY completed. A LOGIN "[ my e-mail address ]" "[ my onetime password ]"
    A NO LOGIN failed.
    * BYE Connection is closed. 13 read:errno=0"

    Running Mailmate 1.14 (5918) -

    % openssl s_client -connect outlook.office365.com:143 -starttls imap -crlf CONNECTED(00000005)
    depth=1 C = US, O = DigiCert Inc, CN = DigiCert Cloud Services CA-1
    verify error:num=20:unable to get local issuer certificate
    verify return:1
    depth=0 C = US, ST = Washington, L = Redmond, O = Microsoft Corporation, CN = outlook.com

    verify return:1

    Certificate chain
    0 s:C = US, ST = Washington, L = Redmond, O = Microsoft Corporation, CN = outlook.com i:C = US, O = DigiCert Inc, CN = DigiCert Cloud Services CA-1 1 s:C = US, O = DigiCert Inc, CN = DigiCert Cloud Services CA-1

    i:C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert Global Root CA

    Server certificate
    -----BEGIN CERTIFICATE----- MIIIpTCCB42gAwIBAgIQDxLciVWCHW2Ta8805Q9gxTANBgkqhkiG9w0BAQsFADBL
    MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMSUwIwYDVQQDExxE
    aWdpQ2VydCBDbG91ZCBTZXJ2aWNlcyBDQS0xMB4XDTIyMDcyNjAwMDAwMFoXDTIz
    MDcyNTIzNTk1OVowajELMAkGA1UEBhMCVVMxEzARBgNVBAgTCldhc2hpbmd0b24x
    EDAOBgNVBAcTB1JlZG1vbmQxHjAcBgNVBAoTFU1pY3Jvc29mdCBDb3Jwb3JhdGlv
    bjEUMBIGA1UEAxMLb3V0bG9vay5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAw
    ggEKAoIBAQDExqNeJz0HhPtPKSmy4DkZwslNIXxjFMAWx39xzl8xZDjcrrPXEca1
    6hBDy303zQE0r3IOni/003PH/Jev1lEVhwHjitV31L/jqJBG0N4U4DroAP/xo/eu
    mFxnQ2LprpH7gqTYjT6EPtL+B4SwiqN5PdNceD14TitOLBnRPtVv4bXRp7Ha/edE
    LgsW42fEsj/tA5xILLxt3gsxjOdIFWHwhyX61ljd+21AI2m4M0noXlXBAsRZNlg0
    S3IY4iFT/qcCJHFBcHKlUiI0rYffV99oOBFXCZSMwOR329q1SyJjDFT+kK4B7sRp
    mbd7OGD10YJ0OH1M9V7EmbvS9xa4dZfxAgMBAAGjggVkMIIFYDAfBgNVHSMEGDAW
    gBTdUdCiMXOpc66PtAF+XYxXy5/w9zAdBgNVHQ4EFgQUcrf5PM7TwFPdaxXdnVcp
    nzMoKfgwggIQBgNVHREEggIHMIICA4IWKi5jbG8uZm9vdHByaW50ZG5zLmNvbYIN
    Ki5ob3RtYWlsLmNvbYIWKi5pbnRlcm5hbC5vdXRsb29rLmNvbYIKKi5saXZlLmNv
    bYIWKi5ucmIuZm9vdHByaW50ZG5zLmNvbYIMKi5vZmZpY2UuY29tgg8qLm9mZmlj
    ZTM2NS5jb22CDSoub3V0bG9vay5jb22CFyoub3V0bG9vay5vZmZpY2UzNjUuY29t
    ghthdHRhY2htZW50Lm91dGxvb2subGl2ZS5uZXSCHWF0dGFjaG1lbnQub3V0bG9v
    ay5vZmZpY2UubmV0giBhdHRhY2htZW50Lm91dGxvb2sub2ZmaWNlcHBlLm5ldIIW
    YXR0YWNobWVudHMub2ZmaWNlLm5ldIIaYXR0YWNobWVudHMtc2RmLm9mZmljZS5u
    ZXSCHWNjcy5sb2dpbi5taWNyb3NvZnRvbmxpbmUuY29tgiFjY3Mtc2RmLmxvZ2lu
    Lm1pY3Jvc29mdG9ubGluZS5jb22CC2hvdG1haWwuY29tghZtYWlsLnNlcnZpY2Vz
    LmxpdmUuY29tgg1vZmZpY2UzNjUuY29tggtvdXRsb29rLmNvbYISb3V0bG9vay5v
    ZmZpY2UuY29tghRzdWJzdHJhdGUub2ZmaWNlLmNvbYIYc3Vic3RyYXRlLXNkZi5v
    ZmZpY2UuY29tMA4GA1UdDwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYI
    KwYBBQUHAwIwgY0GA1UdHwSBhTCBgjA/oD2gO4Y5aHR0cDovL2NybDMuZGlnaWNl
    cnQuY29tL0RpZ2lDZXJ0Q2xvdWRTZXJ2aWNlc0NBLTEtZzEuY3JsMD+gPaA7hjlo
    dHRwOi8vY3JsNC5kaWdpY2VydC5jb20vRGlnaUNlcnRDbG91ZFNlcnZpY2VzQ0Et
    MS1nMS5jcmwwPgYDVR0gBDcwNTAzBgZngQwBAgIwKTAnBggrBgEFBQcCARYbaHR0
    cDovL3d3dy5kaWdpY2VydC5jb20vQ1BTMHwGCCsGAQUFBwEBBHAwbjAlBggrBgEF
    BQcwAYYZaHR0cDovL29jc3B4LmRpZ2ljZXJ0LmNvbTBFBggrBgEFBQcwAoY5aHR0
    cDovL2NhY2VydHMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0Q2xvdWRTZXJ2aWNlc0NB
    LTEuY3J0MAwGA1UdEwEB/wQCMAAwggF9BgorBgEEAdZ5AgQCBIIBbQSCAWkBZwB2
    AOg+0No+9QY1MudXKLyJa8kD08vREWvs62nhd31tBr1uAAABgjnW85EAAAQDAEcw
    RQIgLhN1N0Z3HEmJ0TD7SRYIVDiHgzSDrZCgBf2IT0lXZSgCIQDw6zN6TD1330Xh
    1KBXZljNZWIlTJ4r9xi9wZ106kVgwwB1ADXPGRu/sWxXvw+tTG1Cy7u2JyAmUeo/
    4SrvqAPDO9ZMAAABgjnW8voAAAQDAEYwRAIgB4KLMe5ZgCB5IwfS3fZUbPNGTUJ2
    9SPYi4ILrj68EeQCIGWn/7YkImZ0gmGO1RujumE2l1yF/bYujBkeysD5yRKwAHYA
    s3N3B+GEUPhjhtYFqdwRCUp5LbFnDAuH3PADDnk2pZoAAAGCOdbzMwAABAMARzBF
    AiEAhVbwtFZ5oSR6efbYNZAHlVodkj9SifCwoFrK4xi9CmECIHyhp7lK1Po0zCVj
    igg2BkQgBv0+3n9egZ6QCh2r8NNqMA0GCSqGSIb3DQEBCwUAA4IBAQDLhOIXjbqd
    zfFNBHENvGMFFfVOp3Fs/81rTKD5VEIaQWJcmMXeU6g65NnHDCJdkIt8A13OGHc8
    UHOGIinbyJvCxq724Bv+wkni69k9cQSAm1YjK26QEIVlVuobSIJGd/AK4QGC9OXo
    Xl3MD1xfTXkuxHOVqxm1EN+Cf+XBvw3TVHM8+bt7w9GYtAcmCAQTl0fNSnt7JJME
    69TUOjumKuePU6RVszSErXPcoEdP3tzTlMcBoAmORYqs6ukasZBUfwKd0noVNt6z
    pxceFjtXY0SXOUppPjm7KiJ6fSibXHP2cal8JEbqaHMKIeFE8ab0Gnt9AH7KMb7+
    NwpRQbro93RX
    -----END CERTIFICATE----- subject=C = US, ST = Washington, L = Redmond, O = Microsoft Corporation, CN = outlook.com

    issuer=C = US, O = DigiCert Inc, CN = DigiCert Cloud Services CA-1

    No client certificate CA names sent
    Peer signing digest: SHA256
    Peer signature type: RSA-PSS

    Server Temp Key: ECDH, P-384, 384 bits

    SSL handshake has read 4333 bytes and written 507 bytes

    Verification error: unable to get local issuer certificate

    New, TLSv1.2, Cipher is ECDHE-RSA-AES256-GCM-SHA384
    Server public key is 2048 bit
    Secure Renegotiation IS supported
    Compression: NONE
    Expansion: NONE
    No ALPN negotiated
    SSL-Session:
    Protocol : TLSv1.2 Cipher : ECDHE-RSA-AES256-GCM-SHA384 Session-ID: 424C0000BDE978B879D2FA86A6744447CF1F06DDB1D4B4A8A88E903F815B391A Session-ID-ctx: Master-Key: 4DEC52022C8761D539704C3CE6345B12C85E9930ACF9C33AED96BC5C5D00E7691D30D53D3C696207CDF4EB9B847FFA08 PSK identity: None PSK identity hint: None SRP username: None Start Time: 1672255186 Timeout : 7200 (sec) Verify return code: 20 (unable to get local issuer certificate)

    Extended master secret: yes

    . OK CAPABILITY completed. A LOGIN "[ my e-mail address ]" "[ my onetime password ]"
    A NO LOGIN failed.
    * BYE Connection is closed. 13 read:errno=0

  • Will Wright

    Will Wright December 29th, 2022 @ 02:10 PM

    Same issue, MailMate build 5918. Pretty sure this was working fine yesterday, so I guess Microsoft have made a change.

  • Will Wright

    Will Wright December 29th, 2022 @ 02:14 PM

    Also, I am sorry - I accidentally flagged the comment from @Antti dated 28th Dec 12:24 PM as spam - sorry @Antti! The "flag as spam" button appeared at exactly the same moment I clicked inside the browser window, and there doesn't seem to be any way to un-flag.

    I didn't mark @John Man's comments as spam, honest!

  • Chris Jones

    Chris Jones December 29th, 2022 @ 03:30 PM

    I'm also running into the same issue. I've downgraded from build 5933 to 5918 and still have the issue. I even went so far as to remove the source account and try to re-add but to no avail. I think Microsoft has changed something thats broken OAuth with Mailmate.

  • Nuno Cruz

    Nuno Cruz December 29th, 2022 @ 05:19 PM

    I also have the same issue, can't find a workaround...

  • benny

    benny December 29th, 2022 @ 07:51 PM

    It appears everyone have the same issue:

    10:42:14 C: A3 ID ("name" "MailMate" "version" "r5918" "vendor" "Freron Software" "contact" "mm-imap-id@freron.com")  
10:42:14 S: A3 BAD User is authenticated but not connected.

    That response from the server is incorrect (BAD is misused here), but MailMate can handle that and this is not new (it's an old Exchange issue). The human readable string “User is authenticated but not connected” seems to indicate that the real problem is a backend-issue at Microsoft. It's not possible to know how that works exactly, but I assume the IMAP interface for Exchange needs some kind of connection to the backend and this fails for some reason. This will most likely be a temporary issue.

    Note that before this happens then the authentication completes without problems:

    10:42:13 C: A1 AUTHENTICATE XOAUTH2 ••••••••••  
10:42:14 S: A1 OK AUTHENTICATE completed.

    Therefore the problem is not related to OAuth2. Note that it's also unlikely to be related to the ID command used. This just happens to be the first command requiring access to the backend (I'm guessing here).

    I'm afraid there's not much I can do at my end. I'll reconsider if anyone gets into contact with someone at Microsoft claiming that MailMate does something incorrectly :)

    Note that email clients using a native Exchange protocol will likely not have this issue. In other words, Apple Mail might work as a temporary solution.

  • Chris Jones

    Chris Jones December 29th, 2022 @ 09:14 PM

    Benny,

    Thanks for the update. With Microsoft I only see issues like this rearing their ugly head more frequently. Also, I don't see them investing in their IMAP implementation and only making it increasingly more difficult for users, forcing them to use native solutions.

    Considering how many of us Mailmate users are beholden to our organization's email server and that a good portion of companies use Microsoft Office 365 for email, is there any chance you would re-consider implementing a native Exchange protocol into Mailmate?

    Mailmate is such a wonderful application and extremely powerful, I would hate to lose it. I've been limping by with Outlook since this issue starting happening but it's incredibly painful to use. I miss simple features such as using Vim navigation/action keys to mange and navigate email messages. Why doesn't every application use Vim key bindings ;)

    I know that implementing a new backend protocol is a major deal and would take a lot of time and energy but maybe there is a case for it? I'm a paid user and would be willing to pay a small nominal monthly fee in support of the development. Maybe others would be too?

    Cheers,
    -Chris

  • Mike

    Mike December 30th, 2022 @ 01:03 AM

    There is another workaround (besides changing the mail client): DavMail (https://davmail.sourceforge.net/).

    DavMail is an Exchange SMTP/IMAP/*DAV proxy that is usually operated locally on the computer. I have been using it for years to access the company Exchange with MailMate, which works excellently. In contrast to Exchange IMAP, even tagging via IMAP keywords/exchange categories works here.

    If the problem here is limited to Exchange IMAP, it might be worth trying DavMail. To get you started, here is part of my config:

    a) MailMate

    IMAP server: localhost:1143
    SMTP server: localhost.1025

    b) DavMail > Main:

    Exchange Protocol: EWS
    EWS URL: https://mail.******.de/EWS/Exchange.asmx
    Local IMAP port: 1143
    Local 1025 port: 1025

    I think that's it. If there are any questions, please ask.

  • Will Wright

    Will Wright December 30th, 2022 @ 10:37 AM

    Hi Antti,

    Please can you tell me how I can find MailMate's client id (and secret, if needed)?

    Many thanks

  • Nuno Cruz

    Nuno Cruz December 30th, 2022 @ 11:07 AM

    Thank you for the davmail hint! Lets see if I can set it to work in background, foreground is working fine!

    @will you don't need to get the client id, just let it use davmail and accept it on the first login.

  • benny

    benny December 30th, 2022 @ 01:01 PM

    @Antti: I'm not sure it tells us much that the Analyzer works. It's likely that the problem only happens for specific accounts and/or specific network conditions leading to connections with servers which have trouble connecting to the backend. Again, just guessing. Only Microsoft knows.

    @Chris: Microsoft has actually done more recently for making IMAP/SMTP work by introducing support for OAuth2. It's kind of important to keep the pressure on them to keep it that way :) In any case, I do not have any plans for native support.

    @Antti: Your solution seems to indicate that the problems is somehow related to the OAuth2 support in MailMate? Could you try again with MailMate. Maybe first delete the tokens saved by MailMate to make sure the account is re-authenticated. The tokens can be found in Keychain Access and are named like this:

    com.freron.MailMate.Office365.oauth-refresh-token
com.freron.MailMate.Office365.oauth-token

    I did not know about the proxy-implementation for OAuth2, but it actually worries me that this is now an easily available solution. I've been critical of the use of OAuth2 for desktop email clients because it's often misinterpreted as providing more than two factor authentication security. I've had to go through registration procedures with both Google and Microsoft to get a client id and the “promise” is that this will enable both these companies and IT administrators to specifically lock out MailMate if it should ever do something evil. Sounds great and this does work in practice for server-based clients (web clients), because in this case it's possible to have a shared secret between the servers. This is NOT possible when using a desktop client since the secret has to be part of the application bundle. In other words, the identification/verification of the email client is based on the client id only.

    Eventually something like this will likely happen:

    • Some scammer/hacker/evildoer needs to do something bad and it involves connecting/authenticating with Gmail/Office365. Maybe some kind of virus stealing user credentials/tokens and using them to connect to accounts and steal and/or delete emails.
    • OAuth2 is required to authenticate which means only whitelisted applications can be used to do this. The scammer could use Thunderbird, MailMate, or some other whitelisted app, but it's also possible to just steal the credentials of one of these apps and use them in a script (which is much easier to automate).
    • The reaction from Gmail/Office365/IT-admins might then be to blacklist these apps. If this happens to a small app like MailMate then I'm afraid it'll be difficult to resolve the situation (I can, of course, just make the client id configurable and then users can tell MailMate to pretend to be whatever application is not blacklisted -- the only way around this is to blacklist all desktop apps).

    What I'm saying here is not that OAuth2 is not useful (2FA is good), but that the whole verification process for desktop apps is pretty useless. It's security by obscurity. Apple already takes care of verifying MailMate (at least to some extent) and they have the power to block MailMate if they determine that it has somehow turned evil (for example, if I was somehow hacked and a malware-variant was created and it successfully passed Apple's initial checks). This is real security.

    Open question: Does authentication via native Exchange protocol(s) work the same way? I suspect the answer is yes, but I don't really know. If I'm right then it should be possible for an app/script to pretend to be Apple Mail or even Outlook itself.

  • Will Wright

    Will Wright December 30th, 2022 @ 03:00 PM

    Thank you @Antti, now I am also able to use the Email OAuth 2.0 Proxy as a workaround.

    @Benny before I switched to using the proxy, I first tried deleting MailMate's OAuth2 tokens from the keychain and then re-authenticating. Unfortunately this didn't work. The re-auth flow seemed to work as normal, but I get the same error as before after MailMate sends the ID IMAP command.

    I setup the proxy, and then changed the IMAP account settings in MailMate to use the proxy. This didn't quite work as expected - I had to edit Sources.plist manually and set "oauth2" = ":false". I may have made a mistake changing the settings using the GUI.

  • benny

    benny December 30th, 2022 @ 03:11 PM

    @Antti: I could make an option to disable the ID command, but I'm not sure that makes sense since MailMate would also run the ID command through the proxy? (You can check the logs in the Activity Viewer in MailMate to make sure.)

    @Will: Thanks for the extra data point. It helps to know at least two users have successfully used this workaround.

    Maybe one of you (or both of you) could send me your Sources.plist file and your proxy settings. I'd like to see if I can spot any differences. I can also compare with my own Office365 test account. Use “Help > Send Feedback”.

  • benny

    benny December 30th, 2022 @ 03:16 PM

    Just to make sure: I deleted my own tokens for a test account I have configured. This sent me through authentication including using the Authenticator app on my phone and then the account synchronized.

  • Joshua Wang

    Joshua Wang December 30th, 2022 @ 03:42 PM

    1. I have tried deleting my tokens, and the same issue persists. After deleting my tokens, I am sent through the authentication process, including 2FA. The account did not synchronize.
    2. I have one desktop running build 5928 on my office machine that is permanently inside the internal network (i.e. not on corporate VPN, etc). It has the same Office365 config (hosts/ports/username/etc), but is still able to synchronize - it does not demonstrate this issue. I'm not sure what corporate DNS/networking/IT black magic is at work here, but if this is purely an Office365/Microsoft issue, I would expect all my clients to have this issue?
  • Will Wright

    Will Wright December 30th, 2022 @ 04:55 PM

    @Benny: I've just emailed you my Sources.plist and emailproxy.config.

    If @Antti or anyone else sends emailproxy.config, just be aware that the proxy stores access & refresh tokens in this config file, so it might be worth redacting or removing them :-)

  • benny

    benny December 30th, 2022 @ 05:05 PM

    @Will: Good point on the tokens. Thanks for including the warning. (Seems a bit unsafe to store them in a plain text file.)

    I don't see any obvious differences. The only minor thing is that the scope includes https://outlook.office365.com/POP.AccessAsUser.All which is unnecessary since MailMate cannot use POP3 at all.

    @Joshua: I did change how MailMate gets access tokens in a recent release, but further above we can see that r5918 also fails. This does not seem to be the problem.

    I'm currently out of ideas...

  • Lars

    Lars December 31st, 2022 @ 07:54 AM

    I am encountering the same issue, but it has been spotty (as in, in this very moment it is working for me). While initially, people have been quick to link it to changes in authentication methods offered by Microsoft (that should not be related since OAuth2 is used here) and this could potentially be related to IMAP being disabled or not licensed, some Thunderbird users have had success switching off IPv6 and connecting via IPv4 only (via Reddit).

  • Antti

    Antti December 31st, 2022 @ 10:38 AM

    @Lars: Thanks for the info and links! Everything seems to be working normally again, at least for now. I find it amusing that for Microsoft, noticing, acknowledging customers' complaints, and finally fixing this kind of major issue took so long.

    And thank you Benny for MailMate and for the great support! It was an eye-opening experience having to live without MailMate for a day or two :)

  • Nuno Cruz

    Nuno Cruz December 31st, 2022 @ 12:52 PM

    I still have the issue...

  • Nuno Cruz

    Nuno Cruz December 31st, 2022 @ 01:11 PM

    Just to complete my answer, refreshed the tokens and the behavior is still the same

  • John Man

    John Man December 31st, 2022 @ 02:24 PM

    I still have the same problem but with many thanks to @Lars, turning off IPv6 worked (i.e. IPv4 only) and Office 365 works with Mailmate again!

  • benny

    benny December 31st, 2022 @ 02:47 PM

    @Lars: Thanks for the link. The fact that Thunderbird is also affected seems to indicate that the problem is the behavior of some Office365 servers and not MailMate behavior. That said, if there is something I can do to work around the issue then I'm willing to make changes. I just don't know what those changes could/should be. We'll give it another couple of days to resolve and then try debugging again with the users still experiencing this issue. (I'm not sure how IPv6 vs IPv4 can play a role here, but it's worth keeping it in mind.)

  • benny

    benny December 31st, 2022 @ 03:06 PM

    @John: Sorry, missed your comment at first. It is very interesting to see this “confirmed’ to work with MailMate! Maybe provide exact instructions on how to do this to help other users (and make sure there are no misunderstandings) and then we might also get more data points –– it's tricky with issues which might accidentally resolve at the exact same time as doing some change.

  • John Man

    John Man January 1st, 2023 @ 09:23 AM

    @benny: I just tried re-enabling IPv6 (I get the problem again with Office 365) and then disabling IPv6 (the problem goes away).

    In case helpful for anyone else reading, I did the following from macOS's Terminal:

    1 "sudo networksetup -listallnetworkservices"

    You'll need to enter your macOS administrator password. This command lists all of your network interfaces and their names, e.g. "EXAMPLE".

    2 For each network interface shown, do the following - "sudo networksetup -getinfo EXAMPLE"

    You will have to put quotes around the network interface name if the name has a space in it.

    For each network interface, check that the current setting is "IPv6: Automatic". If it is, continue with these instructins but if not, stop because these instructions are not appropriate.

    3 For each network interface shown, do the following "sudo networksetup -setv6off EXAMPLE"

    If you do step 2 again with that network interface, it should now show "IPv6: Off".

    4 Make sure you check/turn off IPv6 for all of the network interfaces (including your wifi).

    5 Finally, in your browser, go to https://test-ipv6.com to check that you no longer have IPv6 connectivity. Office 365 with Mailmate should now work again.

    I would maybe keep an eye out on (or subscribe to) https://answers.microsoft.com/en-us/outlook_com/forum/all/thunderbi... to see when Microsoft fixes the problem.

    When the problem if fixed and to re-enable IPv6, from macOS's Terminal, follow the above steps but instead of "sudo networksetup -setv6off EXAMPLE" do "sudo networksetup -setv6automatic EXAMPLE". If you go back to the website in step 5 above, it should now show that you have IPv6 connectivity again.

  • Nuno Cruz

    Nuno Cruz January 1st, 2023 @ 06:07 PM

    I can confirm also that turning IPv6 resolved the issue, so we can assume that the server that is providing the service over IPv6 has some kind of issue.´

    Thanks for the hint!

  • Lars

    Lars January 1st, 2023 @ 06:52 PM

    I can now also confirm that disabling IPv6 made MailMate reconnect via IPv4 (= working) and luckily re-enabling IPv6 did not cause it to switch back.

    (I am assuming the reason it was spotty for me is that my DHCP prefix is renewed daily by my ISP, causing short time slots without IPv6 working on my network.)

  • benny

    benny January 2nd, 2023 @ 07:10 AM

    • State changed from “new” to “resolved”

    We'll see if we ever get a technical explanation from Microsoft, but I'm going to assume they are going to fix it. It's worth keeping in mind that this is not a typical network related issue. There's no problem connecting to the server including authenticating the user, but then the server has some internal issue likely triggered when trying to retrieve data from the email account involved. The big question is why this has any relation to whether the original connection was IPv6 og IPv4? :)

    I'll mark the ticket as resolved since a temporary workaround now exists. (If the problem persists then I might look into a workaround built into MailMate.)

  • benny

    benny January 2nd, 2023 @ 07:34 AM

    I should add: The problem is not related to OAuth2. The proxy described further above likely fixes the issue implicitly because it (I assume) creates IPv4 connections instead of IPv6 connections. I guess there's a lesson about false causality to be learned here which also means that I should emphasize that the “IPV6 vs IPv4 explanation” is also just a theory until Microsoft (hopefully) tells us what is causing the issue (otherwise we'll never know since we cannot debug an internal server problem at Microsoft).

  • Christian Bailey

    Christian Bailey January 3rd, 2023 @ 06:58 PM

    I note that Thunderbird users were able to disable IPv6 at the application level:

    "I just disabled ipv6 netwotking in thunderbird advanced configuration editor (network.dns.disableIPv6 = true)"

    Is anything like that possible in MailMate? Turning off every one of six network adapters is quite convoluted.

  • benny

    benny January 4th, 2023 @ 12:41 PM

    @Christian: There's no such setting in MailMate currently. I'm still betting on Microsoft to fix the issue.

    You can likely use a Terminal window to make changes as, e.g., described here. That way it might be easier to switch back again. (This was just quickly googling. I haven't really spent time on what would be the easiest way.)

  • Antelope9

    Antelope9 January 4th, 2023 @ 08:02 PM

    I also have this issue, will try disabling IPv6

  • John Man

    John Man January 5th, 2023 @ 09:32 AM

    People on the Microsoft forums have reported that Microsoft have fixed the issue. I re-enabled IPv6 and Office 365 now works again with MailMate!

  • benny

    benny January 5th, 2023 @ 01:12 PM

    @John: Thanks for the update! If you happen to find anything official from Microsoft then you are welcome to add a link.

  • John Man

    John Man January 12th, 2023 @ 10:59 PM

    From the Microsoft forum just now:

    "Been told by Microsoft today if I want an RCA, I'd have to raise a Premier Support Case - and I have no intention of doing so when this is clearly a bug or config error in key functionality of the Exchange Online service and evidently affecting many customers across Europe.

    The tenant I look after is a non-profit plan offered to charities and the like, so I would never expect anything more than the most basic of service offerings, but this was still a bit of a shocker. If anyone else with deeper corporate pockets, or more comprehensive service plans, wants to try and extract an answer, good luck! :)"

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Mac OS X email client.

Shared Ticket Bins

People watching this ticket

Referenced by

Pages