Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
O365 A004 Bad User is authenticated but not connected
Options
Go to last post Go to first unread
Previous Topic Next Topic
lim  
#1 Posted : Monday, October 10, 2022 8:18:29 PM(UTC)
lim

Rank: Newbie

Groups: Registered
Joined: 10/10/2022(UTC)
Posts: 2
Hong Kong
Hi
I have a program run as window service.
every 15s check mailbox, if new mail arrived, download it

We upgraded EAGetMail from 4.6.5.5 to 5.2.5.6
because changing login with basic auth to OAuth2.0

I login O365 account and saved token in txt like your sample project
I could access the mailbox and download it correctly (using same token),
But it failed after serveral minutes, I got A004 Bad User is authenticated but not connected
after that every connect got A002 NO AUTHENTICATE failed.

re-login could work another 5-30 mins, but it need login manually.

Is there something need setting? or other method to access mailbox?
Please help, Thank you
Back to top

Wanna join the discussion?! Login to your EmailArchitect Support forum accountor Register a new forum account.
Back to top  
ivan  
#2 Posted : Wednesday, October 12, 2022 8:29:31 AM(UTC)
ivan

Rank: Administration

Groups: Administrators
Joined: 11/11/2010(UTC)
Posts: 1,153

Thanks: 9 times
Was thanked: 55 time(s) in 55 post(s)
do you refresh the token by refresh token? Please email to our support email address for assistance.
Back to top
lim  
#3 Posted : Sunday, October 16, 2022 10:16:56 PM(UTC)
lim

Rank: Newbie

Groups: Registered
Joined: 10/10/2022(UTC)
Posts: 2
Hong Kong
OK, I refresh token and it work again,
Sometime it still got Error A004
so I refresh the token even it not yet expire.
Thanks for help
Back to top
johnm  
#4 Posted : Tuesday, November 22, 2022 9:09:26 PM(UTC)
johnm

Rank: Newbie

Groups: Registered
Joined: 11/22/2022(UTC)
Posts: 1
Australia
I have a script that runs every 10 minutes or so that connects to O365. Occasionally this error pops up and typically it works again on the next run.

While I haven't found the cause of the error yet, one theory is that it is related to a throttling of the service by Microsoft. This is something we have experienced with O365 in the past, although with different symptoms.

If I find an explanation or solution I will post it here.
Back to top
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF.NET | YAF.NET © 2003-2024, Yet Another Forum.NET
This page was generated in 0.139 seconds.

EXPLORE TUTORIALS

Send Email

Read and Parse Email

DKIM Solution

© All Rights Reserved, AIFEI Software Limited & AdminSystem Software Limited.