Send WordPress email through Standard SMTP
Host, port, encryption, optional authentication. If it speaks SMTP, NimblyMail connects to it.
Why pair Standard SMTP with NimblyMail
Your web host’s mail server, your ISP’s relay, a self-hosted Postfix, a cPanel mailbox, an enterprise Exchange edge — if it speaks SMTP, NimblyMail connects to it. Configure host, port, encryption (none/SSL/TLS), and optional authentication; everything else — queue, retries, logging, alerts, audits — works exactly like the big-name integrations.
- Universal compatibility. Any host, any port, STARTTLS or SSL — including non-standard ports and self-signed-friendly modes for internal relays.
- Authenticated or open relay. Username/password auth when required, anonymous when your network trusts the source.
- Same operational layer. Background queue, backoff retries, failure alerts, full transcripts — nothing is second-class.
- PHP-constant config. Define the whole connection in wp-config.php for 12-factor deploys and multisite locks.
Connect Standard SMTP in three steps
Gather server details
Host, port (25/465/587/2525…), encryption, and credentials if required — your host or provider lists them.
Enter them in NimblyMail
Choose 'Standard SMTP', fill in the fields, save. Credentials encrypt automatically.
Test and audit
The test email proves the pipe; the audit verifies PTR, SPF, and connectivity for the host.
For self-hosted or ISP servers, deliverability depends on your own DNS: an SPF record naming the server, a PTR (reverse DNS) record matching its hostname, and ideally DKIM signing at the server. The audit checks PTR and SPF automatically.
Standard SMTP + WordPress, answered
Almost always. cPanel, Plesk, and most managed hosts provide SMTP credentials per mailbox — enter them here and WordPress email rides the same server as your regular email.
587 with STARTTLS is the modern standard; 465 with SSL also works. Port 25 is frequently blocked outbound by hosts — NimblyMail's connectivity check in the audit tells you immediately if it is.
The transport differs, not the reliability: NimblyMail's queue, retries, failover, and alerts apply identically. API integrations add delivery-status webhooks; SMTP adds universal compatibility.
More integrations
View all integrations
Elastic Email
ProConnect WordPress to Elastic Email with NimblyMail SMTP for budget-friendly, reliable delivery on both SMTP and API sending.
Setup guide
MailerSend
ProConnect WordPress to MailerSend through NimblyMail SMTP for modern deliverability tooling, templates, and per-domain SMTP credentials.
Setup guide
SMTP2GO
ProConnect WordPress to SMTP2GO with NimblyMail SMTP — redundant global infrastructure, a permanent free plan, and simple SMTP-only setup.
Setup guide
Mailjet
ProConnect WordPress to Mailjet via NimblyMail SMTP for EU-hosted, GDPR-friendly transactional email delivery from Sinch.
Setup guide