DeliveryKit SMTP Mailers – CodeMaster Hub https://codemasterhub.com The Hub for Web Builders and Tools Mon, 04 May 2026 10:26:06 +0000 en-US hourly 1 https://wordpress.org/?v=6.9.4 https://codemasterhub.com/wp-content/uploads/2025/12/cropped-codemaster-hub-icon-512-web-32x32.jpg DeliveryKit SMTP Mailers – CodeMaster Hub https://codemasterhub.com 32 32 Other SMTP Setup in DeliveryKit SMTP https://codemasterhub.com/doc/deliverykit-smtp-documentation/other-smtp-setup-in-deliverykit-smtp/ https://codemasterhub.com/doc/deliverykit-smtp-documentation/other-smtp-setup-in-deliverykit-smtp/#respond Fri, 03 Apr 2026 15:05:36 +0000 https://codemasterhub.com/?post_type=doc&p=1752
Learn how to set up Other SMTP in DeliveryKit SMTP using custom SMTP settings from your hosting provider or email service, including SMTP host, port, encryption, username, and password.

Table of Contents

What Is Other SMTP in DeliveryKit SMTP?

Other SMTP in DeliveryKit SMTP lets you connect your WordPress website to any mail service that provides standard SMTP credentials. Instead of using a built-in mailer integration, you can enter the SMTP details manually and send your website emails through your own mail server or email provider. This option is useful when your hosting provider, cPanel email account, business email service, or private mail server gives you SMTP settings such as SMTP host, port, encryption type, username, and password. In simple terms, Other SMTP is the flexible option for custom email services that are not listed as a dedicated mailer inside DeliveryKit SMTP. In this guide, we will use a cPanel email account as an example, but the same setup steps also apply to many other hosting providers and email services that support SMTP. Before you start, make sure you have your SMTP host, SMTP port, encryption type, username, and password ready. You will enter these details later in the DeliveryKit SMTP connection settings.

Set Up Custom SMTP Settings Using cPanel Email

In this example, we will use a cPanel email account to set up Other SMTP in DeliveryKit SMTP. cPanel is a common hosting control panel, and it provides the SMTP details you need, such as the mail server, port, encryption type, username, and password. If you do not use cPanel, you can still follow the same general steps using the SMTP settings provided by your email hosting company or mail service.

Check Your Email Deliverability Status

In cPanel, go to the Email section and click Email Deliverability.

Make sure the domain you want to use shows Valid in the Email Deliverability Status column before continuing.

If you see a warning such as Problems Exist (DMARC, DKIM, and SPF), click Manage to review and fix the missing or invalid email records before continuing.

If cPanel shows any email deliverability problems, review the listed issues and apply the recommended fixes. If you are not sure how to fix them, contact your hosting provider and ask them to correct the email deliverability records for your domain.

Set Up Mail Client in cPanel

After confirming your email deliverability status is valid, go back to your email account settings in cPanel and open the Mail Client setup page for the email address you want to use. This page shows the SMTP details you will need for the Custom SMTP settings in DeliveryKit SMTP.

In cPanel, go to the Email section and click Email Accounts.

Find the email account you want to use for SMTP, then click Connect Devices.

On the Mail Client setup page, look for the Mail Client Manual Settings section. In most cases, use the Secure SSL/TLS Settings values and keep the SMTP details ready for the next step.

Set Up Other SMTP in DeliveryKit SMTP

In your WordPress dashboard, go to DeliveryKit SMTP > Connections, then click Create New Connection.

Configure Connection

In the Configure Connection section, fill out the Connection Details fields:

Connection Details: Enter a name for this connection. This is only for you, recipients will not see it.

Default From Email: The email address used when an outgoing email does not define a From Email.

Force From Email: If enabled, this From Email will be used for all emails, even if the email has a different From Email.

Default From Name: The name used when an outgoing email does not define a From Name.

Force From Name: If enabled, this From Name will be used for all emails, even if the email has a different From Name.

Default Reply-To Email: The Reply-To address used when an outgoing email does not define a Reply-To Email.

Force Reply-To Email: If enabled, this Reply-To Email will be used for all emails, even if the email has a different Reply-To Email.

In the Choose a Mailer section, select Other SMTP from the grid mailer list.

Configuration

In the Custom SMTP Settings section, start with the Configuration fields.

Enter your SMTP Hostname exactly as shown in your email account setup. In this example, it is mail.yourdomain.com.

Then enter the SMTP Port. For cPanel email accounts using secure SSL/TLS settings, this is commonly 465.

General Settings

Next, configure the General Settings options.

Return Path: Enable this if you want non-delivery notifications to be sent back to the sender address. You can leave it disabled unless you specifically want bounce notices handled this way.

Auto TLS: Keep this enabled if your mail server supports TLS. This is recommended in most cases.

Encryption: Select the encryption method that matches your email provider settings. For most modern SMTP servers, TLS is recommended. If your cPanel mail settings specifically use SSL on port 465, choose SSL instead.

Authentication

In the Authentication section, enable authentication if your SMTP server requires a username and password. This is the standard setup for most cPanel email accounts.

For Authentication Username, enter the full email address of the mailbox you want to use.

For Authentication Password, enter the password for that email account.

Save Connection

If you want this to be your main sending connection, enable Make this the default connection. Then click Save Connection.

The connection will be added to the Connections list, and you should see Connection saved. at the top of the window.

Note: The free version allows you to add only one connection. If you need multiple connections, Conditional Routing, and many other features, you should purchase the DeliveryKit SMTP Pro.

Test SMTP Connection

After saving your SMTP connection, it is recommended to send a test email to make sure everything is working correctly. This helps confirm that your connection settings have been entered properly and that your site can send emails successfully through SMTP. For step-by-step instructions, see the test connection guide here: Test a DeliveryKit SMTP Connection.
]]> https://codemasterhub.com/doc/deliverykit-smtp-documentation/other-smtp-setup-in-deliverykit-smtp/feed/ 0 PHP Default (None) in DeliveryKit SMTP https://codemasterhub.com/doc/deliverykit-smtp-documentation/php-default-none-in-deliverykit-smtp/ https://codemasterhub.com/doc/deliverykit-smtp-documentation/php-default-none-in-deliverykit-smtp/#respond Fri, 03 Apr 2026 13:34:29 +0000 https://codemasterhub.com/?post_type=doc&p=1743
Understand how WordPress sends emails with PHP Default (None), when to use the default WP mail method, when to avoid it, and why a real SMTP mailer is usually better for reliable email delivery.

Table of Contents

What Is PHP Default (None) for WordPress Emails?

PHP Default (None) in DeliveryKit SMTP means your website will send emails using WordPress’s default mail method instead of connecting to a real SMTP or email API service.

When this option is selected, DeliveryKit SMTP does not route your emails through a third-party mailer such as Gmail, Outlook, Brevo, Mailgun, Amazon SES, or other SMTP providers. Instead, WordPress sends emails using its built-in wp_mail() function, which depends on how email sending is configured on your web server.

On many hosting environments, this usually means the server tries to send email through PHP mail or a local mail transfer service. Because of this, delivery depends heavily on your hosting provider’s server configuration, domain authentication, and sender reputation.

In simple terms, PHP Default (None) tells DeliveryKit SMTP: do not use a separate mailer, let WordPress and the server handle email sending in the default way.

What this means in practice

This option can work for basic website emails, such as contact form notifications, password reset emails, order alerts, and admin notices. However, it does not provide the same level of reliability, tracking, authentication support, or deliverability that a real SMTP or email sending service usually provides.

Why it is called PHP Default (None)

It is called PHP Default (None) because no external mailer is selected. The website falls back to the default WordPress email sending behavior, which relies on the server’s PHP mail setup or local mail system.

For better inbox placement and more reliable delivery, most production WordPress websites should use a real SMTP or API-based mailer instead of the default PHP mail method.

How WordPress Sends Emails by Default

By default, WordPress sends emails using its built-in wp_mail() function. This function is used for many common website emails, including password reset emails, user registration notices, comment notifications, contact form messages, WooCommerce order emails, and other plugin-generated emails.

When an email is triggered, WordPress prepares the message details, such as the recipient, subject, message content, headers, and attachments, then passes that data to wp_mail(). Behind the scenes, WordPress uses the PHPMailer library to process the email.

If no SMTP plugin or external mailer is configured, WordPress uses the server’s default mail setup to try to send the email. In many cases, this means the message is handed off to PHP mail or a local mail transfer service running on the hosting server.

This default behavior can work, but it depends entirely on the hosting environment. Some servers are configured correctly for sending mail, while others may block outgoing mail, limit sending, or send messages without proper authentication.

What happens behind the scenes

In simple terms, the process usually works like this:

WordPress creates the email, wp_mail() passes it to PHPMailer, and then the server attempts to send it using its own mail configuration. If the server is not properly configured, the email may fail silently, go to spam, or never reach the recipient.

Why this matters

Because WordPress default email sending relies on the server, delivery quality can vary a lot from one hosting provider to another. Even if the email appears to be sent successfully, it may still be rejected or filtered later by the receiving mail server.

Important note

WordPress does not include its own full email delivery service. It only creates and passes the email to the server for sending. This is why many website owners use a real SMTP or API-based mailer for better reliability and deliverability.

How PHP Default (None) Works in DeliveryKit SMTP

When you choose PHP Default (None) in DeliveryKit SMTP, the plugin does not connect your website to any external mailer service. No SMTP server, email API, or third-party provider is used for sending.

Instead, DeliveryKit SMTP leaves email delivery to WordPress’s default mail system. This means your site continues sending emails through the normal WordPress wp_mail() function and the mail configuration available on your hosting server.

In this mode, DeliveryKit SMTP does not authenticate emails through a dedicated mail service such as Gmail, Outlook, Brevo, Mailgun, Amazon SES, SendGrid, or other SMTP providers. The email is simply generated by WordPress and then handed over to the server to send using its own default mail setup.

What happens when this option is selected

After selecting PHP Default (None), DeliveryKit SMTP will not ask for SMTP credentials, API keys, hostnames, ports, or encryption settings. That is because no external mailer connection is being created.

Your WordPress site will still be able to send common emails, such as password reset emails, contact form notifications, order emails, admin alerts, and other plugin-generated messages, as long as your server allows outgoing mail and is configured correctly.

What DeliveryKit SMTP does and does not do in this mode

In PHP Default (None) mode, DeliveryKit SMTP can still help manage your email setup inside WordPress, but it does not improve delivery by routing messages through a real mail provider. The actual sending depends on your server environment.

This means email success is affected by factors such as your hosting provider, server mail configuration, domain DNS records, sender address, and the reputation of the sending server IP.

Why this option exists

PHP Default (None) is useful for users who want to keep WordPress email sending in its default state, test basic functionality, or temporarily avoid configuring an external mailer. It provides a simple fallback option when you do not want to use SMTP or an email API service.

Important limitation

Although this option is simple, it usually offers less reliable delivery than a real SMTP or API-based mailer. Emails may still be sent, but they are more likely to be delayed, filtered as spam, or blocked completely if the server is not properly configured for sending mail.

In simple terms

PHP Default (None) in DeliveryKit SMTP means: DeliveryKit SMTP stays out of the actual mail transport, and WordPress sends emails using the server’s default mail method.

When to Use WordPress Default Email Sending

WordPress default email sending can be a suitable option in some limited situations. It is usually best for simple websites, temporary setups, testing, or environments where email delivery is not business-critical.

For basic website emails

If your site only sends a small number of emails, such as contact form notifications, password reset emails, admin alerts, or simple user notifications, the default WordPress mail method may be enough, especially on hosting that is already configured correctly for outgoing mail.

For temporary use

PHP Default (None) can be useful when you want to get a site running quickly before setting up a real SMTP or email API mailer. For example, you may use it during initial site setup, development, staging, or while waiting to configure DNS records and verify a sending domain with a mail provider.

For local testing or low-risk environments

On development sites, test installs, or internal projects, using the default WordPress mail method can be acceptable if email reliability is not very important. In these cases, the goal is often just to confirm that email-triggered features are working.

When your hosting provider already handles mail well

Some managed hosting providers or server environments are configured to send basic website emails successfully. If your host has a reliable outgoing mail setup and your site only needs lightweight transactional email, the default method may work without an external mailer.

When you do not need advanced email features

If you do not need delivery logs, analytics, bounce handling, open tracking, sender authentication tools, or higher deliverability, WordPress default email sending may be enough for a very simple use case.

Important reminder

Even when WordPress default email sending works, it is usually not the best choice for production websites that depend on reliable email delivery. If your site sends important emails, such as ecommerce emails, membership emails, booking confirmations, invoices, or customer notifications, using a real SMTP or API-based mailer is the safer option.

When Not to Use WordPress Default Email Sending

WordPress default email sending is not the best choice when email delivery is important for your website. Since it depends on the server’s default mail setup, it can be less reliable and harder to trust for production use.

For business-critical emails

You should not rely on the default WordPress mail method for important emails such as order confirmations, invoices, password reset emails, membership emails, booking confirmations, account notifications, or contact form messages that must be delivered. If these emails fail or go to spam, it can affect your business and your users.

For ecommerce and membership websites

If you run an online store, membership site, LMS, booking system, or any website that sends frequent customer emails, using PHP Default (None) is usually not recommended. These websites depend on reliable email delivery, and a real SMTP or API-based mailer is a much safer choice.

When emails are going to spam or not arriving

If your website emails are not reaching inboxes, arriving late, or being filtered into spam, the default WordPress mail method should be avoided. In many cases, this is a sign that the server is not properly configured for sending mail or that the emails do not have enough authentication and sender trust.

When your hosting provider restricts mail sending

Some hosting providers limit, throttle, or completely block outgoing PHP mail to reduce spam and abuse. In these environments, WordPress default email sending may fail even if your site appears to send the message successfully.

When you need better deliverability

If you want better inbox placement, improved sender reputation, and proper email authentication, you should use a real SMTP or email API service instead of the default WordPress mail method. Dedicated mail providers are built for delivery and usually perform much better than server-based PHP mail.

When you need logs, tracking, or easier troubleshooting

WordPress default email sending is not ideal when you need detailed delivery logs, bounce handling, reporting, or easier troubleshooting. A real mailer service usually gives you better visibility into what happened to your emails.

In most live production websites

For most live websites, especially business, ecommerce, or client websites, PHP Default (None) should only be used as a temporary or fallback option. A real SMTP or API-based mailer is usually the better long-term setup.

Why WordPress Default Email Sending Can Fail

Why WordPress Default Email Sending Can Fail

WordPress default email sending can fail because WordPress itself does not deliver email directly. It only creates the email and passes it to the server’s mail system. If the server is not properly configured, the email may never be sent successfully.

Server mail is not configured correctly

Many hosting servers are not fully configured for reliable outgoing mail. In some cases, PHP mail is disabled, limited, or missing important mail server settings. When that happens, WordPress may try to send the email, but the server cannot deliver it properly.

Hosting providers may restrict outgoing mail

Some hosts block or limit outgoing mail to prevent spam and abuse. This is common on shared hosting. Even if WordPress generates the email correctly, the server may stop it from being sent or limit how many messages can go out.

Email authentication may be missing

If your domain does not have proper SPF, DKIM, and DMARC records, receiving mail servers may not trust your messages. This can cause emails to be rejected, marked as spam, or silently filtered.

The sending server may have a poor reputation

When WordPress uses the server’s default mail system, your emails may be sent from the hosting server’s IP address. If that IP has a poor reputation, or if other users on the same server have abused email sending, your messages may be blocked or sent to spam.

