SMTP Error 101: Cannot Open Connection to Mail Server – Causes and Fixes

TL;DR: SMTP Error 101 means your email client could not open a connection to the mail server, so the message never reached the point of being sent. It is almost always caused by an incorrect SMTP server address, port, or encryption setting, a blocked port, or an outdated password, since Gmail and Yahoo no longer accept regular account passwords for SMTP. Checking your exact server, port, and authentication method against the settings below resolves most cases within minutes.

SMTP Error 101 means your email client failed to open a connection to the mail server before it could even begin the SMTP conversation, so the message never actually sent. It shows up as a client side or library level failure rather than a formal three digit SMTP reply code, which is why Outlook, Gmail plugins, and server logs each describe it slightly differently. This guide walks through what causes the error and the exact settings to check for Gmail, Outlook, and Yahoo.

What is SMTP Error 101?

SMTP Error 101 occurs when your email client fails to connect to the email server, failing to send the email.

Because Error 101 happens at the network and transport layer, before your server has a chance to reply, it is not part of the official SMTP reply code system defined in RFC 5321, which is also why the exact wording differs across email clients. For a full breakdown of the three digit codes that do come from the SMTP protocol itself, see Warmy’s guide to SMTP error codes and messages.

The error is usually communicated through an error message that says “Connection to server has failed” or “SMTP Server Error: 101.” The alarm may also include other messages like “Network is unreachable” or “Cannot connect to SMTP server.”

The error may manifest in different ways due to the client’s behavior or network connectivity state. In a given network environment, the email send failure may be periodic, with emails sending at times and not sending when the error alarms.

Alternatively, you might be unable to send the email at all during the downtime.

What are the reasons behind SMTP Error 101?

• Network connectivity issues: The most common reason of SMTP Error 101 is an issue with the network connection. This might be the result of an unreliable internet connection, network congestion, or temporary disruptions in the network infrastructure.
• Incorrect SMTP server settings​: If the SMTP server settings are incorrect – for example, the wrong server address, port number, or security protocol – connection attempts may fail, resulting in Error 101.
• Firewall or security software interference: Firewalls or security applications on your machine or network may unintentionally prevent connectivity with the SMTP server. Adjusting the settings of these security programs may remedy the problem.
• ISP restrictions: Some Internet Service Providers (ISPs) may prohibit connections to specific SMTP servers, especially if they detect spam or other dangerous email activity. 
• Server downtime or overload: If the SMTP server is offline, undergoing maintenance, or just overwhelmed with requests, it may be unable to receive incoming connections, resulting in Error 101. If your logs show a 450 response instead of 101, that is a related but distinct issue; see Warmy’s guide to SMTP Error 450 for that specific fix.
• Outdated email client: An obsolete email client may be incompatible with modern SMTP protocols or security requirements, resulting in connection failures.

Step-by-step fixes for SMTP Error 101

For Gmail

1. Check internet connection. Ensure your internet connection is stable and strong.
2. Verify SMTP settings. Ensure the following SMTP settings are correct:
   • SMTP server: smtp.gmail.com
   • Port: 587 (with TLS) or 465 (with SSL)
   • Require SSL: Yes
   • Require authentication: Yes
   • Username: Your full Gmail address
   • Password: a 16 character Gmail App Password, not your regular account password
3. Use an App Password or OAuth. Google shut down password only sign in for SMTP in 2025, so you now need to turn on 2-Step Verification and generate an App Password from your Google Account, or connect through OAuth 2.0 if your email client supports it. See Google’s official transition guide for the exact steps.

For Outlook

1. Check network: Like with Gmail, ensure your network connection is stable.
2. SMTP settings. Confirm the following settings:
   • SMTP server: smtp-mail.outlook.com
   • Port: 587
   • Encryption method: STARTTLS
   • Authentication: Yes (your Outlook email and password)
3. Update Outlook. Ensure your Outlook application is updated to the latest version.
4. Confirm modern authentication. Many Microsoft 365 organizational accounts now require an app password or OAuth based modern authentication instead of your regular password, so check with your admin if the credentials above still fail.

Pro Tip: If you are still getting an authentication failure after switching to an App Password, you are probably not looking at Error 101 anymore. That specific rejection is SMTP Error 534, and it has its own fix.

For Yahoo

1. Internet connectivity. Verify that your internet connection is working without interruptions.
2. SMTP configuration:
   • SMTP server: smtp.mail.yahoo.com
   • Port: 465 (SSL) or 587 (TLS)
   • Require SSL/TLS: Yes
   • Authentication required: Yes, using an App Password if two step verification is turned on, which is the default for new Yahoo accounts
3. Check account security. Make sure you have not enabled any security features that block third-party email clients.

General troubleshooting steps for other email services

1. Restart your email client. Sometimes, simply restarting your email client can resolve transient issues.
2. Disable firewall/antivirus. Temporarily disable any firewall or antivirus software that might be blocking your outgoing emails.
3. Check for server downtime. Visit the email service’s official website or third-party status checkers to see if there are any announcements about server maintenance or downtime.
4. Contact ISP. If none of the above steps work, contact your ISP to see if they are blocking SMTP ports 465 or 587.

If the message you are seeing references a different three digit code entirely, the fix is not the same as for a plain connection failure. Warmy’s guides to SMTP Error 442, SMTP Error 530, and SMTP Error 500 walk through those specific causes and solutions.

Technical adjustments

• Command line testing. Advanced users can use command-line tools like telnet or openssl s_client to connect to the SMTP server. This can help verify if the SMTP port is open and accessible from your network.
• Update network drivers. Ensure that your network adapters have the latest drivers installed.

Pro Tip: Match your port to its encryption mode exactly: STARTTLS on port 587, or implicit SSL/TLS on port 465. Mixing them, such as forcing SSL on 587, produces a connection failure that looks identical to Error 101 but has nothing to do with your network.

Pro Tip: Error 101 is a connectivity problem, not a reputation problem, so warmup and sender score will not fix it. Once your connection is restored, run a quick deliverability check to confirm the rest of your setup, SPF, DKIM, and DMARC included, is actually sending clean.

Check your email template with Warmy’s free Email Template Checker once your connection is working again, so a formatting or spam-trigger issue does not undo the fix.

Avoid SMTP Error 101 and optimize email performance with Warmy.io

Warmy.io provides a set of tools and services aimed at improving email deliverability and reducing typical SMTP issues like Error 101. Warmy.io basically provides a complete approach to improve the reliability and efficiency of your email deliverability.

• Free email deliverability test. Warmy’s test helps determine if your emails are likely to reach the inbox or get filtered out by spam filters, providing insights into potential issues that could be causing SMTP errors.
• Blacklist monitoring. Being listed on an email blacklist can severely affect your email deliverability. Warmy.io monitors various blacklists to check if your domain or IP address has been blacklisted and offers solutions to help you get delisted.
• Free SPF and DMARC Record Generators. Warmy.io provides tools to generate Sender Policy Framework (SPF) and Domain-based Message Authentication, Reporting, and Conformance (DMARC) records. These records are crucial for authenticating your outgoing emails and ensuring they are not rejected by recipient servers.

Ultimately, it is essential to minimize the incidences of SMTP errors in order to maintain the integrity and reliability of email communication.

Errors such as Error 101 disrupt the flow, delay critical messages for minutes, if not hours, and cause loss of opportunity.

Email deliverability tools like Warmy.io greatly contribute to improved sender operations. They not only help businesses determine the nature of the SMTP error but also take preventative action to reduce the likelihood of errors from occurring at all. 

Try Warmy for free for seven days!