JMAP Write Operations

Summary

Implement write operations for JMAP accounts: flag changes, move, copy, and delete.

Problem

JMAP accounts are read-only without write operations. Users cannot change flags, organize messages,
or delete mail.

Solution

• Implement flag operations using JMAP Message/Email API
• Implement move/copy using JMAP mailboxIds property
• Implement delete
• Ensure all operations work identically to IMAP operations from user perspective

Implementation

Extend lib/JMAP/ namespace with operations:

• Operation implementations for flag changes, move, copy, delete
• Reuse existing service layer abstractions via dispatcher pattern

JMAP-specific details:

• Flags use JMAP keywords property (no separate read/unread flag)
• Move uses mailboxIds (JMAP allows multi-mailbox; simulate single mailbox behavior)
• Copy adds mailbox ID to mailboxIds
• Delete moves to trash or sets destroyed flag

Service layer remains protocol-agnostic via dispatcher pattern.

Error handling catches JMAP errors and translates to service exceptions.

Affected Components

• lib/JMAP/: operation implementations
• Existing service layer: use dispatcher or extend as needed

Acceptance Criteria

• Flag operations (read/unread, custom flags) work for JMAP accounts
• Move/copy/delete operations work for JMAP accounts
• Operations persist on server
• Operations sync back correctly on next sync
• Behavior matches IMAP for equivalent operations

Out of Scope

• UI changes
• JMAP-specific optimizations

Start by reading the existing operations and service-layer abstractions under lib/JMAP/, then trace how the dispatcher connects protocol operations to IMAP behavior. Implement flag changes, move, copy, and delete using the stated JMAP properties and error translation approach. Done means the operations persist, sync on the next sync, and match equivalent IMAP behavior.