Configure WordPress to Send Email Using SMTP

Verify mail routing independently of the WordPress form

First confirm which system sends the message, which address receives it and whether the chosen sender is authorized. Then test an actual submission and inspect the provider's delivery status. A plugin's success notification may only mean the message was handed to a mail service. Keep credentials private, use the visitor's address for replies and document how failed deliveries will be detected.

Overview

Are you having trouble with emails on your WordPress site? There can be many reasons for errors that you can get while receiving and sending emails. Most of them can be solved with SMTP configuration. We will, therefore, show you the step-by-step guide to configure SMTP in your WordPress site.

What is the Problem with WordPress Emails?

By default, WordPress uses the PHP mail function to send emails. Despite so, this is not the best way to send emails. Consequently, WordPress emails get blocked or land in the spam folders. Most of the time shared hosting providers disable the email configuration to avoid any kind of abuse. Sometimes, they do not have this configured properly. Therefore, emails can be sent or received. Most WordPress hosting providers offer email services. It allows you to create your domain name email such as yourname@yourwebsitename.com. You can create your email account in cPanel. Login to your hosting account, then click on email account under the mail section in cPanel.

Click on +create and fill in all the information to create an email account.

Once, email is created, it is ready to use in WordPress. However, before you start using it, you will need the following information from your hosting provider. 1. SMTP Host for your email address. 2. SMTP Port for secure login. Most likely, you can find this information on their website. If you are unable to locate it, you can contact your hosting provider directly.

Using Your Branded Email Address in WordPress – Configure ‘WP Mail SMTP’ Plugin

WordPress offers various SMTP plugins that can be used to force any FROM address on the email. FROM is very important, here are some reasons. · It allows you to send emails directly through your mail server. · This helps you prevent issues with Spoofing and Sender Domain policy. · It allows you to send emails FROM another email host. WP Mail SMTP plugin is one of the most popular plugin options for this job. It is easy to configure and use. We will, therefore, guide you through the process of WP Mail SMTP. Before we get started, you need to install the plugin. Navigate to the Plugins > Add New. Search ‘WP Mail SMTP’ and click Install.

3. Navigate to the Plugins > Installed Plugins.

4. Under WP Mail SMTP, click the Activate link.

Now, you are at the Setup Wizard page to complete the configuration.

Configure the WP Mail SMTP

There are three different ways to configure WP Mai SMTP on you’re your website.• Use Setup Wizard• Configure on Settings Page• Add code Manually to your wp-config.php file

1. Once, your plugin has been installed and activated, click on WP Mail SMTP in your WordPress dashboard.

Configure With Setup Wizard

Setup Wizard is a quick way to configure this plugin.

3. Choose your SMTP Mailer for example Gmail. Then click Save and Continue.

4. The next page lists all of your mail settings. Set up a Gmail mailer and fill in all the details.View the following document for more information: Set up G Mailer

5. Once done, fill in Client ID, Client Secret, Authorized Redirected URI.6. Click on Connect to Google.7. log in to your Gmail account.8. Click on Allow for all permissions.9. Once the connection is established, you are all set.

Configure on the Settings Page

1. Navigate to the WP MAIL SMTP > Settings page.

• From Email – Enter the email you wish to send FROM• Force From Email – Check this box• From Name – Enter a name you’d like to appear as being sent FROM• Force From Name – Check this if you wish to force the FROM name• Return Path – Check this box

4. Under the Gmail section, put Client ID and Client Secret.Use the above article, and get these IDs from G Mailer.

5. Once done, click the Save Settings button.6. Click on Connect to Google.7. log in to your Gmail account.8. Click on Allow for all permissions.9. Once the connection is established, you are all set.

Add code Manually to your wp-config.php file

This is the more advanced way of configuring WP Mail SMTP. However, it is more secure. You need to manually edit the main configuration file. If you choose this method, you do not need anything in your WordPress. You simply make changes to wp-config.php file and it gets updated automatically.

1. Log into your server using FTP or SSH.2. Once you are logged in, edit wp-config.php file.3. Scroll down in this file to the following line: /* That’s all, stop editing! Happy blogging. */4. Add the following lines just above this line.

5. The only parts you need to change are WPMS_MAIL_FROM, WPMS_MAIL_FROM_NAME, WPMS_SMTP_USER and WPMS_SMTP_PASS.6. Save the file.7. You are all done.

Testing the Plugin

Scroll to the top and click the Email Test Tab. Click the Send Email button to test. You will see a sent message. You can check your inbox to confirm it.

Treat email delivery as a separate integration

A visible success message does not prove that an email reached an inbox. The website, mail provider and receiving server each have a role. Start by identifying the destination address and the supported sending method. Use an authenticated provider or properly configured server mail service, and keep secret credentials on the server rather than in downloadable JavaScript.

Use a sender address that the sending domain is authorized to use. The visitor's email normally belongs in the reply-to field, not as an impersonated sender. Coordinate the relevant domain authentication records with the mail provider and test delivery to the actual destination. Check junk folders and provider logs when a message does not arrive. A successful application response may mean only that the next service accepted the request.

Test required fields, invalid addresses, spam protection and provider failures. Visitors should retain their entered information if a submission fails, and the page should give an alternative contact method. If a hosted form service requires inbox verification, complete that step before treating the form as operational. Assign someone to monitor the inbox and delivery failures so that a working form continues producing timely business responses.

Reduce operational risk with recoverable changes

Security work should begin with the systems and information the business depends on. Keep an inventory of websites, domains, hosting accounts, integrations and the people who own them. Remove unnecessary access, use strong authentication where supported and keep essential software maintained. A tool labelled secure cannot compensate for abandoned administrator accounts or an undocumented dependency.

Backups need a recovery plan. Decide what is included, where copies are stored and how often the data changes. Test restoration into an isolated environment and confirm that the recovered site includes both files and database content. Record the steps and the people who can carry them out. A backup job that reports success is useful evidence, but a successful restore is stronger evidence of recoverability.

For changes, keep a rollback path and avoid altering unrelated settings during an incident. Record the symptoms, recent deployments and relevant logs before attempting a repair. Restrict access to secrets and personal data during investigation. After service is restored, identify the cause and improve the process that allowed it. Clear ownership and tested recovery often matter more to a small business than an impressive list of tools with nobody assigned to operate them.