WordPress站点多表单发件域名邮箱收不到邮件问题求助

Hey there, let's break down your three core issues one by one—this is a super common setup scenario when mixing web hosting, external DNS, and G Suite, so I’ve got practical fixes for each part.

一、自有域名邮箱收不到邮件的核心成因 #

Your problem boils down to misconfigured DNS records and potential server-side routing conflicts:

• MX Record Misalignment: Since you’re using G Suite for email but pointing your website to Bluehost via A records, you probably forgot to update your domain’s MX records to point to G Suite’s servers. Most default setups leave MX records pointing to the web host (Bluehost here), so emails sent to @mydomain.com get routed to Bluehost’s local mail system instead of G Suite.
• Missing/Incorrect SPF/DKIM: Even if MX records are right, without proper SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail) records, G Suite might flag incoming emails as spam or reject them entirely—these records verify that the sender is authorized to use your domain.
• Bluehost’s Local Email Routing: Some web hosts (including Bluehost) default to routing emails sent to your domain to local cPanel mail accounts, ignoring your MX records. This means even if MX is set to G Suite, emails get stuck on Bluehost’s server instead of being forwarded.

二、WP Mail SMTP Multiple Sender Addresses Fix #

WP Mail SMTP’s free version locks you into one default sender, but there are two solid workarounds for per-form senders:

1. Use Your Form Plugin’s Built-In Settings #

Most form plugins (Contact Form 7, Gravity Forms, Ninja Forms) let you set a custom sender address directly in their form-specific mail settings. As long as WP Mail SMTP is configured to use a valid SMTP server (like G Suite’s), the form will override the default sender automatically. For example:

• In Contact Form 7, go to the Mail tab of your form, set the "From" field to support@mydomain.com, and ensure the "From name" matches your team.
• This works because WP Mail SMTP handles the delivery infrastructure, while the form controls the sender identity.

2. Custom Code Hook (Free, For Advanced Users) #

If you need more control, add this code to your theme’s functions.php file or a custom plugin to dynamically swap senders based on the form being submitted:

// Override sender email based on form ID
add_filter('wp_mail_from', 'dynamic_form_sender_email');
function dynamic_form_sender_email($default_email) {
    // Adjust the form ID checks to match your setup
    if (isset($_POST['_wpcf7']) && $_POST['_wpcf7'] == '123') { // Contact Form 7 form ID
        return 'support@mydomain.com';
    } elseif (isset($_POST['form_id']) && $_POST['form_id'] == 'info_form') { // Custom form ID
        return 'info@mydomain.com';
    }
    return $default_email;
}

// Override sender name to match
add_filter('wp_mail_from_name', 'dynamic_form_sender_name');
function dynamic_form_sender_name($default_name) {
    if (isset($_POST['_wpcf7']) && $_POST['_wpcf7'] == '123') {
        return 'Support Team';
    } elseif (isset($_POST['form_id']) && $_POST['form_id'] == 'info_form') {
        return 'Info Team';
    }
    return $default_name;
}

Note: Adjust the form ID checks to match your plugin’s POST parameters (e.g., Gravity Forms uses gf_token or form_id).

三、Get G Suite to Receive All @mydomain.com Emails (No NS Record Changes) #

You don’t need to switch NS records—just fix your domain’s DNS settings in your current domain registrar’s dashboard:

• Update MX Records: Delete all existing MX records and add G Suite’s official ones with correct priorities:
  • Priority 1: ASPMX.L.GOOGLE.COM
  • Priority 5: ALT1.ASPMX.L.GOOGLE.COM
  • Priority 5: ALT2.ASPMX.L.GOOGLE.COM
  • Priority 10: ALT3.ASPMX.L.GOOGLE.COM
  • Priority 10: ALT4.ASPMX.L.GOOGLE.COM
• Add SPF Record: Create a TXT record with content: v=spf1 include:_spf.google.com include:bluehost.com ~all (include bluehost.com only if you’re sending emails from Bluehost’s server; if using WP Mail SMTP with G Suite, use v=spf1 include:_spf.google.com ~all instead).
• Set Up DKIM: In your G Suite Admin Console, generate a DKIM key for your domain, then add a TXT record in your DNS with the key details. This verifies email authenticity.
• Configure DMARC: Add a TXT record: v=DMARC1; p=none; sp=none; rua=mailto:dmarc@mydomain.com to monitor email delivery. Later, you can tighten this to p=quarantine or p=reject to block spoofed emails.
• Fix Bluehost’s Email Routing: Log into Bluehost’s cPanel, go to Email Routing, and select Remote Mail Exchanger. This tells Bluehost to forward all @mydomain.com emails to your MX-record-specified G Suite servers instead of storing them locally.

内容的提问来源于stack exchange，提问作者Eyal Binehaker