The From email address may not match the domain

If your site sends emails from an address that does not match your domain, such as a Gmail or Yahoo address, many mail servers may treat the message as suspicious. This can reduce deliverability or cause the email to fail authentication checks.

Emails may appear sent but still not be delivered

One of the most confusing problems is that WordPress may show no error at all. The email may appear to be sent successfully from the website, but it can still be rejected later by the receiving server, filtered into spam, or dropped before reaching the inbox.

No dedicated email delivery service is involved

With WordPress default email sending, there is no real SMTP provider or email API service handling delivery. This means you do not get the reliability, reputation, routing, and delivery tools that dedicated mail services provide.

Plugins or server settings can conflict

Other plugins, custom code, security rules, firewall settings, or server mail policies can also interfere with email sending. In some cases, the message is created correctly, but another part of the server environment prevents it from leaving the website.

In simple terms

WordPress default email sending can fail because successful delivery depends almost entirely on your server setup, domain authentication, and sender trust. If any part of that setup is weak, your emails may not arrive.

Common Problems with WordPress Default Email Sending

Common Problems with WordPress Default Email Sending

When WordPress uses the default email sending method, several problems can happen. Some issues are obvious, while others are harder to detect because the website may show no clear error.

Emails are not delivered at all

One of the most common problems is that emails never reach the recipient. WordPress may trigger the email correctly, but the server may fail to send it or the receiving mail server may reject it.

Emails go to the spam folder

Even when emails are sent successfully, they may still land in spam. This often happens when the sending server is not trusted, domain authentication is missing, or the sender address does not match the domain.

Password reset or login emails do not arrive

If users do not receive password reset emails, account emails, or login-related notifications, they may be locked out of their accounts. This is a common sign that the default mail setup is not reliable enough.

Contact form messages are missed

Many website owners first notice email problems when contact form notifications stop arriving. The form may appear to submit correctly, but the email notification never reaches the site owner.

WooCommerce or order emails fail

On ecommerce websites, customers may not receive order confirmations, invoices, or status updates. This can create confusion, support requests, and loss of trust.

Emails are delayed

Sometimes emails are not completely lost, but they arrive much later than expected. Delayed emails can still cause problems, especially for password resets, bookings, or time-sensitive notifications.

No clear error message is shown

WordPress default email sending often fails silently. The site may behave as if the email was sent, even though it was later blocked, filtered, or dropped by the server or recipient mail system.

Server limits or hosting restrictions

Some hosting providers limit how many emails can be sent, block PHP mail, or apply strict server rules. In these cases, default WordPress email sending may work only sometimes, or not at all.

Sender address problems

Using a sender email address that does not belong to your domain, such as a free Gmail address, can cause delivery and authentication problems. Many receiving servers treat these messages as suspicious.

Harder troubleshooting

Because no dedicated mail service is being used, it can be harder to find out exactly why an email failed. You may have limited logs, limited error details, and no delivery reporting.

In simple terms

The most common problems with WordPress default email sending are missing emails, spam delivery, delays, and silent failures. This is why many production websites use a real SMTP or API-based mailer instead.

Why Using a Real SMTP Mailer Is Better for WordPress Emails

Using a real SMTP mailer is usually a better choice for WordPress emails because it gives your website a more reliable and trusted way to send messages. Instead of depending on your hosting server’s default mail setup, your emails are sent through a dedicated email service that is built for delivery.

Better email deliverability

Real SMTP and email API providers are designed to send emails properly and improve inbox placement. This means your messages are more likely to reach the recipient instead of being rejected, delayed, or sent to spam.

More reliable sending

With a real mailer, your website is not fully dependent on the hosting server’s default PHP mail configuration. This reduces the risk of silent failures, blocked messages, and server-related delivery issues.

Supports proper authentication

Most SMTP providers help you send emails with proper domain authentication, such as SPF, DKIM, and DMARC. These records help receiving mail servers trust your messages and improve delivery success.

Better for important website emails

If your site sends important emails such as password reset emails, contact form notifications, order confirmations, invoices, booking emails, or membership emails, a real SMTP mailer is a much safer option than the default WordPress mail method.

Improved sender reputation

Dedicated mail services are built to maintain better sending reputation than many shared hosting servers. This helps your emails look more trustworthy to receiving mail systems.

Easier troubleshooting

When you use a real SMTP or API-based mailer, it is usually easier to identify email problems. Many providers offer logs, activity history, error details, and delivery reports, which make troubleshooting much easier.

Better for growing websites

As your website sends more emails, the default WordPress mail method becomes less reliable for production use. A real mailer is better suited for business websites, ecommerce stores, membership sites, booking systems, and client projects.

More professional email setup

Using a real SMTP mailer gives your website a more professional email system. It helps ensure your emails are sent through a trusted channel instead of relying on whatever mail configuration happens to exist on the server.

In simple terms

WordPress default email sending may work for basic use, but a real SMTP mailer is usually better because it improves reliability, deliverability, trust, and control over your website emails.

WordPress Default Email Sending vs SMTP Mailers

WordPress default email sending and SMTP mailers both allow your website to send emails, but they work in very different ways.

How WordPress default email sending works

With the default WordPress method, your site sends emails through wp_mail() and relies on the server’s own mail configuration. No dedicated email provider is involved unless you connect one yourself.

This setup is simple because it does not require SMTP credentials or an external mail service, but delivery depends heavily on your hosting environment. If the server is not configured well for mail, emails may fail, go to spam, or never arrive.

How SMTP mailers work

SMTP mailers send your website emails through a real email service, such as Gmail, Outlook, Brevo, Mailgun, Amazon SES, SendGrid, Postmark, or other providers. Instead of relying only on the hosting server, your site connects to a dedicated mail system that is built for sending email reliably.

This usually improves deliverability, authentication, and overall trust because the emails are routed through a provider designed specifically for email sending.

Main differences

The default WordPress mail method is easier to use at first because it needs little or no setup, but it is usually less reliable. SMTP mailers require extra setup, such as credentials, API keys, or DNS records, but they are usually much better for real website email delivery.

Deliverability

WordPress default email sending often has weaker deliverability because it depends on the server’s mail reputation and configuration. SMTP mailers usually offer much better inbox placement because they are built for authenticated email delivery.

Reliability

The default method may work on some hosts and fail on others. SMTP mailers are usually more stable and predictable, especially for business websites and customer-facing emails.

Authentication

With the default WordPress method, authentication may be weak or missing if the server is not set up properly. SMTP providers usually support SPF, DKIM, and DMARC more effectively, which helps receiving servers trust your emails.

Troubleshooting

Default WordPress email sending can be harder to troubleshoot because failures are often silent. SMTP providers usually offer better logs, error details, and delivery tracking.

Best use case for each

WordPress default email sending may be acceptable for temporary setups, test sites, or very small websites where email is not critical. SMTP mailers are the better choice for production sites, ecommerce stores, membership websites, booking systems, and any site that depends on reliable email delivery.

In simple terms

WordPress default email sending is the simpler option, but SMTP mailers are usually the better option for reliability, deliverability, and long-term use.

Feature WordPress Default Email Sending SMTP Mailers
How emails are sent Uses WordPress wp_mail() and the server’s default mail setup Sends emails through a dedicated SMTP or email API provider
Setup required Usually little or no extra setup Requires mailer setup, credentials, and often DNS authentication
Reliability Depends on the hosting server configuration Usually much more reliable for production websites
Email deliverability Can be weak, emails may fail or go to spam Usually better inbox placement and delivery success
Authentication support May be limited or missing, depending on server setup Usually supports SPF, DKIM, and DMARC properly
Spam risk Higher risk of emails being filtered as spam Lower risk when configured correctly
Server dependency Fully depends on your hosting server mail setup Less dependent on the hosting server for actual delivery
Troubleshooting Often harder, with fewer logs and less visibility Easier, with better logs and delivery reporting
Best for Testing, temporary setups, or very small websites Business sites, stores, memberships, bookings, and important emails
Overall recommendation Acceptable only for limited or temporary use Recommended for most live WordPress websites

Upgrade to DeliveryKit SMTP Pro

Unlock multiple email connections, smart conditional routing, detailed email logs, delivery alerts, dashboard analytics, built-in email testing, manual sending, and easy import/export tools.

Choose the best sending path for every email and manage WordPress email delivery with more control.

Get DeliveryKit SMTP Pro

]]> https://codemasterhub.com/doc/deliverykit-smtp-documentation/php-default-none-in-deliverykit-smtp/feed/ 0 Netcore Email SMTP Setup https://codemasterhub.com/doc/deliverykit-smtp-documentation/netcore-email-smtp-setup/ https://codemasterhub.com/doc/deliverykit-smtp-documentation/netcore-email-smtp-setup/#respond Fri, 03 Apr 2026 11:02:56 +0000 https://codemasterhub.com/?post_type=doc&p=1726
Learn how to set up Netcore Email SMTP in the DeliveryKit SMTP plugin, including account setup, SMTP credentials, authentication, and sending a test email.

Table of Contents

What is Netcore?

Netcore is a customer engagement and email delivery platform that helps businesses send emails at scale. Its email service supports SMTP relay, APIs, and related tools for delivering transactional, triggered, and campaign emails reliably.

For DeliveryKit SMTP users, Netcore can be used as a third-party mailer to send WordPress emails through Netcore’s infrastructure instead of your web server. This can help with authentication, delivery tracking, and more reliable email sending for things like contact forms, notifications, and account emails.

Create a Netcore account

Create a Netcore API Key

To create your Netcore API key, visit https://cpaas.netcorecloud.com/app/settings/integration. You can also access this page from your Netcore dashboard by hovering over the Settings icon, then going to Integration and selecting API.

On the API page, click Create API Key, then copy and save the generated key. You will need this API key later when configuring Netcore in the DeliveryKit SMTP plugin.

Netcore Setup in DeliveryKit SMTP Plugin

In your WordPress dashboard, go to DeliveryKit SMTP > Connections, then click Create New Connection.

Configure Connection

In the Configure Connection section, fill out the Connection Details fields:

Connection Details: Enter a name for this connection. This is only for you, recipients will not see it.

Default From Email: The email address used when an outgoing email does not define a From Email.

Force From Email: If enabled, this From Email will be used for all emails, even if the email has a different From Email.

Default From Name: The name used when an outgoing email does not define a From Name.

Force From Name: If enabled, this From Name will be used for all emails, even if the email has a different From Name.

Default Reply-To Email: The Reply-To address used when an outgoing email does not define a Reply-To Email.

Force Reply-To Email: If enabled, this Reply-To Email will be used for all emails, even if the email has a different Reply-To Email.

In the Choose a Mailer section, select Zoho Mail from the grid mailer list.

Netcore Email Settings

In the Netcore Email Settings section, paste your Netcore API Key into the field provided.

After entering the API key, click Save Connection to store your settings and complete the Netcore mailer setup.

The connection will be added to the Connections list, and you should see Connection saved. at the top of the window.

Note: The free version allows you to add only one connection. If you need multiple connections, Conditional Routing, and many other features, you should purchase the DeliveryKit SMTP Pro.

Test Netcore Email Connection

After saving your Netcore connection, it is recommended to send a test email to make sure everything is working correctly. This helps confirm that your connection settings have been entered properly and that your site can send emails successfully through Netcore Email SMTP.

For step-by-step instructions, see the test connection guide here:

Test a DeliveryKit SMTP Connection.

]]> https://codemasterhub.com/doc/deliverykit-smtp-documentation/netcore-email-smtp-setup/feed/ 0 Zoho Mail SMTP Setup https://codemasterhub.com/doc/deliverykit-smtp-documentation/zoho-mail-smtp-setup/ https://codemasterhub.com/doc/deliverykit-smtp-documentation/zoho-mail-smtp-setup/#respond Fri, 03 Apr 2026 09:51:04 +0000 https://codemasterhub.com/?post_type=doc&p=1691
Learn how to set up Zoho Mail in the DeliveryKit SMTP plugin, including domain setup, SMTP credentials, authentication, and sending a test email.

Table of Contents

What Is Zoho?

Zoho Mail is a business email hosting service that lets you create professional email addresses using your own domain, such as name@yourdomain.com. It is designed for organizations that want secure, ad-free email with privacy-focused hosting, encryption in transit and at rest, custom domain support, and an admin console for managing users, aliases, and mail policies.

In addition to standard email hosting, Zoho Mail also includes features like mobile apps, migration tools, calendar and collaboration options, and its Streams feature for team discussions inside the inbox. For businesses using DeliveryKit SMTP, Zoho Mail can be a good option when you want branded email sending with your own domain and a reliable business mail platform.

Creating a Zoho Mail Account

If you already have a Zoho account, you can sign in and skip this step. To create a new account, go to https://www.zoho.com/mail/ and choose whether you want to sign up for a Business Email or Personal Email account.

In this example, we are creating a Business Email account using a work email address, mail@codemasterhub.com. Enter your name, email address, password, and phone number, accept the terms, then click Sign Up Now to continue.

Verify Your Sign-Up

After submitting the sign-up form, Zoho Mail will send a one-time password (OTP) to the mobile number you entered during registration.

Enter the verification code in the OTP field, then click Verify to continue. If needed, you can click Resend OTP to receive a new code.

Verify Your Email Address

After completing the sign-up process, check your inbox for a verification email from Zoho. Open the email and click Verify Email Address to confirm your email and continue with the account setup.

Confirm the Email Verification

After clicking the verification link in your inbox, you will be redirected to a Zoho confirmation page. Click Verify to confirm your email address and continue with the account setup process.

Access Your Zoho Mail Account

Once your email address is verified, Zoho will show a confirmation screen. Click Access Account to open your Zoho Mail account and continue with the setup.

Open Your Zoho Account Settings

After signing in, click your profile icon in the top-right corner of the page, then click My Account to open your Zoho account settings.

Access Zoho Mail

In your Zoho account area, click the apps icon in the top-right corner of the page, then open Mail to access your Zoho Mail dashboard.

Choose a Zoho Mail Plan Type

At this step, you can choose between a domain-based business email account or a personal email account.

If you want to use a work email address with your own domain, choose Create domain based email account in Zoho. This option is part of Zoho’s paid plans, and you will be redirected to the pricing page to continue.

If you want to use a free Zoho email address such as @zohomail.eu or @zohomail.com, choose Create personal email account. Then enter your preferred username. For example, if you enter example, your email address will be something like example@zohomail.eu, depending on your region.

In this example, we are using the free personal email option. Enter your username, then click Create.

Add Your Heading Text Here

Creating a Zoho API Key

To create your Zoho API key, first visit https://api-console.zoho.com/. If prompted, log in to your Zoho account to continue.

Open the API Console

After logging in, you will be redirected to the Zoho API Console welcome page. Click Get Started to begin creating your OAuth credentials.

Choose the Client Type

On the Choose a Client Type screen, select Server-based Applications, then click Create Now. This option is suitable for connecting Zoho Mail with the DeliveryKit SMTP plugin.

Create a New Client

On the Create New Client screen, enter a clear name in the Client Name field. In Homepage URL, enter your website homepage URL. In Authorized Redirect URIs, enter your WordPress admin URL ending with /wp-admin/admin.php, then click Create.

Note: You can also copy the correct redirect URL directly from your WordPress dashboard. Go to DeliveryKit SMTP >> Connections >> Add New Connection, select Zoho Mail as the mailer, then copy the URL shown in the Authorized Redirect URI field and paste it here.

You may be asked to enter your Zoho account password again to confirm this action. Enter your password, then click Confirm Password to continue.

Copy Your Client ID and Client Secret

