Author Topic: Reset oauth ticket (is that the right term?)  (Read 10017 times)

Scott_Miller

  • Newbie
  • *
  • Posts: 34
Reset oauth ticket (is that the right term?)
« on: December 19, 2017, 06:55:30 am »
I recently had a problem with my outlook.com account in AquaMail. Everything had been working fine for a very long time. Then suddenly I lost the ability to SEND email, getting an authentication error. However, I could still receive email from the same account without any problem. I did not make any changes to the account prior to this failure. Since this is an oauth account, there is no password reset option. I was not able to get this working, so finally I created a new account in AquaMail, setup all my settings for the account again, and then deleted the old account. Everything works again, but certainly this is a solution that is not desirable. Is there a way to get an existing account to go through the authorization phase again? I have 2FA turned on. Thought I should mention that in case it is relevant. I would also add that this is not my primary account, and so I don't send email often. But I do receive and read emal from this account on an almost daily basis.   

Sent from my SM-T820 using Tapatalk


Nedialko Kondev, MobiSystems, AquaMail Support

  • Administrator
  • Sr. Member
  • *****
  • Posts: 250
Re: Reset oauth ticket (is that the right term?)
« Reply #1 on: December 19, 2017, 11:26:05 am »
Hello,

Please long press on the account -> account setup -> Manual -> You'll get to the detailed account settings from there.

Kostya Vasilyev

  • Hero Member
  • *****
  • Posts: 12740
Re: Reset oauth ticket (is that the right term?)
« Reply #2 on: December 19, 2017, 07:42:49 pm »
"Manual" account setup doesn't reset anything.

Here is what I'd do:

I'd go to here: https://account.live.com/Consent/Manage and remove Aqua Mail

Then wait 5-10 minutes and *then* bring up account setup and tap Next there. The app will detect that you've revoked the permission and walk you through re-authenticating.

But going back to the beginning - the app refreshes its OAUTH tokens in both IMAP and SMTP code when it needs them. So i can't off hand thing of any reason they'd "go bad" (although I don't doubt your story).
Creating debug logs for diagnostics: https://www.aqua-mail.com/troubleshooting/

The official FAQ: https://www.aqua-mail.com/faq/

Лог-файлы для диагностики: https://www.aqua-mail.com/ru/troubleshooting/

Вопросы и ответы: https://www.aqua-mail.com/ru/faq/

Scott_Miller

  • Newbie
  • *
  • Posts: 34
Re: Reset oauth ticket (is that the right term?)
« Reply #3 on: December 19, 2017, 08:14:27 pm »
"Manual" account setup doesn't reset anything.

Here is what I'd do:

I'd go to here: https://account.live.com/Consent/Manage and remove Aqua Mail

Then wait 5-10 minutes and *then* bring up account setup and tap Next there. The app will detect that you've revoked the permission and walk you through re-authenticating.

But going back to the beginning - the app refreshes its OAUTH tokens in both IMAP and SMTP code when it needs them. So i can't off hand thing of any reason they'd "go bad" (although I don't doubt your story).
I did some additional checking. First, this behavior occurred on two devices simultaneously, more or less, making me think this might be a Microsoft problem. But other apps, like Outlook on mobile and Outlook on pc did not experience any problems. The last email that I sent prior to the problem was on December 12. I discovered the problem on December 15, when a message remained in my outbox. I corrected the problem be recreating the account on December 16. This morning I remembered reading about a problem with outlook.com that some people were not able to login over the weekend. It is entirely possible that I was a victim of this problem, and that it might have corrected itself if I waited long enough. Unfortunately, I can't confirm that now.

Thanks for the suggestion of logging in to live.com and revoking the permission. I hadn't thought of that. That probably would have solved it.

Sent from my SM-T820 using Tapatalk