# Check sending health

Read domain health before changing sending controls. Barua shows authentication
checks separately from delivery evidence. A small sample or missing feedback
does not become a reputation score.

## Read the current state

Supply `BARUA_MANAGEMENT_KEY` and use the [installed helpers](/docs/guides/quickstart.md):

```sh
node "$BARUA_SKILL/scripts/inspect.mjs" deliverability
```

The result includes the active domain and its version. Check when the evidence
was collected, whether marketing is held, and the recommended next action.
The dashboard's Deliverability screen uses the same saved evidence.
The read requires an active management connection, with no additional grant
and no customer addresses in the response.

Authentication evidence covers domain ownership and DKIM, plus the bounce
domain and sending service. DMARC guidance helps identify a missing policy.
A failed lookup can be unknown rather than proof of broken authentication.

## Change a control

Follow the exact inputs in the [deliverability reference](/skills/barua-setup/references/management.md#deliverability).
Use the current domain and version, and keep the same idempotency key when
retrying the same operation.

Enabling safeguards or resuming marketing requires `launch:write` and the
connection's launch review. Requesting a fresh check requires `setup:write`.
Existing senders stay in observation until safeguards are accepted. A pause
or check request does not turn on sending.
`automaticControlsAvailable` confirms that the active SES sender supports
automatic controls. Legacy Mailgun senders keep observation and manual
pause/resume; finish SES setup before enabling automatic checks.

When resuming after a bounce incident, acknowledge the incident shown in the
current projection. Changing settings cannot clear an unrelated sending pause.
The [owner review guide](/docs/guides/owner-access.md) explains pending approvals.

## Understand a wait

New sender setup asks **Warm up gradually** (recommended) or **Start sending
normally**. No previous-provider history is required. Gradual starts at 100
marketing emails per rolling 24 hours, with a default target of 1,000. Settled
delivery feedback can earn an increase of up to 50% per day. Idle days do not
earn increases. Normal sending skips warm-up limits; health checks still apply.

Read `warmup` for allowance, used or reserved capacity, target and growth
status. Changing pace preserves history and pauses. Enabled marketing Plays
reserve 25% of daily and short-term capacity; service emails use their existing
checks outside these marketing limits.

Marketing held for domain health remains queued with a next eligible check
time. Its approved sending hours and expiry still apply. Defined receipts
and order updates are outside this marketing hold; their existing consent,
suppression and sending controls still apply.

Campaign details show an earliest finish using today's allowance. Unresolved
recipient timing is shown explicitly, and other sending can extend the time.
An estimate never changes the approved audience or expiry.

Delivery counts distinguish marketing from service emails and show feedback
coverage. “Delivered” means the receiving mail server accepted the email.
It does not prove that the message reached the inbox.

Read [email history](/docs/guides/emails.md) for a particular message, or
[recovery guidance](/docs/guides/troubleshooting.md) when an operation's result
is uncertain. Repeating a send is not a way to check whether it arrived.