Archived Forum Post

Index of archived forum posts

Question:

Re-Authentication Failure

Jul 07 '16 at 08:04

Hi,

what does a Re-Authentication Failure mean? A quick Google didn't give me any clear answers. Here is the log from my customer: 

  Login(8577ms):
    DllDate: Apr  7 2016
    ChilkatVersion: 9.5.0.58
    UnlockPrefix: xxxxxxxxxx
    Architecture: Little Endian; 32-bit
    Language: MAC OS X C/C++
    VerboseLogging: 1
    login: xxxxxxxxxx
    authenticateLogin(8577ms):
      loginImap(8577ms):
        ConnectionType: SSL/TLS
        ImapCmdSent: aaab LOGIN "xxxxxxx"
        getCompleteResponse(8577ms):
          ImapCmdResp: aaab NO Re-Authentication Failure
        --getCompleteResponse
      --loginImap
      isOK:
        serverResponse: aaab NO Re-Authentication Failure
      --isOK
    --authenticateLogin
    Failed.
  --Login
--ChilkatLog

2016-07-02, 8:23:53 AM       

----INFO----
Connecting to IMAP server at imap.xxxxxxxxx.ca:993
----IMAP RESPONSE----
* OK IMAP4 Ready iproxy9.xxxxxxxxxx.ca 00021059
----IMAP REQUEST----
aaab LOGIN "xxxxxxxx"
----IMAP RESPONSE----
aaab NO Re-Authentication Failure
Mit freundlichen Grüßen/Regards

Beatrix Willius

http://www.mothsoftware.com Mail Archiver X: The email archiving solution for professionals

Answer

Unfortunately, I have no idea on this one.

One-line error messages are typically useless and cause much time to be wasted in determining the cause of an error.

I would try to find out what "brand"/implemenation of IMAP server this is. Then search for "re-authentication failure <brand>".

Answer

Hi,

thanks! I'll ask the customer. When IT is using Outlook then I'm betting on Exchange. I've googled this and found only Windows stuff.

Mit freundlichen Grüßen/Regards

Beatrix Willius

http://www.mothsoftware.com Mail Archiver X: The email archiving solution for professionals

Answer

Thanks Beatrix,

The mention of "proxy" in this session log line:

makes me think it's somehow related to an intermediate/proxy. Maybe external clients connect to "iproxy9.xxxx.ca", which behaves as an IMAP server (and from the IMAP client's point of view is no different than an actual IMAP server), but under-the-covers interacts with the actual IMAP server located behind a firewall. (This is just a theory.) Maybe the authentication to a user-account on the iproxy9 is translated/routed/mapped to something on the actual server, and this is the cause for "re-authentication failure" as opposed to simply "authentication failure"? Maybe the problem is somehow within the administration/setup of the accounts having to do with iproxy9?