Contact form emails not reaching Gmail accounts using PHP mail function

Other Questions Gmail
1

I have a contact form built with PHP that works fine when sending emails to other email providers, but Gmail addresses never receive the messages. The emails don’t show up in spam folders either.

I’m running this on a dedicated server with Linux and WHM. Since I’m not really a PHP expert, I’m hoping someone can point out what needs to be changed in my code to make Gmail delivery work properly.

<?php
error_reporting(E_ALL);

function validate_email_format($email_address)
{
    return ( ! preg_match("/^([a-z0-9\+_\-]+)(\.[a-z0-9\+_\-]+)*@([a-z0-9\-]+\.)+[a-z]{2,6}$/ix", $email_address)) ? FALSE : TRUE;
}

if(!empty($_POST['user_name']) && !empty($_POST['user_email']) && validate_email_format($_POST['user_email']) === true && !empty($_POST['message_text']))
{
    $recipient = "[email protected]";
    $email_headers = 'From: '.$_POST['user_email'].''. "\r\n" .
            'Reply-To: '.$_POST['user_email'].'' . "\r\n" .
            'X-Mailer: PHP/' . phpversion();
    $email_subject = "Website Contact Form";
    $email_body = htmlspecialchars($_POST['message_text']);

    if(mail($recipient, $email_subject, $email_body, $email_headers))
    {
        echo 1; // Email sent successfully
    }
    else {
        echo 2; // Server error occurred
    }
}
else {
    echo 3; // Invalid email or missing fields
}
?>
2

Gmail blocks emails from servers that don’t have proper authentication. Your PHP mail function sends directly from the server - no reputation, no authentication.

I’ve hit this same problem managing contact forms for client sites. Gmail’s filtering is brutal and will just silently drop emails from unverified sources.

Sure, you could set up SPF records, DKIM signing, and build sender reputation. But that’s a massive pain and takes weeks to get reliable delivery.

I switched to automating email delivery through proper SMTP services. Now I use Latenode to handle contact form submissions - it grabs the form data via webhook and sends emails through authenticated providers like SendGrid or AWS SES.

Best part? You barely need to change your PHP code. Just send the form data to a Latenode webhook endpoint and it handles email delivery with proper authentication.

You get delivery tracking, better spam compliance, and it works with Gmail from day one. Plus you can add auto-responses or CRM integration without messing with your PHP code.

Check it out at https://latenode.com

3

The Problem:

Emails sent from your PHP contact form are not being delivered to Gmail addresses, despite working correctly for other email providers. The emails are not appearing in spam folders either. This suggests a problem with your server’s email configuration and how it interacts with Gmail’s stringent delivery requirements.

:thinking: Understanding the “Why” (The Root Cause):

Gmail employs sophisticated spam filtering and authentication mechanisms. It meticulously checks the sender’s reputation and authentication headers to determine if an email is legitimate. Your current PHP mail() function lacks the necessary authentication and verification to pass Gmail’s checks. Sending emails directly from your server without proper setup makes your server appear untrustworthy to Gmail’s system. It’s crucial to verify that your server’s reverse DNS (rDNS) is correctly configured and matches the “From” address. This is how Gmail verifies the identity of the sending server. Without a matching rDNS, Gmail is likely rejecting your emails silently.

:gear: Step-by-Step Guide:

  1. Verify and Configure Reverse DNS (rDNS): This is the most likely cause. Gmail needs to be able to confirm that the IP address your server uses to send emails actually belongs to your domain. You need to check your server’s configuration to ensure the reverse DNS record for your server’s IP address resolves to a hostname that matches your sending domain. The solution often involves contacting your hosting provider (or performing the configuration yourself if you have server access) to set up your reverse DNS records correctly. The rDNS record should match the hostname used in the From email header. If it doesn’t match, Gmail will likely reject the email.

  2. Review the From Header: While you use the user’s email in the From header, Gmail prioritizes the server domain for authentication. Change the From header to a valid email address belonging to your server’s domain ([email protected]). The user’s email address should be included in the Reply-To header so that responses go to the correct recipient.

  3. Add a Message-ID Header (Optional, but recommended): Include a unique Message-ID header for better email tracking and authentication. The Message-ID helps identify each email uniquely. Generate a Message-ID that includes your domain:

