01
Automatic failover#
BotInbox sends through more than one delivery provider. On Team and Enterprise, if the primary provider has an outage or rejects a send for a temporary reason, the message is retried automatically through a backup provider, with no change to your code. Errors caused by the message itself (an invalid or suppressed recipient, rejected content) are not retried, because they would fail everywhere. Every account is protected during major provider outages.
02
Bring your own SMTP (Team+)#
Team and Enterprise accounts can add their own SMTP server, either as the primary route or as a fallback. Save it with PUT /v0/providers/smtp (host, port 25/465/587/2525, security tls|starttls, username, password, mode primary|fallback) using an account key. The password is encrypted at rest and never returned. POST /v0/providers/smtp/test connects and authenticates without sending mail, and DELETE removes the config. Your SMTP server is used only for inboxes on your verified custom domains, and private or internal hosts are rejected.
curl https://botinbox.dev/v0/providers/smtp -X PUT -H "Authorization: Bearer $BOTINBOX_API_KEY" -H "Content-Type: application/json" \
-d '{"host":"smtp.example.com","port":587,"security":"starttls","username":"agent","password":"...","mode":"fallback"}'03
Receiving during outages#
Inbound mail is accepted through your domain's MX record. If receiving is briefly unavailable, the sender's mail server queues the message and retries for up to several days, so mail is delayed rather than lost.