@remit/api-openapi-types 0.0.31 → 0.0.32

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remit/api-openapi-types",
-  "version": "0.0.31",
+  "version": "0.0.32",
   "type": "module",
   "main": "types.d.ts",
   "types": "types.d.ts",

package/types.d.ts

@@ -2762,6 +2762,25 @@ present only when `count=true`. Thread-specific so the shared `ResultList<T>`
        * SMTP server's Message-ID response (if different)
        */
       smtpMessageId?: string;
+      /**
+       * Whether the IMAP APPEND that files a copy in Sent has been confirmed, and
+the uid it produced. Written between the APPEND and the row delete that
+follows it, so a redelivered APPEND event skips straight to the delete
+instead of filing a second copy of the same message.
+
+Three readings, no absent one: the named sentinel `0` means no APPEND has
+been confirmed for this row. The named sentinel `-1` means an APPEND was
+confirmed but the server named no uid for it — UIDPLUS is an extension, and
+a server without it files the copy and reports nothing. Any positive value
+is the uid the server assigned. Only the latter two mean the copy exists, so
+a value neither of them reads as unfiled, which re-files at worst rather
+than dropping the row of a message that reached no folder.
+
+Deliberately not paired with a uidValidity: this never addresses the
+message, it only records that the copy exists. Everything that names a
+message forever (Message, Quarantine) stores both.
+       */
+      appendedUid: number;
       createdAt: number;
       updatedAt: number;
     }