@push.rocks/smartmta 9.2.0 → 9.3.0

package/changelog.md

@@ -1,5 +1,37 @@
 # Changelog
 
+## 2026-07-26 - 9.3.0
+
+### Fixes
+
+- a submission-permission route no longer claims a recipient this server terminates (routing)
+  - Found empirically in a dcrouter deployment: the same message from the same sender to `admin@central.eu`, a domain that server hosts, was accepted and stored when submitted unauthenticated but permanently lost when submitted over authenticated SMTP minutes later. Log chain: `MTA: skipped MX mx.lossless.directory for central.eu: ... points back at this server because it exactly matches a configured listener identity` → `all MX hosts failed` → `Terminal delivery failure persisted for admin@central.eu`, all after the client had already been given a `250`.
+  - Root cause: `resolveRecipientPolicy` let ANY matched route win over the domain inbound policy. An authenticated submission route (`match: { authenticated: true, senders }`, `action: { type: 'process', allowRelay: true }`, no recipient scope) therefore claimed locally hosted recipients too, and `process` transports via DNS MX — which for such a recipient resolves straight back to this listener, where the self-MX loop guard terminates it permanently. The domain-policy `store` fallback was only reachable when no route matched at all, which is why the unauthenticated path worked.
+  - Resolution now falls through to the domain's inbound policy when the recipient domain is registered AND stores inbound mail locally (`inboundPolicy.defaultAction: 'store'`), the action is `process`, and the route names no recipient scope (`match.recipients` absent, empty, or only match-all patterns `*` / `*@*`).
+  - Deliberately narrow, so nothing that works today starts bouncing: recipient-scoped `process` routes still win (consumers deliver specific local addresses through their own acceptance pipeline that way), `store`/`deliver`/`forward`/`reject` always win, non-local recipients are untouched, and a domain registered for outbound identity only — no `inboundPolicy`, or the send-only `defaultAction: 'reject'` — keeps relaying because its real MX legitimately lives elsewhere. The requirement that the fall-through target be a `store` policy means the change can never turn a working relay into a `550`.
+  - The self-MX loop guard is unchanged; local recipients simply stop reaching it. Authenticated relay to remote domains is unchanged. Mixed envelopes now resolve per recipient: local recipients get `store` and remote recipients keep the submission route, so an envelope addressed to both is handled through the durable `hooks.onAcceptEnvelope` path with only the remote recipients dispatched to the queue.
+  - Encoding recipient intent in `match.headers` is explicitly not recognised for this purpose.
+
+### Security
+
+- AUTH is no longer advertised or accepted on an unencrypted session (smtp)
+  - Found in the same deployment: ports 25 and 587 advertised `AUTH PLAIN LOGIN SCRAM-SHA-256` while offering no `STARTTLS`, so credentials could be solicited over a cleartext channel. `build_capabilities` pushed the AUTH capability whenever auth was configured, ignoring `already_secure`, and `handle_auth`/`handle_auth_scram` only checked `config.auth_enabled`, never `session.secure`.
+  - `AUTH` is now advertised only on an encrypted transport, and an `AUTH` command on a cleartext session is refused with `538 5.7.11 Encryption required for requested authentication mechanism` — so a client that ignores the absent capability cannot send credentials in the clear either. Applies to `PLAIN`, `LOGIN` and `SCRAM-SHA-256`.
+  - BREAKING for deployments that relied on cleartext AUTH: a plain port with no TLS material now offers neither `STARTTLS` nor `AUTH`. Verify that submission ports actually receive `tls.certPem`/`tls.keyPem`.
+
+### Features
+
+- `smtp.tlsTerminatedPorts` for edge-terminated submission ports (smtp)
+  - Declares listener ports whose inbound transport a trusted upstream TLS terminator already encrypted, which is how a proxy-fronted deployment keeps implicit-TLS submission working under the new AUTH gate: the backend leg is plaintext, but the client's channel is encrypted. Sessions on such a port count as encrypted, report `secure: true` to hooks, and do not advertise `STARTTLS`.
+  - Because it is a trust assertion about the peer, it is only honoured together with `smtp.proxyProtocol.required` and a non-empty `trustedIps` — the exact-peer PROXY check is what proves the connection came from the terminator. `start()` throws when a listed port is not among the configured `ports`, is the implicit-TLS `securePort`, or PROXY protocol is not required. Validated on both the TypeScript and the Rust side.
+- `updateOptions` now restarts the Rust SMTP listener when TLS material or `smtp.tlsTerminatedPorts` change, alongside the existing AUTH-presence transition (routing)
+  - Both are listener-level Rust configuration. Previously they were merged into the options and silently never took effect on the running listener, so a renewed certificate could not be applied without a full process restart.
+
+### Known limitations (unchanged, documented)
+
+- `tls.caPem`, `tls.minVersion` and `tls.ciphers` are accepted but not consumed by the Rust listener; only `certPem`/`keyPem` take effect.
+- `auth.required` only turns AUTH availability on — it does not require authentication. A global require-auth flag is incoherent for port 25, which must accept anonymous inbound mail; relay permission is expressed per route via `allowRelay` plus local-recipient resolution. The option name remains misleading.
+
 ## 2026-07-26 - 9.2.0
 
 ### Features

