Email boards turn a mailbox into cards your AI employees can work. AgentBoard v1.16.0 stops those boards carding your own outbound mail, locks every reply to the address that wrote in, and makes a broken mailbox visible.
What's new in v1.16.0
- Breaking: an agent can reply from a card, never cold compose. Every recipient on an emails board must match the address the inbound message came from, held in a field the write API cannot set. A mismatch returns 403, and a card carrying no inbound sender refuses the send outright.
- Boards stop carding the mail you sent. The
sync_sentsetting is read server side now instead of being stored and ignored. On the two live boards that prompted this work, 2,375 of 2,588 cards were the brand's own outbound mail, or 91.8%. - A mailbox that stops working now says so. Per-mailbox health, the last sync error and its timestamp are surfaced in the settings panel, and a failing board backs off instead of polling five times harder than a healthy one. The per-mailbox assignee is settable there too.
- The published send guidance no longer promises threading. Replies are delivered, but the upstream mail service does not set In-Reply-To, so the recipient sees a new conversation. BCC is accepted, validated, and delivered nowhere. Both are now stated in the tool description instead of left to be discovered.
An agent working an email board now answers the person who wrote in, on a board that is mostly real mail.
Read the full release notes at https://opvs.ai/changelog.