SMTP2GO for WordPress – Email Made Easy

By SMTP2GO

★ 5.0/5 (67 ratings)40,000+ active installationsVersion 1.18.0

Resolve email delivery issues, increase inbox placement, track sent email, get 24/7 support, and real-time reporting.

Description

SMTP2GO’s WordPress plugin replaces the default built in wp_mail() functionality (phpmailer) and sends your email via SMTP2GO’s API and industry leading email delivery platform.

SMTP2GO provides valuable insights into every aspect of your email’s life cycle, enabling you to track delivery rates, opens, clicks, and bounce rates. Whether your email is transactional, marketing, newsletter, contact form, or notification – we have got you covered.

The main benefits of using the official SMTP2GO plugin:

  • We have made our plugin as easy and low maintenance as possible – you can set it up in under ten minutes.
  • Take over from the default WordPress email system for more reliable delivery – you can be confident your emails have arrived at their destination inbox successfully.
  • Get access to our intuitive real-time reporting tools. You can uncover what is going on behind the scenes with delivery, open rates, click rates, bounce, and unsubscription reports.
  • We offer secure worldwide servers with intelligent routing for network redundancy and speedy delivery.
  • We handle SPF and DKIM on your behalf. SMTP2GO can even turn your “http” links into “https”.
  • Diagnose and resolve delivery issues with our insightful reporting page, or reach out to our award-winning support team who are available almost 24/7 to help address problems in a timely, friendly fashion.
  • We have a dedicated Review team who constantly monitor the reputations of our IP’s and we proactively alert members to any suspicious changes in their email regimen.
  • Avoid poor reputation and throttling or limitations from over-used shared web hosts and other providers.

Sign up here.

Support

If you have questions or need assistance then feel free to contact the support team by logging into your SMTP2GO dashboard and clicking the support icon on the top right navigation bar.

More information on this plugin is available in our knowledgebase.

About SMTP2GO

Founded in 2006, SMTP2GO is a fast and scalable world class email service provider for sending transactional and marketing emails. It is developed and supported by a team of delivery experts at the forefront of the email industry, providing a reliable SMTP solution for over 35,000 businesses.

Complexities such as reputation monitoring, SPF and DKIM are professionally managed for each customer. Native-English speaking support is available worldwide (agents in the USA, EU, UK, Australia, and New Zealand).

Our data centers are located around the world, meaning lightning-fast connection speeds, network redundancy, and GDPR compliance.

Installation

If you are not an existing customer, you will need an SMTP2GO account – a free plan is available!

Standard:

  1. Click the “Plugins” tab in your WordPress administration (wp-admin) dashboard, and choose “Add New”.
  2. Search for “Email Made Easy” or “SMTP2GO”.
  3. Click the “Install Now” button.
  4. Once the plug in is installed, click “Activate”.

Configuration:

You will need to enable the plugin and enter the required details under the “Settings” tab.

  1. Tick the checkbox labelled “Enable Email Made Easy by SMTPGO”.
  2. Enter your API Key which can be found in your SMTP2GO dashboard: “Sending > API Keys”.

    Note:
    The API Key needs at least the following permissions:

  • Emails (/email/send)
  • Statistics (optional)
  1. Set the default From Email Address.
  2. Set the default From Name.
  3. Save the settings by clicking the “Save Settings” button at the bottom.

    Note:
    The default From Email Address and From Name will only be used if your other plugins don’t specify a sending email address.

You can add custom headers to your emails, such as headers for custom tracking with third-party tools such as “X-Campaign”.

The “Test” tab can be used to send a test email to ensure your settings have been entered correctly.

And that’s it! If any problem occurs, please contact us via the “Support” tab within the SMTP2GO app.

Advanced Setup:

  1. Copy the SMTP2GO directory into your wp-content/plugins directory.
  2. Activate the plugin through the wp-admin “Plugins” page.
  3. Once successfully activated, the SMTP2GO plugin will appear in the “Settings” menu in the WordPress Admin Panel.
  4. Click on “Settings > SMTP2GO” to open the plugin configuration page.
  5. Retrieve a copy of your API key by going to the “Sending > API Keys” section of your SMTP2GO dashboard.
  6. Enable the checkbox “Enable Email Made Easy by SMTPGO”.
  7. Add a default sending name and email address.

Note: The default From Email Address and From Name is only used if these are not specified by any other WordPress function or plugin that is trying to send an email.

API Key Management:

There are three ways to give the plugin your API key. From most to least secure:

  1. An environment variable, read in wp-config.php
  2. A constant in wp-config.php
  3. The plugin settings page (the key is encrypted and stored in the database)

