Have been unable to receive emails since 8 Nov, error message returns "Sending of password for user g.xxxxxxxx@att.net did not succeed. Mail server inbound.att.
Hello, I have been unable to receive emails since 8 Nov, error message returns "Sending of password for user g.xxxxxxxx@att.net did not succeed. Mail server inbound.att.net responded: maildrop busy." Prior to 8 Nov there were no problems. I am able to log into att.net and check my emails, and I can reply to those emails received in Thunderbird prior to 8 Nov. The server returns "incorrect password" when I tried using the wrong password.
I copied my profile then uninstalled and reinstalled Thunderbird without any luck.
I also noticed in the error console two messages regarding chrome and one for "creating services from category 'profile-after-change'" and don't know if they are related to this problem. These messages were created when I opened Thunderbird.
Alle Antworten (4)
Have you checked your mail server settings in Thunderbird? https://www.att.com/esupport/article.html#!/dsl-high-speed/KM1010523 This page says the correct settings for each type of e-mail address.
You could try creating another account in Thunderbird using the IMAP settings. I've found that some ISP's are not supporting POP anymore. It just happened with a client, and when I switched their settings to use IMAP, everything worked great.
Hello Bruce and Thank You.
I did all the basic pre-checks before posting my question. AT&T tech support says they do not support IMAP although I was able to set up an IMAP account but received some emails with headers and no content. I switched back to the POP account and was able to download mail until Wed when I started to receive the "maildrop busy" error message. Any other options? Thanks again.
Side note - email does recognized when I enter an incorrect password while now returning the "maildrop busy" error message. :(
Two other people I've helped here in the last couple of days have also had problems with ATT and e-mail. In both of their cases, it was a problem sending e-mail, though.
I'm thinking that ATT is generally having problems with their e-mail servers, and your "maildrop busy" message confirms that.
So it is up to ATT to fix the problem, even if they won't admit that there is a problem.
Sorry we can't help here.