After the client is created, open the Client Secret tab. Copy the Client ID and Client Secret, then save them somewhere safe. You will need both of these values when configuring Zoho Mail in the DeliveryKit SMTP plugin in WordPress.

Zoho Mail Setup in DeliveryKit SMTP Plugin

In your WordPress dashboard, go to DeliveryKit SMTP > Connections, then click Create New Connection.

Configure Connection

In the Configure Connection section, fill out the Connection Details fields:

Connection Details: Enter a name for this connection. This is only for you, recipients will not see it.

Default From Email: The email address used when an outgoing email does not define a From Email.

Force From Email: If enabled, this From Email will be used for all emails, even if the email has a different From Email.

Default From Name: The name used when an outgoing email does not define a From Name.

Force From Name: If enabled, this From Name will be used for all emails, even if the email has a different From Name.

Default Reply-To Email: The Reply-To address used when an outgoing email does not define a Reply-To Email.

Force Reply-To Email: If enabled, this Reply-To Email will be used for all emails, even if the email has a different Reply-To Email.

In the Choose a Mailer section, select Zoho Mail from the grid mailer list.

Zoho Mail Settings

In the Zoho Mail Settings section, enter your Client ID and Client Secret, then choose the correct Region for your Zoho account.

After that, click Save Connection. Once the connection is saved, the Authorization button will appear so you can continue connecting your Zoho Mail account.

Authorization

In the Authorization section, click Sign in with Zoho to authorize DeliveryKit SMTP to send emails using your Zoho Mail account.

Approve the Authorization Request

Zoho will open a permission screen showing what DeliveryKit SMTP can access. Review the requested permissions, keep the consent checkbox enabled, then click Accept to complete the authorization.

The connection will be added to the Connections list, and you should see Connection saved. at the top of the window.

Note: The free version allows you to add only one connection. If you need multiple connections, Conditional Routing, and many other features, you should purchase the DeliveryKit SMTP Pro.

Test Zoho Mail Connection

After saving your Zoho Mail connection, it is recommended to send a test email to make sure everything is working correctly. This helps confirm that your connection settings have been entered properly and that your site can send emails successfully through Zoho Mail SMTP.

For step-by-step instructions, see the test connection guide here:

Test a DeliveryKit SMTP Connection.

]]> https://codemasterhub.com/doc/deliverykit-smtp-documentation/zoho-mail-smtp-setup/feed/ 0 SparkPost SMTP Setup https://codemasterhub.com/doc/deliverykit-smtp-documentation/sparkpost-smtp-setup/ https://codemasterhub.com/doc/deliverykit-smtp-documentation/sparkpost-smtp-setup/#respond Thu, 02 Apr 2026 10:52:53 +0000 https://codemasterhub.com/?post_type=doc&p=1659
Learn how to set up SparkPost SMTP in DeliveryKit SMTP for WordPress, including account setup, domain authentication, API key creation, and connection settings.

Table of Contents

What Is SparkPost?

SparkPost is a cloud-based email delivery service that helps businesses send transactional and marketing emails with high deliverability. It provides SMTP relay and email APIs, along with features like sending domains, tracking, analytics, templates, and recipient suppression management. For WordPress users, SparkPost can be connected to DeliveryKit SMTP so your website can send emails more reliably through SparkPost’s authenticated infrastructure.

Create a SparkPost Account

Go to https://app.sparkpost.com/join.

If you are creating a new account, first choose your server region: SparkPost for the US region, or SparkPost EU for the Europe region. If you are located in Europe, select SparkPost EU. Otherwise, select SparkPost.

After that, fill out the signup form, complete the verification step, and click Create Account.

Check your inbox for a verification email from SparkPost and click Verify Email Address.

Verify Sending Domain

After you click Verify Email Address in the email, you will be redirected to your SparkPost dashboard.

To start setting up your sending domain, click Add Sending Domain.

Select Sending Domain as the domain type, then enter your domain name.

Using a subdomain is recommended, for example: sub.domain.com.

After entering the domain, click Save and Continue.

You may also see a Domain Alignment popup. Leave the default option selected, then click Save and Continue.

Adding a Bounce Domain

After your sending domain is verified, go to Configuration > Domains, open the Bounce Domains tab, then click Add a Domain.

Select Bounce Domain as the domain type, then enter your bounce domain.

Using a subdomain is recommended, for example: bounce.domain.com.

After entering the domain, click Save and Continue.

Add the required CNAME record to your DNS provider exactly as shown in SparkPost.

After adding the record, check the confirmation box, then click Verify Bounce.

Note: DNS changes may take some time to propagate. If verification does not complete immediately, wait a few minutes and try again.

Set as Default Bounce Domain

To set your bounce domain as the default one, first go to the Domains page and click your verified bounce domain name.

On the domain settings page, enable Set as Default Bounce Domain to use this bounce domain as the default for your SparkPost account.

Creating a SparkPost API Key

To create an API key, go to Configuration > API Keys, then click Create API Key.

Enter a name for your API key, for example: DeliveryKit SMTP.

For API Permissions, you can leave the default All option selected.

You can leave the Allowed IPs field empty unless you want to restrict the API key to specific server IP addresses.

Then click Create API Key.

Your new SparkPost API key will be shown only once after creation. Copy it and save it in a safe place, because you will need it in the next step when configuring SparkPost in DeliveryKit SMTP.

SparkPost Setup in DeliveryKit SMTP Plugin

In your WordPress dashboard, go to DeliveryKit SMTP > Connections, then click Create New Connection.

Configure Connection

In the Configure Connection section, fill out the Connection Details fields:

Connection Details: Enter a name for this connection. This is only for you, recipients will not see it.

Default From Email: The email address used when an outgoing email does not define a From Email.

Force From Email: If enabled, this From Email will be used for all emails, even if the email has a different From Email.

Default From Name: The name used when an outgoing email does not define a From Name.

Force From Name: If enabled, this From Name will be used for all emails, even if the email has a different From Name.

Default Reply-To Email: The Reply-To address used when an outgoing email does not define a Reply-To Email.

Force Reply-To Email: If enabled, this Reply-To Email will be used for all emails, even if the email has a different Reply-To Email.

In the Choose a Mailer section, select SparkPost from the grid mailer list.

SparkPost Settings

Enter your SparkPost API Key. For Region, select US or EU to match the SparkPost account region you selected when creating your account. If you want to use this as your main mailer, enable Make this the default connection. Finally, click Save Connection.

The connection will be added to the Connections list, and you should see Connection saved. at the top of the window.

Note: The free version allows you to add only one connection. If you need multiple connections, Conditional Routing, and many other features, you should purchase the DeliveryKit SMTP Pro.

Test SparkPost Connection

After saving your SparkPost connection, it is recommended to send a test email to make sure everything is working correctly. This helps confirm that your API Key, and connection settings have been entered properly and that your site can send emails successfully through SparkPost SMTP.

For step-by-step instructions, see the test connection guide here:

Test a DeliveryKit SMTP Connection.

]]> https://codemasterhub.com/doc/deliverykit-smtp-documentation/sparkpost-smtp-setup/feed/ 0 SMTP2GO SMTP Setup https://codemasterhub.com/doc/deliverykit-smtp-documentation/smtp2go-smtp-setup/ https://codemasterhub.com/doc/deliverykit-smtp-documentation/smtp2go-smtp-setup/#respond Thu, 02 Apr 2026 09:31:16 +0000 https://codemasterhub.com/?post_type=doc&p=1629
Learn how to set up SMTP2GO in DeliveryKit SMTP, including account setup, sender authentication, SMTP or API credentials, and testing your email connection.

Table of Contents

What is SMTP2GO?

SMTP2GO is an email delivery service that helps you send transactional and other outgoing emails reliably using SMTP relay or API integration. It is designed to improve deliverability, supports sender domain authentication with SPF and DKIM, and includes tools like activity reporting, bounce tracking, and email logs to help monitor your sending performance. For WordPress and DeliveryKit SMTP users, SMTP2GO is a practical option for sending website emails more securely and consistently than the default PHP mail function.

Creating a SMTP2GO Account

To create your SMTP2GO account, visit the pricing page and choose a plan that fits your needs. In this example, we use the Free plan, which is a good option for testing and small websites.

On the pricing page, click the Get Started button under the Free Plan.

A signup popup will appear. Enter your work email address, then click Continue to proceed with the account creation process.

Next, enter your full name, company name, and create a password for your SMTP2GO account. When ready, click Sign Up to continue.

After signing up, check your inbox for the SMTP2GO account activation email. Open the email and click Activate Account to verify your email address and continue.

After verifying your email address, you will be redirected to your SMTP2GO dashboard. From there, click Add a verified sender to continue. You can also go directly to the Verified Senders page by visiting https://app.smtp2go.com/sending/verified_senders/.

On the Verified Senders page, click Add a sender domain. Verifying your domain is the recommended option, because it improves deliverability and lets you send emails from addresses on that domain.

Enter the domain name you want to use for sending emails, then click Continue with this domain.

SMTP2GO will now ask you to verify your DNS. At this step, you can choose Set up automatically if your DNS provider is supported, or Set up manually to add the required DNS records yourself.

If you selected automatic setup, follow the prompts to let SMTP2GO add the DNS records for you. If you selected manual setup, add the required DNS records at your DNS provider, then return to SMTP2GO and click Verify.

After adding the DNS records, click Verify. If you see that the SSL certificate for the link CNAME is still pending, wait a few minutes and click Verify again. In some cases, you may need to try again until the domain and SSL certificate are fully verified.

SMTP2GO API Key

To create an API key in SMTP2GO, go to Sending in the left sidebar, then open API Keys. After that, click Add API Key.

First, copy the generated API Key and save it in a safe place. You will need it later in the DeliveryKit SMTP settings. After that, click Add API Key.

A review permissions popup may appear before the API key is created. By default, the /email/send permission is already selected, and that is enough for connecting SMTP2GO with DeliveryKit SMTP. If you want to add more permissions, open the Permissions tab first and select them before continuing.

SMTP2GO Setup in DeliveryKit SMTP Plugin

In your WordPress dashboard, go to DeliveryKit SMTP > Connections, then click Create New Connection.

Configure Connection

In the Configure Connection section, fill out the Connection Details fields:

Connection Details: Enter a name for this connection. This is only for you, recipients will not see it.

Default From Email: The email address used when an outgoing email does not define a From Email.

Force From Email: If enabled, this From Email will be used for all emails, even if the email has a different From Email.

Default From Name: The name used when an outgoing email does not define a From Name.

Force From Name: If enabled, this From Name will be used for all emails, even if the email has a different From Name.

Default Reply-To Email: The Reply-To address used when an outgoing email does not define a Reply-To Email.

Force Reply-To Email: If enabled, this Reply-To Email will be used for all emails, even if the email has a different Reply-To Email.

In the Choose a Mailer section, select SMTP2GO from the grid mailer list.

SMTP2GO Settings

In the SMTP2GO Settings section, paste your SMTP2GO API Key into the API Key field.

If you want, you can also enable Default Connection to make SMTP2GO your default mailer. When you are done, click Save Connection.

The connection will be added to the Connections list, and you should see Connection saved. at the top of the window.

Note: The free version allows you to add only one connection. If you need multiple connections, Conditional Routing, and many other features, you should purchase the DeliveryKit SMTP Pro.

Test SMTP2GO Connection

After saving your SMTP2GO connection, it is recommended to send a test email to make sure everything is working correctly. This helps confirm that your API Key, and connection settings have been entered properly and that your site can send emails successfully through SMTP2GO SMTP.

For step-by-step instructions, see the test connection guide here:

Test a DeliveryKit SMTP Connection.

]]> https://codemasterhub.com/doc/deliverykit-smtp-documentation/smtp2go-smtp-setup/feed/ 0 Resend SMTP Setup https://codemasterhub.com/doc/deliverykit-smtp-documentation/resend-smtp-setup/ https://codemasterhub.com/doc/deliverykit-smtp-documentation/resend-smtp-setup/#respond Thu, 02 Apr 2026 07:23:40 +0000 https://codemasterhub.com/?post_type=doc&p=1608
Set up Resend SMTP in the DeliveryKit SMTP plugin for WordPress, including account creation, domain verification, API key setup, connection settings, and email testing.

Table of Contents

What Is Resend?

Resend is an email delivery platform built for developers that makes it easy to send transactional emails using API or SMTP. It offers domain verification, email logs, analytics, and a simple setup flow, making it a solid option for WordPress sites that need reliable email delivery through the DeliveryKit SMTP plugin.

Setting Up a Resend Account

To get started, visit the Resend pricing page:

https://resend.com/pricing

In this example, we will use the Free plan to set up Resend.

Click Get started under the Free plan to create your account and continue.

Next, complete the account creation steps. You can create your account manually by entering your details, or use Sign in with Google for a faster one-step signup process.

After your account is created, log in to continue with the Resend setup.

Authorizing Your Domain

Before you can send emails with Resend, you need to add and verify your sending domain. This confirms that you own the domain you want to send from and helps improve email deliverability.

Adding Your Sending Domain

To add a sending domain, log in to your Resend account and go to Domains from the left sidebar, or visit https://resend.com/domains.

Then click Add domain to continue.

Enter your domain name, then choose the region you want to use.

Domain: Using a subdomain is recommended, such as mail.yourdomain.com or mailing.yourdomain.com. This can still be used for sending emails for addresses on your main domain, depending on your setup.

Region: Select the region closest to you or your main audience for the best performance.

When ready, click Add domain.

DNS Records

For Cloudflare and some other DNS providers, you can use Auto configure to add the required DNS records automatically.

If you prefer to add the records yourself, click Manual setup and copy the DNS records into your domain DNS settings manually.

If you used Auto configure, Resend will add the DNS records for you automatically. After the setup is completed, you should see your domain marked as Verified.

Note: Domain verification may take a few minutes after the DNS records are added.

Resend API Key

To create your Resend API key, click API Keys from the left sidebar, or visit https://resend.com/api-keys.

Then click Create API Key.

Enter the API key details, then click Add.

Name: Enter a clear name, such as DeliveryKit SMTP.

Permission: Select Full access.

Domain: If you verified multiple domains, you can limit the API key to a specific domain, or leave it set to All Domains.

Then click Add

After the API key is created, copy and save it in a secure place. Resend only shows the full API key once, and you will need it in the next step when setting up Resend in the DeliveryKit SMTP plugin.

Resend Setup in DeliveryKit SMTP Plugin

In your WordPress dashboard, go to DeliveryKit SMTP > Connections, then click Create New Connection.

Configure Connection

In the Configure Connection section, fill out the Connection Details fields:

Connection Details: Enter a name for this connection. This is only for you, recipients will not see it.

Default From Email: The email address used when an outgoing email does not define a From Email.

Force From Email: If enabled, this From Email will be used for all emails, even if the email has a different From Email.

Default From Name: The name used when an outgoing email does not define a From Name.

Force From Name: If enabled, this From Name will be used for all emails, even if the email has a different From Name.

Default Reply-To Email: The Reply-To address used when an outgoing email does not define a Reply-To Email.

Force Reply-To Email: If enabled, this Reply-To Email will be used for all emails, even if the email has a different Reply-To Email.

In the Choose a Mailer section, select Resend from the grid mailer list.

Resend Settings

In the Resend Settings section, paste your Resend API Key into the matching field.

If you want to use Resend as your main mailer, enable Make this the default connection, then click Save Connection.

The connection will be added to the Connections list, and you should see Connection saved. at the top of the window.

Note: The free version allows you to add only one connection. If you need multiple connections, Conditional Routing, and many other features, you should purchase the DeliveryKit SMTP Pro.

