Mailbox connect — ops runbook

Status (2026-06-09): All four production inboxes are connected in Supabase email_accounts — active, Hostinger IMAP, encrypted passwords present. On-device IMAP confirmed working (Comms → Mailbox). No reconnect needed unless credentials rotate.

Address	Shared	DB verified
[email protected]	yes	✓
[email protected]	no	✓
[email protected]	yes	✓
[email protected]	no	✓

Manual step (only when adding a new mailbox or after a password reset): CI and agents cannot enter Hostinger mailbox passwords. Use a staff admin account in-app.

Programmatic alternative (2026-07): Hostinger now ships a REST API + MCP server for these same mailboxes (bearer token, no IMAP passwords) — see docs/HOSTINGER_MAIL_API.md.

Accounts

Address	Brand	Host
[email protected]	Khobara	Hostinger IMAP
[email protected]	Khobara	Hostinger IMAP
[email protected]	Aldilaijan	Hostinger IMAP
[email protected]	Aldilaijan	Hostinger IMAP

In-app path

1. Sign in as staff with mailbox admin permission.
2. Open Comms → Mailbox (or go to /mailbox/connect).
3. For each account: enter email + mailbox password → Connect.
4. Confirm all four appear under Manage accounts (/mailbox/accounts).
5. Assign read/send to other staff as needed.

Verification

Use docs/DEVICE_QA_CHECKLIST.md — Mailbox section.

Troubleshooting

• Auth failed: confirm Hostinger password; reset in Hostinger panel if needed.
• Account missing in switcher: check mailbox_accounts row is active and staff has grant.
• Send fails: verify From account picker and send grant on that account.