Freron MailMate

Comments and changes to this ticket

• 

  benny December 17th, 2020 @ 07:32 AM

  • State changed from “new” to “fixcommitted”

  I'm seeing something like this (with Safari) if I delete the com.freron.MailMate.Outlook.* tokens in Keychain Access (which is currently how to force re-authentication). But then it works if I relaunch MailMate and take the account online again (with another round of authentication). I'll investigate the issue, but you can also try relaunching.

• 

  benny December 17th, 2020 @ 07:32 AM

  • State changed from “fixcommitted” to “reproduced”

• You flagged this item as spam.
  

  Florian December 17th, 2020 @ 07:40 AM

  Yes, removing the tokens in Keychain Access and auth after relaunch worked. Thanks for the workaround!

  I've noticed that the tokens in Keychain Access were dated to Nov-14 which was also the last used date of a second MailMate entry I had at https://account.live.com/consent/Manage. This entry also used a different icon than the one that is displayed for the current authorized app, but was clearly linked to MailMate.

  Removing that entry didn't solve the issue, though. Only removing the tokens in Keychain Access helped.

• 

  benny December 17th, 2020 @ 07:50 AM

  • State changed from “reproduced” to “cantreproduce”

  I cannot reproduce the issue now, but I also cannot see how it could be related to what was in the keychain. The authentication process (in the browser) does not use that information.

  How outlook.com accounts are synchronized has been changed (to be able to use an external browser) and this really should trigger re-authentication of the account. I'm unsure if there's a bug in how MailMate does this or if it's the authentication server which gets a bit confused. I'll keep an eye on it. Let me know if it fails for you again and you spot a pattern of some kind. In theory, you should not see the issue again as long as you have the refresh token in the keychain.

• 

  benny December 17th, 2020 @ 07:54 AM

  Following the consent-link I also have both variants of MailMate (it's caused by Microsoft having 2 different systems for registering apps and I'm now only using the new one). This is as expected and only the new one should now be needed.

• 

  benny December 17th, 2020 @ 07:58 AM

  For future reference, the error I got from the Microsoft server when it still failed was:

  AADSTS900144: The request body must contain the following parameter: 'client_id'.
  

  That seems to indicate that MailMate did something wrong, but I don't see how that could happen. (I'll take another look.)

• You flagged this item as spam.
  

  Chad Randl February 15th, 2021 @ 08:38 PM

  I am also having this issue when I try to set up my Exchange email account. I don't see a token in Keychain Access as described above. Tried on Safari and then Chrome as default browsers, but both go to login.microsoftonline.com but before I can enter my Exchange password, it closes that window and up pops a new window stating: "Authorization flow completed. You can now close this browser window and return to MailMate." Thanks for any help.

• 

  benny February 18th, 2021 @ 09:44 AM

  @Chad: See my reply to the direct feedback email you sent me.