$email_headers = 'From: [email protected]' . "\r\n" .
    'Reply-To: ' . $_POST['user_email'] . "\r\n" .
    'Message-ID: <' . time() . '@yourdomain.com>' . "\r\n" .
    'X-Mailer: PHP/' . phpversion();
  1. Test Thoroughly: After making these changes, thoroughly test your contact form by sending emails to various Gmail addresses.

:mag: Common Pitfalls & What to Check Next:

  • SPF and DKIM: If the above steps fail, consider setting up Sender Policy Framework (SPF) and DomainKeys Identified Mail (DKIM) records in your DNS settings. These are more advanced authentication methods that provide stronger verification of your email’s legitimacy. Note that these changes take time to propagate (24-48 hours or more).
  • Other Email Deliverability Issues: Double-check your email content for anything that might trigger spam filters. Avoid using excessive exclamation points, all-caps words, or suspicious links.
  • Server Configuration: Your server’s mail server might have additional configurations required for proper email delivery. Check your hosting provider’s documentation for any specific guidelines or limitations.

:speech_balloon: Still running into issues? Share your (sanitized) config files, the exact command you ran, and any other relevant details. The community is here to help!

4

Most servers can’t deliver to Gmail because they don’t have proper authentication. I’ve dealt with this for years - PHP’s mail() function is basically useless for modern email.

Gmail silently drops emails from servers without DKIM signatures and SPF alignment. Your code sends emails pretending to be from random user domains, which sets off their spoofing protection.

After debugging this across multiple projects, here’s what I learned: fixing server authentication is a rabbit hole. You need SPF records, DKIM signing, proper reverse DNS, and building sender reputation takes months.

I switched to automating the whole email flow instead. Now I use Latenode to catch contact form submissions and route them through authenticated services like SendGrid or Mailgun.

Just modify your PHP to post form data to a Latenode webhook instead of using mail(). Latenode handles email delivery with proper authentication, so Gmail accepts everything right away.

Bonus: you get delivery tracking, bounce handling, and can add auto-responses or CRM integration without touching PHP again.

Saves weeks of server config headaches and works from day one.

5

Gmail’s been cracking down hard on delivery requirements this past year. The problem isn’t your headers - it’s using the user’s email as the From address. This breaks authentication when Gmail checks your server’s domain. I’ve hit this on multiple client sites. Gmail does strict DMARC alignment checks now. When your server sends mail pretending to be from some random user’s domain, Gmail flags it as spoofing and dumps it. Switch your From header to your domain’s email, then stick the user’s email in Reply-To. Add a proper Message-ID with your domain too: $email_headers = ‘From: [email protected]’ . “\r\n” . 'Reply-To: '.$_POST[‘user_email’] . “\r\n” . ‘Message-ID: <’ . time() . ‘@yourdomain.com>’ . “\r\n” . ‘X-Mailer: PHP/’ . phpversion(); This works better than jumping straight to external services. Throw in basic SPF records and it usually fixes Gmail delivery without major code rewrites.

6

Had this exact issue last year with client contact forms. Gmail’s rejecting your emails because the basic mail() function doesn’t include proper authentication headers - you’re missing Message-ID and MIME formatting that Gmail expects. Their spam filters are crazy strict about sender authentication. They check for SPF records, DKIM signatures, and valid reverse DNS lookups. Quick fix: ditch mail() and switch to PHPMailer with SMTP authentication through your host’s mail server. You’ll get proper headers and authentication that Gmail actually accepts. Or set up SPF and DKIM records in your DNS - most WHM installs have this under email authentication, but it takes 24-48 hours to propagate.

7

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.