Outlook Error 0x80042109: Fix Sending Mail

Outlook error 0x80042109 means Outlook could not connect to your outgoing mail server (SMTP) to send an email. This fix usually involves checking your internet connection, verifying your SMTP server settings, or temporarily disabling your antivirus or firewall. Below is a practical guide to resolve the issue and get your email moving again.

What Does Error 0x80042109 Mean?

Error 0x80042109 appears when Outlook times out while trying to reach your outgoing mail server. The full message often reads: “Outlook cannot connect to your outgoing (SMTP) e-mail server. If you continue to receive this message, contact your server administrator or Internet service provider (ISP).” This is a client-side connection problem, not a problem with your email content. It can happen with any email account configured in Outlook, including POP3, IMAP, and Exchange accounts, but it is most common with POP3 and SMTP setups.

The error is triggered when Outlook cannot establish a TCP connection to the SMTP server within its timeout period (usually 60 seconds). Common causes include a flaky internet connection, incorrect SMTP server name or port, a firewall or antivirus blocking the connection, or the SMTP server being temporarily down. In rare cases, the issue is caused by a corrupted Outlook profile or an outdated version of Outlook.

Quick Checks Before You Change Anything

Before diving into settings, rule out the simplest problems. These checks take less than a minute and solve a surprising number of cases.

• Check your internet connection: Open a web page in your browser. If it fails, your internet is down and Outlook will also fail. Restart your router or modem.
• Try sending a test email from webmail: Log into your email provider’s web interface and send a message. If that fails, the problem is on the server side, and you need to wait or contact your provider.
• Restart Outlook: Close Outlook completely, wait a few seconds, and reopen it. This clears temporary glitches.
• Reboot your computer: A full restart often resets network connections and clears stuck processes.
• Check if you are using a VPN: If you are on a VPN, disconnect it temporarily. Some VPNs block SMTP ports.

If none of these help, move on to the more targeted fixes below.

Verify Your SMTP Server Settings

The most common cause of 0x80042109 is an incorrect SMTP server name or port. Outlook needs the exact outgoing server address and port number from your email provider. These are not universal—each provider (Gmail, Outlook.com, Yahoo, your ISP, your company) has its own.

1. Open Outlook and go to File > Account Settings > Account Settings.
2. Select your email account and click Change.
3. Click More Settings > Outgoing Server tab.
4. Check the box “My outgoing server (SMTP) requires authentication” and select “Use same settings as my incoming mail server” (or enter the credentials if your provider requires a different login).
5. Go to the Advanced tab. Verify the Outgoing server (SMTP) port number and encryption method. Common defaults are:

• Port 587 with STARTTLS (most common for modern providers)
• Port 465 with SSL/TLS (used by some providers)
• Port 25 with no encryption (rarely used now, often blocked by ISPs)

If you are not sure of the correct port, check your provider’s help page. A very common mistake is using port 25 when your provider requires 587. Also, ensure the “Use the following type of encrypted connection” dropdown matches what your provider specifies. If you changed anything, click OK, then Next and Finish. Try sending again.

Check Your Antivirus and Firewall

Antivirus software and Windows Firewall can block Outlook’s connection to the SMTP server, especially after an update. They sometimes flag Outlook as suspicious or simply block the port. To test this, temporarily disable your antivirus’s email scanning feature (not the whole antivirus) and try sending. If that works, add Outlook to the antivirus’s exception list and re-enable scanning.

For Windows Firewall:

1. Open Control Panel > System and Security > Windows Defender Firewall.
2. Click Allow an app or feature through Windows Defender Firewall.
3. Look for Microsoft Outlook or Outlook in the list. If it is not there, click Allow another app and browse to C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE (the path may vary).
4. Ensure both Private and Public checkboxes are ticked for Outlook.

If you use a third-party firewall (like Norton or McAfee), check its own settings. After making changes, restart Outlook and test.

Increase the Server Timeout

Sometimes the SMTP server is just slow to respond. Outlook has a default timeout of 1 minute, but you can increase it. This is a good fix if you have a slow connection or a large attachment.

1. Go to File > Options > Advanced.
2. Scroll down to Send and receive.
3. Change Server timeout to 2 minutes or 5 minutes.
4. Click OK and restart Outlook.

This does not fix a fundamental connectivity issue, but it can help if the server is occasionally slow. If the error persists even with a longer timeout, the problem is more likely a blocked port or wrong settings.

Repair Your Outlook Profile

A corrupted Outlook profile can also cause 0x80042109. This is less common, but if you have tried everything else, it is worth trying. You can create a new profile without deleting your email account data.

1. Open Control Panel > Mail (or search for “Mail” in Windows).
2. Click Show Profiles.
3. Click Add to create a new profile, give it a name, and set up your email account again.
4. After creating it, choose “Always use this profile” and select the new one from the dropdown.
5. Restart Outlook and test sending.

If the new profile works, you can migrate your emails and contacts from the old profile. If not, you can switch back. This step does not delete your emails; they are stored on the server or in a PST file.

Frequently Asked Questions

Is error 0x80042109 the same as 0x8004210b?

No. 0x80042109 is specifically about the outgoing (SMTP) server. 0x8004210b is about the incoming (POP3) server. The fixes are similar, but you would check incoming server settings for 0x8004210b.

Can a large attachment cause this error?

Yes. A very large attachment (e.g., over 20 MB) can cause the SMTP server to time out, especially on a slow connection. Try sending without the attachment to see if that is the issue. If it is, compress the file or use a file-sharing service.

Does this error mean my email account is hacked?

No. This error is purely a connectivity issue between Outlook and the SMTP server. It does not indicate a security breach. However, if you also see unusual sent items or password changes, you should change your password immediately.

Will reinstalling Outlook fix this?

Rarely. Reinstalling Outlook usually does not change the settings that cause this error. It is more effective to check SMTP settings, firewall, and antivirus. Reinstalling should be a last resort after trying all other fixes.

Why does this error only happen on one computer?

Because the issue is often specific to that computer’s configuration—its firewall, antivirus, network, or Outlook profile. If other devices can send email, the problem is almost certainly local to that machine.

Can I use a different SMTP port to bypass the block?

Yes, but only if your email provider supports it. For example, some providers allow port 587 or 465. If your ISP blocks port 25, switching to 587 can help. Check your provider’s documentation for supported ports.

When to Contact Your Email Provider

If you have verified your SMTP settings, checked your firewall, increased the timeout, and tried a new profile, and the error persists, the problem may be on your email provider’s side. Contact their support team and provide the exact error code and the SMTP server address you are using. They can confirm if the server is down or if there is an authentication issue with your account. Also, check their status page for any ongoing outages.

In summary, error 0x80042109 is a solvable connectivity problem. Start with the quick checks, then move to SMTP settings, firewall, and timeout. Most users resolve it within a few minutes by correcting the SMTP port or enabling authentication.

Related

• Check If Computer Is Domain Joined (4 Ways)
• Fix 0x8007 System Restore Error: Find the Code First
• How to Record a Screencast in Windows 10