Your Peptide BrandSupport
← Support home

Storefront email · Updated September 22, 2026

Sending service setup guides

Your storefront can send through many email services. Here are the ones the WP Mail SMTP plugin supports, how each one connects, and where to find its official setup steps.

Your email account, your control
We recommend that you own your sending account (for example SendGrid or Brevo) and create its credentials yourself. If you’d prefer, YPB can set up and send your storefront email for you as an optional courtesy. Either way, never send a password or key to anyone — including YPB.
Never share passwords or keys
No one from YPB will ask you to send a password, API key, one-time code or verification link by email, chat or support request. Enter credentials yourself, directly in the product that needs them.
Explain it at this level

Showing: High school

How to choose

Grade school

Any service on this list can carry your store’s emails. If you’re not sure, pick SendGrid or Brevo — we have step-by-step guides for both.

High school

Pick a service built for transactional email, that you’re happy to own and pay for if you outgrow its free tier. SendGrid and Brevo have full guides here. Check the “Plugin edition” column: a few services only work with a paid WP Mail SMTP licence.

College

Compare volume pricing, how long each keeps message logs, how it authenticates your domain (CNAME delegation versus TXT keys), whether it separates transactional from marketing streams, and whether its mailer is in the free plugin. API mailers are preferable to generic SMTP for security and error reporting.

Postgraduate

Weigh portability and control: provider lock-in shows up in suppression data, templates and reputation history, not just in the transport. Choose least-privilege credentials, and prefer providers whose domain authentication doesn’t consume your apex SPF lookup budget.

Developer

Mailer availability reflects WP Mail SMTP 4.9.0: Amazon SES, Microsoft 365/Outlook and Zoho are hard-disabled in the free plugin; the rest ship free. Auth types differ — API key, OAuth app consent or SMTP credentials — so hosts, ports and records are never interchangeable between providers.

Supported services

ServiceSigns in withPlugin editionSetup
SendGridAPI keyFree pluginYPB guide · Official guide
Brevo (formerly Sendinblue)API key (v3)Free pluginYPB guide · Official guide
Other SMTPSMTP username and passwordFree pluginYPB guide · Official guide
Google Workspace / GmailGoogle OAuth (one-click setup needs Pro)Free pluginYPB guide · Official guide
MailgunAPI keyFree pluginOfficial guide
MailjetAPI key and secretFree pluginOfficial guide
MailerSendAPI tokenFree pluginOfficial guide
Mandrill (Mailchimp Transactional)API keyFree pluginOfficial guide
PostmarkServer API tokenFree pluginOfficial guide
ResendAPI keyFree pluginOfficial guide
SendLayerAPI keyFree pluginOfficial guide
SMTP.comAPI key and sender nameFree pluginOfficial guide
SMTP2GOAPI keyFree pluginOfficial guide
SparkPostAPI keyFree pluginOfficial guide
Elastic EmailAPI keyFree pluginOfficial guide
Amazon SESAWS access keys (IAM)Pro or higherOfficial guide
Microsoft 365 / OutlookMicrosoft OAuthPro or higherYPB guide · Official guide
Zoho MailZoho OAuthPro or higherOfficial guide

Source: WP Mail SMTP mailer guide, checked September 22, 2026. Provider plans and prices are set by each provider. Some providers also need a paid plan for features such as dedicated IPs.

Setting one up

Grade school

Every service has the same basic steps: make an account, prove you own your domain, make a secret key, and type it into your website yourself.

High school

  1. Create an account with the service using your branded business address.
  2. Add and verify your sending domain there, then add the DNS records it gives you.
  3. Create a key (or sign-in connection) with only the permission needed to send mail.
  4. In WordPress, open WP Mail SMTP, choose the service and paste the key yourself.
  5. Send the plugin’s test email, then check a real storefront email.

College

The steps are the same everywhere; the details differ. Domain verification can be CNAMEs, TXT records or both. Credentials can be an API key, an OAuth consent or SMTP username and password. Enter the credential directly in WordPress, or have your own administrator do it. If YPB is helping you, grant YPB the narrowest WordPress access needed rather than sending the key.

Postgraduate

Treat credential issuance, domain authentication, runtime installation and delivery verification as separate controls, each with its own evidence. Scope keys to sending only, record who issued them and where they’re used, and plan rotation so that replacing a key doesn’t leave another consumer failing silently.

Developer

Prefer wp-config.php constants over database-stored secrets where your deployment allows (WP Mail SMTP constants; enable with WPMS_ON). Never commit secrets to source control or expose them to the browser. Allow the provider’s exact API host through any outbound HTTP block.