Test Resend Connection

After saving your Resend connection, it is recommended to send a test email to make sure everything is working correctly. This helps confirm that your API Key, and connection settings have been entered properly and that your site can send emails successfully through Resend SMTP.

For step-by-step instructions, see the test connection guide here:

Test a DeliveryKit SMTP Connection.

]]> https://codemasterhub.com/doc/deliverykit-smtp-documentation/resend-smtp-setup/feed/ 0 Postmark SMTP Setup https://codemasterhub.com/doc/deliverykit-smtp-documentation/postmark-smtp-setup/ https://codemasterhub.com/doc/deliverykit-smtp-documentation/postmark-smtp-setup/#respond Tue, 31 Mar 2026 13:33:25 +0000 https://codemasterhub.com/?post_type=doc&p=1582
Learn how to set up Postmark SMTP in the DeliveryKit SMTP plugin for WordPress, including server token setup, sender verification, connection settings, and email testing.

Table of Contents

What Is Postmark?

Postmark is an email delivery service designed mainly for transactional email, such as password resets, order confirmations, login alerts, contact form messages, and other important site notifications. It provides both SMTP and API sending options, with a strong focus on fast delivery, inbox reliability, and message tracking. Postmark also separates transactional and promotional email streams to help protect deliverability, making it a solid choice for WordPress sites that need dependable email sending through the DeliveryKit SMTP plugin.

Create a Postmark Account

To get started, create your Postmark account by visiting the Postmark pricing page:

https://postmarkapp.com/pricing

In this example, we will use the Free plan. It is a good option for testing your integration and includes up to 100 emails per month.

On the pricing page, click Start Free Trial under the Free plan to continue.

Use a business email address in the next steps to create your free Postmark account.

Use a business email address in the next steps to create your free Postmark account.

After creating your account, you will receive a confirmation email from Postmark. Open the email and click the Confirm Sender Signature button to verify your sender and activate your account.

After confirming your email, log in to your Postmark account. If your account is still in Test mode, click Request approval in the top right corner and complete the approval process before using Postmark for live sending.

Fill out the approval form with your sending details, then click Request approval to submit your application. Postmark will review your request, and once approved, you can continue setting up your sending domain and server.

Add Your Sending Domain

Once your account is under review or approved, go to the Sender Signatures tab, then click Add Domain or Signature.

For best results, choose to add and verify your domain. This allows you to send emails from addresses on your domain and helps improve deliverability.

Adding a New Sender Signature

Note: Although you can get the Postmark mailer up and running with a Sender Signature for an individual email address, we recommend adding a domain instead to better ensure email delivery.

To send emails from a single email address, you can verify a Sender Signature. The email address associated with your account is verified during signup, but you can add as many additional email addresses as you want.

To begin, click the Add Sender Signature button.

Enter the sender details you want to use, including the From email address. You can also add an optional From name, Reply-To email, and personal note. When ready, click Create Signature.

Note: If you created your Postmark account using the same email address, you do not need to add it again. A sender signature for that email is already available in your account.

Verify Your Domain

To verify your domain, go to Sender Signatures, then click DNS Settings next to your domain.

Postmark will show the DNS records you need to add to your domain DNS settings. Add the required DKIM and Return-Path records exactly as provided by Postmark.

Note: Postmark no longer requires an SPF record here, since SPF handling is managed automatically.

After adding the records at your DNS provider, return to this page and click Verify for each record.

Postmark API Token

Finding Your Postmark API Token

To find your Postmark API token, go to the Servers tab, then click the server you want to use.

Open the API Tokens tab to view your Server API token. Copy this token, you will need it later when configuring Postmark in the DeliveryKit SMTP plugin.

Postmark Setup in DeliveryKit SMTP Plugin

In your WordPress dashboard, go to DeliveryKit SMTP > Connections, then click Create New Connection.

Configure Connection

In the Configure Connection section, fill out the Connection Details fields:

Connection Details: Enter a name for this connection. This is only for you, recipients will not see it.

Default From Email: The email address used when an outgoing email does not define a From Email.

Force From Email: If enabled, this From Email will be used for all emails, even if the email has a different From Email.

Default From Name: The name used when an outgoing email does not define a From Name.

Force From Name: If enabled, this From Name will be used for all emails, even if the email has a different From Name.

Default Reply-To Email: The Reply-To address used when an outgoing email does not define a Reply-To Email.

Force Reply-To Email: If enabled, this Reply-To Email will be used for all emails, even if the email has a different Reply-To Email.

In the Choose a Mailer section, select Postmark from the grid mailer list.

Postmark Settings

In the Postmark Settings section, paste your Server API Token into the matching field.

The Message Stream ID field is optional. Leave it empty to use Postmark’s default transactional stream, or enter a specific Message Stream ID if needed.

If you want to use this as your main mailer, enable Make this the default connection, then click Save Connection.

The connection will be added to the Connections list, and you should see Connection saved. at the top of the window.

Note: The free version allows you to add only one connection. If you need multiple connections, Conditional Routing, and many other features, you should purchase the DeliveryKit SMTP Pro.

Test Postmark Connection

After saving your Postmark connection, it is recommended to send a test email to make sure everything is working correctly. This helps confirm that your API Key, and connection settings have been entered properly and that your site can send emails successfully through Postmark SMTP.

For step-by-step instructions, see the test connection guide here:

Test a DeliveryKit SMTP Connection.

]]> https://codemasterhub.com/doc/deliverykit-smtp-documentation/postmark-smtp-setup/feed/ 0 Mandrill SMTP Setup https://codemasterhub.com/doc/deliverykit-smtp-documentation/mandrill-smtp-setup/ https://codemasterhub.com/doc/deliverykit-smtp-documentation/mandrill-smtp-setup/#respond Tue, 31 Mar 2026 08:15:24 +0000 https://codemasterhub.com/?post_type=doc&p=1547
Set up Mandrill SMTP in DeliveryKit SMTP for WordPress. Learn how to connect your account, add API credentials, configure sender settings, and send a test email.

Table of Contents

What is Mandrill

Mandrill, now known as Mailchimp Transactional, is a transactional email service designed for sending one-to-one emails from websites and applications. It is commonly used for emails such as password resets, order confirmations, welcome emails, and other automated notifications. Mandrill supports SMTP sending, offers scalable delivery infrastructure, and is built to help businesses send fast and reliable transactional emails. It is available as a Mailchimp add-on for transactional email sending.

Creating and Setting Up a Mandrill Account

Mandrill is part of Mailchimp Transactional, so you need a Mailchimp account first.

Log in to your Mailchimp account here:

https://login.mailchimp.com/

In your dashboard, go to Automations > Transactional, then click Try for Free.

In this example, we use the free plan.

After activating the free transactional plan, click Launch App to open the Mandrill dashboard.

In the Mandrill dashboard, you will see a No Sending Domains notice. Click Set up your sending domain to start adding and verifying your domain.

Enter your sending domain name, then click Add domain.

Verify Your Domain and Add DNS Records

In the records table, under Verified Domain?, click View details to open the verification popup.

Mandrill provides two ways to verify your domain:

  • Add the verification TXT record to your domain DNS records.
  • Or enter an email address on the same domain, then click Send verification email to receive a verification link.

In this example, we use the email verification method.

If you use the email verification method, check your inbox for the verification message, then click Verify Your Domain.

DKIM Settings

After your domain is verified, check the DKIM Settings column. If it shows DKIM missing, click View details to see the DNS records you need to add.

Create the two required CNAME records in your domain DNS settings exactly as shown by Mandrill.

After adding the records, allow some time for DNS propagation, then return to Mandrill and test the DNS settings again.

Do the same for DMARC if it is not configured correctly. Add the required DNS record to your domain settings, wait for DNS propagation, then click Test DNS Settings.

Once the DNS records are verified successfully, you should see Authenticated in the Authentication Status column.

Creating Your API Key

In the Mandrill dashboard, go to Settings > SMTP & API Info, then click Add API key.

Copy the API key and save it somewhere secure. You will need it in the next step when configuring Mandrill in the DeliveryKit SMTP plugin.

Mandrill Setup in DeliveryKit SMTP Plugin

In your WordPress dashboard, go to DeliveryKit SMTP > Connections, then click Create New Connection.

Configure Connection

In the Configure Connection section, fill out the Connection Details fields:

Connection Details: Enter a name for this connection. This is only for you, recipients will not see it.

Default From Email: The email address used when an outgoing email does not define a From Email.

Force From Email: If enabled, this From Email will be used for all emails, even if the email has a different From Email.

Default From Name: The name used when an outgoing email does not define a From Name.

Force From Name: If enabled, this From Name will be used for all emails, even if the email has a different From Name.

Default Reply-To Email: The Reply-To address used when an outgoing email does not define a Reply-To Email.

Force Reply-To Email: If enabled, this Reply-To Email will be used for all emails, even if the email has a different Reply-To Email.

In the Choose a Mailer section, select Mandrill from the grid mailer list.

Mandrill Settings

In the Mandrill Settings section, paste your Mandrill API Key into the API key field.

Under Default Connection, check the option if you want this connection to be your default sender.

Then click Save Connection.

The connection will be added to the Connections list, and you should see Connection saved. at the top of the window.

Note: The free version allows you to add only one connection. If you need multiple connections, Conditional Routing, and many other features, you should purchase the DeliveryKit SMTP Pro.

Test Mandrill Connection

After saving your Mandrill connection, it is recommended to send a test email to make sure everything is working correctly. This helps confirm that your API Key, and connection settings have been entered properly and that your site can send emails successfully through Mandrill SMTP.

For step-by-step instructions, see the test connection guide here:

Test a DeliveryKit SMTP Connection.

]]> https://codemasterhub.com/doc/deliverykit-smtp-documentation/mandrill-smtp-setup/feed/ 0 MailerSend SMTP Setup https://codemasterhub.com/doc/deliverykit-smtp-documentation/mailersend-smtp-setup/ https://codemasterhub.com/doc/deliverykit-smtp-documentation/mailersend-smtp-setup/#respond Sat, 28 Mar 2026 14:18:37 +0000 https://codemasterhub.com/?post_type=doc&p=1516
Learn how to set up MailerSend in DeliveryKit SMTP for WordPress. Follow the step by step guide to connect MailerSend, configure sender settings, and test email delivery.

Table of Contents

What is MailerSend

MailerSend is a cloud based email delivery service designed for sending transactional emails reliably and securely. It provides SMTP and API options, along with tools for domain verification, sender management, analytics, and email delivery monitoring. In DeliveryKit SMTP, MailerSend can be used as your mailer to help send WordPress emails more consistently and with better deliverability.

Setting Up a MailerSend Account

To start, you need to create a MailerSend account if you do not have one already. Visit the MailerSend pricing page and choose the plan that best fits your needs.

In this example, we will use the Free plan. The setup steps are generally the same for other plans as well. Click Sign up under the Free plan to continue.

Fill in the signup form with your details, complete the verification step if required, then click Create my account to continue.

MailerSend will send a confirmation email to the address you used during signup. Open the email, then click Verify email address to confirm your email and activate your account.

Authorizing Your Domain

MailerSend provides test credentials that you can use if you want to try the service before adding your own domain. In this guide, we will skip that and add a sending domain instead. Verifying your sending domain confirms that you own it and helps improve email deliverability.

Adding Your Sending Domain

To add your sending domain, log in to your MailerSend account, then go to Email and click Domains.

On the Domains page, click Add domain to start adding your sending domain.

Enter your domain name, then click Add domain to continue.

If your DNS provider is supported, you can click Authorize with Cloudflare and let MailerSend add the DNS records automatically. If you prefer to add the records manually, click Show added DNS records, then copy and add those DNS records in your domain DNS settings.

After the required DNS records are added and detected, MailerSend will mark your domain as Verified. Once you see this status, your sending domain is ready to use.

API Key

To get your MailerSend API key, go to https://app.mailersend.com/api-tokens. You can also access it from your MailerSend dashboard by going to Integrations, then under MailerSend API, click Manage.

On the API tokens page, click Create new token to generate a new MailerSend API token.

Enter a name for the token, choose the domain you want to use, and select the appropriate permissions. In most cases, Sending access is enough for DeliveryKit SMTP. Then click Generate token.

Copy or download the API token and keep it somewhere safe. You will need it in the next step when configuring MailerSend in DeliveryKit SMTP for WordPress.

MailerSend Setup in DeliveryKit SMTP Plugin

In your WordPress dashboard, go to DeliveryKit SMTP > Connections, then click Create New Connection.

Configure Connection

In the Configure Connection section, fill out the Connection Details fields:

Connection Details: Enter a name for this connection. This is only for you, recipients will not see it.

Default From Email: The email address used when an outgoing email does not define a From Email.

Force From Email: If enabled, this From Email will be used for all emails, even if the email has a different From Email.

Default From Name: The name used when an outgoing email does not define a From Name.

Force From Name: If enabled, this From Name will be used for all emails, even if the email has a different From Name.

Default Reply-To Email: The Reply-To address used when an outgoing email does not define a Reply-To Email.

Force Reply-To Email: If enabled, this Reply-To Email will be used for all emails, even if the email has a different Reply-To Email.

In the Choose a Mailer section, select MailerSend from the grid mailer list.

MailerSend Settings

Enter your MailerSend API Key in the matching field. Enable Professional Plan only if your MailerSend account is on a paid plan that supports those features, not on the free plan. If you want to use this connection as the main mailer for your website, check Make this the default connection. Then click Save Connection.

The connection will be added to the Connections list, and you should see Connection saved. at the top of the window.

Note: The free version allows you to add only one connection. If you need multiple connections, Conditional Routing, and many other features, you should purchase the DeliveryKit SMTP Pro.

Test MailerSend Connection

After saving your MailerSend connection, it is recommended to send a test email to make sure everything is working correctly. This helps confirm that your API Token, and connection settings have been entered properly and that your site can send emails successfully through MailerSend SMTP.

For step-by-step instructions, see the test connection guide here:

Test a DeliveryKit SMTP Connection.

]]> https://codemasterhub.com/doc/deliverykit-smtp-documentation/mailersend-smtp-setup/feed/ 0 Mailjet SMTP Setup https://codemasterhub.com/doc/deliverykit-smtp-documentation/mailjet-smtp-setup/ https://codemasterhub.com/doc/deliverykit-smtp-documentation/mailjet-smtp-setup/#respond Sat, 28 Mar 2026 10:21:33 +0000 https://codemasterhub.com/?post_type=doc&p=1486
Learn how to set up Mailjet SMTP in DeliveryKit SMTP for WordPress. Follow the step by step guide to connect Mailjet, configure sender settings, and test email delivery.

Table of Contents

What is Mailjet?

Mailjet is an email delivery service that lets you send transactional and marketing emails through a reliable cloud platform. It provides SMTP and API options for sending emails, along with tools for managing senders, monitoring delivery, and improving email performance. In DeliveryKit SMTP, Mailjet can be used as your mailer to help send WordPress emails more securely and consistently.

Setting Up a Mailjet Account

To get started with Mailjet, visit the Mailjet pricing page and click the Get started button on the Free plan. At the time of writing, Mailjet offers a free plan that includes up to 6,000 emails per month, with a limit of 200 emails per day, which is a good option for testing or small websites.

Fill in the sign up form with your details, then click Create account to continue.

On the plan selection page, choose the Free plan, then click Select Plan to continue.

Mailjet will send a confirmation email to the address you used during signup. Open the email, then click Activate my account to verify your email address and activate your Mailjet account.

