2 min read
WordPress sites send email: password resets, order confirmations, form notifications, CRM campaigns. If that email goes out via PHP’s default mail(), much of it lands in spam or is silently dropped. The fix is a transactional email provider (like Postmark) wired through FluentSMTP.
POSTMARK_MISSING (actionable): outbound email uses PHP mail() with no SMTP provider or relay detected. Configure Postmark or client SMTP via FluentSMTP for reliable delivery.
| PHP mail() | Postmark via SMTP | |
|---|---|---|
| Deliverability | Unreliable, often spam-filtered | Designed for high inbox rates |
| Authentication | No SPF/DKIM/DMARC | Full authentication, verified domain |
| Tracking | None | Delivery/bounce/open data |
| Reputation | Server IP reputation varies | Provider reputation, warmed |
In Postmark → Sender Signatures, add your domain and add the returned SPF and DKIM records to your DNS. Without these, providers reject or spam-filter your mail.
smtp.postmarkapp.com, port 587, TLS)Use a tool like mail-tester.com to confirm SPF, DKIM, and DMARC pass: that’s what determines inbox placement.
Any transactional provider works through FluentSMTP’s “Other SMTP” mailer: Mailgun, Amazon SES, SendGrid, Mailjet, or your client’s existing SMTP service. The pattern is identical: verified domain + authenticated SMTP credentials.
If you already have an SMTP provider account, send us the details and we’ll wire it. If not, we’ll recommend and set up one: it’s included in managed setup.
On managed sites we configure this for you: provider setup, DNS records, FluentSMTP wiring, and a deliverability test (SPF/DKIM/DMARC verified). We also monitor bounce/delivery health.
