A List-Unsubscribe header can appear in raw email without producing a working inbox action. The HTTPS endpoint may reject the POST, the List-Unsubscribe-Post value may be malformed, the mailbox provider may hide the control, or the resulting suppression may affect the wrong message classes. A useful Elementor Site Mailer test follows one synthetic recipient from message source through raw headers, inbox UI, unsubscribe request, suppression record, and subsequent send decisions.
Use this for WordPress sites sending form confirmations, newsletters, account messages, WooCommerce email, and operational alerts through Elementor Site Mailer. Use synthetic addresses in controlled Gmail, Outlook, and Apple Mail accounts rather than asking a customer to test production preferences.
Quick answer
Send uniquely marked messages from representative WordPress sources to controlled mailboxes. Save the raw message source, confirm both List-Unsubscribe and List-Unsubscribe-Post syntax, use the mailbox one-click action, capture the HTTPS POST and response where possible, and verify the recipient enters the expected suppression state promptly. Then send an approved promotional-like test and a separately classified required transaction to confirm scope.
What to check first
- Record sending domain authentication, Site Mailer version, source plugin, message class, recipient fixture, UTC time, message ID, and expected suppression behavior.
- Inspect raw headers for List-Unsubscribe mailto and HTTPS methods, List-Unsubscribe-Post: List-Unsubscribe=One-Click, angle brackets, HTTPS, and recipient-specific token handling.
- Check whether Gmail, Outlook, and Apple Mail display a one-click or unsubscribe control and whether the action requires an unnecessary login or confirmation.
- Record endpoint status, suppression timestamp, displayed method, recipient state, and the result of a new promotional-like message after suppression.
- Test a separately approved required transaction and document whether it is intentionally sent, suppressed, or routed through another sender.
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 |
|---|
| Create controlled mailbox fixtures | Record sending domain authentication, Site Mailer version, source plugin, message class, recipient fixture, UTC time, message ID, and expected suppression behavior. | Raw headers contain both the unsubscribe destination and one-click POST declaration. |
| Inspect exact raw header syntax | Inspect raw headers for List-Unsubscribe mailto and HTTPS methods, List-Unsubscribe-Post: List-Unsubscribe=One-Click, angle brackets, HTTPS, and recipient-specific token handling. | The endpoint returns a bounded success response and creates one suppression record. |
| Exercise the inbox one-click action | Check whether Gmail, Outlook, and Apple Mail display a one-click or unsubscribe control and whether the action requires an unnecessary login or confirmation. | A promotional-like test is suppressed after the action. |
| Verify the suppression record and timing | Record endpoint status, suppression timestamp, displayed method, recipient state, and the result of a new promotional-like message after suppression. | Required transactional handling matches the written business policy. |
Why this usually happens
- Mailbox providers apply their own trust and display rules even when headers are syntactically present.
- One-click unsubscribe uses an HTTPS POST contract that differs from a normal confirmation page link.
- A token can expire, be reused incorrectly, or expose the recipient address in logs.
- WordPress sources may not be classified consistently as promotional-like or required transactions.
- Cached support screens can lag behind the suppression event and encourage an unsafe resend.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
message_id: ELM-UNSUB-20260724-08
source: elementor_form_confirmation
class: promotional_like
list_unsubscribe_methods: [mailto, https]
list_unsubscribe_post: "List-Unsubscribe=One-Click"
inbox_control: visible
endpoint_status: 200
suppression_method: Unsubscribed
suppression_delay_seconds: 4
next_marketing_send: suppressed
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.
- Create controlled mailbox fixtures
- Inspect exact raw header syntax
- Exercise the inbox one-click action
- Verify the suppression record and timing
- Retest approved message classes separately
Decision rule
Pass when raw headers are correct, supported inboxes expose the intended action, the one-click POST succeeds without extra user friction, the correct recipient is suppressed promptly, and later messages follow the documented class policy.
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
- Raw headers contain both the unsubscribe destination and one-click POST declaration.
- The endpoint returns a bounded success response and creates one suppression record.
- A promotional-like test is suppressed after the action.
- Required transactional handling matches the written business policy.
Mistakes to avoid
- Do not test by unsubscribing a real customer.
- Do not call a footer preference page a one-click header test.
- Do not put the recipient email directly in a reusable URL.
- Do not assume every WordPress email should bypass or obey the same suppression rule.
Questions teams ask during testing
Why does Gmail not show the unsubscribe button?
Header syntax is only one factor. Sender reputation, message classification, authentication, and provider policy can affect display.
Should password reset email include one-click unsubscribe?
Required account and security messages need a separate legal and operational classification. Do not copy marketing behavior into them without review.
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, audit Elementor email deliverability.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references