AT&T U-verse login fails, then works?

[epack]

The last week or two I've been getting the below (new to me) error for my AT&T U-Verse account. However, if I simply hit it again for inbounds, no changes made at all, it works uneventfully then, and every time subsequently--until it doesn't. I have noticed that lately when my (win 10 pro) laptop has rebooted, deliberately or otherwise, it *may* occur after it comes up again, but so far I can't prove that. Any ideas?

Thx,
elaine

Description: Failed to login to server "inbound.att.net" for your 03AT-U-Verse account
Diagnosis:
This could suggest the following problems:
- Your username or password is incorrect.
- The server address is incorrect.
- You are trying to connect through an invalid port.

[TrustFire]

You can try disabling pipelining on the affected account/s — if that does not work, you could check out the suggestions at this discussion.

[epack]

I'll certainly check out the other discussion, thanks for that, but given I'm not familiar with pipelining, nevertheless, since it works fine the SECOND time I try the account in question, what makes the first time different? IE, why does IT fail, and an immediate check works fine?

Thx
elaine

[epack]

I disabled the feature on both in/out checks as suggested, and as best as I can tell, the first time I check for inbounds after the machine was rebooted, it continues to fail. Retrying the check then works uneventfully until the next time I reboot. I have it checking for inbounds rather frequently, so I'm quite sure it's working properly. I'll take a closer look at the other suggested convo.

Thanks!

elaine

[epack]

You can try disabling pipelining on the affected account/s — if that does not work, you could check out the suggestions at this discussion.

So I took a look just now, and a couple of observations. I never got the notification mentioned, because we didn't close on our house here until 9 days after the date mentioned But that said, my MWP settings for this account match what was suggested there. I don't use any of the [Windows] clients mentioned, and by now, of course, I'm on Windows 10. It hasn't failed in my client tho, just in MWP, and that is very recent new behavior--I keep a close eye on my inbounds, as I get a LOT of email, and use MWP to read and kill a lot of stuff I don't necessarily want to respond to and/or keep.

elaine

[TrustFire]

Does your MailWasher startup with Windows or do you run it manually?

[epack]

Starts with Windows.

[TrustFire]

For the purpose of testing, you might want to disable MailWasher from starting-up with Windows just to see whether that resolves your issue — your internet connection does not seem to be ready before MailWasher makes its initial mail check.

[epack]

>your internet connection does not seem to be ready before MailWasher makes its initial mail check

Is there a sequence it normally follows in doing this? Other than in the order they are listed in settings? Right now, the AT&T one is 5th in line of about 20-25 accounts it checks (don't ask so you'd think that would be enough time. Of the ones above it, the first two are gmail, the next two are two different own domain accounts. I'd originally had it somewhere around 12th-15th or so, where it still did this, but later moved it up solely so I wouldn't have to scroll to it so I could kick it off manually