Problem/Motivation
The CLI notes globally disabled suppression but can then print SUPPRESSED based on history. The settings form does not surface the known mailer coverage and retention caveats. Operators cannot distinguish historical evidence from what the current mail path will actually do.
Evidence and scope
Reviewed 1.0.0-alpha1, source commit 02fd9d36af5237e712cecb7155d79725f7824880. Location: src/Commands/PostmarkWebhookCommands.php:34.
Disabled-mode wording is code-confirmed. No live admin accessibility assessment was performed.
Proposed resolution
Build a read-only would-this-send preview on the shared decision service, reporting effective enabled state, reason, expiry and known adapter coverage. Add structured Drush output. Expose secret configured/not configured, recent successful intake and aggregate error/duplicate counts without displaying credentials or mailbox metrics labels.
Acceptance criteria
Disabled suppression must never be reported as an enforced block. Tests cover JSON output, missing secret, unsupported mail path and privacy-safe diagnostics. Keep this read-only; it must not send test mail or mutate consent.
Comments
Comment #2
jmcerdaImplemented the protected no-send policy preview, effective mail-path coverage reporting, and structured Drush status/diagnostics commands. Globally disabled suppression cannot appear as an enforced block. Diagnostics expose credential readiness and fixed aggregate accepted/duplicate/authenticated-rejection counters without mailbox or secret labels. Update 10004 creates counters without reconstructing past totals.
All six compatibility jobs are green, including actual Drush command discovery, aliases and JSON output. Kernel and HTTP tests cover disabled and unsupported paths, preview permissions/no-cache behavior, absence of preview writes, atomic concurrent counters and update idempotency. The implementation is awaiting integration.
Comment #6
jmcerdaIntegrated into the 1.x development branch and included in 1.0.0-alpha2. The release tag and branch are mirrored to Drupalcode. The six-job Drupal 10/11 and Mailer Plus integration matrix passes. See the release notes for database updates and retained-history limitations. This records module publication; site deployment is a separate operation.