Using an environment variable (most secure):

If your host lets you set server environment variables (for example in your hosting control panel, your web server or PHP-FPM config, or a Docker or container setting), store the key in a variable called SMTP2GO_API_KEY and read it with PHP’s getenv() function. Add these lines to wp-config.php, above the line that says “That’s all, stop editing!”:

define('SMTP2GO_USE_CONSTANTS', true);
define('SMTP2GO_API_KEY', getenv('SMTP2GO_API_KEY'));

The key is never written to wp-config.php or the database, so it can’t leak from a copied file or a database backup, and you can change it without editing any site files.

If the environment variable isn’t set, or PHP can’t see it, the plugin shows a notice saying the SMTP2GO_API_KEY constant is empty and emails won’t be sent until it’s fixed. Some PHP-FPM setups hide environment variables from PHP by default (clear_env = yes). If so, ask your host to pass the variable through to PHP.

Using a constant in wp-config.php:

You can also put the key in wp-config.php directly:

define('SMTP2GO_USE_CONSTANTS', true);
define('SMTP2GO_API_KEY', 'api-XXXXXXXXXXXXXXXXXXXXXXXX');

SMTP2GO_USE_CONSTANTS must be set to true, or the plugin ignores SMTP2GO_API_KEY and uses the key saved in the settings. While the constant is in use, the settings page shows “The API key is defined as a constant in your wp-config.php file” instead of the API key field. If a key was saved in the settings earlier, a “Delete API Key from Database” link lets you remove it. Because the key sits in plain text in wp-config.php, keep that file out of version control and backups that others can access.

Saving the key in the plugin settings:

When you save your API key in the plugin settings, it is encrypted before being stored in the database (this requires the OpenSSL PHP extension, which most hosts provide).

By default the key is encrypted using your site’s WordPress AUTH_KEY salt. If those salts ever change (for example, some security plugins and hosts rotate them automatically), the stored API key can no longer be decrypted and you will be asked to re-enter it.

To avoid this, you can define your own encryption key in wp-config.php:

define('SMTP2GO_ENCRYPTION_KEY', 'your-long-random-string');

Use a long, random value. You can generate one with openssl rand -base64 32. Keep it safe and don’t change it once it’s set.

When SMTP2GO_ENCRYPTION_KEY is added, an API key that has already been saved will be re-encrypted with it the next time it’s decrypted, so you don’t need to re-enter your key. If you later remove or change this constant, the plugin will not be able to decrypt the stored key and will show a notice asking you to enter it again.

If you store your API key in wp-config.php instead (using SMTP2GO_USE_CONSTANTS and SMTP2GO_API_KEY), it is never saved to the database, so this encryption setting doesn’t apply.

Fast Accept:

The “Use Fast Accept” setting makes sending quicker. When it is enabled, SMTP2GO accepts each email immediately and processes it in the background, instead of waiting until processing is finished before responding to your site. This can noticeably speed up pages and forms that send email, such as contact forms and checkout pages.

Because the response comes back before the email has been fully processed, a successful send in WordPress only means SMTP2GO has accepted the email, not that it has been delivered. Use your SMTP2GO reports or webhooks if you need to track final delivery.

FAQ

Do I need an SMTP2GO account?

Yes, the SMTP2GO WordPress plugin uses SMTP2GO’s API to deliver emails and get statistics. Creating an account on SMTP2GO quick and simple – sign up here.

Once logged into your account and you have completed the required setup steps, you can get an API Key (Sending > API Keys) which you’ll need to get the plugin up and running.

How much will it cost me?

SMTP2GO offers a free plan that includes 1,000 emails per month. You can use this for your WordPress site but also any other email and SMTP needs you have! One account can cover all your inbox delivery and SMTP needs.

For more email volume per month and fewer restrictions, you can easily upgrade to one of the many available plans to suit your sending needs. Paid plans start at $10 USD/month – check out our pricing here.

Can you tell me about the compatibility of this plugin?

Sure can! We replace the default wp_mail so most other plugins that need to send email will be compatible.

We are always looking to improve, so if you do find any compatibility issues, please let us know.

Email Made Easy has been tested for Linux and other Unix type operating systems. We do not recommend using the plugin on Windows/IIS based systems as we do not currently support these platforms.

We also recommend keeping your WordPress up to date and only use the the most recent version of WordPress, or no more than one major release behind.

Can I get support?

