starred/warmbly
1
0
Fork 0
mirror of https://github.com/warmbly/warmbly.git synced 2026-10-13 00:02:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

feat: keep mailbox health and usage unknown until Cloud and account status checks finish with refresh and incomplete-data regressions

Browse Source
This commit is contained in:
Matthew Meszaros
2026-10-09 16:27:20 +00:00
committed by Devin AI
parent 2cf19ebedf
commit cdb102ca56
5 changed files with 115 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/content/docs/guides/mailboxes.mdx
+2
View File
@@ -7,6 +7,8 @@ Browsing filters, searches and view choices are [remembered in your browser tab]
A mailbox is a sender account you connect to Warmbly. Every warmup message and campaign email goes out through one you own.
The Accounts list checks mailbox health and, on linked self-hosted instances, Cloud warmup standing separately from the mailbox inventory. While those checks are loading or refreshing, it shows **Checking…** rather than treating missing results as Idle, Healthy, or zero sent. A failed or incomplete check shows **Unavailable**, not a measured zero or a claim that the mailbox recovered. A displayed health score is an account-health assessment, not proof that the provider confirmed a send; check send records and the mailbox's error details when investigating a stopped mailbox.
### Diagnostic participation and stopping
New mailboxes default to diagnostic participation **off**. The organization-authorized mailbox PATCH exposes `test_mode` (`off`, `diagnostic`, `legacy`), separate `test_send_enabled` and `test_receive_enabled` flags, and optional positive `shared_daily_limit`/`rolling_recipient_limit`. These are API controls, not new dashboard switches. Diagnostic mode sends disclosed tests but does not manufacture reads, stars, importance or spam rescue. Existing upgraded mailboxes with NULL participation retain legacy behavior until explicitly changed. Set `test_mode=off` to stop future diagnostic send/receive admission; current protocol-2 workers also recheck queued sends/actions. Already accepted old-worker commands or a provider send underway cannot be recalled. A local Cloud alias unlink stops local authority, not an independently cloud-owned mailbox or provider grant: pause/remove that mailbox on Cloud separately. See [send safety, repair evidence and rollout](/development/send-safety/).