Authenticating Your Domain

Before you can start sending emails through Mailjet, you need to authenticate your domain. This confirms that you own the domain you want to send from and helps improve email deliverability.

Adding Your Sending Domain

In your Mailjet dashboard, click your account menu in the top right corner, then select Account settings.

Under Senders and Domains, click Add a domain or sender address to start adding your sending domain.

Scroll down to the Domains section, then click Add domain.

Enter your domain name, optionally add a label for easier identification, then click Add.

Mailjet gives you multiple ways to validate your domain. You can either upload a temporary empty file to your website, add the provided DNS record to your domain settings, or use Configure automatically if your DNS provider is supported. After completing one of these methods, click Validate my domain.

After your domain is validated, click Authenticate this domain (SPF/DKIM) to continue with domain authentication.

Domain Authentication Setup

Add the SPF and DKIM records shown by Mailjet to your DNS settings. For the SPF record, if your domain already has an existing SPF TXT record, do not create a second one. Instead, add the include:spf.mailjet.com part to your current SPF record. After saving the DNS changes, return to Mailjet and click Refresh.

Once Mailjet shows that both SPF and DKIM look good, your domain authentication is complete.

API Key

To connect your site with Mailjet, you need both your API Key and Secret Key. In your Mailjet dashboard, open the API menu in the left sidebar, then click API Key Management.

Mailjet already provides a default Primary API Key. Next to it, click Generate Secret Key to create the Secret Key you will need for DeliveryKit SMTP.

Copy both the API Key and Secret Key and save them somewhere safe. You will need both of them in the next step when configuring Mailjet in WordPress.

Mailjet Setup in DeliveryKit SMTP Plugin

In your WordPress dashboard, go to DeliveryKit SMTP > Connections, then click Create New Connection.

Configure Connection

In the Configure Connection section, fill out the Connection Details fields:

Connection Details: Enter a name for this connection. This is only for you, recipients will not see it.

Default From Email: The email address used when an outgoing email does not define a From Email.

Force From Email: If enabled, this From Email will be used for all emails, even if the email has a different From Email.

Default From Name: The name used when an outgoing email does not define a From Name.

Force From Name: If enabled, this From Name will be used for all emails, even if the email has a different From Name.

Default Reply-To Email: The Reply-To address used when an outgoing email does not define a Reply-To Email.

Force Reply-To Email: If enabled, this Reply-To Email will be used for all emails, even if the email has a different Reply-To Email.

In the Choose a Mailer section, select Mailjet from the grid mailer list.

Mailjet Settings

Paste your Mailjet API Key and Mailjet Secret Key into the matching fields. If you want to use this connection as the main mailer for your website, check Make this the default connection. Then click Save Connection.

The connection will be added to the Connections list, and you should see Connection saved. at the top of the window.

Note: The free version allows you to add only one connection. If you need multiple connections, Conditional Routing, and many other features, you should purchase the DeliveryKit SMTP Pro.

Test Mailjet Connection

After saving your Mailjet connection, it is recommended to send a test email to make sure everything is working correctly. This helps confirm that your API Key , Secret Key, and connection settings have been entered properly and that your site can send emails successfully through Mailjet SMTP.

For step-by-step instructions, see the test connection guide here:

Test a DeliveryKit SMTP Connection.

]]> https://codemasterhub.com/doc/deliverykit-smtp-documentation/mailjet-smtp-setup/feed/ 0 Mailgun SMTP Setup https://codemasterhub.com/doc/deliverykit-smtp-documentation/mailgun-smtp-setup/ https://codemasterhub.com/doc/deliverykit-smtp-documentation/mailgun-smtp-setup/#respond Fri, 27 Mar 2026 10:46:45 +0000 https://codemasterhub.com/?post_type=doc&p=1438
Learn how to configure Mailgun SMTP in DeliveryKit SMTP for WordPress and send reliable transactional emails using Mailgun’s secure SMTP relay service.

Table of Contents

What is Mailgun?

Mailgun is an email delivery platform built for developers and businesses that need to send, receive, and track emails at scale. It offers tools for transactional email delivery, analytics, and email infrastructure, with support for both API-based sending and standard SMTP sending.

Mailgun SMTP is Mailgun’s SMTP relay service, which lets you send emails through Mailgun without running your own mail server. It uses domain-based SMTP credentials, supports TLS, and works with apps, websites, and plugins that send email through standard SMTP authentication, which makes it a practical option for WordPress sites using DeliveryKit SMTP.

Creating a Mailgun Account

To create a new Mailgun account, open the Mailgun signup page:

https://signup.mailgun.com/new/signup

  1. Enter your Full Name.
  2. Enter your Company name.
  3. Enter your Work Email address.
  4. Create your Password.
  5. Confirm your Password.
  6. Click the Create Account button to continue.

Note: Uncheck Add payment info now if you want to start with the free plan that allows up to 100 messages per day.

Verify Your Email Address

After creating your Mailgun account, Mailgun will send a verification email to the address you used during signup.

  1. Open your email inbox.
  2. Find the email from Mailgun with the account verification message.
  3. Open the email and click the Verify your email address button.

Note: If you do not see the email, check your spam or junk folder.

Verify Your Phone Number

After verifying your email address, Mailgun will ask you to complete account verification by SMS.

  1. Select your country code.
  2. Enter your mobile phone number.
  3. Click the Send Verification Code button.
  4. Check your phone for the SMS verification code.
  5. Enter the code to complete the verification process.

Note: Mailgun requires phone verification to help prevent abuse and secure new accounts.

Adding a Domain

After completing account verification, you need to add your sending domain in Mailgun.

  1. In your Mailgun dashboard, click Send in the left sidebar.
  2. Click Domains.
  3. Click the Add new domain button.

This will open the domain setup screen, where you can add and configure your domain for sending emails.

Add new domain

On the Add new domain screen, enter the domain you want to use with Mailgun.

  1. In the Domain name field, enter your domain or subdomain.
  2. Select your Domain region.
  3. Choose your IP assignment option.
  4. Review the Advanced settings if needed.
  5. Click the Add Domain button.

Note: Mailgun recommends using a subdomain such as mg.yourdomain.com. Using a subdomain can still allow you to send emails from your root domain, depending on your configuration.

Important: If you use a subdomain, make sure to configure the MX records for that subdomain for optimal delivery.

Domain settings

After adding your domain, Mailgun will open the Domain settings page, where you can configure the required DNS records.

You can choose one of these setup methods:

  • Automatic setup: Click Log in to your provider and let Mailgun add the DNS records automatically, if your DNS provider is supported.
  • Manual setup: Copy the required DNS records from Mailgun and add them manually in your domain DNS zone.

Under the DNS records tab, Mailgun will display the records you need to add, such as SPF and DKIM.

Note: If you prefer full control or your DNS provider is not supported for automatic setup, use the manual setup option and enter the records yourself.

The screenshot below shows the Mailgun DNS records added manually in Cloudflare. Make sure the CNAME record is set to DNS only and is not proxied.

Check domain status

After adding the DNS records to your domain, return to the Mailgun Domain settings page and click the Check status button.

Mailgun will verify the records and update the domain status after the DNS changes are detected.

If the domain verification is successful, you will see a green check icon next to the domain name, and the DNS records in the table will show statuses such as Verified or Active.

Create Mailgun API Key

To create a Mailgun API key, click the arrow next to your profile name in the top right corner to open the account menu, then click API Security.

On the API keys page, click the Create key button.

In the popup, enter a description for the API key, for example API Key for DeliveryKit SMTP Plugin, then click Create Key.

Copy the API key and save it in a safe place. You will need it in the next step when configuring Mailgun in the DeliveryKit SMTP plugin.

Mailgun Setup in DeliveryKit SMTP Plugin

In your WordPress dashboard, go to DeliveryKit SMTP > Connections, then click Create New Connection.

Configure Connection

In the Configure Connection section, fill out the Connection Details fields:

Connection Details: Enter a name for this connection. This is only for you, recipients will not see it.

Default From Email: The email address used when an outgoing email does not define a From Email.

Force From Email: If enabled, this From Email will be used for all emails, even if the email has a different From Email.

Default From Name: The name used when an outgoing email does not define a From Name.

Force From Name: If enabled, this From Name will be used for all emails, even if the email has a different From Name.

Default Reply-To Email: The Reply-To address used when an outgoing email does not define a Reply-To Email.

Force Reply-To Email: If enabled, this Reply-To Email will be used for all emails, even if the email has a different Reply-To Email.

In the Choose a Mailer section, select Mailgun from the grid mailer list.

Mailgun Settings

In the Mailgun Settings section, enter your Mailgun details:

  • Mailgun API Key: Paste the API key you copied from your Mailgun account.
  • Domain Name: Enter the Mailgun sending domain you added and verified.
  • Region: Select the Mailgun region that matches your account, either US or EU.

If you want to use this connection as your main mailer, enable Make this the default connection under Default Connection.

After entering the details, click the Save Connection button.

The connection will be added to the Connections list, and you should see Connection saved. at the top of the window.

Note: The free version allows you to add only one connection. If you need multiple connections, Conditional Routing, and many other features, you should purchase the DeliveryKit SMTP Pro.

Test Mailgun Connection

After saving your Mailgun connection, it is recommended to send a test email to make sure everything is working correctly. This helps confirm that your API Key , and connection settings have been entered properly and that your site can send emails successfully through Mailgun SMTP.

For step-by-step instructions, see the test connection guide here:

Test a DeliveryKit SMTP Connection.

]]> https://codemasterhub.com/doc/deliverykit-smtp-documentation/mailgun-smtp-setup/feed/ 0 Elastic Email SMTP Setup https://codemasterhub.com/doc/deliverykit-smtp-documentation/elastic-email-smtp-setup/ https://codemasterhub.com/doc/deliverykit-smtp-documentation/elastic-email-smtp-setup/#respond Wed, 25 Mar 2026 10:58:15 +0000 https://codemasterhub.com/?post_type=doc&p=1402
Learn how to set up Elastic Email SMTP in DeliveryKit SMTP for WordPress and send emails through a reliable SMTP relay with better deliverability and easy configuration.

Table of Contents

What is Elastic Email SMTP

Elastic Email is an email communication platform that offers tools for email marketing, transactional email sending, and integrations through API and SMTP. It is designed to help businesses send newsletters, automated emails, and system-generated messages from one platform.

Elastic Email SMTP is Elastic Email’s SMTP relay service, which lets you send emails from your website, server, or application using standard SMTP credentials. In WordPress, it can be used with DeliveryKit SMTP to route outgoing emails through Elastic Email for easier setup, domain-based sending, and access to delivery logs and performance tracking.

Creating an Elastic Email Account

To create your Elastic Email account, open the Elastic Email Email API pricing page and make sure the Email API tab is selected. Then click the Try for Free button to begin the registration process.

Elastic Email offers a free plan for testing basic features with limited sending, so you can get started without choosing a paid plan right away. A credit card is not required unless you want to upgrade to a paid plan later.

After you sign up, Elastic Email will send a verification email to the address you used during registration. Once you verify your email address and log in to your account, you can access the dashboard and continue with the SMTP setup in DeliveryKit SMTP.

Enter Your Details

On the signup page, you can create your Elastic Email account by entering your details in the form. You can also choose to sign up with your Google account if you prefer.

Enter your email address, create a password, then fill in your first name and last name. After that, check the box to agree to the Terms of Use.

You can also choose whether you want to receive emails about new products, best practices, or special offers. This option is optional, so you can leave it unchecked if you do not want promotional emails.

Complete the reCAPTCHA verification, then click the Sign up button to create your account.

Tell Elastic Email About Your Business

After creating your account, Elastic Email will ask a few basic questions about your business. This step helps personalize your account setup and dashboard experience.

Select the industry that best describes your business, then choose the number of employees in your organization.

Once you have selected the appropriate options, click the Continue button to move to the next step.

Answer the Onboarding Questions

Elastic Email will now ask how you heard about their service and what made you choose it. Select the answers that best match your situation.

If you choose Other for the second question, you can also enter a short custom message in the optional text field.

After completing both questions, click the Continue button to proceed.

Complete the Final Onboarding Survey

Elastic Email will ask a few final questions about your goals, your experience with email marketing, and whether you have used another email marketing provider before.

Select the options that best match your needs. You can choose one or more goals, then select your experience level and indicate whether you are new to email marketing or moving from another provider.

After completing the survey, click the Finish survey button to continue to your Elastic Email account dashboard.

Verifying Your Domain

Before using Elastic Email SMTP in DeliveryKit SMTP, you should verify your sending domain in your Elastic Email account. Domain verification helps confirm that you own the domain and improves email deliverability.

In the Elastic Email dashboard, open the left sidebar and click Settings. In the Domains section, click Manage domains to start the domain setup process.

On the next screen, you can add your domain and follow the verification steps provided by Elastic Email.

Start Domain Verification

On the Domains page, make sure the Domain verification tab is selected. Then click the Start Verification button in the top right corner. This will begin the process of adding and verifying your domain in Elastic Email.

Choose Domain Verification

Elastic Email will show two verification options. Since you want to verify your sending domain, click the Verify domain button under the I own a domain option.

This is the recommended option because it allows you to use email addresses from your domain as the From Email address and helps improve deliverability.

Enter Your Domain

In the Domain field, enter the domain name you want to verify, such as codemasterhub.com.

After entering your domain, click the Continue button to move to the next step.

Log In to Your Domain Provider

Elastic Email will now ask you to log in to the platform where your domain is managed. This is usually your domain registrar, hosting provider, or DNS provider.

Open your domain provider in a new browser tab, then find the DNS management area for your domain. This may be labeled as DNS settings, DNS zone, or DNS records.

Once you are ready to add the required DNS records, return to Elastic Email and click Continue.

Check for an Existing SPF Record

Elastic Email will first ask you to check whether your domain already has an SPF record in its DNS settings.

Look for a TXT record for your domain that starts with v=spf1. This is your SPF record. Elastic Email uses this check to decide the correct next step for your domain verification setup.

If you do not see an SPF TXT record, select I did not find the record described above. If you already have one, select I found the record described above.

Merge Elastic Email Into Your Existing SPF Record

If your domain already has an SPF record, do not create a second SPF record. Instead, edit your existing TXT record and merge the Elastic Email value into it.

Elastic Email will show you the value that needs to be added to your current SPF record:

include:_spf.elasticemail.com

For example, if your existing SPF record is:

v=spf1 a mx include:_spf.google.com ~all

After adding Elastic Email, it should look like this:

v=spf1 a mx include:_spf.elasticemail.com include:_spf.google.com ~all

Make sure everything stays in a single SPF TXT record. Do not split it into multiple SPF records, because that can cause verification and deliverability problems.

Add the Recommended DNS Records and Verify

After completing the SPF step, Elastic Email will also show additional recommended records, such as DKIM, CNAME, and DMARC.

Open each section and add the required DNS records in your domain’s DNS settings exactly as provided by Elastic Email. These records help improve domain authentication, sending reputation, and email deliverability.

Once you have added all required and recommended DNS records, return to Elastic Email and click Verify record.

Continue to the Next Step

After your required SPF record is verified, Elastic Email will mark it as completed.

If you have also added the recommended records, you can click Re-verify domain to check them again. Once you are ready to continue, click Next.

Domain Verification Completed

If your domain verification is successful, Elastic Email will show a confirmation message letting you know that your domain is verified.

At this point, you can send emails from any address that uses your verified domain, such as company@codemasterhub.com or info@codemasterhub.com.

Click Continue to finish the domain verification process and move on to the next step.

Set a Default Sender