package/dist_ts/00_commitinfo_data.js

@@ -3,7 +3,7 @@
  */
 export const commitinfo = {
     name: '@push.rocks/smartmta',
-    version: '9.2.0',
+    version: '9.3.0',
     description: 'A high-performance, enterprise-grade Mail Transfer Agent (MTA) built from scratch in TypeScript with Rust acceleration.'
 };
 //# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiMDBfY29tbWl0aW5mb19kYXRhLmpzIiwic291cmNlUm9vdCI6IiIsInNvdXJjZXMiOlsiLi4vdHMvMDBfY29tbWl0aW5mb19kYXRhLnRzIl0sIm5hbWVzIjpbXSwibWFwcGluZ3MiOiJBQUFBOztHQUVHO0FBQ0gsTUFBTSxDQUFDLE1BQU0sVUFBVSxHQUFHO0lBQ3hCLElBQUksRUFBRSxzQkFBc0I7SUFDNUIsT0FBTyxFQUFFLE9BQU87SUFDaEIsV0FBVyxFQUFFLHlIQUF5SDtDQUN2SSxDQUFBIn0=

package/dist_ts/mail/routing/classes.unified.email.server.d.ts

@@ -231,6 +231,19 @@ export interface IUnifiedEmailServerOptions {
         recipientValidation?: boolean;
         /** Listener port that should use implicit TLS. Defaults to 465 when present. */
         securePort?: number;
+        /**
+         * Listener ports whose inbound transport is already encrypted by a trusted
+         * upstream TLS terminator (an edge proxy that terminates TLS and forwards
+         * the decrypted stream here). Sessions on these ports count as encrypted:
+         * AUTH is offered even though this process performed no handshake, and
+         * STARTTLS is not advertised.
+         *
+         * Only honoured together with `proxyProtocol.required` — the exact-peer
+         * PROXY check is what proves the connection came from the terminator.
+         * Startup fails when a listed port is not bound, is the implicit-TLS
+         * `securePort`, or PROXY protocol is not required.
+         */
+        tlsTerminatedPorts?: number[];
         /** Timeout for RCPT policy callbacks. Defaults to 5000 ms. */
         recipientValidationTimeoutMs?: number;
         /** Timeout for message acceptance callbacks. Defaults to 30000 ms. */
@@ -405,6 +418,13 @@ export declare class UnifiedEmailServer extends EventEmitter {
     private unregisterBridgeStateHandler;
     private unregisterBridgeEventHandlers;
     private startSmtpServer;
+    /**
+     * Validate and resolve the ports whose transport an upstream proxy already
+     * encrypted. Misconfiguration here would let a peer claim an encrypted
+     * channel and be offered AUTH in cleartext, so every case fails startup
+     * rather than degrading silently.
+     */
+    private resolveTlsTerminatedPorts;
     /** Whether the current options require SMTP AUTH support on the listener. */
     private isAuthConfigured;
     /**
@@ -429,6 +449,29 @@ export declare class UnifiedEmailServer extends EventEmitter {
     private handleRustRcptToRequest;
     private evaluateDefaultRcptToPolicy;
     private resolveRecipientPolicy;
+    /**
+     * Whether a matched route is a pure submission-permission route that must
+     * not claim a recipient whose inbound mail this server terminates.
+     *
+     * A route qualifies only when ALL of the following hold:
+     * - the recipient domain is registered here AND its inbound policy stores
+     *   mail locally, i.e. this server really is the destination. A domain
+     *   registered for outbound purposes only (`inboundPolicy` absent, or
+     *   `defaultAction: 'reject'` for send-only domains) keeps relaying, because
+     *   its real MX legitimately lives elsewhere;
+     * - the action is `process`, the only action whose transport is DNS-MX
+     *   relay. `store`, `deliver`, `forward` and `reject` all express a
+     *   deliberate disposition for the recipient and always win;
+     * - the route names no recipient scope. `match.recipients` is the only way a
+     *   route states which recipients it is for, and a pattern that matches every
+     *   address states nothing. Recipient-scoped `process` routes keep winning —
+     *   consumers use them for local addresses handled by their own acceptance
+     *   pipeline. Encoding recipient intent in `match.headers` is not supported
+     *   for this purpose.
+     */
+    private isSubmissionPermissionRouteForLocalRecipient;
+    /** Whether a recipient pattern list narrows the route to specific recipients. */
+    private routeNamesRecipientScope;
     private getRejectionReasonForResolution;
     private notifyRecipientRejected;
     private buildPolicySession;