Send a WordPress test email with Regal Send

Updated September 20, 2026

Send a WordPress test email with Regal Send to verify that the active mailer can prepare and submit a message. The result reports transport acceptance or a safe failure category without exposing passwords, API keys, OAuth tokens or raw provider responses.

Before you send a WordPress test email#

Open Regal Send and confirm that the intended mailer is selected. Complete its configuration and, for Google or Microsoft, confirm that its connection state is Connected. For Elastic Email, save an API key with the required sending permission. For SMTP, save the host, port, encryption and authentication details supplied by the provider.

Use a recipient inbox you can check. A successful result means the configured transport accepted the request. It does not prove that the recipient server placed the message in the inbox.

How to send the test message#

1. In WordPress, open Regal Send, then Test Email.
2. Review the Active mailer card. Resolve a Not configured or Authentication problem state before testing.
3. Enter a valid recipient email address.
4. Select HTML to test a styled message with a plain-text alternative, or select Plain text for a text-only message.
5. Select Send test email.
6. Wait for the result before trying again. Regal Send blocks duplicate submissions while the request is running.
7. Check the recipient inbox and spam folder.

What the Test Email result shows#

• Transport result: whether the configured transport accepted or rejected this request.
• Diagnostic: an evidence-based category such as configuration, authentication, permission, sender, recipient, TLS, connection or provider response.
• Mailer and format: the active delivery method and selected message type.
• Logging mode: the privacy mode applied to this email attempt.
• Duration: the time Regal Send spent in the transport operation.
• Provider identifiers: safe response, request or message identifiers when the provider supplies them.
• Retryable: whether the failure is likely to be temporary, such as a rate limit or server error.

Provider acceptance is not final delivery. Delivery can still be affected by recipient-server policy, spam filtering, domain authentication and mailbox rules. Google provides a practical introduction to email sender requirements, while Microsoft documents email authentication methods.

Troubleshoot a failed WordPress test email#

Configuration#

Complete the fields for the selected mailer. Check the SMTP host and port, Elastic Email API key, or OAuth Client ID and secret. Save settings before testing again.

Authentication#

Replace an invalid SMTP password or Elastic Email API key. For Google or Microsoft, use the provider Reconnect control and complete consent again. Authentication details are encrypted and are never shown in Test Email diagnostics.

Permission#

Confirm that Google granted the Gmail send scope or that Microsoft granted delegated Mail.Send. For Elastic Email, confirm that the API key has SendHttp access. Do not add broader permissions unless another documented workflow requires them.

Sender#

Confirm that the From Email is accepted by the provider. Gmail requires the connected mailbox or an authorised sender alias. Elastic Email requires a verified sender or domain. SMTP providers may restrict sending to the authenticated mailbox.

TLS or connection#

Confirm the SMTP port and encryption combination, the server certificate, firewall rules and outbound connectivity. A rate-limited result is marked retryable, so wait before testing again.

No Regal Send result was captured#

Another mail plugin may have intercepted wp_mail(). Deactivate competing email delivery plugins and use one mail transport plugin at a time. Regal Send shows a conflict warning when it detects a known active mail plugin.

How Test Email interacts with logging#

The test uses the normal WordPress mail path and the current Regal Send logging mode. Logging Off creates no record. Metadata Only records the result and safe message metadata without the body. Full Logging can retain the message body, so use a non-sensitive recipient and remember that test content may be stored until it is deleted.

What to check after a successful result#

• Confirm that the message arrived in the intended inbox.
• Check the displayed sender name and address.
• Verify HTML and plain-text rendering as needed.
• Review spam placement and the receiving system’s authentication results.
• Open Email Logs when logging is enabled and confirm the accepted transport record.