Cannot get the Win 11 Outlook client to connect to any vmin hosted email account.
Settings are configured correctly. I can config teh account on a phone. But cannot get any account to connect via outlook. autoconfig and autodiscover are setup in DNS.
Symptoms are to config the full server and login information. Then continue and it pops up a dialog with waiting for your email provider spinny wheel and then eventually fails with “Sign in failed. Please try again in a few minutes. You may need an app password.”
Troubleshooting details shows error as INVALIDCREDENTIALS TEMPORARILYUNAVAILABLE.
Credentials are correct and tested with multiple other clients.
And round an round it goes. No combination of settings gets your email configured from a vmin account.
Nothing in f2b with the right creds then it wouldn’t be a failed connection. I can’t even see the connection attempt. Unless WIN 11 outlook client is going through some kind of proxy as it is not using the ip of the public gateway on the network we are on. We configured a test account so can filter any connections trying to connect to that account.
Tried all the usual stuff. I had a thought it might be something to do with letsencrypt cert on the test accounts rather than a commercial one. There is no way to configure accept all certs on the advanced config on the outlook client.
Should’t impact. LE is used by thousands of user’s mail servers for many varied client programs.
I assume you have created a mail account in Usermin and tested send+receive to a another user. tried to a gmail account as well?
As Win 11 has been around or a while now this is highly unlikely to be anything to do with Webmin/Virtualmin
I assume you have set up Outlook withe the appropriate setting from
There was a point in time when outlook would not connect to imap servers not saying this is the problem but since this issue I just use thunderbird which just worked
Yes, we have done all the basics. The only thing we can see is different with this client is it is IPV6 only. No IP4 address configured. It is a remote client so not easy to remote control the no IT person.
We managed to walk the client through it step by step. Short story is they must have somehow banned themselves, but we could not find any evidence in f2b. Worked this morning and is now setup.
I apologies for any inconvenience. Thank you to all for responding to this thread.