Start with the right service
AT&T Mail includes several legacy address endings. The address domain helps identify the right account, but it does not mean an old server configuration is still correct. Begin with official AT&T webmail and current security requirements.
Configuration quick reference
| Reference | What to check |
|---|---|
| Connection and access | IMAP imap.mail.att.net:993 SSL; SMTP smtp.mail.att.net:465 or 587. POP inbound.att.net:995 SSL, outgoing outbound.att.net:465. |
| Account authority | Use the original provider for identity verification, account recovery, eligibility and billing. |
Official reference: AT&T server reference. Check the provider’s current instructions before changing settings. Reviewed October 14, 2026.
Work through the problem
- Check the exact address ending and sign in using AT&T’s official mail route.
- If webmail fails, follow the provider’s password or account-recovery process first.
- Use OAuth where supported. Otherwise check whether your app requires an AT&T secure mail key.
- Confirm both incoming encryption and outgoing authentication; do not turn encryption off to suppress an error.
Keep a useful diagnostic record
Note the exact error, the application and version, and whether the same account works on the provider’s website. Record whether sending, receiving or sign-in fails. Remove private message content from screenshots before sharing them.
If you use POP or local folders, preserve those messages before removing an account. A new account configuration may not recover data stored only on the old device.
Choose your next step
For an app-only problem, compare authorization and settings with the official reference above. For an account restriction or failed identity check, continue with the original provider. Independent assistance cannot bypass these controls.
Related guides: IMAP, POP and SMTP · Password recovery · Email synchronization.