Resend a WordPress email from Regal Send logs

Updated September 20, 2026

Resend a WordPress email from Regal Send when Full Logging retained the complete original body and every attachment copy. The review step lets an authorised administrator confirm or change To, CC and BCC recipients before creating a separate new send attempt.

When you can resend a WordPress email#

Exact resend is available only for a complete Full Logging record. Regal Send checks eligibility before showing the review action. It refuses resend when the body is missing, there is no valid To recipient, an attachment copy is missing, or an encrypted attachment fails its integrity check.

• The original record must use Full Logging.
• At least one retained HTML or plain-text body must be available.
• The record must contain a valid To recipient.
• Every retained attachment must have a valid encrypted copy.
• The current active mailer must be configured for the new send attempt.

Metadata Only records deliberately do not retain message bodies. They show an explanation instead of a resend control. This protects the privacy choice made when the original email was logged.

How to review and resend an email#

1. In WordPress, open Regal Send, then Email Logs.
2. Open the email record you need.
3. In Resend this email, select Review and resend.
4. Review the original subject, retained plain-text and HTML content, and the attachment list.
5. Check the To recipients. Add or remove addresses as required, separating multiple addresses with commas.
6. Expand CC and BCC recipients when those fields need review or editing.
7. Select Confirm and resend.
8. Approve the confirmation prompt.
9. Review the newly created linked email log.

What Regal Send preserves#

The resend rebuilds the original subject, HTML body, plain-text alternative, Reply-To recipients and safe semantic headers. Retained attachment copies are decrypted into temporary files only for the send operation. Inline attachments with a retained Content ID are rebuilt as embedded content. Normal attachments keep their retained filename and MIME type.

Temporary decrypted files are removed on success and failure. The encrypted retained copy remains protected in Regal Send private storage until the associated log is deleted.

What can change during resend#

Resend uses the mailer that is active when you confirm, not necessarily the mailer used by the original record. It also applies the current Regal Send sender rules. This allows an administrator to recover from an old provider failure by selecting and configuring a working mailer before resending.

To, CC and BCC are explicitly reviewable. The original Reply-To recipients are preserved. Recipient fields accept valid email addresses separated by commas and reject malformed values before any provider request is made.

How original and new logs are handled#

The original log is never changed or deleted by resend. Regal Send creates a new log and records the original log ID as its resend source. The new detail screen links back to the original record.

If current logging is Full, the new record retains complete content again. If it is Metadata Only, the new record follows that privacy mode. If logging is Off, Regal Send still creates a metadata-only operational record for the explicit resend so the attempt and its outcome are auditable.

Troubleshoot resend availability#

The record says Metadata Only#

The body was not retained, so exact resend is unavailable. Send a new message from the originating plugin or workflow. Enable Full Logging only when the privacy and storage implications are acceptable for future messages.

A retained attachment is unavailable#

Regal Send fails closed and does not submit a partial message. The attachment copy may have been removed, corrupted or unavailable from private storage. Recreate the message from its original workflow instead.

The current mailer is not configured#

Open Regal Send settings, configure the selected mailer, and use Test Email to verify it. Return to the original log and review the resend again.

The resend attempt failed#

Open the linked new log and review its safe error category, provider status and retryable state. The original log remains unchanged, so you can correct the configuration and begin a new reviewed attempt.

Privacy and security considerations#

• Only users with Regal Send management capability can access or submit resend.
• Every submission uses a WordPress nonce and explicit confirmation.
• Recipient input is validated before sending.
• Encrypted attachment integrity is checked before temporary decryption.
• Provider credentials and raw sensitive errors are never displayed in the resend review.
• BCC recipients are visible to the administrator reviewing the operation but remain BCC recipients in the new message.

Review the WordPress nonce guidance for background on request verification. Nonces complement capability checks and do not replace them.