Learning Centre

Why Is My Website Contact Form Not Sending Emails?

Find out why your website contact form is not sending emails, from DNS and spam filtering to hosting issues, and learn how to troubleshoot enquiry delivery problems.

—
On this page

    Definition

    Website Contact Form Email Delivery

    A website contact form sends an enquiry from your website to one or more email recipients. When a form stops sending emails, the issue is usually caused by mail server configuration, spam filtering, missing DNS authentication, blocked sending methods, form errors or hosting restrictions.

    A form can appear to submit successfully while the email still fails in the background. That is why troubleshooting should check the website, hosting, DNS records, sender address, recipient mailbox and email platform together.

    Key Takeaways

    • Most contact form email issues come from configuration problems, not the form field itself. SMTP settings, sender addresses, DNS records and spam filters are common causes.
    • If your form says the message was sent, check whether the website generated the email, whether the mail server accepted it and whether the recipient mailbox filtered it.
    • Professional help is worthwhile when enquiries are business-critical, multiple providers are involved, DNS records are unclear or the issue keeps returning after basic fixes.

    Quick explanation

    Why Contact Form Emails Stop Arriving

    Your website contact form may not be sending emails because the website cannot create the email, the hosting server is blocking the message, the SMTP login is wrong, the recipient mailbox is rejecting it, or the domain's DNS records do not prove the email is legitimate. The tricky part is that these problems can look the same from the outside. A visitor may see a success message, but the email may still be rejected, quarantined or placed in spam. In other cases, the form may fail before it even reaches the mail server. For a business, this matters because a broken contact form can quietly stop enquiries. Unlike a visible website outage, a form issue can go unnoticed for days if nobody is testing it. The safest approach is to test the full path from form submission to inbox, not just the website screen.
    Contact form issues often sit between the website, hosting, DNS and email platform.
    Contact form issues often sit between the website, hosting, DNS and email platform.

    Common Contact Form Email Problems

    Start by identifying what is actually happening. A form that fails on screen needs different troubleshooting from a form that submits but never reaches the inbox.

    The form shows a success message, but no email arrives

    Likely cause

    The website may be creating the message, but it could be blocked by the mail server, rejected because of missing authentication, sent to spam, or delivered to the wrong recipient address.

    Solution

    Check spam and quarantine folders, confirm the recipient address, review SMTP settings and test whether the website's sender domain has correct SPF, DKIM and DMARC records.

    The form displays an error when submitted

    Likely cause

    The form may have a validation problem, a broken script, an expired API key, a blocked CAPTCHA service, or a mail service connection failure.

    Solution

    Test the form with simple data, check browser and server errors, confirm CAPTCHA settings and verify that any connected mail or form service is active.

    Emails only fail sometimes

    Likely cause

    Intermittent failures can be caused by rate limits, server load, temporary provider outages, greylisting, spam filtering changes or DNS propagation after recent record updates.

    Solution

    Record the time of failed submissions, compare them with website logs and mail logs where available, and check whether recent hosting, DNS or email platform changes align with the issue.

    Mail configuration

    SMTP Settings Are Often the First Place to Check

    SMTP is the standard method many websites use to send email through a recognised mail server. Instead of relying on basic server mail functions, the website signs in to an email service or transactional mail platform and asks it to send the message. If the SMTP username, password, port, encryption method or server name is wrong, contact form emails may fail. SMTP can also stop working after a password reset, mailbox licence change, security policy update or provider setting change. Some business email platforms restrict automated sending from websites. For example, SMTP authentication may need to be enabled, or the form may need to send through an approved application method. This depends on the provider and the organisation's security settings. The sender address also matters. A form that tries to send from a visitor's Gmail, Outlook or Yahoo address through your website is more likely to fail authentication. A safer setup is usually to send from an authorised address on your business domain, then set the visitor's address as the reply-to value.
    Correct SMTP configuration helps the website send form notifications through an approved mail pathway.
    Correct SMTP configuration helps the website send form notifications through an approved mail pathway.

    A Successful Form Submission Does Not Always Mean Email Delivery

    Many forms show a success message after the website accepts the form data. That does not always prove the email reached the recipient inbox. Delivery can still fail later because of SMTP errors, DNS authentication problems, spam filtering or mailbox rules.

    DNS and authentication

    How DNS Records Affect Contact Form Emails

    DNS does more than point your domain to a website. It also tells receiving mail servers which systems are authorised to send email for your domain. If those records are missing or incorrect, form notifications can be treated as suspicious. SPF tells receiving servers which mail systems are allowed to send for your domain. DKIM adds a digital signature to help prove the message was not altered. DMARC tells receivers what to do when SPF or DKIM checks fail. These records do not guarantee inbox placement. Spam filtering also considers sender reputation, content, recipient behaviour and provider rules. However, incorrect DNS authentication can make contact form emails much more likely to be rejected, quarantined or marked as spam. DNS changes can also create temporary confusion during propagation. If your website, hosting or email platform has recently changed, some networks may still see old records while others see new ones. That can cause inconsistent results for a short period.
    DNS records support both website routing and email authentication.
    DNS records support both website routing and email authentication.

    Key Terms Used in Contact Form Email Troubleshooting

    These terms often appear when diagnosing why a website form is not sending or why form emails are not arriving.

    SMTP
    SMTP is the mail sending method a website may use to send form notifications through an email server or transactional mail service.
    SPF, DKIM and DMARC
    These DNS-based email authentication records help receiving mail servers verify whether email from a domain is legitimate.
    Reply-to address
    The reply-to address is the email address used when you reply to a form notification. It can be different from the authorised sender address.

    Form Failure vs Email Delivery Failure

    It helps to separate website-side issues from mail-side issues. The symptoms can overlap, but the right fix depends on where the message fails.

    Area Form Failure Email Delivery Failure
    What the visitor sees The form may show an error, fail to submit or keep loading. The form may show a success message even though the email does not reach the inbox.
    Likely causes Validation errors, JavaScript issues, CAPTCHA problems, broken form code or server-side errors. SMTP failure, spam filtering, incorrect recipient address, DNS authentication problems or mailbox rules.
    Where to investigate Website logs, form settings, script errors, CAPTCHA configuration and recent website changes. SMTP logs, DNS records, email platform settings, spam quarantine and recipient mailbox rules.

    Example SMTP Error

    A website or mail log may show an SMTP response that explains why the email was not sent. The exact wording depends on the provider, but the pattern can be useful.

    text
    Form submission accepted by website
    Mail method: SMTP
    SMTP response: 535 Authentication unsuccessful
    Result: Notification email not sent

    This example suggests the form worked, but the mail server rejected the login. It is not a DNS or spam folder issue.

    Diagnosis process

    How to Test a Contact Form Email Issue

    A structured test prevents guesswork. The aim is to find the point where the enquiry stops, then fix that part of the chain.

    1. Submit a controlled test enquiry

      Use a clear test message, include a unique phrase and note the exact time of submission. This makes it easier to search logs, inboxes and spam folders.

    2. Check the recipient and sender settings

      Confirm the notification recipient, sender address, reply-to address and any conditional routing rules. A simple typo or old staff email address can stop enquiries reaching the right person.

    3. Review mail, DNS and hosting settings

      Check SMTP credentials, email authentication records, spam quarantine, server logs and any recent hosting, DNS, form, plugin or platform changes.

    Contact Form Email Checklist

    Use this checklist before assuming the contact form itself is broken. The issue may sit in the website, email platform, DNS, mailbox or hosting environment.

    • Confirm the basics

      Check that the form recipient is correct, the mailbox exists, the inbox is not full and the message has not landed in spam, junk or quarantine.

    • Check authorised sending

      Make sure the website sends from an approved business domain address and that SMTP, SPF, DKIM and DMARC are configured correctly for the chosen mail pathway.

    • Review recent changes

      Look for recent hosting moves, DNS edits, email migrations, password resets, CAPTCHA changes, form updates, plugin updates or security policy changes.

    Common Mistakes That Break Contact Form Emails

    Many form issues are avoidable. These mistakes are common when websites, hosting, domains and email are managed separately.

    Using the visitor's email address as the sender

    Do this instead

    Send from an authorised business domain address and use the visitor's address as the reply-to value. This improves alignment with email authentication checks.

    Changing DNS without documenting old records

    Do this instead

    Record existing DNS settings before making changes. Website, email, SSL, verification and third-party records may all depend on the same DNS zone.

    Testing only with one mailbox

    Do this instead

    Test with more than one recipient type if possible. A message may reach one provider and be filtered by another, especially when authentication or reputation is weak.

    Using SMTP for Website Contact Forms

    Advantages

    • SMTP usually provides a clearer, more reliable sending path than basic server mail functions when it is configured correctly.
    • It allows the website to send through an authorised mail service, which can help with authentication and troubleshooting.
    • SMTP errors often provide useful diagnostic information, such as authentication failure, blocked sending or connection problems.

    Considerations

    • SMTP depends on correct credentials, provider settings and security policies, so password changes or mailbox changes can break sending.
    • Some providers apply rate limits, authentication controls or application restrictions that need to be understood before connecting a website.
    • SMTP does not guarantee inbox placement. Spam filtering, sender reputation and message content still affect the final result.

    When to get help

    Can You Fix a Contact Form Email Problem Yourself?

    Some basic checks are safe for a business owner or internal team. You can submit a test enquiry, check spam folders, confirm the recipient address and review whether a recent password change or mailbox change occurred. Be more careful with DNS, hosting and mail server settings. A wrong DNS edit can affect the website, business email, SSL certificates, verification records and third-party services. Changing sender authentication without understanding the full email setup can also make deliverability worse. Professional help is justified when enquiries are business-critical, the form has stopped working after a migration, the domain is managed by multiple providers, email authentication is missing, or nobody has clear access to the hosting, DNS and mailbox settings. If the issue is urgent, collect useful details before requesting help. Include the form page, test submission time, expected recipient, sender address, recent changes and any visible error messages. This helps reduce diagnosis time.
    Clear access and recent-change history make contact form troubleshooting faster.
    Clear access and recent-change history make contact form troubleshooting faster.

    Our approach

    How We Approach Broken Website Forms

    We treat contact form email issues as an infrastructure problem, not just a design problem. A form depends on the website code, hosting environment, domain DNS, mail provider, spam filtering and mailbox configuration working together. Our website maintenance and repair work can include broken forms, display errors, speed issues, database problems and technical faults on Dobble-built or third-party websites where the scope is agreed. We also provide domain and DNS audits, email deliverability audits, managed hosting and email hosting and management where appropriate. For business email, we primarily use Microsoft 365, with other reputable third-party providers used where client requirements call for them. We configure email systems with the correct DNS authentication where it is part of the agreed work, but no provider can guarantee every email will reach the inbox or avoid spam filtering. For hosting, maintenance, domain and email clients, support is available 24 hours a day, 7 days a week. Emergency support is available, with typical response times within 4 hours. For clients outside an SLA, emergency work is charged on an ad hoc basis, with quotes, predictions or capped timing supplied before work begins where applicable.
    Form reliability depends on website, hosting, DNS and email systems being managed together.
    Form reliability depends on website, hosting, DNS and email systems being managed together.

    Contact Form Email FAQs

    These questions cover common issues businesses notice when website enquiries stop arriving.

    Why does my contact form say sent, but I never receive the email?

    The website may have accepted the form submission, but the email may have failed later. Check SMTP settings, spam folders, quarantine, recipient addresses, DNS authentication and recent hosting or email changes.

    Can missing SPF, DKIM or DMARC records stop contact form emails?

    Yes, missing or incorrect authentication records can cause messages to be rejected or filtered, especially if the form sends from your business domain. They improve trust, but they do not guarantee inbox placement.

    Should my contact form send from the customer's email address?

    Usually no. It is generally safer to send from an authorised address on your own domain and place the customer's email in the reply-to field. This helps avoid authentication problems.

    Need Help Diagnosing a Broken Contact Form?

    If your website form has stopped sending enquiries, we can help review the website, hosting, DNS and email setup. Start with a clear description of the issue and any recent changes, and we will help identify the practical next step.

    Ask Us a Question View Website Maintenance

    Keep learning

    Tap to call
    Enquire now

    Ask Dobble

    Ask a question

    Send us your question and the Dobble team will get back to you.

    Prefer to talk to us directly?

    Get in touch

    Contact us

    Tell us about your project and the Dobble team will be in touch shortly.

    Prefer to talk to us directly?