DOCUMENTATION / EMAIL

Check sending health

Read domain health before changing sending controls. Authentication checks and delivery evidence stay separate. Missing feedback is not a reputation score.

Read the current state

Supply BARUA_MANAGEMENT_KEY and use the installed helpers:

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

Check the active domain, version, evidence dates and marketing holds. The dashboard uses the same evidence. Any active management connection can read it, without additional grants. It contains no customer addresses.

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.

Read provider reports

providerMonitoring includes available SES evidence and optional Google Postmaster reports, with report and collection dates. Missing or stale values remain unknown. Some providers and low-volume domains have no reports.

Provider warnings do not change warm-up or pause sending. Google spam rates and SES complaints cover different populations; do not combine them into one score.

With setup:write, deliverability.monitoring.refresh queues a check using the current domain and version. It has a 15-minute cooldown and respects provider retry delays. deliverability.google.connect returns an owner link: only the owner can accept the optional disclosure and authorize Google. Disconnect needs the current connection generation. See the provider-report reference.

Change a control

Follow the exact inputs in the deliverability reference. 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 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.

Campaigns estimate their earliest finish using today's allowance. Unresolved timing and other sends can extend it. Estimates do not change approval 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 or recovery guidance. Do not repeat a send to check whether it arrived.

Unsubscribe

Footer links open a Barua confirmation page. Opening the link changes nothing; the recipient must confirm. Email-client one-click unsubscribe sends that confirmation directly. If confirmation fails, retry the same link. Repeated confirmation is safe. See the unsubscribe reference for agent checks and suppression scope.