Email Check plugin: a test failed without an error message

The test email failed, but the nanoPost Email Check plugin did not receive an error message explaining why. If your site uses an email-sending plugin, start with its own settings and log: it may have more information about the attempt.

You do not need to run commands to begin. The checks below help you gather enough detail to fix a setting or ask the right person for help. If you maintain the site’s code, you can jump to developer checks.

Look for more detail in your sending plugin

Open Plugins > Installed Plugins and identify anything used to send, queue or disable email. A sending plugin is the one that connects WordPress to your email service. If someone else configured it, ask them which plugin and service the site uses.

Open that plugin’s settings and look for an email log, error log or test-email screen. Compare any error there with the time of the failed test in Tools > Email Check. If logging was off, enable it using that plugin’s instructions and run Send test now again to capture a fresh attempt.

If you find an error message, paste it into the error decoder. If you find a setting that intentionally blocks email, check why it was enabled before changing it. A staging site, a separate copy used for testing changes, may be configured to prevent messages reaching real customers.

Ask for help with the evidence you have

If there is still no explanation, send your host or the sending plugin’s support team:

  • The exact time of a failed test and the timezone shown by your site.
  • The names of the plugins involved in sending, queuing or disabling email.
  • Any error from the sending plugin’s own log, or confirmation that it recorded none.
  • Whether this is the live site or a staging copy, and whether sending used to work.

Ask them to investigate a failed WordPress email test for which Email Check received no error text. Some hosts add their own sending code, so the host may need to check components you cannot see in the ordinary plugin list.

When a setting is corrected, return to Tools > Email Check, press Send test now, and check both the new result and the receiving mailbox. What a pass means explains why those are separate checks.

Isolate a plugin conflict on a staging copy

If the logs do not identify the cause, a developer can test whether changing the active plugins changes the result. Use a staging copy for this work: disabling a sending plugin on a live shop or membership site can alter how customer messages are sent.

Keep Email Check active. Disable one relevant plugin at a time, run a new test and record the result. Restore that plugin before testing another, so each comparison changes one thing. A changed result identifies something to investigate; it does not by itself prove that the plugin is defective.

A passing test after removing the configured mailer may use a different sending route. Confirm delivery and restore the intended configuration before treating the problem as resolved.

Developer checks

The missing message tells you that the test returned a failure result without an error being captured through wp_mail_failed, WordPress’s mail-failure event. It does not identify the component responsible.

There are several places to investigate in the WordPress sending function: a pre_wp_mail filter can stop the function early; custom code can replace wp_mail(); and a replacement mailer can return failure without throwing the exception that core catches. These are code paths to inspect, rather than a diagnosis from the warning alone.

With WP-CLI, the command-line tool for WordPress, run the following from the site’s WordPress directory. The first command prints the file defining the active sending function:

wp eval '$f = new ReflectionFunction( "wp_mail" ); echo $f->getFileName(), PHP_EOL;'

Core defines it in wp-includes/pluggable.php. A different path points to the replacement code. Check must-use plugins as well as ordinary plugins; hosts can install sending integrations there.

The next command checks whether a callback is registered on the filter that can stop sending early:

wp eval 'var_dump( has_filter( "pre_wp_mail" ) );'

A true result establishes that the filter has a callback. Read the callback to find out what it returns; its presence alone does not mean it blocks mail. If neither check explains the failure, inspect the configured mailer’s send method and its own error handling.

For the source-level explanation of which errors reach WordPress, the mail-failure hook guide follows the relevant paths through the sending code.