Absolutely! The SMTP2GO support team has agents located in the US, EU, UK, and the Pacific to cover all time zones providing assistance when you need it most. If you have questions or need help then feel free to contact the support team by logging into your SMTP2GO dashboard and clicking on the support icon on the top-right. We can be reached by instant message, ticket, or phone.

How do I avoid emails going to the spam or junk folder?

  1. Check that your domain names are fully verified in the “Sending > Verified Sender” section of your SMTP2GO account.

  2. Make sure your domain has a great reputation and isn’t listed on any blacklists. A good place to start checking is MXToolbox.

  3. Think about your email content and subject line to avoid words and phrases that could trigger a spam filter.

If you’re needing extra help, our support team has lots of tips and tricks to help you out. You can find the support tab in your SMTP2GO dashboard.

Why am I being asked to re-enter my API key?

Your stored API key is encrypted using your site’s WordPress salts. If those salts are changed, the key can no longer be decrypted. Re-enter your API key to fix this. To stop it happening again, define a dedicated SMTP2GO_ENCRYPTION_KEY constant in wp-config.php. See “API Key Management” in the Installation section.

Should I enable Fast Accept?

If sending email makes your site feel slow, Fast Accept can help, because SMTP2GO responds as soon as it accepts the email rather than after processing it. The trade-off is that WordPress won’t know about problems that happen after the email is accepted, so check your SMTP2GO reports or set up webhooks to monitor delivery.

Changelog

v1.18.0

  • add optional SMTP2GO_ENCRYPTION_KEY constant to encrypt the stored API key independently of WordPress salts
  • automatically re-encrypt a saved API key with SMTP2GO_ENCRYPTION_KEY when it is added
  • add admin notices when the API key can’t be decrypted, is empty or invalid, is rejected by SMTP2GO, or is missing the /email/send permission
  • add optional fast accept setting for faster API responses
  • fix fatal error when the SMTP2GO_API_KEY constant is empty (e.g. an unset environment variable)
  • report failed sends through the wp_mail_failed action
  • prevent CSV formula injection in log downloads
  • fix usage bar display and failed-response handling
  • fix sender name field pattern validation in Chromium
  • only check for conflicting plugins in the admin
  • update smtp2go-php to 1.3.2

v1.17.1

  • test against version 7.1

v1.17.0

  • test against version 7.0
  • add region selector
  • fix sender name field pattern attribute regex compatibility with Chromium
  • add extra current_user_can checks on admin actions

v1.16.0

  • add “API Region” setting to pin requests to a specific regional endpoint (US, EU, AU)
  • add smtp2go_api_region filter for programmatic per-environment overrides
  • add SMTP2GO_API_REGION constant support (when SMTP2GO_USE_CONSTANTS is true)

v1.15.0

  • security updates

v1.14.1

  • use WordPress’s replacement PHPMailer verify email address function

v1.14.0

  • check WordPress 6.9 compatibility

v1.13.1

  • remove unnecessary API key permission check

v1.13.0

  • better handling of API key permissions
  • make stats permission optional
  • update smtp2go composer package to better handle rate limiter and api authentication

v1.12.2

  • lock down admin URL’s

v1.12.1

  • lock down admin URL’s

v1.12.0

  • add API request logging option
  • add API key into wp-config.php option
  • improve reply-to header formatting logic
  • many automated test updates
  • refactor class loader error handling and improve namespace check
  • add setting to force sender email address in plugin configuration

v1.11.1

  • update readme

v1.11.0

  • test with new WordPress version
  • add more API error handling

v1.10.1

  • update readme

v1.10.0

  • encrypt API key in database
  • check WordPress 6.6 compatibility

v1.9.0

  • add upsell modal if user is on free plan
  • validate API key when entered
  • e2e Github action tests
  • iterate Guzzle version in composer package

v1.8.2

  • check WordPress 6.5 compatibility

v1.8.1

  • fix get_plugins getting called when not available

v1.8.0

  • add checking and warning for conflicting plugins

v1.7.1

  • admin and readme text correction

v1.7.0

  • bring back PHP 7.4 compatability

v1.6.1

  • require PHP 8.1

v1.6.0

  • use new smtp2go composer package with retry feature

v1.5.6

  • readme updated
  • test on WordPress 6.3
  • rename smtp2go dir to app for FlyWheel compatability

v1.5.4

  • drop testing / supporting PHP 7.2

v1.5.3

  • ensure phpmailer is set to use the ‘mail’ mailer

v1.5.2

  • tested on WordPress 6.2

v1.5.1

  • missed moving the tested up to version number with Readme update

v1.5.0

  • remove sender domains fn
  • upgrade smtp2go-oss/smtp2go-php to 1.1.2