1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
//! JMAP protocol implementation for RusMES
//!
//! This crate implements the JSON Meta Application Protocol (JMAP) for the RusMES mail
//! server, providing an HTTP/JSON API for email access as defined in:
//!
//! - **RFC 8620** — The JSON Meta Application Protocol (core protocol)
//! - **RFC 8621** — Using JMAP for Email (Email, Mailbox, Thread, EmailSubmission,
//! VacationResponse, SearchSnippet, Identity)
//!
//! # Module Overview
//!
//! | Module | Contents |
//! |--------|----------|
//! [`api`] | Axum-based HTTP server (`JmapServer`), request dispatch, auth middleware |
//! [`blob`] | Blob upload (`POST /upload/:account`) and download (`GET /download/…`) endpoints |
//! [`eventsource`] | Server-Sent Events push channel (`GET /eventsource`) for state-change notifications |
//! [`session`] | JMAP Session resource (`GET /.well-known/jmap`), capability advertisement |
//! [`types`] | Shared JSON types: `Email`, `JmapRequest`, `JmapResponse`, `JmapError`, etc. |
//! [`methods`] | Method handlers for all JMAP objects (see sub-modules below) |
//!
//! ## Method Handlers
//!
//! | Sub-module | RFC | Methods |
//! |-----------|-----|---------|
//! `methods::mailbox` | RFC 8621 §2 | `Mailbox/get`, `Mailbox/set`, `Mailbox/query`, `Mailbox/changes`, `Mailbox/queryChanges` |
//! `methods::email` | RFC 8621 §4 | `Email/get`, `Email/set`, `Email/query` |
//! `methods::email_advanced` | RFC 8621 §4 | `Email/changes`, `Email/queryChanges`, `Email/copy`, `Email/import`, `Email/parse` |
//! `methods::thread` | RFC 8621 §3 | `Thread/get`, `Thread/changes` |
//! `methods::submission` | RFC 8621 §7 | `EmailSubmission/get`, `EmailSubmission/set`, `EmailSubmission/query`, `EmailSubmission/changes` |
//! `methods::identity` | RFC 8621 §5 | `Identity/get`, `Identity/set`, `Identity/changes` |
//! `methods::vacation` | RFC 8621 §8 | `VacationResponse/get`, `VacationResponse/set` |
//! `methods::search_snippet` | RFC 8621 §9 | `SearchSnippet/get` |
//!
//! # Example — Starting the JMAP server
//!
//! ```rust,no_run
//! use rusmes_jmap::JmapServer;
//! use axum::Router;
//!
//! // Obtain the JMAP routes and nest them inside an Axum application.
//! let app: Router = JmapServer::routes();
//! // e.g. axum::serve(listener, app).await.unwrap();
//! ```
//!
//! # EventSource Push
//!
//! The [`eventsource::EventSourceManager`] can be used to broadcast state-change
//! notifications to JMAP clients that maintain a long-lived SSE connection:
//!
//! ```rust,no_run
//! use rusmes_jmap::EventSourceManager;
//!
//! let manager = EventSourceManager::new();
//! // Notify all connected clients that the Email state has changed:
//! manager.notify_change("Email".to_string(), "new-state-token".to_string());
//! ```
//!
//! # Blob Handling
//!
//! [`BlobStorage`] supports two persistence backends:
//!
//! - **Memory** (default, via [`BlobStorage::new`]): blobs live in-memory and are
//! lost on restart. Existing callers are unaffected.
//! - **Filesystem** (via [`BlobStorage::new_filesystem`]): blobs are written to
//! `<root>/blobs/<id>` with a JSON sidecar and survive server restarts. The
//! in-memory index is rebuilt by scanning `.meta.json` sidecars on open.
//!
//! Both backends enforce a configurable `max_blob_size` (default 50 MiB) and
//! return [`UploadError::TooLarge`] before writing any bytes when the limit is
//! exceeded. Uploaded blobs are referenced by `blobId` strings throughout JMAP
//! Email import/parse operations.
pub use JmapServer;
pub use ;
pub use ;
pub use ;
pub use ;
pub use ;