Tell me what you need 
Guide · WordPress forms

Why your WordPress contact form says it sent, but nothing arrives

A form that says “thanks” while the email never lands is one of the most common WordPress problems, and one of the most costly because you don’t know about the enquiries you’ve lost. Here are seven checks, in the order I’d do them.

  1. 1. Check the form really received the message

    Before blaming email, confirm the form itself works. If your form plugin keeps a list of entries (WPForms and Gravity Forms do; Contact Form 7 only does with an add-on such as Flamingo), submit a test and look for it there.

    If the entry is missing, the problem is the form, not email: a JavaScript error, a caching plugin serving a stale page, or a spam or reCAPTCHA setting rejecting the submission. If the entry is there but no email arrived, carry on.

  2. 2. Look in the obvious places

    Search the inbox, spam and junk folders for the form’s subject line. Check the notification recipient in the form settings for typos, and make sure the mailbox isn’t full.

    If the recipient is on your own domain, send a normal email to it from a personal account. If that fails too, the problem is the mailbox or your email provider, not WordPress.

  3. 3. Look at the “From” address

    A very common cause: the form sets the “From” address to whatever the visitor typed in. Your server is then sending an email that claims to come from, say, a Gmail address, which it has no right to send as. Gmail, Outlook and others increasingly reject or spam this.

    Set “From” to an address on your own domain (for example [email protected] or [email protected]) and put the visitor’s address in “Reply-To”, so you can still reply to them directly.

  4. 4. Check SPF, DKIM and DMARC

    These are three records in your domain’s DNS that tell receiving servers who is allowed to send email as your domain. SPF lists permitted sending servers. DKIM adds a signature to each message. DMARC says what to do when those checks fail.

    If your website’s server isn’t covered by your SPF record and nothing signs the message with DKIM, receivers may treat it as suspicious. A free email-testing tool will tell you which checks pass. The records have to match whichever service actually sends the email, so change them carefully: a wrong SPF record can break your normal email.

  5. 5. Stop sending through the web server

    By default WordPress hands email to the web server, which is often unreliable, shared with other sites and not authenticated as you. The robust fix is to send through a proper email service, either your email provider’s SMTP details or a transactional email service, using a plugin such as WP Mail SMTP.

    That authenticates the messages properly, and most services also show a log of what was accepted, delayed or rejected. That log is the quickest way to stop guessing.

  6. 6. Test it properly

    Send a test from the form and open the received message’s full headers (in Gmail, “Show original”). Look for SPF, DKIM and DMARC all showing “pass”.

    Test to more than one mailbox, such as Gmail and Outlook, because they filter differently. A message arriving in your own inbox doesn’t mean it will reach a customer’s.

  7. 7. Rule out the less common causes

    Hosting companies sometimes block or limit outgoing email. Security or spam plugins can block submissions. A caching or optimisation plugin can break the form’s scripts. An email forward on your domain can fail even though the form is fine.

    If you’ve been through all of this and it still fails, the cause is usually specific to your host or your mail setup, which is where a quick look from someone who does this regularly saves hours.

Enquiries still not arriving?

Tell me what you’re seeing and include your website address. I’ll reply with any questions and tell you what I think it needs.