Fixed

• Fastmail: if xin reply draft creation fails with invalidProperties (header:In-Reply-To/References) when using header:*:asMessageIds, retry with raw threading header text (header:*:asText) to ensure replies can still be sent.

Highlights

• Fix reply threading headers (Fastmail-friendly): replies now set In-Reply-To / References via JMAP parsed header forms (asMessageIds), avoiding RFC 5322 formatting pitfalls.
  • This resolves Fastmail errors like: invalidProperties (header:In-Reply-To).

Changes

• Use Header::as_message_ids() + HeaderValue::AsTextAll() for threading headers during reply.
• Add unit test for reply header building.
• Update mock tests to strictly verify the JMAP request format.

Bugfix release for Fastmail strict JMAP capability handling.

Fixed

• Include urn:ietf:params:jmap:submission in request using for Identity/* (via jmap-client fork), avoiding "Unknown method".
• Avoid setting the forbidden $draft keyword when creating drafts/sending.

Changed

• Keep provider quirks fixed in the dependency (jmap-client fork) and keep xin-side code clean.

Initial public release.\n\n- Fastmail-first JMAP CLI\n- JSON-first output contract with optional --plain\n- Search/get/watch/history flows\n- Basic send + reply helpers\n