#2804 new
Tom Burtonwood

Accounts "unavailable"

Reported by Tom Burtonwood | April 10th, 2021 @ 05:38 PM

Hi longtime user first time poster.

right now all my accounts are "Unavailable" nothing has changed at my end as far as i know.

running mac 11.2.3

i did update to big sur recently and at one point mac OS was bugging me to reenter passwords etc which i ignored. but everything seems to work.

i just looked in the internet accounts section in system prefs and it isn't bugging me to enter things - so ... ?

but yeah i can't send or receive email connect to mailmate right now. kinda odd and annoying.

Comments and changes to this ticket

  • benny

    benny April 12th, 2021 @ 12:04 PM

    That is very strange and I guess most likely related to the OS upgrade. First try the latest test release: https://updates.mailmate-app.com/archives/MailMate_r5793.tbz

    If that doesn't help then open the Activity Viewer in MailMate and relaunch MailMate. See if there is anything which might indicate why connections fail.

  • Daniel B

    Daniel B April 12th, 2021 @ 04:38 PM

    I am also experiencing this issue. It appears to be associated with Outlook accounts, not Gmail accounts.
    - I experience a ~similar issue with Mail.app on iOS, in that I am forced to re-login more frequently for these accounts than others, but it works correctly in that case. - I experienced this issue with both 2FA enabled and 2FA not-enabled accounts, no discernible difference. - Upgrading to r5793 from 5757(? whatever the test autoupdate gave me today...) did not correct the problem, but it changed the behavior. Now, rather than only occasionally and randomly being prompted to login to my browser to enable access, I am repeated prompted until I click cancel. It still doesn't work even temporarily, but something changed.

    Activity log:

    16:30:38 Error: Failed multiple retries (1). Final error code was 15.
    16:30:38 Terminating non-running connection...
    16:30:41 Running action
    16:30:41 Handling request
    16:30:41 Trying to disconnect nicely (8)...
    16:30:41 C: A2 LOGOUT
    16:30:41 S: * BYE Microsoft Exchange Server IMAP4 server signing off.
    16:30:41 S: A2 OK LOGOUT completed.
    16:30:41 Clearing connection to imap.outlook.com
    16:30:41 Ready to run action (type: 1000, retry count: 0)
    16:30:41 Clearing connection to imap.outlook.com
    16:30:41 Trying to connect to imap.outlook.com on port 993 (CFNetwork) without STARTTLS (required)
    16:30:41 Resolved hostname (imap.outlook.com).
    16:30:41 Prepare secure connection...
    16:30:41 Successful connection.
    16:30:41 Initiating secure connection...
    16:30:41 Returned (4)...
    16:30:41 Protocol version: kTLSProtocol12
    16:30:41 S: * OK The Microsoft Exchange IMAP4 service is ready. []
    16:30:41 C: A0 CAPABILITY
    16:30:42 S: A0 OK CAPABILITY completed.
    16:30:42 Retrieving password (keychain or user request)
    16:30:42 C: A1 AUTHENTICATE XOAUTH2 ••••••••••
    16:30:42 S: A1 NO AUTHENTICATE failed.
    16:30:42 Error: Server response: “A1 NO AUTHENTICATE failed.”. Command attempted: “A1 AUTHENTICATE XOAUTH2 ••••••••••”.
    16:30:42 Retrieving password (keychain or user request)
    16:30:42 Error code: 12
    16:30:42 Failed action (1000). Reset observed read/write timeouts: 8/8

    16:30:42 Handling reply
    16:30:44 Terminating non-running connection...
    16:32:44 Running action
    16:32:44 Handling request
    16:32:44 Trying to disconnect nicely (30)...
    16:32:44 C: R2 LOGOUT
    16:32:44 Error: Connection error (Broken pipe).
    16:32:44 Clearing connection to imap.outlook.com
    16:32:44 Ready to run action (type: 3, retry count: 0)
    16:32:44 Disconnecting
    16:32:44 Clearing connection to imap.outlook.com
    16:32:44 Completed action (3). Observed read/write timeouts: 8/8

    16:32:44 Handling reply

  • benny

    benny April 12th, 2021 @ 07:45 PM

    I seem to be getting multiple reports about this and a quick attempt to fix it did not work. It may not be easily done. Try disabling OAuth2 and do it using a password (or if 2FA, an application specific password) instead. Let me know if that works or not.

  • Daniel B

    Daniel B April 12th, 2021 @ 08:26 PM

    This appears to have worked, at least for one account. I had to quit and re-open MailMate, though. Taking the account offline and online again didn't work, even with a manual sync.

  • benny

    benny April 13th, 2021 @ 06:47 AM

    • State changed from “new” to “reproduced”

    What I think triggers the problem: Some time ago (in test releases) I found out that I could switch outlook.com (non-Office365 Microsoft email accounts) to use the same app registration (MailMate registeration for OAuth2 at Microsoft) as I had created for Office365. The OAuth2-support for Office365 is quite new, but MailMate has supported it for outlook.com for quite some time. The latter method has been deprecated though (as far as I understand) and therefore I was glad to discover that it also worked when using the new app registration. Now, it seems, something changed at Microsoft and this no longer works. I'm not sure who's to blame. For now, I recommend the password-approach since it's likely more robust at this time.

    (The error I'm getting is about a missing client_id, but I'm pretty sure that's not the real problem.)

  • mom

    mom June 14th, 2021 @ 01:52 AM

    I am also unable to access with mail mate or synchronize my hotmail account since upgrading my Mac operating system from Catalina to Big Sur

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