Closed Bug 242597 Opened 21 years ago Closed 20 years ago

POP3.ATTGLOBAL.NET refuses valid login attempt "INVALID LOGIN"

Categories

(MailNews Core :: Networking: POP, defect)

x86
Windows 98
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: jrace, Assigned: sspitzer)

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6) Gecko/20040113 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6) Gecko/20040113 Using identical valid login strings I can access my ATTGLOBAL.NET POP mail account via ATT's web interface using the Mozilla browser, but when I enter the correct string (cut-and-pasted to preclude typos) into the appropriate fields of the Mozilla mail client, I am repeatedly refused by ATT's POP3 server, complaining "Sending of password did not succeed. Mail server pop3.attglobal.net responded: directory status: INVALID LOGIN" Reproducible: Always Steps to Reproduce: 1. Input <usinet.jrace> into AccounSettings/AccountName during configuration 2. Input <password> into password entry field when requested after keying GetMessages 3. Get error Actual Results: Tried again about 20 times. Expected Results: Successfully logged in There are many login-problem bugs reported (e.g. 234421) but nothing I can find precisely identical.
I just inspected pop3.attglobal.net and it does only offer USER/PASS. That's the default and is very uncritical - normally. "usinet.jrace" is your username, different from your mailaddress? Did you already try "jrace@attglobal.net" or "usinet.jrace@attglobal.net" as username? Is Mozilla the only client having problems, resp. did you already try others?
Product: MailNews → Core
FWIW, I am an attglobal.net user. The "usinet." prefix on the user ID is proper for some purposes (attglobal.net offers other services than ordinary ISPing, such as extranets; the "usinet." narrows it down to the set of US ISP accounts), but the POP server doesn't want it. So I'd put this down to user error.
Misoperation actually resulted from a different problem. Close this report
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.