WordPress contact form not sending email: Why do form notifications fail to arrive, and how can you fix them?

What happens if the “From” address does not match the domain?

If the “From” address does not belong to the website’s domain, the receiving server may treat the message as spoofed and send it to spam or reject it. Contact Form 7’s Best practices for email setup page states this explicitly: the “From” field must use an address belonging to the site’s domain. For example, if the site is on ornekfirma.com, the sender address should be something like bilgi@ornekfirma.com; a Gmail or Hotmail address is not entered in this field.

Another common mistake is putting the email address entered by the visitor into the “From” field. WPForms notification documentation states that this practice can raise phishing suspicions and harm the domain’s reputation. The correct method is to put the visitor’s address in “Reply-To”; clicking “Reply” on the incoming notification then sends the response directly to the visitor.

Contact Form 7 documentation highlights another detail: the plugin’s default template uses a wordpress@alanadi-style address in “From,” and some hosts may block sending if that address does not actually exist. Creating this address as a real mailbox with the hosting provider or replacing “From” with an existing business address is recommended.

Can missing SPF and DKIM cause form notifications to land in spam?

Yes; if the domain lacks SPF and DKIM records or those records do not cover the sending server, form notifications may land in spam or not be delivered at all. SPF lists which servers may send email on behalf of the domain; DKIM adds a digital signature associated with the domain to the message. Even if “From” is correct, missing records prevent the receiving server from verifying that the message actually came from that domain.

A frequent trap in form notifications is that business email is with one provider, the website is on another server, and SPF covers only the email provider. In this case, messages leaving the site through PHP mail cannot pass SPF checks. How to set up SPF, DKIM, and DMARC and test them with Gmail’s “Show original” in the guide to email going to spam is explained with example records.

How do you diagnose missing form notifications?

Diagnosis begins by distinguishing whether the problem is in the form, on the server, or at the recipient’s end, and can be performed through a few simple checks. Following the sequence below instead of randomly changing plugins generally reveals the broken link quickly:

1. Spam and junk folders: Check spam, junk, and other tabs in the intended recipient mailbox; if the message is there, the issue concerns authentication rather than sending.
2. Recipient address: Open “To” in the form notification settings; confirm that the address is spelled correctly and is still used.
3. Test a different mailbox: Temporarily direct notifications to an address with another provider and submit the form; if the message arrives there, the problem is the receiving server’s filter.
4. WordPress test email: Most SMTP and email logging plugins allow a test message from the panel; bypass the form to see whether the server sends email.
5. Email log: An email logging plugin records which message the site sent, when, to whom, and whether it encountered an error.

If the message never appears in the log, the problem lies within the form or a plugin conflict. If it appears as “sent” but does not reach the recipient, the problem is on the server, DNS, or recipient side. An error recorded in the log often indicates that the server rejected the send request.

Settings to check in Elementor, Contact Form 7, WPForms, and WooCommerce

Each form plugin places notification settings on a different screen, but the fields to check are the same: recipient, “From,” “Reply-To,” and whether submissions are recorded. Because plugin interfaces can change between versions, the following describes fields to check rather than menu paths.

Elementor form email not arriving

In an Elementor Pro form, the email action is defined among the form’s actions after submission; the recipient, subject, “From,” and “Reply-To” are set there. Elementor’s help page recommends that the form’s “From” address use the website’s domain and that the visitor’s email field be selected as the reply address. The same page recommends using Elementor’s Submissions feature to check whether the form works and trying another recipient address because the original may have been flagged as spam.

Contact Form 7 not sending email

In Contact Form 7, notifications are managed in the Mail section of the form editing screen; Mail (2) is used if a second message will be sent to the visitor. According to the plugin documentation, “Reply-To” is entered under Additional headers in these sections. The documentation also recommends care with values from optional fields and avoiding an empty or very short message body; otherwise, sending may fail on some hosts.

WPForms notifications

According to WPForms documentation, notifications are enabled by default and the default recipient is the site’s administrator email address. If that address belongs to someone who installed the site years ago, notifications may be going to that person. When “From” does not match the website’s domain, the plugin displays a warning below the field; this warning should not be ignored.

WooCommerce order emails

WooCommerce order emails also leave through the same wp_mail() infrastructure; order confirmations are therefore likely to be affected in a store whose form notifications fail. According to WooCommerce email troubleshooting documentation, every transactional email attempt is logged; sent and failed order-email attempts are also added as order-specific notes. The sender address in WooCommerce settings is also recommended to belong to the site’s domain.

