Skip to main content

Troubleshoot Email Delivery Issues

Introduction​

This document explains how Divi Form Builder delivers email notifications and outlines steps to resolve common delivery failures. Email transmission depends on WordPress’s wp_mail() function and the server or SMTP configuration used by the host.

1. Email Delivery Process​

  1. Form submission triggers Divi Form Builder’s email routine.
  2. Divi Form Builder passes email parameters to WordPress’s wp_mail().
  3. WordPress invokes the server’s mail handler (PHP mail or configured SMTP).
  4. The server sends the message to the recipient’s mail server.
note

Divi Form Builder uses WordPress’s mail functions and does not include a built-in mail server. Issues in PHP mail or hosting configuration must be addressed at the server level or by using an SMTP/transactional email service.

2. Preliminary Verification​

2.1 Form Module Settings​

  • Confirm Email Notifications and/or Email Confirmation are enabled.
  • Verify the Recipient Email address for accuracy.
  • Use a Sender Email address on the site’s domain (e.g., [email protected]) to reduce spam filtering.

2.2 Validation Testing​

  • Complete all required fields to ensure form submission succeeds.
  • Review any custom validation rules that could block submissions.

3. SMTP Configuration​

  1. Install an SMTP plugin (for example, WP Mail SMTP).
  2. Enter SMTP server details: host, port, encryption, credentials.
  3. Send a test email via the plugin’s settings.
    • If the test fails, adjust SMTP settings before further troubleshooting.
  4. See the WP Mail SMTP setup guide for detailed instructions.
tip

An SMTP service or transactional email provider (Mailgun, SendGrid, Amazon SES) can improve reliability over PHP mail.

4. Notification and Confirmation Setup​

  1. In the Form Module, open the Email Notification settings:
    • Verify To, From, Subject, and Message fields.
  2. If using Email Confirmation, confirm its settings do not conflict with the notification email.
  3. Advise recipients to inspect spam or junk folders if messages are not found in the inbox.
note

For more information on email notification and confirmation click HERE and HERE.

5. Conflict Detection​

5.1 Plugin Conflicts​

  1. Temporarily deactivate plugins related to email, forms, or security.
  2. Resubmit the form.
  3. If emails send successfully, reactivate plugins individually to identify the conflicting extension.

5.2 Child Theme Conflicts​

  1. Switch to a core Divi theme.
  2. Submit the form again.
  3. A successful delivery indicates a child theme-related conflict.

6. Debugging and Log Inspection​

  1. Enable WordPress debug logging by adding to wp-config.php: 
    define( 'WP_DEBUG', true );
    define( 'WP_DEBUG_LOG', true );
    define( 'WP_DEBUG_DISPLAY', false );
  2. Submit the form and review /wp-content/debug.log for errors.
  3. Examine the server’s mail logs or hosting control panel for mail delivery errors.

7. Alternative Delivery Methods​

  • Use a dedicated transactional email service (Mailgun, SendGrid, Amazon SES).
  • Implement a workflow with Zapier or Make (Integromat) to capture form data and send emails externally.

8. Best Practices​

  • Maintain the latest versions of WordPress, themes, and plugins.
  • Monitor delivery using email testing tools such as Mailtrap or service-provided logs.
  • Use domain-based sender addresses to enhance deliverability.