@serve.zone/dcrouter 34.7.0 → 34.7.1

package/readme.md

@@ -161,7 +161,7 @@ Bootstrap behavior:
 | `baseDir` | Root directory for dcrouter runtime data. Defaults to `~/.serve.zone/dcrouter`. |
 | `coreTrafficConfig` | Main CoreTraffic route configuration for HTTP/HTTPS/TCP/SNI traffic. `smartProxyConfig` remains accepted as a legacy alias. |
 | `emailConfig` | UnifiedEmailServer configuration: hostname, ports, domains, and mail routes. |
-| `emailOutboundMode` | Outbound SMTP mode. Defaults to `remoteIngress`; explicit `direct` mode lets unmanaged/static senders dial from the hub. |
+| `emailOutboundMode` | Outbound SMTP mode; explicit `direct` mode lets unmanaged/static senders dial from the hub. With the database enabled it seeds the stored email settings on first start only; after that the stored settings are authoritative, they default to `remoteIngress`, and the mode changes through the email settings API or Ops UI. Without the database it is read directly on every delivery and has no default: while it is unset, outbound mail defers. |
 | `emailPortConfig` | External-to-internal email port mapping and received-email storage path. |
 | `tls` | Legacy/static TLS and ACME contact settings used to seed certificate config. |
 | `dnsNsDomains` | Nameserver hostnames used for generated NS records and DoH routes. A zone becomes authoritative by having its public NS records observed naming one of these. |

package/ts/00_commitinfo_data.ts

@@ -3,6 +3,6 @@
  */
 export const commitinfo = {
   name: '@serve.zone/dcrouter',
-  version: '34.7.0',
+  version: '34.7.1',
   description: 'A multifaceted routing service handling mail and SMS delivery functions.'
 }

package/ts/classes.dcrouter.ts

@@ -116,7 +116,13 @@ export interface IDcRouterOptions {
   /** SmartBucket configuration for durable SmartMTA queue and attachment blobs. */
   emailBlobStorage?: ISmartMtaBlobStorageConfig;
 
-  /** Outbound SMTP connection mode. Defaults to direct unless DB settings override it. */
+  /**
+   * Outbound SMTP connection mode. With the database enabled it seeds the
+   * stored email settings on first start only; after that the stored settings
+   * are authoritative, and they default to `remoteIngress`. Without the
+   * database it is read directly on every delivery and has no default: while
+   * it is unset, outbound mail defers.
+   */
   emailOutboundMode?: TEmailOutboundMode;
 
   /**

package/ts/email/classes.coremail-gateway.manager.ts

@@ -149,6 +149,20 @@ const contractError = (
     ) satisfies plugins.servezoneInterfaces.data.ICoreMailErrorData,
   );
 
+/**
+ * Whether a replayed envelope is the one the stored handoff was prepared with.
+ * Compares values, never encodings: the stored envelope is whatever the
+ * document store returns, and its key order is not part of the data. The
+ * recipient order is, as it is in the submission digest.
+ */
+const isSameCoreMailEnvelope = (
+  storedArg: plugins.servezoneInterfaces.data.ICoreMailEnvelope,
+  replayedArg: plugins.servezoneInterfaces.data.ICoreMailEnvelope,
+): boolean =>
+  storedArg.mailFrom === replayedArg.mailFrom
+  && storedArg.rcptTo.length === replayedArg.rcptTo.length
+  && storedArg.rcptTo.every((recipientArg, indexArg) => recipientArg === replayedArg.rcptTo[indexArg]);
+
 /**
  * Answers a wire-9 request with the handler's own contract refusal: TypedRequest 9
  * answers an error of another class, TypedRequest 8's `TypedResponseError`
@@ -580,7 +594,7 @@ export class CoreMailGatewayManager {
         || existing.submissionDigest !== submissionDigest
         || existing.rawMimeSha256 !== message.rawMime.sha256
         || existing.rawMimeLengthBytes !== message.rawMime.lengthBytes
-        || JSON.stringify(existing.envelope) !== JSON.stringify(message.envelope)
+        || !isSameCoreMailEnvelope(existing.envelope, message.envelope)
       ) {
         throw contractError('IDEMPOTENCY_CONFLICT');
       }

package/ts_web/00_commitinfo_data.ts

@@ -3,6 +3,6 @@
  */
 export const commitinfo = {
   name: '@serve.zone/dcrouter',
-  version: '34.7.0',
+  version: '34.7.1',
   description: 'A multifaceted routing service handling mail and SMS delivery functions.'
 }