Skip to main content
Contact Form Going to Spam
Forms Email Delivery Troubleshooting

Contact Form Going to Spam

Overview

A contact form submission landing in the spam folder is a near-miss. The message was sent, it was received — but it is invisible unless you manually check spam. For a contractor handling service calls, missed messages in spam mean missed jobs. The fix requires addressing the technical reasons receiving email servers distrust the message, not just marking it “not spam” in your inbox.

Why Form Emails Go to Spam

1. No SPF Record

An SPF (Sender Policy Framework) DNS record tells receiving servers which mail servers are authorized to send email on behalf of your domain. If no SPF record exists, or if the server sending your form emails is not listed in it, receiving servers treat the message as suspicious.

2. No DKIM Signature

DKIM (DomainKeys Identified Mail) adds a cryptographic signature to outgoing email that receiving servers can verify. Without DKIM, email lacks authentication — a signal spam filters act on.

3. Sending From a Server IP With Poor Reputation

WordPress sites on shared hosting send email through the server’s local mail handler. Shared hosting IPs often have poor sending reputations because other accounts on the same server have sent spam. Receiving servers may distrust all email from that IP.

4. The “From” Address Does Not Match the Domain

If the form sends notifications with a “From” address like wordpress@yoursite.com or noreply@hosting-provider.com instead of an address on your actual domain, spam filters flag the mismatch.

5. Spam Trigger Words or Formatting

The subject line or body of the notification email may contain words or patterns that trigger spam filters. Subjects like “Contact Form Submission” are commonly over-represented in spam.

6. The Receiving Inbox Is Misconfigured

Gmail and Outlook aggressively filter email from unrecognized sources. Without a prior sending history and proper authentication, even correctly configured email may initially land in spam.

How to Fix It

1. Configure SPF Add an SPF TXT record to your domain’s DNS that includes the sending service you use. If sending through Gmail: v=spf1 include:_spf.google.com ~all. If through a transactional service, they will provide the specific record.

2. Configure DKIM Use an SMTP plugin with a transactional email service (SMTP2GO, Brevo, Resend, Mailgun). These services provide DKIM DNS records to add to your domain. Once configured, all outgoing email is cryptographically signed.

3. Switch to a Transactional Email Service Stop relying on the server’s local mail handler. Connect WordPress to a dedicated transactional email service using WP Mail SMTP or FluentSMTP. These services maintain high sending reputations and handle authentication properly.

4. Use a Consistent “From” Address Set the form notification “From” address to an email on your own domain (e.g., hello@yourcompany.ca). Ensure that address is covered by your SPF and DKIM records.

5. Check Deliverability After making changes, submit a test form and use a tool like mail-tester.com to score the email. A score of 9/10 or higher indicates strong deliverability.

Technical Website Support

Spam deliverability problems require DNS-level changes and SMTP configuration. Once SPF, DKIM, and a reliable sending service are in place, form emails reliably reach the inbox.