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 |
|---|---|---|
info@khobara.com.kw | yes | ✓ |
abdulrahman@khobara.com.kw | no | ✓ |
info@aldilaijan.com | yes | ✓ |
abdulrahman@aldilaijan.com | 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 |
|---|---|---|
info@khobara.com.kw | Khobara | Hostinger IMAP |
abdulrahman@khobara.com.kw | Khobara | Hostinger IMAP |
info@aldilaijan.com | Aldilaijan | Hostinger IMAP |
abdulrahman@aldilaijan.com | Aldilaijan | Hostinger IMAP |
In-app path
- Sign in as staff with mailbox admin permission.
- Open Comms → Mailbox (or go to
/mailbox/connect). - For each account: enter email + mailbox password → Connect.
- Confirm all four appear under Manage accounts (
/mailbox/accounts). - 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_accountsrow is active and staff has grant. - Send fails: verify From account picker and send grant on that account.