InstaWP Docs

Appearance

SMTP / Email from InstaWP Servers ​

Yes — your InstaWP site can send real email to real inboxes.

InstaWP servers don't run a local mail server, so WordPress can't send mail on its own: a bare wp_mail() call has nothing to hand the message to. You need to configure an SMTP provider — and that works fine.

Outbound SMTP submission on ports 587 and 465 is open to every provider. Only port 25 is blocked, for anti-spam reasons (it stops a compromised site relaying mail directly to mail exchangers). That's standard practice across hosts, and no provider needs port 25 anyway — they all use 587 or 465.

MethodPort / protocolWorks on InstaWP
Authenticated SMTP submission587 (STARTTLS)✅ Yes
Authenticated SMTP submission465 (implicit TLS)✅ Yes
HTTPS API mailers (SendGrid, Mailgun, Postmark, Brevo, Resend, …)443✅ Yes
Direct-to-MX / unauthenticated SMTP25❌ Blocked
PHP mail() / wp_mail() with no SMTP configured—❌ No — local mail is disabled, and the call can appear to succeed while the message is discarded

Gmail / Google Workspace, Microsoft 365, Amazon SES, SendGrid, Mailgun, Brevo, Postmark, or your own host's SMTP server — all of them work with their normal credentials. There are no per-provider, per-plan or per-server differences.

Scope

This describes sites hosted on InstaWP (sandbox and pay-per-use hosting).

Set up SMTP on your site ​

  1. Install an SMTP plugin such as WP Mail SMTP, FluentSMTP or Post SMTP.
  2. Enter your provider's SMTP host, port 587 (or 465), and your username and password / API key.
  3. Set the From address to a domain you own and switch on the plugin's Force From Email option.
  4. Send a test email from the plugin.

Why the From address matters ​

This is the most common cause of "my emails aren't sending" on InstaWP.

By default WordPress sends as wordpress@<your-subdomain>.instawp.site. That address can never be a verified sender with your email provider — instawp.site is a shared domain you don't own and can't publish SPF or DKIM records for, so providers reject or silently drop the message.

Always send from an address on a domain you control (for example hello@yourdomain.com), and enable Force From Email so plugins and WooCommerce can't override it.

Note that an open port only guarantees your site can reach your provider. Whether the message lands in the inbox is down to your sending domain's SPF, DKIM and DMARC records and your provider's reputation — configure those with your email provider.

Testing email without delivering it ​

Using Mailtrap ​

Mailtrap is a sandbox mail-testing service: it captures outgoing email so you can inspect it instead of sending it to real people.

InstaWP has a one-click Mailtrap integration — add your API key on the Integrations page, then enable it on a site from the site actions menu. It installs and configures WP Mail SMTP against a Mailtrap testing inbox (port 587, with authentication and auto-TLS), so your site's mail is captured for inspection rather than delivered.

It's a convenience for testing — not a requirement for sending. For real delivery to real inboxes, configure your own provider as described above. See Add a Mailtrap Integration.

Using a Plugin ​

You can use a third-party plugin like Email Log to inspect the mails your InstaWP site sends, from inside the wp-admin screen itself.

Still not sending? ​

  • Check the From address is on a domain you own, with SPF and DKIM set up at your DNS provider.
  • Read the SMTP plugin's own email log / debug output — it shows the provider's exact error.
  • Re-check the SMTP username, password or API key; an expired key is the next most common cause.
  • Make sure the port is 587 or 465, never 25.

Docs are open. Edit them on GitHub. Built with VitePress.

© InstaWP