Elastic Email will now ask you to set a default sender address for your verified domain. This will be used as the default From email address for sending.

Enter the local part of the email address in the field, for example mail, which will create the full sender address mail@codemasterhub.com.

After entering the sender name, click Set default sender. If you do not want to do this right now, click Not right now.

Finish the Domain Setup

Elastic Email will show a success message confirming that your domain is verified and that the default sender has been set.

Once you see this confirmation, click Finish to complete the domain setup process.

Create API Key

To create an API key in Elastic Email, go to Settings in the left sidebar. In the API section, click Create additional API key.

This will open the API key creation screen, where you can generate a new key for use with Elastic Email and DeliveryKit SMTP.

Create a New API Key

On the API key creation page, enter a name for the key, such as DeliveryKit SMTP.

In the Permissions section, select Plugin. This option is intended for typical third-party plugin integrations and is suitable for DeliveryKit SMTP.

You can also set an expiration date or access restriction if needed, but these options are optional.

When everything is ready, click Create to generate the API key.

Copy the API Key

Elastic Email will now show your newly created API key.

Copy this API key and save it in a safe place. You will need it later in the DeliveryKit SMTP plugin settings when configuring the Elastic Email connection.

Important: once you close this window, Elastic Email will not show this API key again.

After copying the key, click Close.

Elastic Email Setup in DeliveryKit SMTP Plugin

In your WordPress dashboard, go to DeliveryKit SMTP > Connections, then click Create New Connection.

Configure Connection

In the Configure Connection section, fill out the Connection Details fields:

Connection Details: Enter a name for this connection. This is only for you, recipients will not see it.

Default From Email: The email address used when an outgoing email does not define a From Email.

Force From Email: If enabled, this From Email will be used for all emails, even if the email has a different From Email.

Default From Name: The name used when an outgoing email does not define a From Name.

Force From Name: If enabled, this From Name will be used for all emails, even if the email has a different From Name.

Default Reply-To Email: The Reply-To address used when an outgoing email does not define a Reply-To Email.

Force Reply-To Email: If enabled, this Reply-To Email will be used for all emails, even if the email has a different Reply-To Email.

In the Choose a Mailer section, select Elastic Email  from the grid mailer list.

Elastic Email Settings

In the Elastic Email Settings section, paste the Elastic Email API key you created earlier into the Elastic Email API Key field.

Make sure the From Email address configured above is already verified in your Elastic Email account.

If you want to use this connection as your main mailer, enable Make this the default connection under Default Connection.

When everything is ready, click Save Connection.

The connection will be added to the Connections list, and you should see Connection saved. at the top of the window.

Note: The free version allows you to add only one connection. If you need multiple connections, Conditional Routing, and many other features, you should purchase the DeliveryKit SMTP Pro.

Test Elastic Email Connection

After saving your Elastic Email connection, it is recommended to send a test email to make sure everything is working correctly. This helps confirm that your API Key , and connection settings have been entered properly and that your site can send emails successfully through Elastic Email SMTP.

For step-by-step instructions, see the test connection guide here:

Test a DeliveryKit SMTP Connection.

]]> https://codemasterhub.com/doc/deliverykit-smtp-documentation/elastic-email-smtp-setup/feed/ 0 SendGrid SMTP Setup https://codemasterhub.com/doc/deliverykit-smtp-documentation/sendgrid-smtp-setup/ https://codemasterhub.com/doc/deliverykit-smtp-documentation/sendgrid-smtp-setup/#respond Tue, 24 Mar 2026 11:01:55 +0000 https://codemasterhub.com/?post_type=doc&p=1376
Set up SendGrid in DeliveryKit SMTP with step-by-step instructions for creating an API key, configuring sender details, connecting your mailer, and sending a test email successfully.

Table of Contents

What is SendGrid SMTP

SendGrid is an email delivery service that lets your website or application send messages through SendGrid’s SMTP relay instead of relying on your web server’s default mail system. It is commonly used to improve delivery reliability, support authenticated sending, and manage transactional emails such as contact form messages, account emails, and order notifications.

Create a SendGrid Account

Start by creating your SendGrid account from the official pricing page.

  1. Open
    SendGrid Pricing
    and choose the plan you want. You can start with the free trial if it fits your needs.
  2. Continue to the account creation form and enter your basic details:
    your name, email address, and password.
  3. Check your inbox for the SendGrid verification message, then enter the confirmation code to verify your email address.
  4. Complete phone verification for account security and 2FA setup. Select your country code, enter your phone number, choose SMS or voice call, then enter the verification code you receive.
  5. After verification is complete, sign in to your SendGrid account dashboard and continue with the next setup steps.

Single Sender Verification

Add a Single Sender to Your SendGrid Account

If you want to verify one approved sending address in SendGrid, you can use the Single Sender option.

To begin, log in to your SendGrid dashboard and go to Settings > Sender Authentication. In the Single Sender Verification section, click Get Started.

Create a Sender

After clicking the Create New Sender button, SendGrid will open the Create a Sender form. Here, you need to enter the sender details that will be used for verification.

  • From Name: Enter the name you want recipients to see.
  • From Email Address: Enter the email address you want to verify.
  • Reply To: Enter the email address where replies should be sent.
  • Company Address: Enter your physical mailing address.
  • Company Address Line 2: Add extra address details if needed, this field is optional.
  • City: Enter your city.
  • State: Select your state or region.
  • Zip Code: Enter your postal code.
  • Country: Select your country.
  • Nickname: Add an internal name to help you identify this sender later in your SendGrid account.

Once all required fields are completed, click Create to save your sender profile.

Verify Your Single Sender Email

After you create the sender, SendGrid will show a confirmation message and send a verification email to the address you entered.

Open your inbox, find the verification email from SendGrid, and click the verification link inside it. This step is required before the sender can be used for sending emails.

If you do not receive the email right away, check your spam or junk folder. You can also click the Resend email button in SendGrid to send the verification email again.

Once the email address is verified, your Single Sender Identity will be ready to use in SendGrid.

After completing the verification, you will see a confirmation message showing that your sender identity has been verified successfully.

Authenticating Your Domain in SendGrid

Domain authentication confirms that your emails are sent from a domain you own and control. This helps build your domain’s reputation as a trusted sending source and can improve email deliverability. It also removes the “via sendgrid.net” notice that may otherwise appear in your outgoing emails.

Sender Authentication

To get started, log in to your SendGrid dashboard and go to Settings > Sender Authentication. In the Domain Authentication section, click Authenticate Your Domain.

Authenticate Your Domain

On the Authenticate Your Domain screen, select your DNS provider from the DNS host dropdown. If your provider is not listed, choose Other Host (Not Listed) and enter your DNS host name if requested.

Next, choose whether you want to brand the links for this domain. For most setups, you can leave Yes selected. Then click Next to continue.

Enter Your Domain Details

On the next screen, enter the domain you want to send emails from in the From Domain field. This should be your own domain name, such as example.com.

Under Advanced Settings, enable Use custom return path. In the Return Path field, enter a simple subdomain value such as sub. SendGrid will use this to generate the DNS records needed for domain authentication.

After entering your domain details, click Next to continue.

Install DNS Records

SendGrid will now display the DNS records required for domain authentication. Open your DNS manager, usually in your domain registrar, hosting panel, or DNS provider, and add each record exactly as shown in SendGrid.

  • Copy the Type, Host, and Value for each record.
  • Add every required record to your domain’s DNS zone.
  • Do not change the record names or values unless your DNS provider requires a different host format.
  • If your DNS provider automatically appends your domain name, enter only the host prefix instead of the full domain.

When all records have been added, return to SendGrid and continue to the verification step.

After adding all the required DNS records to your domain, return to your SendGrid dashboard and check the box labeled I have added these records. Then click the Verify button.

DNS changes can take up to 48 hours to fully propagate, so if verification does not work right away, wait a while and try again later. Once the records are detected successfully, you will see a confirmation message showing that your domain has been authenticated.

Generating an API Key

After creating your SendGrid account and setting up your sender identity, the next step is to generate an API key so DeliveryKit SMTP can connect to SendGrid and send emails from your website.

In your SendGrid dashboard, go to Email API > Integration Guide from the left menu. On the setup method screen, locate the SMTP Relay option and click Choose to continue.

On the SMTP Relay setup screen, enter a name for your new API key in the My First API Key Name field. This name is only for your own reference, so you can use something clear such as DeliveryKit SMTP. Then click the Create Key button to generate your SendGrid API key.

SendGrid will now generate your API key. Keep this page open, as you will need to copy and use this API key in a later step.

Sendgrid Setup in DeliveryKit SMTP Plugin

In your WordPress dashboard, go to DeliveryKit SMTP > Connections, then click Create New Connection.

Configure Connection

In the Configure Connection section, fill out the Connection Details fields:

Connection Details: Enter a name for this connection. This is only for you, recipients will not see it.

Default From Email: The email address used when an outgoing email does not define a From Email.

Force From Email: If enabled, this From Email will be used for all emails, even if the email has a different From Email.

Default From Name: The name used when an outgoing email does not define a From Name.

Force From Name: If enabled, this From Name will be used for all emails, even if the email has a different From Name.

Default Reply-To Email: The Reply-To address used when an outgoing email does not define a Reply-To Email.

Force Reply-To Email: If enabled, this Reply-To Email will be used for all emails, even if the email has a different Reply-To Email.

In the Choose a Mailer section, select Sendgrid  from the grid mailer list.

SendGrid Settings

In the SendGrid Settings section, paste your SendGrid API key into the SendGrid API Key field.

Next, enter your verified domain or subdomain in the Sending Domain field. This field is optional, but it is recommended to use a verified sending domain for better deliverability and alignment with your SendGrid setup.

Default Connection: Enable this option if you want this connection to be the default sender for your WordPress website.

When you are done, click Save Connection.

The connection will be added to the Connections list, and you should see Connection saved. at the top of the window.

Note: The free version allows you to add only one connection. If you need multiple connections, Conditional Routing, and many other features, you should purchase the DeliveryKit SMTP Pro.

Test Sendgrid Connection

After saving your Sendgrid connection, it is recommended to send a test email to make sure everything is working correctly. This helps confirm that your API Key , and connection settings have been entered properly and that your site can send emails successfully through Sendgrid SMTP.

For step-by-step instructions, see the test connection guide here:

Test a DeliveryKit SMTP Connection.

]]> https://codemasterhub.com/doc/deliverykit-smtp-documentation/sendgrid-smtp-setup/feed/ 0 Amazon AWS SMTP Setup https://codemasterhub.com/doc/deliverykit-smtp-documentation/amazon-aws-smtp-setup/ https://codemasterhub.com/doc/deliverykit-smtp-documentation/amazon-aws-smtp-setup/#respond Tue, 10 Mar 2026 08:39:39 +0000 https://codemasterhub.com/?post_type=doc&p=1328
Set up Amazon AWS SMTP in DeliveryKit SMTP for WordPress to send emails securely and improve deliverability with a reliable AWS mail connection.

Table of Contents

What is Amazon AWS SES

Amazon AWS SES, short for Amazon Simple Email Service, is a cloud-based email sending service from Amazon Web Services that helps websites, apps, and businesses send transactional and marketing emails at scale. It is designed to provide reliable delivery, flexible sending options, and tools for managing sender identity, authentication, reputation, and performance. With Amazon SES, you can send messages such as verification emails, password resets, order updates, contact form notifications, and other important website emails through Amazon’s infrastructure instead of relying on standard web hosting mail.

Amazon AWS SMTP refers to using Amazon SES through the SMTP protocol, which allows email clients, plugins, and applications to connect to SES just like a traditional SMTP mail server. Instead of using the Amazon SES API directly, you generate SMTP credentials in your AWS account and use them in your mailer settings to send email through Amazon’s servers. This makes Amazon AWS SMTP a practical option for WordPress plugins such as DeliveryKit SMTP, because it allows you to connect Amazon SES easily while improving deliverability, reliability, and sending control.

Configuring an Amazon AWS Account

Before you begin, you will need to create a free Amazon Web Services (AWS) account. Although the account itself is free and this mailer setup does not require any paid AWS services, Amazon will still ask you to add a valid credit card during the registration process.

After your AWS account is created, Amazon will try to detect your region automatically based on the address you entered. If the system cannot determine your region with confidence, you will be asked to select the closest available region manually before continuing.

Creating an IAM User

After creating your Amazon Web Services account, the next step is to create an IAM user. This user will later provide the access keys required for your Amazon AWS SMTP setup.

To get started, open the AWS IAM Users page:
https://console.aws.amazon.com/iam/home#users

On this page, click the Create user button to continue.

On the Specify user details page, enter a User name.

Recommended format: yourdomain_deliverykitsmtp

After entering the user name, click Next.

On the Set permissions page, select Attach policies directly.

In the search bar, type AmazonSESFullAccess. You should see one result with the same name. Select the checkbox next to this option to grant the user permission to access Amazon SES.

When you are ready, click Next to proceed.

On the next page, you will see a summary of all the details you selected for this user. Review the information to make sure everything is correct, then click Create user.

You will be redirected to the Users list, where you will see a User created successfully message.

On the Users page, click the User name of the user you created to continue.

From the tabs displayed on this page, click Security credentials.

Then scroll down to the Access keys section and click Create access key.

For the Access key best practices & alternatives section, select Other.

Then click Next.

On the next page, you can leave the description tag empty and click Create access key to proceed.

AWS will now display a success message along with the Access key ID and Secret access key for your user. Be sure to securely save a copy of these keys before leaving this page.

Switching AWS to Production Mode

All Amazon SES accounts are placed in Sandbox Mode by default. This is limiting because your account will have a low monthly sending quota and can send emails only to email addresses that have been verified in Amazon SES.

To send emails more freely and increase your sending quota, you will need to move your Amazon SES account from Sandbox Mode to Production Mode.

Keep the Access Keys tab open, then open the Amazon Service Quotas dashboard in a new tab:

https://console.aws.amazon.com/servicequotas/

Selecting Your Region

After opening the dashboard, click the Select a Region dropdown and choose your region from the list. Be sure to select the same region you used when setting up your Amazon AWS account.

Requesting a Quota Increase

To request an increase to your monthly email sending limit, click AWS services in the sidebar menu.

Then type Amazon Simple Email Service into the search bar.

You should see a single result named Amazon Simple Email Service (Amazon SES). Click this option to continue.

On the next page, select the option next to Sending quota to begin the request for a quota increase.

Then click Request quota increase.

A Case classification form will then appear for you to review and complete. This is an important step because Amazon uses this form to help prevent spam and to confirm that your website will be sending emails for legitimate purposes.

In the Change quota value field, enter your desired daily sending quota. For example, you can request a daily sending quota of 400 emails.

Click Request

Immediately after submitting the request, you should receive two emails from Amazon Web Services. Both emails simply confirm that a new support case has been created.

AWS usually reviews these requests within one business day. While you wait for the result, you can continue with the next setup steps.

Amazon SES Setup in DeliveryKit SMTP Plugin

In your WordPress dashboard, go to DeliveryKit SMTP > Connections, then click Create New Connection.

Configure Connection

In the Configure Connection section, fill out the Connection Details fields:

Connection Details: Enter a name for this connection. This is only for you, recipients will not see it.

Default From Email: The email address used when an outgoing email does not define a From Email.

Force From Email: If enabled, this From Email will be used for all emails, even if the email has a different From Email.

Default From Name: The name used when an outgoing email does not define a From Name.

Force From Name: If enabled, this From Name will be used for all emails, even if the email has a different From Name.

