Fix Server Denied POP3 Access Error

This guide walks you through resolving the “server denied POP3 access for the given username and password” error, a common issue when setting up email in a mail client like Outlook, Thunderbird, or Apple Mail. You’ll learn the most likely causes—incorrect credentials, wrong server settings, or security blocks—and the exact steps to fix each one so you can get back to reading your email.

What You’ll Need

Your full email address (e.g., name@example.com)
Your email account password (or an app-specific password if you use two-factor authentication)
Access to your email provider’s support or settings page (to confirm server names and ports)
The mail client you’re using (Outlook, Thunderbird, Apple Mail, etc.)

Step-by-Step

Verify your username and password. The most common cause is a typo. Type your full email address as the username (most providers require it, not just the part before the @). Double-check that the password is correct by logging into your email provider’s webmail in a browser. If you can’t log in there, reset your password first.
Check for app-specific passwords. If you have two-factor authentication (2FA) enabled, your regular password won’t work in a mail client. Log into your email provider’s security settings and generate an app password specifically for mail. Use that app password in your mail client instead of your normal one.
Confirm the incoming server settings. Open your mail client’s account settings and verify the incoming server (POP3) details. Common settings are:
– Server: pop.example.com (replace with your provider’s actual server, e.g., pop.gmail.com for Gmail, pop.mail.yahoo.com for Yahoo)
– Port: 995 (SSL/TLS) or 110 (STARTTLS)
– Encryption: SSL/TLS or STARTTLS (most providers require SSL/TLS on port 995)
– Authentication: Password (or Normal password)
If you’re unsure, check your provider’s help page for the exact POP3 server and port.
Test the server connection manually. Use a command-line tool like Telnet or an online POP3 tester to see if the server accepts your credentials. For Telnet, open a terminal and type: telnet pop.example.com 110 (or 995 for SSL). Then type USER your@email.com and PASS yourpassword. If you get a positive response like “+OK”, your credentials are correct; if you get “-ERR”, the server is rejecting them.
Check if POP3 is enabled on your email account. Some providers (like Gmail) require you to enable POP access in your account settings before it works. Log into your webmail, go to Settings, and look for “Forwarding and POP/IMAP” or similar. Enable POP access and save changes.
Update your mail client’s password. If you recently changed your email password, your mail client may still be using the old one. Go into your account settings, find the password field, and enter the current password. Also check if your client has a “password expired” or “re-enter password” prompt.
Try a different port or encryption method. If your provider changed its security requirements, your old settings might be outdated. Try switching from SSL/TLS to STARTTLS on port 110, or vice versa. Some providers also support port 995 with STARTTLS.
Disable any security software temporarily. Firewalls or antivirus programs can block POP3 connections. Temporarily disable them and try again. If it works, add an exception for your mail client.
Remove and re-add the account. If nothing else works, delete the email account from your mail client and set it up again from scratch. This clears any cached credentials or corrupted settings. When re-adding, enter the correct server settings and credentials.

Common Mistakes

Using the wrong username format. Some providers want just the part before @, while others want the full email address. Always use the full address unless your provider explicitly says otherwise.
Confusing POP3 and IMAP servers. POP3 and IMAP often have different server addresses (e.g., pop.gmail.com vs. imap.gmail.com). Using the IMAP server for POP3 will cause authentication failures.
Forgetting to update the password after a change. If you changed your email password recently, your mail client still has the old one. Update it in the account settings.
Using the wrong port. Port 110 is for plain POP3, but many providers require SSL on port 995. Using the wrong port can cause the server to reject the connection.
Ignoring two-factor authentication. If 2FA is on, you must use an app-specific password, not your regular one. Many people overlook this.

Tips

Use the provider’s official settings. Check your email provider’s help page for the exact POP3 server, port, and encryption type. Don’t guess.
Write down your app password. If you generate an app password, store it in a secure password manager so you can use it in multiple devices.
Test with a different mail client. If one client fails, try setting up the same account in another client (e.g., try Outlook if Thunderbird fails). This helps isolate whether it’s a client-specific issue.
Keep your mail client updated. Outdated clients may have bugs or lack support for newer security protocols.
Consider using IMAP instead. If you keep hitting POP3 issues, IMAP is often more reliable and syncs across devices. It’s worth switching if your provider supports it.

Troubleshooting

If you’ve followed all the steps and still get the error, try these additional checks:

Check if the server is down. Visit your provider’s status page or use a service like DownDetector to see if there are widespread outages. If the server is down, you’ll have to wait.
Try a different network. Sometimes your ISP or office network blocks POP3 ports. Try connecting via a mobile hotspot or a different Wi-Fi network.
Check for account lockouts. Too many failed login attempts can temporarily lock your account. Wait 15-30 minutes and try again, or check your provider’s security settings for any lockout notifications.
Look for special characters in your password. Some mail clients mishandle passwords with special characters like @, #, or spaces. Try changing your password to a simpler one (temporarily) to see if that fixes it.
Contact your email provider’s support. If you’ve exhausted all options, there may be an account-specific issue. Provide them with the exact error message and your settings, and they can advise.

Frequently Asked Questions

Why does my mail client say “server denied POP3 access” even though I can log in via webmail?

This usually means your client is using the wrong server settings or an outdated password. Webmail uses a different login process; your client needs the correct POP3 server and port, and if you have 2FA, an app password.

What is an app-specific password and where do I get one?

An app-specific password is a separate password generated by your email provider for use with third-party apps. You create it in your account’s security settings, usually under “App passwords” or “Two-factor authentication.” It’s a long random string that you enter in your mail client.

Can I use my regular password if I don’t have two-factor authentication?

Yes, if 2FA is off, your regular password should work. But make sure it’s the current password and that you’re typing it correctly.

What’s the difference between POP3 and IMAP?

POP3 downloads emails to your device and deletes them from the server (by default), while IMAP syncs emails across devices, keeping them on the server. If you use multiple devices, IMAP is usually better.

Why does my provider require an app password even though I don’t have 2FA enabled?

Some providers enforce app passwords for all third-party apps as a security measure, even without 2FA. Check your provider’s help documentation to see if this applies.

I’m using the correct settings but still get the error. What else can I do?

Try clearing your mail client’s cache, restarting the app, or reinstalling it. Also, check if your email account has been compromised—change your password immediately if you see suspicious activity.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →