{"id":4300,"date":"2022-05-11T11:53:01","date_gmt":"2022-05-11T08:53:01","guid":{"rendered":"https:\/\/www.scalahosting.com\/kb\/?p=4300"},"modified":"2022-05-11T11:59:27","modified_gmt":"2022-05-11T08:59:27","slug":"fixing-smtp-host-connectivity-issues-in-wordpress","status":"publish","type":"post","link":"https:\/\/www.scalahosting.com\/kb\/fixing-smtp-host-connectivity-issues-in-wordpress\/","title":{"rendered":"Fixing SMTP Host Connectivity Issues in WordPress"},"content":{"rendered":"\n

Reliable email communication<\/b> is an important part of any online project. You use it for marketing purposes like <\/span>newsletters and promotions<\/b>, but you also rely on it for essential things like registration notifications and password reset links. If you have a contact form on your website, you also receive feedback from your customers via email, so it’s crucial to make sure messages are delivered on time, all the time.<\/span><\/p>\n\n\n\n

Unfortunately, out of the box, WordPress can’t guarantee this. By default, it sends emails via the web server, which, compared to the alternative, is not particularly reliable or secure.<\/span><\/p>\n\n\n\n

Fortunately, you have a couple of means of configuring WordPress to work with your hosting <\/span>account’s SMTP service<\/b>. Even then, however, configuration errors could lead to connectivity issues. Today, we’ll show you how to fix them.<\/span><\/b><\/p>\n\n\n\n

WordPress and SMTP<\/b><\/b><\/h2>\n\n\n\n

WordPress users have been facing email deliverability issues for a while now. The CMS is used on <\/span>a vast range of hosting platforms<\/b>, and its developers can’t assume that the configuration will be the same everywhere. For example, they can’t be sure whether every hosting account comes with an <\/span>SMTP mail server<\/b><\/a>.<\/span><\/p>\n\n\n\n

SMTP<\/b> stands for <\/span>S<\/i><\/b>imple <\/span><\/i>M<\/i><\/b>ail <\/span><\/i>T<\/i><\/b>ransfer <\/span><\/i>P<\/i><\/b>rotocol<\/span><\/i> \u2013 the <\/span>communication protocol<\/b> we’ve been using for sending email for decades. Although it’s a pretty standard feature on most hosting accounts, it’s not necessarily available everywhere. And even if it was, there would inevitably be some differences in the configuration settings.<\/span><\/p>\n\n\n\n

Because of this, by default, WordPress uses a <\/span>PHP function<\/b> called <\/span>PHP mail()<\/b>. In theory, it does the same job as SMTP in that it allows email messages to be sent to a specific recipient. However, it <\/span>doesn’t require authentication<\/b>, and it can’t attach your domain’s <\/span>SPF and DKIM records<\/b><\/a> to the email<\/b>. As a result, the communication is less secure, and your messages are more likely to end up in the recipient’s spam folder.<\/span><\/p>\n\n\n\n

Because of all these issues, the <\/span>PHP mail() function<\/span><\/i> isn’t particularly popular with developers, and some hosting providers even <\/span>disable it deliberately <\/b>to prevent security incidents on their shared servers. Thankfully, if your hosting account comes with an <\/span>active SMTP server<\/b>, you can configure WordPress to work with it.<\/span><\/p>\n\n\n\n

You can either use a plugin or edit <\/span>WP’s configuration files<\/b> to set up a more reliable email communication channel between your site and its visitors. More information about how to do that is available right here.<\/span><\/p>\n\n\n\n

Unfortunately, it’s not uncommon for WordPress to encounter issues with the SMTP protocol. The error often reads something like “<\/span>Could not connect to SMTP host<\/span><\/i>,” and it always results in unsent emails.<\/span><\/p>\n\n\n\n

Let’s take a closer look at the problem and see what might be causing it.<\/span><\/b><\/p>\n\n\n\n

When Do You See SMTP Errors in WordPress?<\/b><\/b><\/h2>\n\n\n\n

Where you see the alerts depends on your individual setup. For example, it could be displayed by your contact form plugin either in the <\/span>WordPress dashboard<\/b><\/a> or on the site’s front end. If you’re using an <\/span>add-on to enable SMTP<\/b>, errors may be recorded in its back-end interface and logs.<\/span><\/p>\n\n\n\n

Issues are a bit more difficult to diagnose if you’ve <\/span>enabled SMTP manually<\/b>, though you can still scan the logs to try and figure out what has gone wrong. Whether or not you’re using a plugin, after you enable the <\/span>SMTP connection<\/b>, it’s a good idea to <\/span>test the functionality thoroughly<\/b> before sending emails to your customers.<\/span><\/p>\n\n\n\n

In most cases, issues arise when WordPress tries to connect to the SMTP server. The CMS needs to know <\/span>the SMTP server’s address, the networking port, and the login credentials<\/b> for the email account that acts as a sender. If all this information is available, WP uses it to connect to the SMTP server, go through the authentication process, and send the message.<\/span><\/p>\n\n\n\n

On the face of it, it’s a relatively simple process. However, quite a few things could go wrong, meaning troubleshooting may be more tricky than you think.<\/span><\/b><\/p>\n\n\n\n

Troubleshooting SMTP Errors in WordPress<\/b><\/b><\/h2>\n\n\n\n

Quite a few things happen when WordPress or a plugin sends an email, so it pays to check them all whenever you encounter any issues. Let’s start with the obvious.<\/span><\/p>\n\n\n\n

Check whether the SMTP server is working<\/b><\/h3>\n\n\n\n

You first need to determine whether you’re <\/span>experiencing a global issue or something WordPress-related<\/b>. Many people will try to send a test email to see if everything’s working. However, if you’re on a managed hosting account, you most likely have an even easier option.<\/span><\/p>\n\n\n\n

SPanel users<\/b><\/a>, for example, can check whether the mail server is running correctly via the Admin Interface. They need to go to <\/span>Server Status<\/b> and look for the green tick next to the <\/span>Exim Email Server<\/b> service.<\/span><\/p>\n\n\n\n

\"Fixing<\/figure><\/div>\n\n\n\n

Make sure your domain is correctly pointed<\/b><\/h3>\n\n\n\n

Thanks to <\/span>your operating system’s hosts file<\/span><\/a>, you can build your WordPress website without pointing the domain to it. However, if you want to send emails, the domain must be resolving to <\/span>the correct nameservers<\/b>.<\/span><\/p>\n\n\n\n

If you register the domain while creating your ScalaHosting account, it will be pointed to the correct server automatically. If that’s not the case, you can find information on the required DNS settings inside your <\/span>Welcome Email<\/b>. After you change the <\/span>domain’s nameservers<\/b><\/a>, you need to leave <\/span>up to 48 hours<\/b> (it usually takes a lot less) for the changes to propagate globally.<\/span><\/p>\n\n\n\n

Check if you’re using the correct email address<\/b><\/h3>\n\n\n\n

While <\/span>configuring WordPress to work with SMTP<\/b>, you’ll specify the address it’ll work with. Of course, it must be an existing address. There’s almost certainly a tool for managing email accounts inside your <\/span>web hosting control panel<\/b>. If you use <\/span>ScalaHosting’s SPanel<\/b><\/a>, you’ll find it on the User Interface’s homepage.<\/span><\/p>\n\n\n\n

\"Fixing<\/figure><\/div>\n\n\n\n

After you open it and scroll down, you’ll see a list of all currently existing email accounts.<\/span><\/p>\n\n\n\n

\"Fixing<\/figure><\/div>\n\n\n\n

If the account you want to use as a sender doesn’t exist, you can use the form above the list to create it.<\/span><\/p>\n\n\n\n

Check your email quotas<\/b><\/h3>\n\n\n\n

Every email account has <\/span>allocated storage space<\/b> that can not be exceeded. If you reach the account’s limit, problems with sending and receiving emails will appear immediately, and they could very well affect your <\/span>WordPress website communication<\/b>.<\/span><\/p>\n\n\n\n

Usually, you can check and manage your email quotas via your web hosting control panel. SPanel users, for example, can <\/span>log in to the User Interface <\/b>and open the <\/span>Email Accounts<\/b> tool that contains a list of all active email accounts.<\/span><\/p>\n\n\n\n

Next to each address, you can see how much storage it’s using, and the <\/span>Change quota<\/b> option from the <\/span>Actions <\/b>drop-down lets you modify the allocated space.<\/span><\/p>\n\n\n\n

\"Fixing<\/figure><\/div>\n\n\n\n

Clean up your messages<\/b><\/h3>\n\n\n\n

You may also experience email deliverability issues if <\/span>anti-spam tools flag your messages<\/b>. False positives are not unheard of when it comes to spam filters, and even if your customers have agreed to receive emails from you, you still have to stick to a few <\/span>specific rules when composing your messages<\/b>. Do your due diligence and make sure you follow the guidelines to the letter.<\/span><\/p>\n\n\n\n

Make sure you’re using the correct SMTP settings<\/b><\/h3>\n\n\n\n

When <\/span>setting up an email client,<\/b> you’re often asked for the incoming and outgoing server settings. Usually, we’re talking about the server name, port, and login credentials. Get any of these details wrong, and the email client won’t work. Things are not too dissimilar when it comes to WordPress.<\/span><\/p>\n\n\n\n

You need to provide the <\/span>SMTP server name <\/b>and the port, pick between<\/span> SSL<\/b><\/a> and TLS encryption<\/b>, and ensure authentication is enabled. To find the server name and port, you can look into your welcome email. If you’re a ScalaHosting customer, you’ll find them in the <\/span>My Details <\/b>> <\/span>Email History <\/b>menu inside your Client Area.<\/span><\/p>\n\n\n\n

\"Fixing<\/figure><\/div>\n\n\n\n

You can also retrieve the SMTP server and port from the list of email accounts on SPanel’s User Interface. Click the <\/span>Actions<\/b> drop-down next to one of the accounts and select <\/span>Connect devices<\/b>.<\/span><\/p>\n\n\n\n

\"Fixing<\/figure><\/div>\n\n\n\n

The information you need is available in the <\/span>Outgoing Server <\/b>section.<\/span><\/p>\n\n\n\n

Make sure you know which email provider you’re using<\/b><\/h3>\n\n\n\n

Most web hosts let you use <\/span>a third-party provider like Gmail<\/b> for your email services. Different email providers have <\/span>different SMTP settings<\/b>, so if you’ve recently moved your emails to a third-party service, you need to <\/span>update WP’s configuration<\/b>, or you risk experiencing deliverability issues.<\/span><\/p>\n\n\n\n

As an SPanel user, you can easily determine whether you’re using a third-party provider for email communication. Simply log in to the User Interface and open the <\/span>Mail Route<\/b> tool. If the <\/span>Local mail exchanger<\/b> radio button is selected, you’re <\/span>using your own VPS for handling email communication<\/b>. If the other option is selected, you’ve switched to a third-party provider, and you need to get the correct SMTP settings from it.<\/span><\/p>\n\n\n\n

\"Fixing<\/figure><\/div>\n","protected":false},"excerpt":{"rendered":"

Reliable email communication is an important part of any online project. You use it for marketing purposes like newsletters and promotions, but you also rely on it for essential things like registration notifications and password reset links. If you have a contact form on your website, you also receive feedback from your customers via email, […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_seopress_robots_primary_cat":"","_seopress_titles_title":"","_seopress_titles_desc":"","_seopress_robots_index":"","_seopress_analysis_target_kw":"","footnotes":""},"categories":[34],"tags":[],"class_list":["post-4300","post","type-post","status-publish","format-standard","hentry","category-web-hosting"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/posts\/4300","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/comments?post=4300"}],"version-history":[{"count":2,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/posts\/4300\/revisions"}],"predecessor-version":[{"id":4312,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/posts\/4300\/revisions\/4312"}],"wp:attachment":[{"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/media?parent=4300"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/categories?post=4300"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/tags?post=4300"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}