Elementor Site Mailer shows whether a recipient was suppressed manually or through unsubscribe behavior. Those labels should not be treated as interchangeable. Manual entries may represent support, risk, bounce, legal, or testing decisions. Unsubscribed entries represent a recipient action or compatible mail flow. Removing either without source evidence can restart unwanted mail, hide a deliverability fault, or override an operational control.
Use this for support, marketing operations, privacy teams, and site administrators reviewing Site Mailer suppressions. The audit is especially useful after a migration, staff change, bulk import, complaint, or a report that valid form confirmations are no longer arriving.
Quick answer
Export or review suppression rows with a case-safe recipient reference, method, timestamp, actor where available, related message ID, business reason, and affected message classes. Reconstruct the source from Site Mailer, WordPress, help desk, and consent evidence. Remove a row only with named authorization and a documented message class, then use one synthetic or owner-approved message to verify the result.
What to check first
- Capture recipient reference, Manual or Unsubscribed method, created time, last related message, source plugin, message class, support case, and current business relationship.
- For Manual rows, identify the authorized actor or process and whether the reason was complaint, invalid address, risk, bounce, testing, or temporary incident control.
- For Unsubscribed rows, preserve the related message ID, header method, request time, endpoint result, and scope expected by the published preference policy.
- Review whether To, CC, BCC, Reply-To, aliases, case normalization, plus-addressing, and shared mailboxes create multiple identities for one person or role.
- Require an owner, purpose, removal authorization, single-message test, expected outcome, and rollback action before changing any row.
Diagnostic table
Use this table to keep the work practical. It connects the symptom to evidence and a verification step.
| Action | Evidence to collect | How to verify |
|---|
| Inventory recipient-level evidence | Capture recipient reference, Manual or Unsubscribed method, created time, last related message, source plugin, message class, support case, and current business relationship. | Every reviewed row has a source, reason, owner, and message scope. |
| Reconstruct the source and intended scope | For Manual rows, identify the authorized actor or process and whether the reason was complaint, invalid address, risk, bounce, testing, or temporary incident control. | Manual and Unsubscribed rows are reported separately. |
| Resolve identity and message-class ambiguity | For Unsubscribed rows, preserve the related message ID, header method, request time, endpoint result, and scope expected by the published preference policy. | Removal actions have authorization and a bounded verification message. |
| Require named authorization for removal | Review whether To, CC, BCC, Reply-To, aliases, case normalization, plus-addressing, and shared mailboxes create multiple identities for one person or role. | Support access exposes only the recipient information needed for the task. |
Why this usually happens
- Manual is a mechanism label, not a complete business reason.
- An unsubscribe can be valid for promotional-like mail while a required transaction needs another approved route.
- Shared and aliased addresses can make recipient identity ambiguous.
- Support teams may remove a symptom before fixing the failed form or sender authentication issue.
- Logs and suppression data can expose personal information to users who only need status access.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
case_id: ELM-SUP-20260724-17
recipient_ref: sha256:8a31...
method: Manual
created_utc: 2026-07-22T14:08:00Z
reason: invalid_address_confirmed
source_case: HD-1842
affected_classes: [form_confirmation]
removal_authorized: false
owner: email_operations
next_review: 2026-08-22
Safe fix order
Do the work in a sequence that makes each result easy to prove. Stop if a step produces new evidence that changes the incident scope.
- Inventory recipient-level evidence
- Reconstruct the source and intended scope
- Resolve identity and message-class ambiguity
- Require named authorization for removal
- Send one bounded test and restore controls if needed
Decision rule
Keep a suppression when its source or permission is unclear. Remove it only when an authorized owner confirms the recipient, purpose, message class, and current permission, and when the underlying address or delivery problem is fixed. Never use a test send to discover consent.
What to tell the client or owner
Give the site owner the affected version, exact workflow, observed result, business impact, evidence location, temporary control, named owner, and next review time. Remove credentials and personal data from shared screenshots and logs.
Production verification checklist
- Every reviewed row has a source, reason, owner, and message scope.
- Manual and Unsubscribed rows are reported separately.
- Removal actions have authorization and a bounded verification message.
- Support access exposes only the recipient information needed for the task.
Mistakes to avoid
- Do not bulk-remove manual entries after an import without provenance.
- Do not override Unsubscribed because a campaign is urgent.
- Do not post full recipient exports in a shared ticket.
- Do not test removal with a batch or a production automation.
Questions teams ask during testing
Can an administrator remove an Unsubscribed recipient?
The interface may allow it, but the organization still needs a valid permission and policy basis. Technical capability is not authorization.
Why keep Manual and Unsubscribed separate in reports?
They reflect different initiating events and usually require different evidence, owners, and recovery decisions.
When HandL WP should help
Bring in HandL WP when this affects a production site, paid lead flow, checkout, email delivery, or a managed fleet. We can preserve evidence, isolate the failing layer, make the smallest corrective change, and verify the result across WordPress, the external service, logs, and the user journey.
If this is active on a production site, review an Elementor suppression issue.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references