Default Reply-To Email: The Reply-To address used when an outgoing email does not define a Reply-To Email.

Force Reply-To Email: If enabled, this Reply-To Email will be used for all emails, even if the email has a different Reply-To Email.

In the Choose a Mailer section, select Amazon SES (AWS)  from the grid mailer list.

Amazon SES Settings

Copy the Access Key ID and Secret Access Key from the Amazon AWS Access keys tab, then paste them into the corresponding fields in the Amazon SES Settings section.

Region: Enter the exact AWS region you selected earlier in your Amazon AWS account.

Default Connection: Enable this option if you want this connection to be the default sender for your WordPress website.

Then click Save Connection.

The connection will be added to the Connections list, and you should see Connection saved. at the top of the window.

Note: The free version allows you to add only one connection. If you need multiple connections, Conditional Routing, and many other features, you should purchase the DeliveryKit SMTP Pro.

Test Amazon SES Connection

After saving your Amazon SES connection, it is recommended to send a test email to make sure everything is working correctly. This helps confirm that your Access Key ID , Secret Access Key , and connection settings have been entered properly and that your site can send emails successfully through Amazon SES SMTP.

For step-by-step instructions, see the test connection guide here:

Test a DeliveryKit SMTP Connection.

]]> https://codemasterhub.com/doc/deliverykit-smtp-documentation/amazon-aws-smtp-setup/feed/ 0 Outlook SMTP Setup https://codemasterhub.com/doc/deliverykit-smtp-documentation/outlook-smtp-setup/ https://codemasterhub.com/doc/deliverykit-smtp-documentation/outlook-smtp-setup/#respond Mon, 09 Mar 2026 15:35:14 +0000 https://codemasterhub.com/?post_type=doc&p=1310
Set up Outlook SMTP in DeliveryKit SMTP for WordPress with this step by step guide. Learn how to create the connection, configure Microsoft email settings, and test email delivery.

Table of Contents

What Is the Microsoft 365 / Outlook.com Mailer?

The Microsoft 365 / Outlook.com Mailer lets your WordPress site send email through Microsoft’s mail servers by using a Microsoft 365 business account or an Outlook.com account. In DeliveryKit SMTP, this mailer can be used for transactional emails such as contact form messages, password resets, notifications, and other website emails.

Microsoft supports authenticated SMTP for both Microsoft 365 and Outlook.com accounts, and Microsoft 365 environments may also use SMTP relay in some setups. This gives you a trusted sending infrastructure backed by Microsoft for outgoing email delivery.

To create the app required for Outlook / Microsoft 365 setup, sign in to the Microsoft Azure portal.

Setting Up Outlook in DeliveryKit SMTP

In your WordPress dashboard, go to DeliveryKit SMTP > Connections, then click Create New Connection.

Configure Connection

In the Configure Connection section, fill out the Connection Details fields:

Connection Details: Enter a name for this connection. This is only for you, recipients will not see it.

Default From Email: The email address used when an outgoing email does not define a From Email.

Force From Email: If enabled, this From Email will be used for all emails, even if the email has a different From Email.

Default From Name: The name used when an outgoing email does not define a From Name.

Force From Name: If enabled, this From Name will be used for all emails, even if the email has a different From Name.

Default Reply-To Email: The Reply-To address used when an outgoing email does not define a Reply-To Email.

Force Reply-To Email: If enabled, this Reply-To Email will be used for all emails, even if the email has a different Reply-To Email.

In the Choose a Mailer section, select 365 / Outlook  from the grid mailer list.

Configuring a Microsoft Azure Account

To create a Microsoft Azure account, go to:

https://azure.microsoft.com/en-us/free/

Then click Try Azure for free.

If you are asked to sign in, log in with your Microsoft account.

If you do not already have an Azure account, you will be redirected to the Create your Azure free account page. Complete the required fields and follow the on-screen steps to create your account.

Create an Application ID

To create the Application ID required for the Outlook mailer, sign in to your Microsoft Azure account and open the Azure portal.

In the top search bar, search for App registrations, then click it from the results.

On the App registrations page, click New registration.

In the registration form, enter a name for your application. This name is only for your own reference in Microsoft Azure.

Under Supported account types, select Accounts in any organizational directory and personal Microsoft accounts.

If this option is not available in your account, select Accounts in any organizational directory instead.

In the Redirect URI section, choose Web from the platform dropdown.

Authorized Redirect URI: Copy the redirect URI shown in your DeliveryKit SMTP Outlook settings and paste it into the URI field.

After completing the form, click Register.

Once the app is created, you will be redirected to the Overview page.

There, locate the Application (client) ID and copy it. You will use this value in the next steps inside DeliveryKit SMTP.

In the Microsoft 365 / Outlook Settings section, paste the Application (Client) ID, Directory (Tenant) ID, and Client Secret you copied earlier.

Default Connection: Enable this option if you want this connection to be used as your default sender.

Then click Save Connection.

After saving the connection, the Sign in with Microsoft button will appear. Click it to connect your Microsoft account and complete the authorization process.

The connection will be added to the Connections list, and you should see Connection saved. at the top of the window.

Note: The free version allows you to add only one connection. If you need multiple connections, Conditional Routing, and many other features, you should purchase the DeliveryKit SMTP Pro.

Test Outlook Connection

After saving your Outlook connection, it is recommended to send a test email to make sure everything is working correctly. This helps confirm that your Client ID , Client Secret, and connection settings have been entered properly and that your site can send emails successfully through Outlook SMTP.

For step-by-step instructions, see the test connection guide here:

Test a DeliveryKit SMTP Connection.

]]> https://codemasterhub.com/doc/deliverykit-smtp-documentation/outlook-smtp-setup/feed/ 0 Google Workspace / Gmail SMTP Setup https://codemasterhub.com/doc/deliverykit-smtp-documentation/gmail-smtp-setup/ https://codemasterhub.com/doc/deliverykit-smtp-documentation/gmail-smtp-setup/#respond Mon, 09 Mar 2026 09:26:02 +0000 https://codemasterhub.com/?post_type=doc&p=1273
Set up Google Workspace or Gmail SMTP in DeliveryKit SMTP for WordPress. Learn how to create the connection, configure sender details, and send emails securely.

Table of Contents

What Is Gmail SMTP?

Gmail SMTP is Google’s outgoing mail service that allows websites, apps, and email clients to send email through Google’s mail servers. In DeliveryKit SMTP, it can be used to send WordPress emails through a Gmail account or a Google Workspace account.

This can be a useful option for sending contact form messages, notifications, password reset emails, order emails, and other transactional messages from your website.

Depending on your setup, Google may allow sending through authenticated SMTP for individual accounts or through SMTP relay for Google Workspace environments. This gives you a familiar and trusted sending infrastructure backed by Google.

Create a Project in Google Cloud Console

Creating or Choosing a Project

To begin, sign in to Google Cloud Console:

https://console.cloud.google.com/home/dashboard

After opening the dashboard, click Create Project.

Note! The Create Project button may be different or in a different position depending on your workspace and whether or not you have a previous project.

In the New Project window, enter a name for your project and complete any additional fields shown for your account, such as organization, location, or billing account.

Then click Create to continue.

Enabling the Gmail API

Next, you need to enable the Gmail API for your project.

In your Google Cloud Console sidebar, go to APIs & Services > Library.

If needed, make sure the correct project is selected at the top of the page.

In the API Library, search for Gmail API and click it from the results.

Then click Enable to activate the Gmail API for your project.

Creating Application Credentials

After you enable the Gmail API, you may be redirected to the Gmail API Overview page.

From there, click Create Credentials to begin creating the credentials required for your application.

If you are not redirected automatically, go to APIs & Services > Credentials in Google Cloud Console, then click Create Credentials.

Choose the Credential Type

After clicking Create Credentials, Google may open a setup wizard to help you choose the correct credential type for your project.

If the wizard appears, select Gmail API from the Select an API dropdown.

Under What data will you be accessing?, choose User data.

Then click Next to continue.

Configuring Your OAuth Consent Screen

Google will now ask for some basic information about your app.

This setup is mainly for your own use, especially if only you will connect the app. Even so, some fields are still required.

App name: Enter a name for your app. This can be any name you want, such as DeliveryKit SMTP App.

User support email: Select your email address from the available options.

App logo: You can upload a logo for your app if you want. This is optional.

Developer contact information: Enter an email address where Google can contact you about this project.

After completing these fields, click Save and continue.

Configuring Scopes (Optional)

This step is optional for this setup and can be skipped. In the Scopes section, scroll down to the bottom of the page and click Save and Continue to proceed.

Setting Up Your OAuth Client ID

Next, you need to enter some details for your OAuth Client ID.

From the Application type dropdown, select Web application.

After selecting this option, additional fields will appear automatically for your OAuth client configuration.

Setting Up Your OAuth Client ID

Next, complete the OAuth client fields.

Name: Enter a name for your OAuth 2.0 client. This name is only used to identify the client in Google Cloud Console and will not be shown to end users.

Google may automatically add the domains from the URIs you enter below to your OAuth consent screen as authorized domains.

Authorized JavaScript origins: This section is used for requests sent directly from a browser.

Authorized redirect URIs: This section is used for requests sent from a web server.

Copy the redirect URL shown in your DeliveryKit SMTP Gmail setup and paste it into the Authorized redirect URIs field.

After that, click Create.

Note: It may take 5 minutes to a few hours for Google’s settings to take effect.

Your Credentials

After the OAuth client is created, Google will show your application credentials, including the Client ID.

You can copy the Client ID now or return to it later in the next steps.

When you are finished, click Done.

Updating the Publishing Status From Testing to Production

After creating your OAuth app, review its audience and publishing status.

In Google Cloud Console, go to Google Auth platform > Audience. In some older Google Cloud layouts, this may appear under APIs & Services > OAuth consent screen.

Next, click Audience. In the Publishing status section, click Publish app.

In the Push to production popup, click Confirm.

Granting Your Site Google / Gmail Permissions

Next, in the Clients panel, locate your app under OAuth 2.0 Client IDs, then click the pencil icon to edit it.

In the Additional information section, under Client secrets, click Add Secret to create a secret key.

You will now see the new Client secret listed below the default one. Click the copy icon to copy its value.

Then copy both the Client ID and Client Secret, and paste them into the corresponding fields in your DeliveryKit SMTP Gmail settings.

Setting Up Gmail on DeliveryKit SMTP

In your WordPress dashboard, go to:

DeliveryKit SMTP > Connections

In the Create Connection section, click Add New Connection.

Configure Connection

In the Configure Connection section, fill out the Connection Details fields:

Connection Details: Enter a name for this connection. This is only for you, recipients will not see it.

Default From Email: The email address used when an outgoing email does not define a From Email.

Force From Email: If enabled, this From Email will be used for all emails, even if the email has a different From Email.

Default From Name: The name used when an outgoing email does not define a From Name.

Force From Name: If enabled, this From Name will be used for all emails, even if the email has a different From Name.

Default Reply-To Email: The Reply-To address used when an outgoing email does not define a Reply-To Email.

Force Reply-To Email: If enabled, this Reply-To Email will be used for all emails, even if the email has a different Reply-To Email.

In the Choose a Mailer section, select Google (Gmail) from the grid mailer list.

In the Google (Gmail) Settings section, paste the Client ID and Client Secret you copied from the Additional information section.

Default Connection: Enable this option if you want this connection to be used as your default sender.

Then click Save Connection.

After saving the connection, the Sign in with Google button will appear on the same screen. Click it, then complete the Google authorization process to finish the setup.

After the setup is completed, you will be redirected back to your WordPress dashboard.

The connection will be added to the Connections list, and you should see Connection saved. at the top of the window.

Note: The free version allows you to add only one connection. If you need multiple connections, Conditional Routing, and many other features, you should purchase the DeliveryKit SMTP Pro.

Test Gmail Connection

After saving your Gmail connection, it is recommended to send a test email to make sure everything is working correctly. This helps confirm that your Client ID , Client Secret, and connection settings have been entered properly and that your site can send emails successfully through Gmail SMTP.

For step-by-step instructions, see the test connection guide here:

Test a DeliveryKit SMTP Connection.

]]> https://codemasterhub.com/doc/deliverykit-smtp-documentation/gmail-smtp-setup/feed/ 0 SendLayer SMTP Setup https://codemasterhub.com/doc/deliverykit-smtp-documentation/sendlayer-smtp-setup/ https://codemasterhub.com/doc/deliverykit-smtp-documentation/sendlayer-smtp-setup/#respond Sun, 08 Mar 2026 09:08:48 +0000 https://codemasterhub.com/?post_type=doc&p=1248
Set up SendLayer in DeliveryKit SMTP for WordPress with this step by step guide. Learn how to connect your account, enter API or SMTP details, and test email delivery.

Table of Contents

What Is SendLayer?

SendLayer is a transactional email delivery service designed to help websites and apps send important emails reliably, including password resets, order confirmations, account notifications, and other automated messages. It supports sending through both SMTP and API, with a strong focus on deliverability, reliability, and scalability. SendLayer also helps authenticate your domain with the DNS records needed to improve trust with mailbox providers such as Gmail, Yahoo, and Outlook. Learn more on the official website: https://sendlayer.com/

Create a SendLayer Account

Before you can connect DeliveryKit SMTP to SendLayer, you need to create a SendLayer account. If you do not have one yet, follow SendLayer’s official step by step account creation guide. SendLayer’s documentation explains that you can start from its signup or pricing flow, create your account, complete the required details, and then continue to the dashboard.

Official guide:
https://sendlayer.com/docs/creating-your-account/

Once your account has been created, log in to your SendLayer dashboard here:
https://app.sendlayer.com/login

After signing in, you can continue with the SendLayer mailer setup in the next steps.

Authorizing Your Domain in SendLayer

Before you can send emails with SendLayer, you need to authorize your domain. This helps email servers verify that you are the legitimate owner of the sending domain and that your messages are coming from a trusted source.

Authorizing your domain is an important step for improving email deliverability and reducing the chance of your messages being marked as spam.

For full step by step instructions, see SendLayer’s official guide to authorizing your domain:

https://sendlayer.com/docs/authorizing-your-domain/

Setting Up SendLayer on DeliveryKit SMTP

In your WordPress dashboard, go to:

DeliveryKit SMTP > Connections

In the Create Connection section, click Add New Connection.

Configure Connection

In the Configure Connection section, fill out the Connection Details fields:

Connection Details: Enter a name for this connection. This is only for you, recipients will not see it.

Default From Email: The email address used when an outgoing email does not define a From Email.

Force From Email: If enabled, this From Email will be used for all emails, even if the email has a different From Email.

Default From Name: The name used when an outgoing email does not define a From Name.

Force From Name: If enabled, this From Name will be used for all emails, even if the email has a different From Name.

Default Reply-To Email: The Reply-To address used when an outgoing email does not define a Reply-To Email.

Force Reply-To Email: If enabled, this Reply-To Email will be used for all emails, even if the email has a different Reply-To Email.

Create an API Key in SendLayer

Create an API Key in SendLayer

To create or manage your SendLayer API key, follow SendLayer’s official guide:

https://sendlayer.com/docs/managing-api-keys/

After you create the API key, click the copy icon next to it to copy the key.

Go back to the SendLayer connection settings in your WordPress dashboard, then paste the API key you copied into the appropriate field.

Default Connection: Enable this option if you want this connection to be used as the default sender for outgoing emails.

Then click Save Connection.

The connection will be added to the Connections list, and you should see Connection saved. at the top of the window.

Note: The free version allows you to add only one connection. If you need multiple connections, Conditional Routing, and many other features, you should purchase the DeliveryKit SMTP Pro.

