Forum Discussion
New Outlook returns INVALIDCREDENTIALS TEMPORARILYUNAVAILABLE, IMAP mailbox after hosting migration
Hello,
I am experiencing a mailbox-specific problem in New Outlook for Windows and would like to know if anyone has seen something similar.
Environment
- New Outlook for Windows
- External IMAP account hosted on SiteGround (following the migration from RoundCube).
- Custom domain
- Same Windows PC and same Microsoft account
Problem
The mailbox fails to be added to New Outlook with:
INVALIDCREDENTIALS TEMPORARILYUNAVAILABLE
The mailbox address has been removed from this post for privacy reasons.
Facts already verified
1. Webmail works correctly.
2. Outlook Classic works correctly on the same PC.
3. IMAP connectivity works.
4. SMTP connectivity works.
5. DNS resolution is correct.
6. SSL certificate is valid.
7. Full email address is used as username.
8. Password was changed and also tested with a simple password without special characters.
9. Account was completely removed and re-added.
10. Cached Windows credentials were removed.
Important observation
The mailbox was recently migrated to a new hosting provider 8SiteGround). The email address remained the same, but the IMAP/SMTP server changed.
To isolate the issue, I created a brand-new test mailbox on the same domain and the same SiteGround server.
Results:
- Existing migrated mailbox -> FAILS in New Outlook.
- New test mailbox on the same server -> WORKS in New Outlook.
- Both mailboxes work in Webmail.
- Both mailboxes work in Outlook Classic.
This seems to indicate that the issue is related to the specific mailbox identity rather than:
- IMAP configuration
- SMTP configuration
- DNS
- SSL certificate
- Hosting provider
- New Outlook installation
Question
Could New Outlook or the Microsoft cloud synchronization service still have historical IMAP server information, mailbox metadata, or a cached backend association linked to this specific email address from before the hosting migration?
Has anyone experienced a mailbox-specific INVALIDCREDENTIALS TEMPORARILYUNAVAILABLE error after changing hosting providers while keeping the same email address?
Thank you.
daniele
4 Replies
- kocabeanadvancedCopper Contributor
Hello Robert,
We have the same New Outlook IMAP server migration issue and need assistance requesting a Microsoft-side reset of the old server association.
Your profile link is not opening correctly for us. Could you please initiate a private message or advise how we can contact you securely?
We have the technical evidence and can provide the affected mailbox address privately.
Thank you,
Koca Bean Technical Support When switching hosting providers for IMAP accounts, your server-side cache for New Outlook needs to be reset. Currently, you can't do this yourself.
For instructions on how to request a reset see;
- Goutham ValugulaBrass Contributor
Hi Daniele,
Your tests narrow this down well. One thing to keep in mind is that New Outlook doesn't connect to your mail server from your PC. Microsoft's cloud service logs in to the IMAP server for you. Outlook Classic and webmail connect directly from your own IP, so they can work while the cloud login fails.
The TEMPORARILYUNAVAILABLE part of the error looks like the server's own "temporary authentication failure" response, not a wrong password. Two things could explain a failure that affects only the migrated mailbox:
- Login throttling or blocking on the SiteGround side. The migrated mailbox may have collected failed logins during the move, and its attempts from Microsoft's IP ranges may now be rate-limited or blocked. The new test mailbox has no such history, so it works. Ask SiteGround support to check the mail/auth logs for that mailbox and to clear or whitelist any block.
- A stale record on Microsoft's side. If this address was added before the migration, the Microsoft account may still hold the old connection. Remove it under Settings > Accounts in New Outlook, and also check outlook.com and account.microsoft.com for any connected-account entry for that address. Wait a little, then re-add it with the explicit IMAP/SMTP server names (993 and 465 or 587, SSL).
To tell which one it is, try adding the same mailbox with a different Microsoft account, or through a temporary alias. If it works there, the problem is tied to the Microsoft account. If it still fails, it points to the SiteGround side.
- danieleperinCopper Contributor
Hi Goutham
SiteGround support have carried out all the necessary checks.
I’ve created a new email address on the same domain (so using the exact same IMAP/SMTP servers) and this new email address works perfectly in the new Outlook.
So the problem, as you said, is down to the Microsoft servers.
Thank you
Daniele