Since the 19th of Jan, outlook.com has struggled to pick up my btconnect e-mail.
I get the occasional message come through, but everytime I go in to outlook.com and check my other account settings I always get the following popup:
"4:03 PM We couldn't get your messages: There was a problem connecting to the other server. If you've been seeing this message for a while, consider checking your account settings or contacting your other email service."
I have nearly a 400 email backlog. I know the settings in outlook.com are correct as I use the same details to access the webmail!
Wondering whether this is upgrade related...
Cheers,
Roy
Solved! Go to Solution.
I have found the problem.
There is a good chance it is upgrade related - if your account has been migrated then you'll need to change the settings in outlook.com to point to the new server. If it's not been migrated, double check that outook.com is still pointed to mail.btconnect.com rather than smtp.outlook.com.
Hope that helps,
Adrian
Adrian,
One would assume if I had ben upgraded then I wouldnit be able to log in to the old OWA web mail client.
If I login to business.bt.com with my @btconnect.com email addy and password, I still end up at OWA.
Cheers,
Roy
Hi,
Actually, you will still be able to log into the old webmail even after you are migrated - I have an account that has been migrated but I can still log on to email.btconnect.com. I am guessing this is in case there are any messages that don't get copied over to the new service.
When you log in to the self-care pages, do you get the "Manage Mailboxes" link, or a button that says "Email Summary" - if the former then the account is, as you said, not migrated. If the latter, then it has been migrated.
BTW - as you probably noticed, I had a brain-fart in my previous post. The incoming servers are pop3.btconnect.com for non-migrated and pop.outlook.com for migrated accounts.
Adrian
Yep, I still; get the "Manage mailboxes" link, so not migrated.
Still can't understand why outlook.com is not picking up my mail!
Cheers,
Roy
I have found the problem.