@remit/mailbox-service 0.0.38 → 0.0.39

package/README.md

@@ -1,11 +1,11 @@
 # @remit/mailbox-service
 
-IMAP mailbox synchronization service for Remit. Provides connection management, mailbox discovery, and message sync with DynamoDB persistence.
+IMAP mailbox synchronization service for Remit. Provides connection management, mailbox discovery, and message sync. Persistence is injected: the service takes repository ports, never a database client.
 
 ## Features
 
 - **ImapFlow-based**: Modern async/await IMAP client with native envelope parsing
-- **Mailbox Sync**: Discovers and syncs mailbox metadata from IMAP to DynamoDB
+- **Mailbox Sync**: Discovers and syncs mailbox metadata from IMAP into the mailbox repository
 - **Message Sync**: Newest-first sync strategy with dual-watermark tracking
 - **Address Extraction**: Parses and stores envelope addresses with role tracking
 
@@ -55,10 +55,11 @@ await connection.disconnect();
 ```typescript
 import { MailboxSyncService } from "@remit/mailbox-service";
 
-const syncService = new MailboxSyncService({
-  client: dynamoDBClient,
-  table: "remit-table",
-});
+const syncService = new MailboxSyncService(
+  mailboxRepository,
+  mailboxSpecialUseRepository,
+  logger,
+);
 
 const result = await syncService.syncMailboxes(
   { accountId: "acc-123" },
@@ -103,7 +104,7 @@ const synced = await messageSyncService.syncMessages(
 
 | Export               | Description                               |
 | -------------------- | ----------------------------------------- |
-| `MailboxSyncService` | Syncs mailbox list from IMAP to DynamoDB  |
+| `MailboxSyncService` | Syncs mailbox list from IMAP into the store |
 | `MessageSyncService` | Syncs messages with newest-first strategy |
 
 ### Types

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remit/mailbox-service",
-  "version": "0.0.38",
+  "version": "0.0.39",
   "type": "module",
   "main": "src/index.ts",
   "types": "src/index.ts",

package/src/body-parse.ts

@@ -9,7 +9,7 @@ type FailureCode = QuarantineItem["failureCode"];
  *
  * This type is the whole reason the sync path can quarantine anything. Before
  * it, every catch site on the body path saw one undifferentiated `unknown`
- * covering mailparser, S3, DynamoDB and SQS alike, so "the message is built in
+ * covering mailparser, S3, the database and SQS alike, so "the message is built in
  * a way Remit could not read" was indistinguishable from "S3 returned a 503".
  * Recording the second as the first advances the cursor past mail that is
  * perfectly fine and never fetches it again.

package/src/mailbox-cursor.ts

@@ -33,8 +33,8 @@ export interface MailboxCursorGuardDeps {
 /**
  * `cursorState` is total per RFC 032 (defaults to `normal`) — but that default
  * only applies to rows written after this field existed. A row persisted
- * before this migration (DynamoDB attribute never written / Postgres column
- * genuinely NULL) reads back with the attribute absent despite the type
+ * before this migration (the column genuinely NULL) reads back absent
+ * despite the type
  * saying otherwise, so every consumer here treats `undefined` the same as
  * `normal` defensively rather than trusting the type.
  */

package/src/mailbox-management.ts

@@ -100,7 +100,7 @@ export const validateMailboxOperation = (
  * Service for managing mailbox operations (create, rename, delete).
  *
  * Implements an optimistic local-first pattern:
- * 1. Updates are applied locally first (DynamoDB)
+ * 1. Updates are applied locally first
  * 2. Changes are queued for IMAP sync via SQS
  * 3. Worker processes queue and syncs to IMAP server
  */
@@ -244,7 +244,7 @@ export class MailboxManagementService {
 
 		this.log.info({ mailboxId, path }, "Deleted mailbox on IMAP server");
 
-		// Delete the mailbox entity from DynamoDB
+		// Delete the mailbox entity from the local store
 		await this.mailboxService.delete(accountId, mailboxId);
 
 		return { success: true };

package/src/mailbox-queue.ts

@@ -83,7 +83,7 @@ export interface MailboxQueueConfig {
  * Service for mailbox management with automatic IMAP sync queueing.
  *
  * Implements optimistic local-first pattern:
- * 1. Updates local DynamoDB state immediately
+ * 1. Updates local state immediately
  * 2. Enqueues mailbox management event to SQS for worker to sync to IMAP
  *
  * This follows the same pattern as FlagQueueService (RFC 014).

package/src/message-move.ts

@@ -115,7 +115,7 @@ export interface DeleteOptions {
  * Service for moving, copying, and deleting messages.
  *
  * Implements optimistic local-first pattern:
- * 1. Updates local DynamoDB state immediately (Message + ThreadMessage)
+ * 1. Updates local state immediately (Message + ThreadMessage)
  * 2. Enqueues event to SQS for worker to sync to IMAP
  *
  * Following RFC 016 for message deletion and moving.

package/src/mime-walker.ts

@@ -266,8 +266,8 @@ const toRecord = (
  * **Part-path uniqueness**: some IMAP servers (and the `message/rfc822`
  * inner-body convention) return child nodes with an empty `part` field.
  * Assigning ROOT_PART_PATH to every such node would produce duplicate keys
- * and cause a DynamoDB "multiple operations on one item" error in
- * `upsertBodyParts`. Non-root nodes without a `part` therefore receive a
+ * and make `upsertBodyParts` write the same body part twice. Non-root nodes
+ * without a `part` therefore receive a
  * synthetic path `<parentPath>.<siblingIndex>` that is stable across
  * repeated syncs of the same message.
  */
@@ -287,7 +287,7 @@ export const walkMimeStructure = (root: MimeNode): BodyPartRecord[] => {
 			partPath = ROOT_PART_PATH;
 		} else {
 			// Non-root node without an IMAP part path — synthesise one so
-			// the DynamoDB keys remain unique. This happens most commonly
+			// the body-part keys remain unique. This happens most commonly
 			// for the body of a message/rfc822 attachment, whose inner
 			// structure imapflow attaches as a childNode with part="".
 			partPath = `${parentPath}.${siblingIndex}`;

package/src/pass-through-unit-of-work.ts

@@ -2,9 +2,9 @@ import type { IUnitOfWork, UnitOfWorkRepositories } from "@remit/data-ports";
 
 /**
  * Runs the write set against fixed repositories with no surrounding
- * transaction. For backends (DynamoDB) that have no cross-entity transaction:
- * the writes are not atomic, matching that backend's own guarantees. The
- * Postgres path injects a real transactional unit of work instead.
+ * transaction: the writes are not atomic. For a backend that has no
+ * cross-entity transaction this matches its own guarantees; the SQLite path
+ * injects a real transactional unit of work instead.
  */
 export class PassThroughUnitOfWork implements IUnitOfWork {
 	constructor(private repos: UnitOfWorkRepositories) {}