How to Fix Outlook Error 0x80042110 When POP3 Receiving Fails

POP3 is simple and reliable, which is why many people still use it, but error 0x80042110 can stop it cold. The message usually says your POP3 server does not support the connection encryption type you have specified, or that the server denied the connection while Outlook was receiving mail. Sending may still work while downloading fails, which makes the problem feel confusing.

Quick Answer

Error 0x80042110 happens when Outlook and your POP3 server disagree about encryption or port settings, or when a damaged message or security program blocks the download. Set the POP3 port to 995 with SSL/TLS, or 110 with no encryption only if your provider requires it, check the stuck message in webmail, and test with email scanning paused. Matching the provider’s exact settings fixes most cases.

What Does Outlook Error 0x80042110 Mean?

This error appears during the receiving stage of a POP3 session. Outlook connects, signs in, and then tries to secure the session or download messages using a method the server does not accept. The session ends, and Outlook reports that the POP3 server denied or could not support the connection.

Unlike a total connection failure, this problem is usually about compatibility. Your password can be correct, your internet can be fine, and yet one wrong encryption choice, such as demanding SSL on a port that expects no encryption, is enough to trigger the error every single time you press Send and Receive.

Main Causes Behind the POP3 Receiving Error

• Mismatched encryption: SSL/TLS is enabled on a port that does not support it, or disabled on a port that requires it.
• Wrong POP3 port: Port 995 expects SSL/TLS, while the legacy port 110 normally expects a plain or STARTTLS connection.
• A corrupted or oversized message: One bad email on the server can block the whole download queue.
• Antivirus mail scanning: Deep inspection can break older POP3 sessions.
• Server-side limit: Too many rapid connections or a temporary provider restriction can deny access.
• Outdated root certificates or very old security settings: The computer cannot negotiate a secure session the server accepts.

Step 1: Match the POP3 Port and Encryption Exactly

This is the first and most important fix. Use only the combination your provider publishes, not a mix that looks reasonable.

1. Go to File > Account Settings > Account Settings, select the POP3 account, and choose Change.
2. Choose More Settings and open the Advanced tab.
3. For a secure setup, set the incoming POP3 port to 995 and tick the option for an encrypted SSL/TLS connection.
4. Set the outgoing SMTP port to 587 with STARTTLS, or as your provider directs.
5. If your provider specifically uses port 110, remove the SSL requirement for the incoming server unless they tell you to use STARTTLS.
6. Click OK, then Next and Finish, and test with Send/Receive.

If you are unsure which combination your provider wants, check their official help pages rather than guessing. A single wrong tick box here is responsible for a large share of 0x80042110 cases. Our broader guide on solving Outlook cannot connect to the server problems covers the related port checks for IMAP and SMTP too.

Step 2: Clear a Stuck or Damaged Message in Webmail

POP3 downloads messages in order. If one message is damaged, extremely large, or has a malformed header, Outlook may fail at the same point every time.

1. Sign in to your mailbox through your provider’s webmail in a browser.
2. Look for the oldest unread message, a message with a huge attachment, or a message that looks unusual.
3. Open, move, or delete that suspect message in webmail. Move it to another folder if you want to keep it.
4. Empty webmail spam or trash folders if they are extremely full.
5. Return to Outlook and run Send/Receive again.

If downloading now completes, the problem was that single message, not your Outlook installation. You can forward the needed content to yourself from webmail or download only its attachment there.

Step 3: Test Antivirus Email Scanning and the Firewall

POP3 is an older protocol, and aggressive mail shields sometimes mishandle it. A careful short test will tell you if security software is involved.

1. Note your current antivirus settings so you can restore them exactly.
2. Pause only the email scanning or mail shield feature, not the whole antivirus.
3. Run Send/Receive in Outlook.
4. If it works, update your antivirus, then re-enable scanning and add Outlook as a trusted application if the option exists.
5. Confirm Outlook is allowed through Windows Firewall on your private network.

Microsoft’s official advice for similar receiving problems, including checking account settings and interference from other programs, is summarised in its guide on troubleshooting Outlook email setup. Follow it alongside the steps here if your account was recently added or changed.

Step 4: Adjust Timeouts and Connection Habits

On slow connections or with large mailboxes, Outlook may give up before the server finishes responding.

1. Open Account Settings, choose More Settings, and go to the Advanced tab.
2. Increase the Server Timeouts value to two or three minutes.
3. Close other devices or programs that are polling the same POP3 mailbox at the same moment.
4. Avoid pressing Send/Receive repeatedly in quick succession, which can trigger a temporary server lock.
5. Restart Outlook and your router, wait a full minute, then test once.

Step 5: Repair the Account or Test a New Profile

If settings are correct and no single message is to blame, the account entry or profile may be damaged.

1. Try the built-in repair: go to File > Account Settings, select the account, and choose Repair where available.
2. If repair changes nothing, open Control Panel, go to Mail > Show Profiles, and add a new profile.
3. Add the POP3 account fresh, using the verified port and encryption combination from Step 1.
4. Point the new profile to your existing PST file so you keep your downloaded mail.
5. Test the new profile before removing anything old.

Tips for Keeping POP3 Reliable

• Leave a copy wisely: If you read mail on several devices, consider the setting to leave a copy on the server for a limited number of days, so one device does not empty the mailbox for the others.
• Watch mailbox size: A nearly full server mailbox receives and downloads poorly. Archive old mail regularly.
• Consider IMAP: If your provider offers IMAP and you use multiple devices, IMAP avoids many POP3 sync and stuck-message quirks entirely.
• Keep records of settings: Save a note of the working server names, ports, and encryption so a future reinstall takes minutes.

Conclusion

Outlook error 0x80042110 is almost always a receiving-side mismatch: the wrong POP3 port and encryption pairing, one bad message blocking the queue, or a security program interrupting the session. Match your provider’s exact settings, clear the suspect message in webmail, and test your mail shield. With those checks done in order, POP3 downloading normally resumes without reinstalling Outlook or risking your stored mail.

Frequently Asked Questions

Why can I send mail but not receive it with error 0x80042110?

Sending uses the SMTP server, while receiving uses the POP3 server, and they have separate ports and encryption rules. A wrong POP3 setting blocks downloads even when your outgoing settings are perfectly correct.

Should POP3 use port 995 or port 110?

Prefer port 995 with SSL/TLS because it is encrypted and widely supported. Use port 110 only if your provider specifically requires it, and follow their encryption instructions exactly, because 110 paired with the wrong SSL setting triggers this error.

Can one email really block all my downloads?

Yes. POP3 downloads in sequence, so a corrupted or oversized message can stop the session at the same point every time. Removing or moving that message in webmail often lets the rest download normally.

Will switching to IMAP stop this error?

IMAP does not use POP3, so this specific error would not occur, and IMAP is usually better for multiple devices. Only switch after confirming your provider supports it and you understand that mail management changes from download-based to server-based.

Is error 0x80042110 a sign my account is hacked?

Not by itself. It is a protocol and settings error. Still, if you also see password rejections or unfamiliar sent messages, change your password from webmail, enable two-step verification, and check your account activity with your provider.