Email Deliverability Is Not Just an Email Problem
Hosting choices affect contact forms, order emails, DNS authentication, and whether customers receive important messages. Here's what to check.
Hosting and Email Are Connected
Many site owners think email deliverability belongs entirely to Gmail, Microsoft 365, or their newsletter platform. But web hosting still affects transactional messages, contact forms, password resets, order emails, and DNS records.
A fast website is not enough if customers never receive receipts or leads disappear.
Shared Hosting Mail Is Fragile
Shared hosting often includes email, but shared mail servers can develop reputation problems. If neighbouring accounts send spam, deliverability can suffer. One compromised WordPress install on a shared server can poison the IP for everyone.
That doesn't mean shared-hosted email is always bad. It means business-critical mail deserves more care than "whatever came free with hosting." For production sites, use a dedicated email service — see our [Email Hosting Options guide](/guides/email-hosting-options) and [Email vs Google Workspace comparison](/guides/email-hosting-vs-google-workspace).
SMTP Matters
Websites should send mail through authenticated SMTP or a transactional email service, not raw PHP mail(). SMTP gives clearer logs, better authentication, and more predictable delivery.
For WordPress, use a reputable SMTP plugin (FluentSMTP, Post SMTP, WP Mail SMTP) connected to:
- Google Workspace or Microsoft 365 (if you already pay for it)
- Amazon SES (cheapest at scale, ~$0.10 per 1,000 emails)
- Postmark (best deliverability, $15/month for 10,000 emails)
- Mailgun, Brevo, or SendGrid (good free tiers for low volume)
DNS Authentication
SPF, DKIM, and DMARC records tell receiving servers which systems are allowed to send mail for the domain. Without them, your transactional mail looks like spoofing to spam filters.
Hosting migrations often break these records accidentally. Moving DNS providers, changing nameservers, or replacing old TXT records without checking email authentication can damage deliverability. Learn the record types in our [DNS Records Explained guide](/guides/dns-records-explained).
Contact Forms Need Monitoring
Contact forms should be tested after migrations, PHP upgrades, SMTP changes, and plugin updates. A form that says "message sent" may still fail behind the scenes — queued in a mail log, rejected by the receiving server, or silently dropped.
Send test messages to external addresses (Gmail, Outlook, not your own domain). Check SMTP logs where available. For WooCommerce stores, test order confirmation and password reset emails specifically — these are the ones customers notice when they fail.
Hosting Checklist for Email
Before launching or migrating a site, verify:
- SPF, DKIM, and DMARC records are present and correct
- SMTP is configured, not raw PHP
mail() - Contact form sends to an external test address
- Order/password reset emails are tested (if applicable)
- Mail server IP isn't on common blocklists
Verdict
Treat email as part of hosting operations. Use proper SMTP, preserve DNS authentication, test forms after every hosting change, and don't rely on "free email included" for anything that matters.
For deeper guidance, see our guides on [Email Hosting Options](/guides/email-hosting-options) and [How to Migrate Email Hosting](/guides/how-to-migrate-email-hosting).