WordPress SMTP setup: PHP mail, a business account, or a transactional service?

For a WordPress contact form not sending email, the lasting solution is to send notifications through an authenticated SMTP connection instead of the server’s PHP mail function. WordPress SMTP setup usually uses an SMTP plugin; the plugin routes wp_mail() calls to the selected mail server. Elementor’s help page also recommends this approach and mentions WP Mail SMTP and services such as SendGrid as examples; the products named here are examples only.

There are two common SMTP options. The first is a business email account on the domain: for example, Google Workspace’s Send email from apps and devices page specifies smtp.gmail.com, port 465 or 587, a full email address and an app password, and a daily limit of 2,000 messages for the Gmail SMTP server. The second is transactional email services; these are designed for automated messages such as order confirmations, password resets, and form notifications, and generally provide their own sending logs.

Whichever route is selected, the “From” address in the SMTP plugin must be compatible with the SMTP account; WPForms documentation also states that most SMTP services require this match. If no business address exists on the domain yet, how to create one in the How to get business email article is explained.

Why is storing form submissions in the database necessary?

However well email is configured, separately storing form submissions in the database is the closest precaution to eliminating the risk of loss. Contact Form 7’s Flamingo documentation states that the plugin does not store submitted messages anywhere; important messages can be permanently lost if the mail server has a problem or a setting is incorrect. The free Flamingo plugin from the same developer records these messages in the database.

To avoid losing inquiries because a WordPress contact form is not sending email, Elementor Pro’s Submissions feature can be used; it makes data viewable in the WordPress panel and downloadable as CSV. Because submission recording in other form plugins such as WPForms can vary by version and plan, check separately whether the feature is enabled in the version used. Because records contain personal data, also remember to restrict access to authorized users and regularly remove unnecessary old records.

Common mistakes and the correct method

The most common mistake with form notifications is treating the symptom while leaving the cause; changing the form plugin, for example, does not change the sending route. Common mistakes encountered in practice and their correct alternatives are as follows:

• Entering a Gmail address in From: Set the sender address to a business address belonging to the website’s domain.
• Making the visitor’s address the sender: Put the visitor’s address in “Reply-To.”
• Installing multiple SMTP plugins: Keep only one sending plugin active at a time; conflicts complicate diagnosis.
• Not adding the new sender to SPF: Update SPF when the SMTP service changes; the domain should have a single SPF record.
• Leaving a password exposed in plugin settings: Use an app password or service API key where possible, and retain access only for the necessary person.
• Not testing after updates: After a plugin, theme, or PHP update, submit each form once and check the notification.

The common feature of these mistakes is that the problem can remain unnoticed for weeks. Missing notifications are often discovered only when a customer calls and says “I submitted the form but never heard back.”

Form notification testing checklist

After configuration is complete, verify actual delivery through real form submissions and more than one recipient type. Complete this checklist before considering a WordPress contact form not sending email to be resolved:

1. Submit every form on the site separately, including contact, quotation, appointment, and newsletter forms.
2. Test notifications by sending to both a business mailbox and an address with a different provider.
3. In the received message, check that “From” belongs to the domain and “Reply-To” points to the visitor.
4. In Gmail’s “Show original,” verify that SPF and DKIM results show PASS.
5. Confirm that sending is recorded without errors in the email log.
6. Check in the panel that the submission is also stored in the database.
7. If there is a store, test customer and administrator order emails using a test order.

Repeat this checklist after every major update as well as after initial setup. A brief monthly test prevents lost inquiries from being discovered months later.

When should you consult a specialist for a WordPress contact form not sending email?

Specialist support saves time if diagnostic steps do not identify the source, DNS records are inaccessible, or store order emails are affected. Where multiple providers send email on behalf of the same domain, merging SPF correctly requires care; an incorrect edit can affect business email itself. If the hosting company has disabled sending entirely, the solution requires an infrastructure decision rather than a plugin setting.

At Onur Freelance, these issues are handled within the annual WordPress maintenance and updates service: contact forms and any order emails are tested after updates, and the work performed is recorded. Maintenance costs 500–2,000 TL per month depending on the site’s size and scope; the scope is clarified in the initial consultation. If the site’s hosting will also be reorganized, the hosting prices page’s annual 2,000 TL package is opened in the business’s name. Onur Freelance is not an official support channel for WordPress, plugin developers, or email providers and does not promise that email will reach the inbox under all circumstances; the aim is to make the sending route verifiable and traceable.