Keychain Failure

Note that I already re downloaded the app and copied it over the existing app in the applications directory. That did not solve it.

I've had several reports about this recently. It is some kind of system issue, but I don't know what triggers it. For some users, it helped to simply reboot. For others, re-installing MailMate or even updating macOS helped.

Another possibility would be to reset the keychain in the Keychain Access preferences pane. I don't think any users have tried that yet.

At one point I suspected that the iCloud keychain somehow played a role, e.g., if the user changed the password, but I'm not so sure anymore.

Hi,

1. I have deleted everything linked to Mailmate from Keychain Access expect the info about Mailmate licence.
   
2. I re-installed the Mailmate
   
3. I refreshed oauth-token for every email account I used before in the Mailmate.

And it works. It looks like problem with the Keychain and stored informations inside.

Best, P

@Piotr: Thanks for the data-point! I'm not sure what this tells us when you didn't do anything to the MailMate license entry in Keychain Access... Maybe any change to the keychain would trigger it to work again...

Another data point: A user reports that the issue was resolved by deleting the license key in Keychain Access and then re-register MailMate.

Just to let you know that a reboot fixed it for me. The only notable thing that happened was that I had to redo the gmail oauth earlier...

@Sjoerd: I also have other reports about a reboot fixing the issue. I'm thinking maybe the solution depends on the problem which might not be the same in all reports about the keychain failure. (The OAuth2 values are also saved in the keychain and therefore it makes sense that re-authentication could be triggered too.)

Another observation after I experienced this issue myself (I'm still not able to reproduce it though). Instead of rebooting I tried killing the system daemon handling access to the keychain. I did it brute force like this:

sudo killall -KILL securityd

I then relaunched MailMate and everything was back to normal (after entering keychain password(s) once). There might be side-effects though. Googling this approach I also found this question which indicates that there might really be problematic side-effects. In other words, look out for any system behavior which might still require a reboot.

The above is just side-stepping the real issue: Figuring out how MailMate gets into this state and then find out how to avoid it.