⚠️ Important: 2026 email deliverability update
Major inbox providers (Gmail, Yahoo, Microsoft, Apple) now require DMARC alignment to reliably accept email from your domain. That means messages sent "from" [email protected] must be DKIM-signed by your domain, not just a shared sender.
Wordify's shared outbound gateway does not provide domain-aligned DKIM signing, so it should only be used for low-stakes mail (internal notifications, admin alerts to addresses you control). For anything customer-facing, such as WooCommerce receipts, password resets, contact form submissions and newsletters, you should send through a dedicated transactional email provider that supports DKIM and DMARC alignment for your domain.
Recommended providers that work well with WordPress:
Postmark: excellent deliverability, simple setup, great for transactional mail
Amazon SES: cheapest at scale, slightly more technical to configure
Mailgun: solid all-rounder with a generous free tier
SendGrid: widely supported, good for higher volumes
Brevo (formerly Sendinblue): good option if you also need marketing email
SMTP2GO: straightforward, WordPress-friendly
To connect any of these to WordPress, we recommend the free FluentSMTP or WP Mail SMTP plugins, which handle the API/SMTP connection and let you route mail through your chosen provider. Once configured, publish matching SPF, DKIM, and DMARC records at your DNS host to achieve full alignment.
Your Wordify site is already configured to send outbound emails for low-volume traffic. However, given the current best practices you can improve the email deliverability from your site by following this guide.
If you want to send a high-volume email, speak to our support team about options.
Note: SMTP ports 465, 587 and 2525 are all supported for sending through your own email provider, and we recommend port 587. Port 25 is blocked on all Wordify servers as an anti-spam protection. See "Which SMTP ports work from Wordify sites?" below.
Things you can do to improve the reliability of outbound email:
1. Use the correct From address in outbound emails
If you're setting the from address, use the custom domain of your website. For example, if your site was example.org you could use the outbound email [email protected]
Site URL: example.org -> From Address: [email protected]
Do not use a From email address belonging to a separate domain such as gmail.com to send via Wordify as google's policies won't allow the recipient to receive the email.
2. Set an SPF record
If you're using a custom domain, adding Wordify to your SPF record can help. SPF records exist as DNS TXT type records and allow external parties to check what sending hosts a particular domain allows.
If you don't have an existing record, simply create a TXT DNS record as follows:
v=spf1 include:relay.wordifymail.com ~all
If you have an existing SPF record such as:
v=spf1 include:msoffice.net ~all
Modify it to add the "include:relay.wordifymail.com" as follows:
v=spf1 include:msoffice.net include:relay.wordifymail.com ~all
You can check your SPF record using this online tool: https://mxtoolbox.com/spf.aspx
3. Setup your own Outbound email gateway
If you want to improve email deliverability, send higher email volumes and get more information about the emails you're sending, a dedicated email gateway is a great way to go.
Popular options are:
Postmark: excellent deliverability, simple setup, great for transactional mail
Amazon SES: cheapest at scale, slightly more technical to configure
Mailgun: solid all-rounder with a generous free tier
SendGrid: widely supported, good for higher volumes
Brevo (formerly Sendinblue): good option if you also need marketing email
SMTP2GO: straightforward, WordPress-friendly
We recommend using the Fluent SMTP plugin to configure the services: https://en-au.wordpress.org/plugins/fluent-smtp/ and where possible, use the HTTP API rather than SMTP.
Which SMTP ports work from Wordify sites?
When you connect an SMTP plugin to your email provider, use one of these ports:
Port 587 (TLS/STARTTLS): supported on every Wordify server, and our recommended choice.
Port 465 (SSL/TLS): supported on every Wordify server.
Port 2525: supported. Some providers offer it as an alternative to 587.
Port 25: blocked, by design. Port 25 is the unauthenticated server-to-server mail port that spammers abuse. Blocking it protects the sending reputation of your site and every other site on the platform, and SMTP plugins never need it.
If your provider offers an HTTP API option in the plugin (SendGrid, Mailgun, Postmark and Brevo all do), we recommend it over SMTP. It avoids mail ports entirely and is usually faster and more reliable.
4. I'm using DKIM and DMARC on my domain, what do i need to do?
If your domain is currently using a DMARC policy along with corresponding DKIM keys, you will need to set up a custom gateway as per step 3 to send email out from Wordify using your domain.
Unfortunately, Wordify doesn't support custom DKIM keys presently, so a dedicated gateway account is required so you can see the appropriate keys.
If you need help with outbound email please contact us to discuss options.