Test SendLayer Connection

After saving your SendLayer connection, it is recommended to send a test email to make sure everything is working correctly. This helps confirm that your API Key, Sender Name, and connection settings have been entered properly and that your site can send emails successfully through SendLayer SMTP.

For step-by-step instructions, see the test connection guide here:

Test a DeliveryKit SMTP Connection.

]]> https://codemasterhub.com/doc/deliverykit-smtp-documentation/sendlayer-smtp-setup/feed/ 0 Test a DeliveryKit SMTP Connection https://codemasterhub.com/doc/deliverykit-smtp-documentation/test-a-deliverykit-smtp-connection/ https://codemasterhub.com/doc/deliverykit-smtp-documentation/test-a-deliverykit-smtp-connection/#respond Fri, 06 Mar 2026 11:24:54 +0000 https://codemasterhub.com/?post_type=doc&p=1221
The Email Test feature in DeliveryKit SMTP allows you to quickly verify that your mailer connection is working correctly. It helps you confirm that your website can send emails successfully and makes it easier to identify configuration issues before using the connection for real website emails.

How to Send a Test Email

In your WordPress dashboard, go to DeliveryKit SMTP > Email Test.

Connection: If you only have one connection, it will already be selected. If you have multiple connections, choose the connection you want to test from the dropdown list.

To: Enter the email address where you want to receive the test email.

Send As: Select HTML or Plain Text to choose the email format.

The Subject and Content are generated automatically by the plugin template.

Click Send Email.

If the connection is working correctly, you should receive the test email in your inbox.

Troubleshooting

If you do not receive the test email, check the Email Log tab to review the error details.

If you are unable to solve the issue, create a support ticket at codemasterhub.com/support/ and include the exact error message so it can be reviewed.

]]> https://codemasterhub.com/doc/deliverykit-smtp-documentation/test-a-deliverykit-smtp-connection/feed/ 0 SMTP.com Setup https://codemasterhub.com/doc/deliverykit-smtp-documentation/smtp-com-setup/ https://codemasterhub.com/doc/deliverykit-smtp-documentation/smtp-com-setup/#respond Fri, 06 Mar 2026 09:39:46 +0000 https://codemasterhub.com/?post_type=doc&p=1194
Learn how to set up SMTP.com in DeliveryKit SMTP for WordPress and improve the reliability and deliverability of your website emails.

Table of Contents

What Is SMTP.com?

SMTP.com is a professional email delivery service designed for sending transactional and marketing emails with better speed, reliability, and inbox placement. It provides businesses and website owners with the tools needed to send emails securely through SMTP or API, making it a popular choice for websites that need dependable email delivery for user notifications, password resets, purchase confirmations, and similar messages.

Setting Up SMTP.com Account

Before you begin the SMTP.com connection setup in DeliveryKit SMTP, you need an active SMTP.com account. This account will be used to connect your website to SMTP.com so your emails can be sent more reliably. If you already have an account, log in and keep it open in another browser tab. If you do not have one yet, create a new SMTP.com account first.

During registration, SMTP.com may require a few additional verification steps. These checks help protect the platform from abuse and support better email deliverability for all users. After signing up, check your inbox for the activation email and open the verification link to activate your account. You may also be asked to agree to SMTP.com’s terms or usage policy.

After activation, SMTP.com may review your account before it is fully approved. In some cases, this process can take up to 24 hours and may require you to provide extra details about your website or how you plan to send emails. Keep an eye on your inbox in case their team contacts you for more information.

Once your SMTP.com account has been activated and approved, you can continue with the setup in DeliveryKit SMTP. It is recommended to keep your SMTP.com dashboard open, because you will need information from your account in the next steps.

Create Account in SMTP.com

To get started, open the SMTP.com trial signup page at trial.smtp.com. On the Start Free Trial form, enter the required account details to begin creating your SMTP.com account. Continue through the registration steps and complete the payment information section as requested on the signup form, even if you are starting with a trial account.

After submitting the form, follow any verification or onboarding steps shown by SMTP.com. Once your account has been created, keep your SMTP.com dashboard open in a separate browser tab, because you will need it during the next stages of the DeliveryKit SMTP setup.

Setting Up Your Site’s DNS Settings

Domain authentication is an essential part of email delivery because it helps email providers recognize that your messages are coming from a legitimate and authorized source. Without proper authentication, your emails are more likely to be filtered, flagged, or sent to spam.

To send emails with SMTP.com, you need to add the required DNS records for your domain. SMTP.com uses SPF to help authorize your sending service, and you will also need to configure DKIM so your outgoing messages can be cryptographically signed. These records work together to improve trust, support deliverability, and help protect your domain from spoofing.

SMTP.com provides an onboarding process that makes it easier to find the DNS records needed for your domain. Log in to your SMTP.com account and follow the onboarding steps to access your domain authentication settings and copy the exact SPF and DKIM values provided for your account.

You must then add these DNS records in your domain’s DNS manager, which is usually available through your hosting provider, domain registrar, or DNS service such as Cloudflare. If you are not sure how to add the records, SMTP.com provides setup tutorials for different hosting providers and DNS platforms here: DNS setup guides for different providers.

After adding the records, allow time for DNS changes to propagate. Once the records have been detected and verified in your SMTP.com account, you can continue with the connection setup in DeliveryKit SMTP.

Sending Domain

Enter your website’s domain in the What is your sending domain? field. This should be the domain you want to use for sending emails from your site. After entering the domain, click Next to continue and start the verification process.

Email Authentication (SPF, DKIM, DMARC)

Email authentication is a key part of successful email delivery. It helps mailbox providers verify that your messages are genuinely being sent from an authorized source and not from someone pretending to use your domain.

SMTP.com uses standard email authentication methods, including SPF, DKIM, and DMARC. SPF helps define which servers are allowed to send emails for your domain. DKIM adds a digital signature to your outgoing messages so receiving servers can verify that the message was sent legitimately and was not altered in transit. DMARC works with SPF and DKIM to help protect your domain from spoofing and tells receiving servers how to handle messages that fail authentication.

To complete your SMTP.com setup, you should add the required SPF and DKIM records provided in your SMTP.com account to your domain’s DNS settings. You may also configure a DMARC record on your domain to improve protection and reporting. These records help improve deliverability, support domain trust, and reduce the risk of your emails being rejected or sent to spam.

For more information, see SMTP.com’s guide to email authentication.

Setting Up SMTP.com in DeliveryKit SMTP

In your WordPress dashboard, go to:

DeliveryKit SMTP > Connections

In the Create Connection section, click Add New Connection.

Configure Connection

In the Configure Connection section, fill out the Connection Details fields:

Connection Details: Enter a name for this connection. This is only for you, recipients will not see it.

Default From Email: The email address used when an outgoing email does not define a From Email.

Force From Email: If enabled, this From Email will be used for all emails, even if the email has a different From Email.

Default From Name: The name used when an outgoing email does not define a From Name.

Force From Name: If enabled, this From Name will be used for all emails, even if the email has a different From Name.

Default Reply-To Email: The Reply-To address used when an outgoing email does not define a Reply-To Email.

Force Reply-To Email: If enabled, this Reply-To Email will be used for all emails, even if the email has a different Reply-To Email

Choose a Mailer

In the Choose a Mailer section, select SMTP.com from the mailers grid list. This will load the SMTP.com connection settings so you can enter the required account details and complete the setup.

Create an API Key in SMTP.com

To complete the SMTP.com connection in DeliveryKit SMTP, you will need to enter the API Key and Sender Name from your SMTP.com account.

To quickly access your API settings, click the Get API Key link in the SMTP.com section of the connection settings. This will take you to your SMTP.com API page, where you can create or copy your API Key: my.smtp.com/settings/api.

Once you have your API Key and Sender Name, return to DeliveryKit SMTP and enter them in the corresponding fields to continue the setup.

SMTP.com Settings

In the SMTP.com Settings section in DeliveryKit SMTP, enter your SMTP.com API Key in the API Key field.

After that, move to the Sender Name field. To quickly find the correct value for this field, click the Get Sender Name link. This will open your SMTP.com senders page, where you can locate the sender name or channel you need to use: my.smtp.com/senders/.

Next, enter the Sender Name (Channel) exactly as it appears in your SMTP.com account.

If you want this SMTP.com connection to be used as your main sending connection, enable the Default Connection option. When this option is checked, DeliveryKit SMTP will use this connection as the default sender unless another connection is selected by a routing rule or other configuration.

After completing all required fields, click Save Connection to save your SMTP.com connection settings.

The connection will be added to the Connections list, and you should see Connection saved. at the top of the window.

Note: The free version allows you to add only one connection. If you need multiple connections, Conditional Routing, and many other features, you should purchase the DeliveryKit SMTP Pro.

Test Your SMTP.com Connection

After saving your SMTP.com connection, it is recommended to send a test email to make sure everything is working correctly. This helps confirm that your API Key, Sender Name, and connection settings have been entered properly and that your site can send emails successfully through SMTP.com. For step-by-step instructions, see the test connection guide here: Test a DeliveryKit SMTP Connection.
]]> https://codemasterhub.com/doc/deliverykit-smtp-documentation/smtp-com-setup/feed/ 0 Brevo (Sendinblue) SMTP Setup https://codemasterhub.com/doc/deliverykit-smtp-documentation/brevo-smtp-setup/ https://codemasterhub.com/doc/deliverykit-smtp-documentation/brevo-smtp-setup/#respond Thu, 05 Mar 2026 11:16:00 +0000 https://codemasterhub.com/?post_type=doc&p=1134
Brevo (formerly Sendinblue) is a reliable email delivery service you can use with DeliveryKit SMTP to send WordPress emails through a dedicated SMTP connection. In this guide, you’ll create a Brevo SMTP connection, add it to DeliveryKit SMTP, and send a quick test email to confirm everything is working.

Table of Contents

What Is Brevo?

Brevo (formerly Sendinblue) is a full marketing and communications platform that also offers powerful transactional email delivery for websites and apps. For WordPress, “transactional” usually means important automated emails like password resets, order confirmations, contact form notifications, membership emails, and admin alerts.

Instead of relying on your hosting server’s built-in mail function (which is often limited and can cause poor deliverability), Brevo sends your messages through its own email infrastructure using SMTP or an API. This typically results in better inbox placement, clearer sending reputation, and more reliable delivery. Brevo also includes tools like sender verification, basic reporting, and deliverability features that make it a solid choice when you want WordPress emails to arrive consistently and look professional.

Create and Verify Your Brevo Account

Step 1: Open the Brevo Transactional Email page

Go to:

https://www.brevo.com/products/transactional-email/

Step 2: Sign up

Click the Sign up free button.

Choose one of these signup methods:

  • Enter your email and password Or:
  • Use Sign up with Google
  • Use Sign up with Apple

Step 3: Enter your account information

In the next steps, fill in the required information as requested:

  • Company name*
  • Website*
  • Address*
  • Zipcode*
  • City*
  • Country*

Then click Continue.

Step 4: Tell Brevo about your organization

In the Tell us about your organization section, fill out the fields:

  • How many people are on your team?
  • How many contacts do you need to have?

Then click Continue.

Step 5: Verify your mobile number

Enter your mobile number, then click Send verification code.

You will receive a code via SMS.

Enter the code in the verification field, then click Verify.

Step 6: Confirm your plan

After verification, your free plan (up to 300 emails per day) is ready.

If you need a higher daily sending limit, click Upgrade Plan and choose a paid plan.

Authorizing Your Domain


To ensure your emails deliver successfully, you must authorize your domain in Brevo. This must be the same domain used in your From Email.

For example, if your From Email is info@example.com, the domain you must verify in Brevo is example.com.

Setting Up a Domain in Brevo (Sendinblue)

To start the domain verification process, sign in to your Brevo account.

Step 1: Open the domain settings

After logging in, click your company name >> My profile in the top-right corner of the dashboard.

From the sidebar menu, select:

Senders, Domains & Dedicated IPs

From the next page, click the Domains tab, then click the Add a domain button.

In the Add a domain popup, enter your domain name without http, https, or www, then click Add Domain.

In the Authenticate your domain popup, choose Authenticate the domain yourself, then click Continue.

Adding DNS Records

To authorize your domain, you must add specific DNS records for it. This helps protect your domain, improves email security, and is critical for reliable email delivery.

To proceed, open a new browser tab or window. Then log in to the service where you manage your domain’s DNS (this is often your domain registrar or hosting provider).

Locate the DNS management area, such as:
DNS Settings, DNS Records, DNS Management, or Zone Editor.

After you add the DNS records, return to Brevo and click Authenticate this email domain.

Note: DNS changes can take up to 24 hours to fully apply. Usually it works within about 2 hours. With fast DNS providers like Cloudflare, it can take as little as 2 minutes.

After the records apply, go back to the Domains list. Under Domain status, you should see Authenticated.

If it does not show Authenticated, the DNS records are not applied yet, or they were entered incorrectly.

Add a Sender

In the Senders, Domains & Dedicated IPs page, click the Senders tab, then click the Add Senders button.

On the Add a Sender page, enter your From Name and From Email, then click the Add Sender button.

Note: The sender email must use an authenticated domain.
Example: If you authenticated example.com, your sender email can be anything@example.com.

After adding the sender, you should see Verified and DMARC is configured for that email in the Senders list.

Setting Up Brevo on DeliveryKit SMTP

In your WordPress dashboard, go to:

DeliveryKit SMTP > Connections

In the Create Connection section, click Add New Connection.

Configure Connection

In the Configure Connection section, fill out the Connection Details fields:

Connection Details: Enter a name for this connection. This is only for you, recipients will not see it.

Default From Email: The email address used when an outgoing email does not define a From Email.

Force From Email: If enabled, this From Email will be used for all emails, even if the email has a different From Email.

Default From Name: The name used when an outgoing email does not define a From Name.

Force From Name: If enabled, this From Name will be used for all emails, even if the email has a different From Name.

Default Reply-To Email: The Reply-To address used when an outgoing email does not define a Reply-To Email.

Force Reply-To Email: If enabled, this Reply-To Email will be used for all emails, even if the email has a different Reply-To Email.

Choose a Mailer

In the Choose a Mailer section, click Brevo in the mailers grid list.

Create an API Key in Brevo

Open a new browser tab, then go to:

https://app.brevo.com/settings/keys/api

You can also access this page from the Brevo sidebar menu, below Senders, domains, IPs.

On the Keys page, make sure you are in the API keys & MCP tab, then click Generate a new API key.

In the Name your API key field, enter a name for the key, then click Generate.

After the API key is generated, in Your API Key, click the copy icon to copy it, then click OK.

Go back to the Brevo connection settings in your WordPress dashboard, then paste the API key you copied.

In Sending Domain, enter the same domain you authenticated in Brevo.

Default Connection: Enable this if you want this connection to be the default sender for outgoing emails.

Then click Save Connection.

The connection will be added to the Connections list, and you should see Connection saved. at the top of the window.

Note: The free version allows you to add only one connection. If you need multiple connections, Conditional Routing, and many other features, you should purchase the DeliveryKit SMTP Pro.

Test Brevo Connection

After saving your Brevo connection, it is recommended to send a test email to make sure everything is working correctly. This helps confirm that your API Key, Sender Name, and connection settings have been entered properly and that your site can send emails successfully through Brevo SMTP.

For step-by-step instructions, see the test connection guide here:

Test a DeliveryKit SMTP Connection.

]]> https://codemasterhub.com/doc/deliverykit-smtp-documentation/brevo-smtp-setup/feed/ 0