@framers/agentos-ext-channel-email 0.4.1 → 0.4.2

package/README.md

@@ -79,10 +79,20 @@ await email.sendEmail({
 });
 ```
 
-Through Resend the fields go in the request's `headers` ([custom headers](https://resend.com/docs/dashboard/emails/custom-headers)); through SMTP nodemailer writes each into the message. `headers` is a plain object of names and values. A name is printable US-ASCII with no space or colon, the field name of RFC 5322, and a value is a string with no line break or other control character than the tab, so no field can end and start another. Each value is read once, and the fields are sent as read.
+Through Resend the fields go in the request's `headers` ([custom headers](https://resend.com/docs/dashboard/emails/custom-headers)); through SMTP nodemailer writes each into the message as given, folded at its white space. Both transports get the same text, so `headers` takes only what both carry alike:
+
+- `headers` is a plain object of names and values, made in this realm or in another, such as a `vm` context. A list, a `Map` or text is refused.
+- A name is printable US-ASCII with no space or colon, the field name of RFC 5322, given once in any case.
+- A value is a string of printable US-ASCII words, with one space or tab between each two and none at either end. An empty or blank value is refused: nodemailer would leave the field out, and Resend would send it empty. So is a character outside US-ASCII, which nodemailer would write as an RFC 2047 encoded word that a structured field such as `List-Unsubscribe` cannot hold; percent-encode a link instead. A line break or any other control character is refused, so no field can end and start another, and so is white space at either end or two white-space characters in a row, which nodemailer can fold into a line of white space alone: obsolete syntax ([RFC 5322 section 4.2](https://www.rfc-editor.org/rfc/rfc5322#section-4.2)) that a message must not be written with.
+- No word may be so long that the name, a colon, a space and the word pass 998 characters, the longest line [RFC 5322 section 2.1.1](https://www.rfc-editor.org/rfc/rfc5322#section-2.1.1) allows: a field folds only at its white space, so a word stays on one line. A `List-Unsubscribe` link holds at most 980 characters.
+- `In-Reply-To` and `References` list message ids, each in angle brackets, such as `<id@example.com>`.
+
+Each value is read once, and the fields are sent as read. A value with a double quote, such as a `List-Id` of `"Weekly summary" <weekly.example.com>`, arrives as written through both transports. Two differences stay, and neither changes what a field means: nodemailer writes a name in its own case, such as `List-ID` for `List-Id`, and RFC 5322 makes field names case-insensitive; and it writes `Sender` as the address it parses from the value, the same mailbox. Resend's [custom headers](https://resend.com/docs/dashboard/emails/custom-headers) page and its [send call](https://resend.com/docs/api-reference/emails/send-email) do not say how Resend writes a long field into the message.
 
 `headers` adds fields and never replaces the service's own: `From`, `To`, `Cc`, `Bcc`, `Reply-To`, `Subject`, `Date`, `Message-ID`, `MIME-Version` and every `Content-` field are refused, in any case. The recipients, the reply-to and the subject have their own options, and the From comes from the configuration's `from`. A name given twice in different cases is refused too. A refusal throws an `Error` before either transport is used, naming the field, or its place in the object when its name is at fault, and none of its value. The `emailSend` tool and the channel adapter add no header fields.
 
+The subject goes out on one line through both transports: each line break in it, and each other control character but the tab, is sent as a space, as nodemailer writes a line break in a subject.
+
 ## Suppressions and unsubscribe tokens
 
 Two stores a sender reads, each on the host's SQL database: `SqlSuppressionStore` keeps the addresses not to mail, each named by its SHA-256, and `SqlRecipientCapability` keeps opaque tokens, such as an unsubscribe link's, each naming a recipient and a scope. Both take [`@framers/sql-storage-adapter`](https://www.npmjs.com/package/@framers/sql-storage-adapter)'s adapter on SQLite or PostgreSQL, or any handle with its `run` and `get` (`?` placeholders, positional parameters), so the pack gains no dependency.
@@ -97,7 +107,8 @@ import {
   emailPreferencesDdl,
 } from '@framers/agentos-ext-channel-email';
 
-const db = await createDatabase({ url: process.env.DATABASE_URL });
+// strict: with DATABASE_URL unset, throw rather than open a local database in its place
+const db = await createDatabase({ url: process.env.DATABASE_URL, strict: true });
 await db.exec(emailPreferencesDdl('mail')); // mail_suppressions and mail_capabilities
 
 // A bounce reported by the provider: the store gets the address's hash, never the address.
@@ -114,17 +125,17 @@ const link = `https://example.com/unsubscribe?t=${token}`;
 const grant = await tokens.find(token); // { recipient: 'account-1', scope: 'weekly-summary' }, or null
 ```
 
-`suppress(scope, addressHash, reason, day)` records an address in a scope with its reason and its day (`YYYY-MM-DD`), and no end. The reason is `bounce`, `complaint`, `suppressed` (the provider refused a message because its own list held the address) or `manual`. A second record of the address in the scope writes nothing and keeps the first, so a provider's repeated event is harmless; `suppress` answers `true` only for the call that recorded it, and two hosts recording one address at once leave one row. `isSuppressed(scope, addressHash)` answers for one scope. A scope is one list, and a host that keeps one passes `DEFAULT_SUPPRESSION_SCOPE` (`mail`) everywhere. `addressHash` is the SHA-256 of the address as 64 lower-case hexadecimal characters, which the host computes the same way wherever it reads or writes the record. Any other value, an address among them, throws a `TypeError` that holds none of it, so a mistake stores nothing and is never answered as not suppressed.
+`suppress(scope, addressHash, reason, day)` records an address in a scope with its reason and its day (`YYYY-MM-DD`), and no end: the store has no call that lifts an address, so an operator lifts one by deleting its row (`DELETE FROM <prefix>_suppressions WHERE scope = ? AND address_hash = ?`). The reason is `bounce`, `complaint`, `suppressed` (the provider refused a message because its own list held the address) or `manual`. A second record of the address in the scope writes nothing and keeps the first, so a provider's repeated event is harmless; `suppress` answers `true` only for the call that recorded it, and two hosts recording one address at once leave one row. `isSuppressed(scope, addressHash)` answers for one scope. A scope is one list, and a host that keeps one passes `DEFAULT_SUPPRESSION_SCOPE` (`mail`) everywhere. `addressHash` is the SHA-256 of the address as 64 lower-case hexadecimal characters, which the host computes the same way wherever it reads or writes the record. Any other value, an address among them, throws a `TypeError` that holds none of it, so a mistake stores nothing and is never answered as not suppressed.
 
-`issue(recipient, scope, nonce, key)` answers base64url of HMAC-SHA256 over the nonce under the key, 43 characters, and stores the token's SHA-256 beside the recipient and the scope: the token carries neither, and the table holds nothing it can be recovered from. The same nonce under the same key gives the same token, so each message takes a nonce of its own, such as its id. Issuing it again for the same recipient and scope writes nothing; for another recipient or scope it throws, and the first token keeps its recipient and scope. The key is 32 bytes or more, given as bytes; a different key gives different tokens for the same nonces. `find(token)` answers the recipient and the scope, or `null` for a token that is malformed, unknown, revoked or past its expiry: it looks the token up by its SHA-256 and compares in constant time. `revoke(recipient)` ends every token of the recipient, in every scope, and answers how many it ended. Each revoked row stays, marked with the time of the revoke, so `issue` refuses a revoked token's nonce for every recipient, scope and expiry: a revoked link never works again and never comes to name someone else. A message that needs a working token after a revoke takes a new nonce, and the token it gets works. A token has no expiry unless `issue`'s options set `expiresAt`, in epoch milliseconds.
+`issue(recipient, scope, nonce, key)` answers base64url of HMAC-SHA256 over the nonce under the key, 43 characters, and stores the token's SHA-256 beside the recipient and the scope: the token carries neither, and the table holds nothing it can be recovered from. The same nonce under the same key gives the same token, so each message takes a nonce of its own, such as its id. Issuing it again for the same recipient, scope and expiry writes nothing; for another recipient, scope or expiry it throws, and the first token keeps all three. The key is 32 bytes or more, given as bytes; a different key gives different tokens for the same nonces. `find(token)` answers the recipient and the scope, or `null` for a token that is malformed, unknown, revoked or past its expiry: it looks the token up by its SHA-256 and compares in constant time. `revoke(recipient)` ends every token of the recipient, in every scope, and answers how many it ended. Each revoked row stays, marked with the time of the revoke, so `issue` refuses a revoked token's nonce for every recipient, scope and expiry: a revoked link never works again and never comes to name someone else. A message that needs a working token after a revoke takes a new nonce, and the token it gets works. A token has no expiry unless `issue`'s options set `expiresAt`, in epoch milliseconds.
 
-`suppressionStoreDdl(prefix)` makes the table `<prefix>_suppressions`, `recipientCapabilityDdl(prefix)` makes `<prefix>_capabilities` (`token_hash`, `recipient`, `scope`, `expires_at`, `revoked_at`) with its index on the recipient, and `emailPreferencesDdl(prefix)` makes both. The prefix is a lower-case letter and at most 39 lower-case letters, digits or underscores, and it keeps two hosts on one database apart. The statements are `CREATE ... IF NOT EXISTS` and run on SQLite and PostgreSQL. A token's row refuses its nonce for as long as it stays, revoked or not. A host that deletes a recipient's rows, by its own foreign key with `ON DELETE CASCADE` or by hand, never issues their nonces again: each message's nonce is one no other message ever had, such as a random id or a row id that is never reused. A host that cannot promise that calls `revoke` with each deletion and keeps the rows. Each store checks every argument before its first statement and lets a database error through as it was thrown. A store made on the handle that the adapter's `transaction` gives its callback writes inside that transaction.
+`suppressionStoreDdl(prefix)` makes the table `<prefix>_suppressions` (`scope`, `address_hash`, `reason`, `suppressed_on`), `recipientCapabilityDdl(prefix)` makes `<prefix>_capabilities` (`token_hash`, `recipient`, `scope`, `expires_at`, `revoked_at`) with its index on the recipient, and `emailPreferencesDdl(prefix)` makes both. The prefix is a lower-case letter and at most 39 lower-case letters, digits or underscores, and it keeps two hosts on one database apart. The statements are `CREATE ... IF NOT EXISTS` and run on SQLite and PostgreSQL. A token's row refuses its nonce for as long as it stays, revoked or not. A host that deletes a recipient's rows, by its own foreign key with `ON DELETE CASCADE` or by hand, never issues their nonces again: each message's nonce is one no other message ever had, such as a random id or a row id that is never reused. A host that cannot promise that calls `revoke` with each deletion and keeps the rows. Each store checks every argument before its first statement. A scope, a recipient and a nonce are strings of 1 to 512 characters with no U+0000, which PostgreSQL's text refuses, and no lone surrogate, which UTF-8 cannot encode, so a driver would store something else in its place: any other value throws a `TypeError` that holds none of it, and a name is stored as given on every backend. A database error passes through as it was thrown. A store made on the handle that the adapter's `transaction` gives its callback writes inside that transaction. On a server, open the database as the example does, with the adapter's `strict` option (0.6.15 or later): without it, a `url` that is unset opens a local SQLite database in its place, and the record a sender reads before each send would live there.
 
 ## Errors and retries
 
 A refusal from Resend throws `EmailApiError`, with `status` (the HTTP status), `type` (Resend's error name, such as `validation_error`, or `unknown` when the answer's body is not JSON, names no error, or names one that is not 1 to 64 letters, digits, `_`, `.`, `:` or `-`) and `retryAfterSeconds` (the answer's `retry-after`, or `null`). Its message names the status and the type and never carries Resend's message, which can quote an address.
 
-`fetch`'s own errors pass through as it throws them: a `TypeError` when the connection fails, and a `TimeoutError` when `timeoutMs` passes before an answer comes. A deadline that passes while an answer's body is being read throws no `TimeoutError`: a refusal then throws `EmailApiError` with `type` `unknown`, and an accepted send resolves with an empty `messageId`. The key is trimmed at each send. A key, an `idempotencyKey` or a `userAgent` that holds a character an HTTP header cannot carry (a line break or another control character other than a tab, or a character above U+00FF) throws an `Error` before any request, and its message names which one and none of its value. `ResendTransport.send` checks a message's `headers` by the rules for names and values in [header fields](#header-fields), though not against the fields the service writes, and throws the same way: a reply through Resend whose message id holds a line break is refused rather than sent in `In-Reply-To` and `References`.
+`fetch`'s own errors pass through as it throws them: a `TypeError` when the connection fails, and a `TimeoutError` when `timeoutMs` passes before an answer comes. A deadline that passes while an answer's body is being read throws no `TimeoutError`: a refusal then throws `EmailApiError` with `type` `unknown`, and an accepted send resolves with an empty `messageId`. The key is trimmed at each send. A key, an `idempotencyKey` or a `userAgent` that holds a character an HTTP header cannot carry (a line break or another control character other than a tab, or a character above U+00FF) throws an `Error` before any request, and its message names which one and none of its value. `ResendTransport.send` checks a message's `headers` by the rules for names and values in [header fields](#header-fields), though not against the fields the service writes, and throws the same way.
 
 A send is tried again only on the terms of Resend's [errors](https://resend.com/docs/api-reference/errors) and [rate limit](https://resend.com/docs/api-reference/rate-limit) pages, as `retryWaitSeconds` decides:
 
@@ -136,7 +147,19 @@ The wait is the answer's `retry-after` when it has one, else as many seconds as
 
 ## Reading mail
 
-`readInbox`, `searchEmails`, `extractCodes` and `replyToEmail` read through IMAP: the `imap` account (`host`, `user` and `password`, with `port` and `secure`, by default TLS on port 993), or the SMTP account when `imap` is not given. With Resend, reading needs `imap`. A reply goes out through the transport that sends, threaded with `In-Reply-To` and `References`. The pack's factory reads the account from the secrets `email.imap.host`, `email.imap.user` and `email.imap.password`, or from `IMAP_HOST`, `IMAP_USER` and `IMAP_PASSWORD`.
+`readInbox`, `searchEmails`, `extractCodes` and `replyToEmail` read through IMAP: the `imap` account (`host`, `user` and `password`, with `port` and `secure`, by default TLS on port 993), or the SMTP account when `imap` is not given. With Resend, reading needs `imap`. The pack's factory reads the account from the secrets `email.imap.host`, `email.imap.user` and `email.imap.password`, or from `IMAP_HOST`, `IMAP_USER` and `IMAP_PASSWORD`.
+
+`searchEmails` finds the messages whose subject, body or From holds `query`, ignoring case, and gives the last `limit` it finds (20 by default), newest first. Each search answers UIDs, and the messages are fetched by those UIDs, which need not follow the messages' sequence numbers once a message has been removed ([RFC 3501 section 2.3.1.1](https://www.rfc-editor.org/rfc/rfc3501#section-2.3.1.1)).
+
+`extractCodes(messageId, pattern?)` and `replyToEmail(messageId, body, html?)` name an INBOX message by its Message-ID, with or without its angle brackets: `<id@example.com>` and `id@example.com` name the same message. An IMAP search matches every Message-ID that holds the text ([RFC 3501 section 6.4.4](https://www.rfc-editor.org/rfc/rfc3501#section-6.4.4)), so each searches for the id in angle brackets and takes only the message whose own id is that one. `extractCodes` answers no codes for an id that is not one message id or that no message has.
+
+A reply goes out through the transport that sends:
+
+- to the original's Reply-To, or its From when it names none ([RFC 5322 section 3.6.2](https://www.rfc-editor.org/rfc/rfc5322#section-3.6.2));
+- under the original's subject on one line, with `Re: ` before it unless it starts with `Re:` in any case;
+- threaded as [RFC 5322 section 3.6.4](https://www.rfc-editor.org/rfc/rfc5322#section-3.6.4) has it: `In-Reply-To` names the original, and `References` lists the ids of the original's own References, or the one id of its In-Reply-To when its References lists none, then the original's id. Only fields of those very names are read, each whole however it is folded. An id in them that holds a character outside printable US-ASCII, or that is too long for one line, is left out, so whatever the original holds, both transports send the same reply.
+
+`replyToEmail` throws an `Error` that holds none of the id when the id is not one message id of printable US-ASCII with no space, or is too long for one line of `In-Reply-To`, before the original is read; and when no message in INBOX has the id, or the original names no address to reply to, before anything is sent.
 
 ## In an agent
 
@@ -146,7 +169,7 @@ A model names the tools' arguments and the channel's blocks, so `emailSend` and
 
 They send each attachment as they checked it: a copy of its own `filename`, `content`, `path` and `contentType`, each read once, with a Buffer's bytes copied. They refuse the same way an attachment that is not an object, one that gives any of those four through a getter or a setter, and one whose `filename` or `contentType` is not a string. Any other property of an attachment is left out.
 
-The subject, the bodies and the message id a reply names must be text. Through SMTP, nodemailer reads the file or fetches the address an object body names into the message, and writes an object subject or message id marked `prepared` into the headers as it is. So `sendEmail` and `replyToEmail`, whoever calls them, throw a `TypeError` that names the field, never its value, before anything is sent on either transport: `subject`, `body` and the reply's `messageId` must be strings, and `html` a string when given (`null` leaves the HTML part out). `emailSend` and `emailReply` answer it as `{ success: false, error }`, and the adapter throws it.
+The subject, the bodies and the message id a reply names must be text. Through SMTP, nodemailer reads the file or fetches the address an object body names into the message, and writes an object subject or message id marked `prepared` into the headers as it is. So `sendEmail` and `replyToEmail`, whoever calls them, throw a `TypeError` that names the field, never its value, before anything is sent on either transport: `subject`, `body` and the reply's `messageId` must be strings, and `html` a string when given (`null` leaves the HTML part out). `emailSend` and `emailReply` answer it as `{ success: false, error }`, and the adapter throws it. A reply whose message id is not one message id, or names no message in INBOX, is answered and thrown the same way, with the `Error` [reading mail](#reading-mail) describes.
 
 ## API
 

package/dist/EmailChannelAdapter.d.ts

@@ -49,7 +49,9 @@ export declare class EmailChannelAdapter {
      * filename before anything is sent, a reply included; what is sent is the copy `requireAgentAttachments` made of
      * each attachment, so a Buffer is sent as the bytes it held then. A text block's `text`, an HTML block's `html` (or
      * its `text`), the `subject` in `platformOptions` and `replyToMessageId` must be strings when given: otherwise the
-     * service throws a `TypeError` naming the field before anything is sent.
+     * service throws a `TypeError` naming the field before anything is sent. A reply goes to the original's Reply-To, or
+     * its From, as `EmailService.replyToEmail` sends it, and a `replyToMessageId` that is not one message id, or that no
+     * message in the inbox has, throws an `Error` before anything is sent.
      */
     sendMessage(conversationId: string, content: MessageContent): Promise<ChannelSendResult>;
     sendTypingIndicator(_conversationId: string, _isTyping: boolean): Promise<void>;

package/dist/EmailChannelAdapter.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"EmailChannelAdapter.d.ts","sourceRoot":"","sources":["../src/EmailChannelAdapter.ts"],"names":[],"mappings":"AACA;;GAEG;AAEH,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,mBAAmB,CAAC;AAGtD,MAAM,MAAM,eAAe,GAAG,MAAM,CAAC;AACrC,MAAM,MAAM,iBAAiB,GAAG,MAAM,CAAC;AACvC,MAAM,MAAM,uBAAuB,GAAG,cAAc,GAAG,YAAY,GAAG,WAAW,GAAG,cAAc,GAAG,OAAO,CAAC;AAC7G,MAAM,MAAM,gBAAgB,GAAG,MAAM,CAAC;AAEtC,MAAM,WAAW,iBAAiB;IAChC,QAAQ,EAAE,eAAe,CAAC;IAC1B,UAAU,EAAE,MAAM,CAAC;IACnB,MAAM,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;CACjC;AAED,MAAM,WAAW,qBAAqB;IACpC,MAAM,EAAE,uBAAuB,CAAC;IAChC,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,YAAY,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;CACxC;AAED,MAAM,WAAW,cAAc;IAC7B,MAAM,EAAE,KAAK,CAAC;QAAE,IAAI,EAAE,MAAM,CAAC;QAAC,CAAC,GAAG,EAAE,MAAM,GAAG,GAAG,CAAA;KAAE,CAAC,CAAC;IACpD,gBAAgB,CAAC,EAAE,MAAM,CAAC;IAC1B,eAAe,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;CAC3C;AAED,MAAM,WAAW,iBAAiB;IAChC,SAAS,EAAE,MAAM,CAAC;IAClB,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAED,MAAM,MAAM,mBAAmB,GAAG,CAAC,KAAK,EAAE,GAAG,KAAK,IAAI,GAAG,OAAO,CAAC,IAAI,CAAC,CAAC;AAEvE,qBAAa,mBAAmB;IAC9B,QAAQ,CAAC,QAAQ,EAAE,eAAe,CAAW;IAC7C,QAAQ,CAAC,WAAW,WAAW;IAC/B,QAAQ,CAAC,YAAY,EAAE,SAAS,iBAAiB,EAAE,CAEjD;IAEF,OAAO,CAAC,OAAO,CAAe;IAC9B,OAAO,CAAC,WAAW,CAAuB;IAC1C,OAAO,CAAC,QAAQ,CAAuC;IACvD,OAAO,CAAC,YAAY,CAAuB;gBAE/B,OAAO,EAAE,YAAY;IAI3B,UAAU,CAAC,KAAK,EAAE,iBAAiB,GAAG,OAAO,CAAC,IAAI,CAAC;IAWnD,QAAQ,IAAI,OAAO,CAAC,IAAI,CAAC;IAK/B,iBAAiB,IAAI,qBAAqB;IAc1C;;;;;;;;OAQG;IACG,WAAW,CAAC,cAAc,EAAE,MAAM,EAAE,OAAO,EAAE,cAAc,GAAG,OAAO,CAAC,iBAAiB,CAAC;IAyCxF,mBAAmB,CAAC,eAAe,EAAE,MAAM,EAAE,SAAS,EAAE,OAAO,GAAG,OAAO,CAAC,IAAI,CAAC;IAIrF,EAAE,CAAC,OAAO,EAAE,mBAAmB,EAAE,WAAW,CAAC,EAAE,gBAAgB,EAAE,GAAG,MAAM,IAAI;CAI/E"}
+{"version":3,"file":"EmailChannelAdapter.d.ts","sourceRoot":"","sources":["../src/EmailChannelAdapter.ts"],"names":[],"mappings":"AACA;;GAEG;AAEH,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,mBAAmB,CAAC;AAGtD,MAAM,MAAM,eAAe,GAAG,MAAM,CAAC;AACrC,MAAM,MAAM,iBAAiB,GAAG,MAAM,CAAC;AACvC,MAAM,MAAM,uBAAuB,GAAG,cAAc,GAAG,YAAY,GAAG,WAAW,GAAG,cAAc,GAAG,OAAO,CAAC;AAC7G,MAAM,MAAM,gBAAgB,GAAG,MAAM,CAAC;AAEtC,MAAM,WAAW,iBAAiB;IAChC,QAAQ,EAAE,eAAe,CAAC;IAC1B,UAAU,EAAE,MAAM,CAAC;IACnB,MAAM,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;CACjC;AAED,MAAM,WAAW,qBAAqB;IACpC,MAAM,EAAE,uBAAuB,CAAC;IAChC,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,YAAY,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;CACxC;AAED,MAAM,WAAW,cAAc;IAC7B,MAAM,EAAE,KAAK,CAAC;QAAE,IAAI,EAAE,MAAM,CAAC;QAAC,CAAC,GAAG,EAAE,MAAM,GAAG,GAAG,CAAA;KAAE,CAAC,CAAC;IACpD,gBAAgB,CAAC,EAAE,MAAM,CAAC;IAC1B,eAAe,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;CAC3C;AAED,MAAM,WAAW,iBAAiB;IAChC,SAAS,EAAE,MAAM,CAAC;IAClB,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAED,MAAM,MAAM,mBAAmB,GAAG,CAAC,KAAK,EAAE,GAAG,KAAK,IAAI,GAAG,OAAO,CAAC,IAAI,CAAC,CAAC;AAEvE,qBAAa,mBAAmB;IAC9B,QAAQ,CAAC,QAAQ,EAAE,eAAe,CAAW;IAC7C,QAAQ,CAAC,WAAW,WAAW;IAC/B,QAAQ,CAAC,YAAY,EAAE,SAAS,iBAAiB,EAAE,CAEjD;IAEF,OAAO,CAAC,OAAO,CAAe;IAC9B,OAAO,CAAC,WAAW,CAAuB;IAC1C,OAAO,CAAC,QAAQ,CAAuC;IACvD,OAAO,CAAC,YAAY,CAAuB;gBAE/B,OAAO,EAAE,YAAY;IAI3B,UAAU,CAAC,KAAK,EAAE,iBAAiB,GAAG,OAAO,CAAC,IAAI,CAAC;IAWnD,QAAQ,IAAI,OAAO,CAAC,IAAI,CAAC;IAK/B,iBAAiB,IAAI,qBAAqB;IAc1C;;;;;;;;;;OAUG;IACG,WAAW,CAAC,cAAc,EAAE,MAAM,EAAE,OAAO,EAAE,cAAc,GAAG,OAAO,CAAC,iBAAiB,CAAC;IAyCxF,mBAAmB,CAAC,eAAe,EAAE,MAAM,EAAE,SAAS,EAAE,OAAO,GAAG,OAAO,CAAC,IAAI,CAAC;IAIrF,EAAE,CAAC,OAAO,EAAE,mBAAmB,EAAE,WAAW,CAAC,EAAE,gBAAgB,EAAE,GAAG,MAAM,IAAI;CAI/E"}

package/dist/EmailChannelAdapter.js

@@ -53,7 +53,9 @@ class EmailChannelAdapter {
      * filename before anything is sent, a reply included; what is sent is the copy `requireAgentAttachments` made of
      * each attachment, so a Buffer is sent as the bytes it held then. A text block's `text`, an HTML block's `html` (or
      * its `text`), the `subject` in `platformOptions` and `replyToMessageId` must be strings when given: otherwise the
-     * service throws a `TypeError` naming the field before anything is sent.
+     * service throws a `TypeError` naming the field before anything is sent. A reply goes to the original's Reply-To, or
+     * its From, as `EmailService.replyToEmail` sends it, and a `replyToMessageId` that is not one message id, or that no
+     * message in the inbox has, throws an `Error` before anything is sent.
      */
     async sendMessage(conversationId, content) {
         const textBlock = content.blocks.find((b) => b.type === 'text');

package/dist/EmailChannelAdapter.js.map

@@ -1 +1 @@
-{"version":3,"file":"EmailChannelAdapter.js","sourceRoot":"","sources":["../src/EmailChannelAdapter.ts"],"names":[],"mappings":";AAAA,cAAc;AACd;;GAEG;;;AAGH,+DAAgE;AAiChE,MAAa,mBAAmB;IAY9B,YAAY,OAAqB;QAXxB,aAAQ,GAAoB,OAAO,CAAC;QACpC,gBAAW,GAAG,OAAO,CAAC;QACtB,iBAAY,GAAiC;YACpD,MAAM,EAAE,WAAW,EAAE,WAAW,EAAE,QAAQ,EAAE,SAAS;SACtD,CAAC;QAGM,gBAAW,GAAkB,IAAI,CAAC;QAClC,aAAQ,GAA6B,IAAI,GAAG,EAAE,CAAC;QAC/C,iBAAY,GAAkB,IAAI,CAAC;QAGzC,IAAI,CAAC,OAAO,GAAG,OAAO,CAAC;IACzB,CAAC;IAED,KAAK,CAAC,UAAU,CAAC,KAAwB;QACvC,IAAI,CAAC;YACH,MAAM,IAAI,CAAC,OAAO,CAAC,UAAU,EAAE,CAAC;YAChC,IAAI,CAAC,WAAW,GAAG,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE,CAAC;YAC5C,IAAI,CAAC,YAAY,GAAG,IAAI,CAAC;QAC3B,CAAC;QAAC,OAAO,GAAQ,EAAE,CAAC;YAClB,IAAI,CAAC,YAAY,GAAG,GAAG,CAAC,OAAO,CAAC;YAChC,MAAM,GAAG,CAAC;QACZ,CAAC;IACH,CAAC;IAED,KAAK,CAAC,QAAQ;QACZ,MAAM,IAAI,CAAC,OAAO,CAAC,QAAQ,EAAE,CAAC;QAC9B,IAAI,CAAC,WAAW,GAAG,IAAI,CAAC;IAC1B,CAAC;IAED,iBAAiB;QACf,IAAI,IAAI,CAAC,YAAY,EAAE,CAAC;YACtB,OAAO,EAAE,MAAM,EAAE,OAAO,EAAE,YAAY,EAAE,IAAI,CAAC,YAAY,EAAE,CAAC;QAC9D,CAAC;QACD,IAAI,CAAC,IAAI,CAAC,OAAO,CAAC,SAAS,EAAE,CAAC;YAC5B,OAAO,EAAE,MAAM,EAAE,cAAc,EAAE,CAAC;QACpC,CAAC;QACD,OAAO;YACL,MAAM,EAAE,WAAW;YACnB,cAAc,EAAE,IAAI,CAAC,WAAW,IAAI,SAAS;YAC7C,YAAY,EAAE,EAAE,QAAQ,EAAE,OAAO,EAAE;SACpC,CAAC;IACJ,CAAC;IAED;;;;;;;;OAQG;IACH,KAAK,CAAC,WAAW,CAAC,cAAsB,EAAE,OAAuB;QAC/D,MAAM,SAAS,GAAG,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,KAAK,MAAM,CAAC,CAAC;QAChE,MAAM,SAAS,GAAG,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,KAAK,WAAW,IAAI,CAAC,CAAC,IAAI,KAAK,MAAM,CAAC,CAAC;QAC1F,MAAM,IAAI,GAAG,SAAS,EAAE,IAAI,IAAI,EAAE,CAAC;QACnC,MAAM,IAAI,GAAG,SAAS,EAAE,IAAI,IAAI,SAAS,EAAE,IAAI,CAAC;QAEhD,sDAAsD;QACtD,MAAM,OAAO,GAAI,OAAO,CAAC,eAAe,EAAE,OAAkB,IAAI,sBAAsB,CAAC;QAEvF,sBAAsB;QACtB,MAAM,WAAW,GAA0E,EAAE,CAAC;QAC9F,KAAK,MAAM,KAAK,IAAI,OAAO,CAAC,MAAM,EAAE,CAAC;YACnC,IAAI,KAAK,CAAC,IAAI,KAAK,UAAU,IAAI,KAAK,CAAC,IAAI,KAAK,OAAO,EAAE,CAAC;gBACxD,WAAW,CAAC,IAAI,CAAC;oBACf,QAAQ,EAAE,KAAK,CAAC,QAAQ,IAAI,KAAK,CAAC,IAAI,IAAI,YAAY;oBACtD,IAAI,EAAE,KAAK,CAAC,GAAG;oBACf,OAAO,EAAE,KAAK,CAAC,OAAO;iBACvB,CAAC,CAAC;YACL,CAAC;QACH,CAAC;QAED,kHAAkH;QAClH,mCAAmC;QACnC,MAAM,OAAO,GAAG,IAAA,6CAAuB,EAAC,WAAW,EAAE,IAAI,CAAC,OAAO,CAAC,SAAS,KAAK,QAAQ,CAAC,CAAC;QAE1F,IAAI,OAAO,CAAC,gBAAgB,EAAE,CAAC;YAC7B,MAAM,MAAM,GAAG,MAAM,IAAI,CAAC,OAAO,CAAC,YAAY,CAAC,OAAO,CAAC,gBAAgB,EAAE,IAAI,EAAE,IAAI,CAAC,CAAC;YACrF,OAAO,EAAE,SAAS,EAAE,MAAM,CAAC,SAAS,EAAE,SAAS,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE,EAAE,CAAC;QAC9E,CAAC;QAED,MAAM,MAAM,GAAG,MAAM,IAAI,CAAC,OAAO,CAAC,SAAS,CAAC;YAC1C,EAAE,EAAE,cAAc;YAClB,OAAO;YACP,IAAI,EAAE,IAAI;YACV,IAAI;YACJ,WAAW,EAAE,OAAO,KAAK,SAAS,IAAI,OAAO,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,OAAO,CAAC,CAAC,CAAC,SAAS;SAC/E,CAAC,CAAC;QAEH,OAAO,EAAE,SAAS,EAAE,MAAM,CAAC,SAAS,EAAE,SAAS,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE,EAAE,CAAC;IAC9E,CAAC;IAED,KAAK,CAAC,mBAAmB,CAAC,eAAuB,EAAE,SAAkB;QACnE,2CAA2C;IAC7C,CAAC;IAED,EAAE,CAAC,OAA4B,EAAE,WAAgC;QAC/D,IAAI,CAAC,QAAQ,CAAC,GAAG,CAAC,OAAO,CAAC,CAAC;QAC3B,OAAO,GAAG,EAAE,CAAC,IAAI,CAAC,QAAQ,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC;IAC7C,CAAC;CACF;AAxGD,kDAwGC"}
+{"version":3,"file":"EmailChannelAdapter.js","sourceRoot":"","sources":["../src/EmailChannelAdapter.ts"],"names":[],"mappings":";AAAA,cAAc;AACd;;GAEG;;;AAGH,+DAAgE;AAiChE,MAAa,mBAAmB;IAY9B,YAAY,OAAqB;QAXxB,aAAQ,GAAoB,OAAO,CAAC;QACpC,gBAAW,GAAG,OAAO,CAAC;QACtB,iBAAY,GAAiC;YACpD,MAAM,EAAE,WAAW,EAAE,WAAW,EAAE,QAAQ,EAAE,SAAS;SACtD,CAAC;QAGM,gBAAW,GAAkB,IAAI,CAAC;QAClC,aAAQ,GAA6B,IAAI,GAAG,EAAE,CAAC;QAC/C,iBAAY,GAAkB,IAAI,CAAC;QAGzC,IAAI,CAAC,OAAO,GAAG,OAAO,CAAC;IACzB,CAAC;IAED,KAAK,CAAC,UAAU,CAAC,KAAwB;QACvC,IAAI,CAAC;YACH,MAAM,IAAI,CAAC,OAAO,CAAC,UAAU,EAAE,CAAC;YAChC,IAAI,CAAC,WAAW,GAAG,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE,CAAC;YAC5C,IAAI,CAAC,YAAY,GAAG,IAAI,CAAC;QAC3B,CAAC;QAAC,OAAO,GAAQ,EAAE,CAAC;YAClB,IAAI,CAAC,YAAY,GAAG,GAAG,CAAC,OAAO,CAAC;YAChC,MAAM,GAAG,CAAC;QACZ,CAAC;IACH,CAAC;IAED,KAAK,CAAC,QAAQ;QACZ,MAAM,IAAI,CAAC,OAAO,CAAC,QAAQ,EAAE,CAAC;QAC9B,IAAI,CAAC,WAAW,GAAG,IAAI,CAAC;IAC1B,CAAC;IAED,iBAAiB;QACf,IAAI,IAAI,CAAC,YAAY,EAAE,CAAC;YACtB,OAAO,EAAE,MAAM,EAAE,OAAO,EAAE,YAAY,EAAE,IAAI,CAAC,YAAY,EAAE,CAAC;QAC9D,CAAC;QACD,IAAI,CAAC,IAAI,CAAC,OAAO,CAAC,SAAS,EAAE,CAAC;YAC5B,OAAO,EAAE,MAAM,EAAE,cAAc,EAAE,CAAC;QACpC,CAAC;QACD,OAAO;YACL,MAAM,EAAE,WAAW;YACnB,cAAc,EAAE,IAAI,CAAC,WAAW,IAAI,SAAS;YAC7C,YAAY,EAAE,EAAE,QAAQ,EAAE,OAAO,EAAE;SACpC,CAAC;IACJ,CAAC;IAED;;;;;;;;;;OAUG;IACH,KAAK,CAAC,WAAW,CAAC,cAAsB,EAAE,OAAuB;QAC/D,MAAM,SAAS,GAAG,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,KAAK,MAAM,CAAC,CAAC;QAChE,MAAM,SAAS,GAAG,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,KAAK,WAAW,IAAI,CAAC,CAAC,IAAI,KAAK,MAAM,CAAC,CAAC;QAC1F,MAAM,IAAI,GAAG,SAAS,EAAE,IAAI,IAAI,EAAE,CAAC;QACnC,MAAM,IAAI,GAAG,SAAS,EAAE,IAAI,IAAI,SAAS,EAAE,IAAI,CAAC;QAEhD,sDAAsD;QACtD,MAAM,OAAO,GAAI,OAAO,CAAC,eAAe,EAAE,OAAkB,IAAI,sBAAsB,CAAC;QAEvF,sBAAsB;QACtB,MAAM,WAAW,GAA0E,EAAE,CAAC;QAC9F,KAAK,MAAM,KAAK,IAAI,OAAO,CAAC,MAAM,EAAE,CAAC;YACnC,IAAI,KAAK,CAAC,IAAI,KAAK,UAAU,IAAI,KAAK,CAAC,IAAI,KAAK,OAAO,EAAE,CAAC;gBACxD,WAAW,CAAC,IAAI,CAAC;oBACf,QAAQ,EAAE,KAAK,CAAC,QAAQ,IAAI,KAAK,CAAC,IAAI,IAAI,YAAY;oBACtD,IAAI,EAAE,KAAK,CAAC,GAAG;oBACf,OAAO,EAAE,KAAK,CAAC,OAAO;iBACvB,CAAC,CAAC;YACL,CAAC;QACH,CAAC;QAED,kHAAkH;QAClH,mCAAmC;QACnC,MAAM,OAAO,GAAG,IAAA,6CAAuB,EAAC,WAAW,EAAE,IAAI,CAAC,OAAO,CAAC,SAAS,KAAK,QAAQ,CAAC,CAAC;QAE1F,IAAI,OAAO,CAAC,gBAAgB,EAAE,CAAC;YAC7B,MAAM,MAAM,GAAG,MAAM,IAAI,CAAC,OAAO,CAAC,YAAY,CAAC,OAAO,CAAC,gBAAgB,EAAE,IAAI,EAAE,IAAI,CAAC,CAAC;YACrF,OAAO,EAAE,SAAS,EAAE,MAAM,CAAC,SAAS,EAAE,SAAS,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE,EAAE,CAAC;QAC9E,CAAC;QAED,MAAM,MAAM,GAAG,MAAM,IAAI,CAAC,OAAO,CAAC,SAAS,CAAC;YAC1C,EAAE,EAAE,cAAc;YAClB,OAAO;YACP,IAAI,EAAE,IAAI;YACV,IAAI;YACJ,WAAW,EAAE,OAAO,KAAK,SAAS,IAAI,OAAO,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,OAAO,CAAC,CAAC,CAAC,SAAS;SAC/E,CAAC,CAAC;QAEH,OAAO,EAAE,SAAS,EAAE,MAAM,CAAC,SAAS,EAAE,SAAS,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE,EAAE,CAAC;IAC9E,CAAC;IAED,KAAK,CAAC,mBAAmB,CAAC,eAAuB,EAAE,SAAkB;QACnE,2CAA2C;IAC7C,CAAC;IAED,EAAE,CAAC,OAA4B,EAAE,WAAgC;QAC/D,IAAI,CAAC,QAAQ,CAAC,GAAG,CAAC,OAAO,CAAC,CAAC;QAC3B,OAAO,GAAG,EAAE,CAAC,IAAI,CAAC,QAAQ,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC;IAC7C,CAAC;CACF;AA1GD,kDA0GC"}

package/dist/EmailService.d.ts

@@ -45,10 +45,12 @@ export interface SendEmailOptions {
     idempotencyKey?: string;
     /**
      * Header fields added to the message, by name, such as `List-Unsubscribe` and `List-Unsubscribe-Post`: through Resend
-     * the request's `headers`, through SMTP fields nodemailer writes into the message. A name is printable US-ASCII with no
-     * space or colon, given once in any case, and a value is a string with no line break or other control character than
-     * the tab. A field the service writes itself is refused, in any case: `From`, `To`, `Cc`, `Bcc`, `Reply-To`, `Subject`,
-     * `Date`, `Message-ID`, `MIME-Version` and any `Content-` field.
+     * the request's `headers`, through SMTP fields nodemailer writes into the message as given. A name is printable
+     * US-ASCII with no space or colon, given once in any case. A value is a string of printable US-ASCII words, one space
+     * or tab between each two and none at either end, with no word so long that the name, a colon, a space and the word
+     * pass 998 characters, RFC 5322's longest line; `In-Reply-To` and `References` list message ids, each in angle
+     * brackets. A field the service writes itself is refused, in any case: `From`, `To`, `Cc`, `Bcc`, `Reply-To`,
+     * `Subject`, `Date`, `Message-ID`, `MIME-Version` and any `Content-` field.
      */
     headers?: Record<string, string>;
 }
@@ -98,31 +100,61 @@ export declare class EmailService {
      * `subject` and `body` must be strings, and `html` a string when it is given (`null` sends no HTML part, as
      * `undefined` does): any other value throws a `TypeError` naming the field, never its value, before either transport
      * is used. An object body would have nodemailer read the file its `path` names or fetch the address its `href` names
-     * into the message, and an object subject marked `prepared` would be written into the headers as it is.
+     * into the message, and an object subject marked `prepared` would be written into the headers as it is. The subject
+     * goes out on one line through either transport: each line break in it, and each other control character but the
+     * tab, is sent as a space, as nodemailer writes a line break in a subject.
      *
      * `headers` adds fields to the message and never replaces one the service writes. It must be a plain object of names
-     * and values: a name printable US-ASCII with no space or colon, given once in any case, and none of `From`, `To`,
-     * `Cc`, `Bcc`, `Reply-To`, `Subject`, `Date`, `Message-ID`, `MIME-Version` or a `Content-` field, in any case; a value
-     * a string with no line break or other control character than the tab. Anything else throws an `Error` that names the
-     * field, or its place when its name is at fault, and none of its value, before either transport is used. Each value is
-     * read once, and the fields are sent as read.
+     * and values, made in this realm or another: a name printable US-ASCII with no space or colon, given once in any case,
+     * and none of `From`, `To`, `Cc`, `Bcc`, `Reply-To`, `Subject`, `Date`, `Message-ID`, `MIME-Version` or a `Content-`
+     * field, in any case; a value a string of printable US-ASCII words, one space or tab between each two and none at
+     * either end, with no word so long that the name, a colon, a space and the word pass 998 characters, and for
+     * `In-Reply-To` and `References` message ids, each in angle brackets. Anything else throws an `Error` that names the
+     * field, or its place when its name is at fault, and none of its value, before either transport is used. Each value
+     * is read once, and both transports send the fields as read: nodemailer writes each value as given, folded at its
+     * white space, except `Sender`, which it writes as the address it parses from the value.
      */
     sendEmail(options: SendEmailOptions): Promise<{
         messageId: string;
     }>;
     readInbox(folder?: string, limit?: number): Promise<EmailMessage[]>;
+    /**
+     * The messages of `folder` (INBOX unless given) whose subject, body or From holds `query`, ignoring case, received on
+     * or after `since` when it is given: the last `limit` (20 unless given) the search finds, newest first. The search
+     * answers UIDs, and the messages are fetched by those UIDs, which need not follow the messages' sequence numbers.
+     */
     searchEmails(options: SearchEmailOptions): Promise<EmailMessage[]>;
+    /**
+     * The codes in the INBOX message whose Message-ID is `messageId`, given with or without its angle brackets: the
+     * matches of `pattern` when it is given, else runs of four to eight digits, then the codes that phrases such as "code
+     * is", "OTP:", "is your" or "enter ... to" point to, each once. The message is searched for by the id in angle brackets
+     * and fetched by the UID the search answers; a search matches every Message-ID that holds the text, so only the
+     * message whose own id is the one given counts. An id that is not one message id, or that no message has, gives no
+     * codes.
+     */
     extractCodes(messageId: string, pattern?: string): Promise<{
         codes: string[];
         messageId: string;
     }>;
     /**
-     * Replies to the message whose Message-ID is `messageId`, reading its sender, subject and References through IMAP,
-     * and sends `body` with `html`, when given, through the transport that sends, threaded with `In-Reply-To` and
-     * `References`. `messageId` and `body` must be strings, and `html` a string when it is given (`null` sends no HTML
-     * part): any other value throws a `TypeError` naming the field, never its value, before the original is read or
-     * anything is sent. Besides the bodies' files and addresses (see `sendEmail`), an object message id marked `prepared`
-     * would be written into the `In-Reply-To` header as it is.
+     * Replies to the INBOX message whose Message-ID is `messageId`, given with or without its angle brackets, and sends
+     * `body` with `html`, when given, through the transport that sends. The original is searched for by the id in angle
+     * brackets and fetched by the UID the search answers; a search matches every Message-ID that holds the text, so the
+     * original is the message whose own id is the one given. The reply goes to the original's Reply-To, or its From when
+     * it names none (RFC 5322 section 3.6.2), under its subject with one `Re: ` before it unless it starts with one in any
+     * case, on one line. It is threaded as RFC 5322 section 3.6.4 has it: `In-Reply-To` names the original, and
+     * `References` lists the ids of the original's own References, or the one id of its In-Reply-To when its References
+     * lists none, then the original's id. Only fields of those very names are read, each whole however it is folded, and
+     * an id in them that holds a character outside printable US-ASCII, or that is too long for one line, is left out, so
+     * both transports send the same fields whatever the original holds.
+     *
+     * `messageId` and `body` must be strings, and `html` a string when it is given (`null` sends no HTML part): any other
+     * value throws a `TypeError` naming the field, never its value, before the original is read or anything is sent.
+     * Besides the bodies' files and addresses (see `sendEmail`), an object message id marked `prepared` would be written
+     * into the `In-Reply-To` header as it is. A message id that is not one id of printable US-ASCII with no space, or that
+     * is too long for one line of `In-Reply-To`, throws an `Error` before the original is read; no message with that id,
+     * or an original that names no address to reply to, throws an `Error` before anything is sent. None of these errors
+     * holds the id.
      */
     replyToEmail(messageId: string, body: string, html?: string): Promise<{
         messageId: string;

package/dist/EmailService.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"EmailService.d.ts","sourceRoot":"","sources":["../src/EmailService.ts"],"names":[],"mappings":"AACA;;;;;GAKG;AAKH,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,sBAAsB,CAAC;AAQ1D,sGAAsG;AACtG,MAAM,WAAW,WAAW;IAC1B,0GAA0G;IAC1G,IAAI,CAAC,EAAE;QACL,IAAI,EAAE,MAAM,CAAC;QACb,IAAI,EAAE,MAAM,CAAC;QACb,QAAQ,EAAE,MAAM,CAAC;QACjB,IAAI,CAAC,EAAE,MAAM,CAAC;QACd,MAAM,CAAC,EAAE,OAAO,CAAC;KAClB,CAAC;IACF,wFAAwF;IACxF,MAAM,CAAC,EAAE,aAAa,CAAC;IACvB,iIAAiI;IACjI,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,IAAI,CAAC,EAAE;QACL,IAAI,EAAE,MAAM,CAAC;QACb,IAAI,EAAE,MAAM,CAAC;QACb,QAAQ,EAAE,MAAM,CAAC;QACjB,IAAI,CAAC,EAAE,MAAM,CAAC;QACd,MAAM,CAAC,EAAE,OAAO,CAAC;KAClB,CAAC;CACH;AAED,MAAM,WAAW,gBAAgB;IAC/B,EAAE,EAAE,MAAM,CAAC;IACX,OAAO,EAAE,MAAM,CAAC;IAChB,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,WAAW,CAAC,EAAE,KAAK,CAAC;QAClB,QAAQ,EAAE,MAAM,CAAC;QACjB,OAAO,CAAC,EAAE,MAAM,GAAG,MAAM,CAAC;QAC1B,IAAI,CAAC,EAAE,MAAM,CAAC;QACd,WAAW,CAAC,EAAE,MAAM,CAAC;KACtB,CAAC,CAAC;IACH,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,EAAE,CAAC,EAAE,MAAM,CAAC;IACZ,GAAG,CAAC,EAAE,MAAM,CAAC;IACb,kEAAkE;IAClE,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB;;;;;;OAMG;IACH,OAAO,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;CAClC;AAED,MAAM,WAAW,YAAY;IAC3B,SAAS,EAAE,MAAM,CAAC;IAClB,IAAI,EAAE,MAAM,CAAC;IACb,EAAE,EAAE,MAAM,CAAC;IACX,OAAO,EAAE,MAAM,CAAC;IAChB,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,KAAK,EAAE,MAAM,EAAE,CAAC;IAChB,GAAG,EAAE,MAAM,CAAC;CACb;AAED,MAAM,WAAW,kBAAkB;IACjC,KAAK,EAAE,MAAM,CAAC;IACd,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,KAAK,CAAC,EAAE,MAAM,CAAC;CAChB;AAMD,qBAAa,YAAY;IACvB,OAAO,CAAC,MAAM,CAAc;IAC5B,OAAO,CAAC,WAAW,CAAuC;IAC1D,OAAO,CAAC,MAAM,CAAgC;IAC9C,OAAO,CAAC,OAAO,CAAS;gBAEZ,MAAM,EAAE,WAAW;IAI/B;;;OAGG;IACG,UAAU,IAAI,OAAO,CAAC,IAAI,CAAC;IA8B3B,QAAQ,IAAI,OAAO,CAAC,IAAI,CAAC;IAS/B,IAAI,SAAS,IAAI,OAAO,CAEvB;IAED;;;OAGG;IACH,IAAI,SAAS,IAAI,QAAQ,GAAG,MAAM,GAAG,IAAI,CAGxC;IAID;;;;;;;;;;;;;;;;;;;OAmBG;IACG,SAAS,CAAC,OAAO,EAAE,gBAAgB,GAAG,OAAO,CAAC;QAAE,SAAS,EAAE,MAAM,CAAA;KAAE,CAAC;IAiDpE,SAAS,CAAC,MAAM,GAAE,MAAgB,EAAE,KAAK,GAAE,MAAW,GAAG,OAAO,CAAC,YAAY,EAAE,CAAC;IAgDhF,YAAY,CAAC,OAAO,EAAE,kBAAkB,GAAG,OAAO,CAAC,YAAY,EAAE,CAAC;IA+DlE,YAAY,CAAC,SAAS,EAAE,MAAM,EAAE,OAAO,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC;QAAE,KAAK,EAAE,MAAM,EAAE,CAAC;QAAC,SAAS,EAAE,MAAM,CAAA;KAAE,CAAC;IA+DxG;;;;;;;OAOG;IACG,YAAY,CAChB,SAAS,EAAE,MAAM,EACjB,IAAI,EAAE,MAAM,EACZ,IAAI,CAAC,EAAE,MAAM,GACZ,OAAO,CAAC;QAAE,SAAS,EAAE,MAAM,CAAA;KAAE,CAAC;YA8DnB,aAAa;IAuB3B,OAAO,CAAC,gBAAgB;IAqCxB,OAAO,CAAC,eAAe;IA4BvB,OAAO,CAAC,qBAAqB;IAM7B,OAAO,CAAC,cAAc;CAGvB"}
+{"version":3,"file":"EmailService.d.ts","sourceRoot":"","sources":["../src/EmailService.ts"],"names":[],"mappings":"AACA;;;;;GAKG;AAKH,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,sBAAsB,CAAC;AAQ1D,sGAAsG;AACtG,MAAM,WAAW,WAAW;IAC1B,0GAA0G;IAC1G,IAAI,CAAC,EAAE;QACL,IAAI,EAAE,MAAM,CAAC;QACb,IAAI,EAAE,MAAM,CAAC;QACb,QAAQ,EAAE,MAAM,CAAC;QACjB,IAAI,CAAC,EAAE,MAAM,CAAC;QACd,MAAM,CAAC,EAAE,OAAO,CAAC;KAClB,CAAC;IACF,wFAAwF;IACxF,MAAM,CAAC,EAAE,aAAa,CAAC;IACvB,iIAAiI;IACjI,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,IAAI,CAAC,EAAE;QACL,IAAI,EAAE,MAAM,CAAC;QACb,IAAI,EAAE,MAAM,CAAC;QACb,QAAQ,EAAE,MAAM,CAAC;QACjB,IAAI,CAAC,EAAE,MAAM,CAAC;QACd,MAAM,CAAC,EAAE,OAAO,CAAC;KAClB,CAAC;CACH;AAED,MAAM,WAAW,gBAAgB;IAC/B,EAAE,EAAE,MAAM,CAAC;IACX,OAAO,EAAE,MAAM,CAAC;IAChB,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,WAAW,CAAC,EAAE,KAAK,CAAC;QAClB,QAAQ,EAAE,MAAM,CAAC;QACjB,OAAO,CAAC,EAAE,MAAM,GAAG,MAAM,CAAC;QAC1B,IAAI,CAAC,EAAE,MAAM,CAAC;QACd,WAAW,CAAC,EAAE,MAAM,CAAC;KACtB,CAAC,CAAC;IACH,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,EAAE,CAAC,EAAE,MAAM,CAAC;IACZ,GAAG,CAAC,EAAE,MAAM,CAAC;IACb,kEAAkE;IAClE,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB;;;;;;;;OAQG;IACH,OAAO,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;CAClC;AAED,MAAM,WAAW,YAAY;IAC3B,SAAS,EAAE,MAAM,CAAC;IAClB,IAAI,EAAE,MAAM,CAAC;IACb,EAAE,EAAE,MAAM,CAAC;IACX,OAAO,EAAE,MAAM,CAAC;IAChB,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,KAAK,EAAE,MAAM,EAAE,CAAC;IAChB,GAAG,EAAE,MAAM,CAAC;CACb;AAED,MAAM,WAAW,kBAAkB;IACjC,KAAK,EAAE,MAAM,CAAC;IACd,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,KAAK,CAAC,EAAE,MAAM,CAAC;CAChB;AA4BD,qBAAa,YAAY;IACvB,OAAO,CAAC,MAAM,CAAc;IAC5B,OAAO,CAAC,WAAW,CAAuC;IAC1D,OAAO,CAAC,MAAM,CAAgC;IAC9C,OAAO,CAAC,OAAO,CAAS;gBAEZ,MAAM,EAAE,WAAW;IAI/B;;;OAGG;IACG,UAAU,IAAI,OAAO,CAAC,IAAI,CAAC;IA8B3B,QAAQ,IAAI,OAAO,CAAC,IAAI,CAAC;IAS/B,IAAI,SAAS,IAAI,OAAO,CAEvB;IAED;;;OAGG;IACH,IAAI,SAAS,IAAI,QAAQ,GAAG,MAAM,GAAG,IAAI,CAGxC;IAID;;;;;;;;;;;;;;;;;;;;;;;;OAwBG;IACG,SAAS,CAAC,OAAO,EAAE,gBAAgB,GAAG,OAAO,CAAC;QAAE,SAAS,EAAE,MAAM,CAAA;KAAE,CAAC;IAiDpE,SAAS,CAAC,MAAM,GAAE,MAAgB,EAAE,KAAK,GAAE,MAAW,GAAG,OAAO,CAAC,YAAY,EAAE,CAAC;IAgDtF;;;;OAIG;IACG,YAAY,CAAC,OAAO,EAAE,kBAAkB,GAAG,OAAO,CAAC,YAAY,EAAE,CAAC;IAoExE;;;;;;;OAOG;IACG,YAAY,CAAC,SAAS,EAAE,MAAM,EAAE,OAAO,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC;QAAE,KAAK,EAAE,MAAM,EAAE,CAAC;QAAC,SAAS,EAAE,MAAM,CAAA;KAAE,CAAC;IA+DxG;;;;;;;;;;;;;;;;;;;OAmBG;IACG,YAAY,CAChB,SAAS,EAAE,MAAM,EACjB,IAAI,EAAE,MAAM,EACZ,IAAI,CAAC,EAAE,MAAM,GACZ,OAAO,CAAC;QAAE,SAAS,EAAE,MAAM,CAAA;KAAE,CAAC;YAoEnB,aAAa;IAuB3B,OAAO,CAAC,gBAAgB;IAqCxB,OAAO,CAAC,eAAe;IA4BvB,OAAO,CAAC,qBAAqB;IAM7B,OAAO,CAAC,cAAc;CAGvB"}

package/dist/EmailService.js

@@ -47,6 +47,24 @@ const ResendTransport_js_1 = require("./ResendTransport.js");
 const messageHeaders_js_1 = require("./messageHeaders.js");
 const messageText_js_1 = require("./messageText.js");
 // ---------------------------------------------------------------------------
+// Helpers
+// ---------------------------------------------------------------------------
+/**
+ * The fields nodemailer writes in a form of its own whatever value it is given (its `FORMATTED_HEADERS`) and that
+ * `sendEmail` lets a caller add, in lowercase: `Sender`, an address nodemailer parses and writes again, and
+ * `References`, whose message ids nodemailer writes as they are once the check has passed them. Every other added
+ * field is given to nodemailer as a prepared value, which it writes as given, folded at its white space.
+ */
+const FORMATTED_BY_NODEMAILER = new Set(['sender', 'references']);
+/** A checked field as nodemailer's `headers` list takes it, so nodemailer writes the value Resend would be given. */
+function smtpField(key, value) {
+    return { key, value: FORMATTED_BY_NODEMAILER.has(key.toLowerCase()) ? value : { prepared: true, foldLines: true, value } };
+}
+/** The first address an envelope's list names, such as its Reply-To or its From, or `undefined`. */
+function firstAddress(list) {
+    return list?.find((entry) => typeof entry?.address === 'string' && entry.address !== '')?.address;
+}
+// ---------------------------------------------------------------------------
 // Service
 // ---------------------------------------------------------------------------
 class EmailService {
@@ -121,19 +139,24 @@ class EmailService {
      * `subject` and `body` must be strings, and `html` a string when it is given (`null` sends no HTML part, as
      * `undefined` does): any other value throws a `TypeError` naming the field, never its value, before either transport
      * is used. An object body would have nodemailer read the file its `path` names or fetch the address its `href` names
-     * into the message, and an object subject marked `prepared` would be written into the headers as it is.
+     * into the message, and an object subject marked `prepared` would be written into the headers as it is. The subject
+     * goes out on one line through either transport: each line break in it, and each other control character but the
+     * tab, is sent as a space, as nodemailer writes a line break in a subject.
      *
      * `headers` adds fields to the message and never replaces one the service writes. It must be a plain object of names
-     * and values: a name printable US-ASCII with no space or colon, given once in any case, and none of `From`, `To`,
-     * `Cc`, `Bcc`, `Reply-To`, `Subject`, `Date`, `Message-ID`, `MIME-Version` or a `Content-` field, in any case; a value
-     * a string with no line break or other control character than the tab. Anything else throws an `Error` that names the
-     * field, or its place when its name is at fault, and none of its value, before either transport is used. Each value is
-     * read once, and the fields are sent as read.
+     * and values, made in this realm or another: a name printable US-ASCII with no space or colon, given once in any case,
+     * and none of `From`, `To`, `Cc`, `Bcc`, `Reply-To`, `Subject`, `Date`, `Message-ID`, `MIME-Version` or a `Content-`
+     * field, in any case; a value a string of printable US-ASCII words, one space or tab between each two and none at
+     * either end, with no word so long that the name, a colon, a space and the word pass 998 characters, and for
+     * `In-Reply-To` and `References` message ids, each in angle brackets. Anything else throws an `Error` that names the
+     * field, or its place when its name is at fault, and none of its value, before either transport is used. Each value
+     * is read once, and both transports send the fields as read: nodemailer writes each value as given, folded at its
+     * white space, except `Sender`, which it writes as the address it parses from the value.
      */
     async sendEmail(options) {
         this.requireRunning();
         // Each is read once, so the value checked is the value sent.
-        const subject = (0, messageText_js_1.requireText)('subject', options.subject);
+        const subject = (0, messageText_js_1.oneLine)((0, messageText_js_1.requireText)('subject', options.subject));
         const body = (0, messageText_js_1.requireText)('body', options.body);
         const html = (0, messageText_js_1.optionalText)('html', options.html);
         const headers = (0, messageHeaders_js_1.requireAddedHeaders)(options.headers);
@@ -164,8 +187,8 @@ class EmailService {
             cc: options.cc,
             bcc: options.bcc,
             // A list, so nodemailer adds each field under its own name: an object with `key` and `value` properties would be
-            // read as one field named by its `key`.
-            headers: headers === undefined ? undefined : Object.entries(headers).map(([key, value]) => ({ key, value })),
+            // read as one field named by its `key`. Each value is prepared, so nodemailer writes it as Resend is given it.
+            headers: headers === undefined ? undefined : Object.entries(headers).map(([key, value]) => smtpField(key, value)),
             attachments: options.attachments?.map((a) => ({
                 filename: a.filename,
                 content: a.content,
@@ -219,6 +242,11 @@ class EmailService {
         }
     }
     // ── Search Emails ──
+    /**
+     * The messages of `folder` (INBOX unless given) whose subject, body or From holds `query`, ignoring case, received on
+     * or after `since` when it is given: the last `limit` (20 unless given) the search finds, newest first. The search
+     * answers UIDs, and the messages are fetched by those UIDs, which need not follow the messages' sequence numbers.
+     */
     async searchEmails(options) {
         this.requireRunning();
         const client = await this.getImapClient();
@@ -243,12 +271,13 @@ class EmailService {
                 const uidList = Array.isArray(uids) ? uids : [];
                 const limitedUids = uidList.slice(-(options.limit ?? 20));
                 if (limitedUids.length > 0) {
+                    // The search answered UIDs, so the fetch reads its range as UIDs rather than sequence numbers.
                     for await (const msg of client.fetch(limitedUids, {
                         envelope: true,
                         source: true,
                         flags: true,
                         uid: true,
-                    })) {
+                    }, { uid: true })) {
                         const envelope = msg.envelope;
                         const source = msg.source?.toString() ?? '';
                         const bodyText = this.extractPlainText(source);
@@ -275,53 +304,66 @@ class EmailService {
         }
     }
     // ── Extract Verification Codes ──
+    /**
+     * The codes in the INBOX message whose Message-ID is `messageId`, given with or without its angle brackets: the
+     * matches of `pattern` when it is given, else runs of four to eight digits, then the codes that phrases such as "code
+     * is", "OTP:", "is your" or "enter ... to" point to, each once. The message is searched for by the id in angle brackets
+     * and fetched by the UID the search answers; a search matches every Message-ID that holds the text, so only the
+     * message whose own id is the one given counts. An id that is not one message id, or that no message has, gives no
+     * codes.
+     */
     async extractCodes(messageId, pattern) {
         this.requireRunning();
+        const wanted = (0, messageHeaders_js_1.oneMessageId)(messageId);
+        if (wanted === undefined)
+            return { codes: [], messageId };
         const client = await this.getImapClient();
         try {
             const lock = await client.getMailboxLock('INBOX');
+            let source;
             try {
-                // Search for the specific message
-                const uids = await client.search({ header: { 'message-id': messageId } }, { uid: true });
+                const uids = await client.search({ header: { 'message-id': wanted } }, { uid: true });
                 const uidList = Array.isArray(uids) ? uids : [];
-                if (uidList.length === 0) {
-                    return { codes: [], messageId };
-                }
-                for await (const msg of client.fetch(uidList, { source: true })) {
-                    const source = msg.source?.toString() ?? '';
-                    const bodyText = this.extractPlainText(source);
-                    const htmlBody = this.extractHtmlBody(source);
-                    const fullText = bodyText + ' ' + htmlBody;
-                    // Apply custom or default code extraction patterns
-                    const regex = pattern
-                        ? new RegExp(pattern, 'g')
-                        : /\b(\d{4,8})\b/g;
-                    const codes = [];
-                    let match;
-                    while ((match = regex.exec(fullText)) !== null) {
-                        codes.push(match[1] ?? match[0]);
-                    }
-                    // Also look for common verification code patterns
-                    const verifyPatterns = [
-                        /(?:code|verification|OTP|pin)\s*(?:is|:)\s*(\w{4,8})/gi,
-                        /(\d{6})\s*(?:is your|to verify)/gi,
-                        /(?:enter|use)\s+(\w{4,8})\s+(?:to|as|for)/gi,
-                    ];
-                    for (const vp of verifyPatterns) {
-                        while ((match = vp.exec(fullText)) !== null) {
-                            const code = match[1];
-                            if (code && !codes.includes(code)) {
-                                codes.push(code);
-                            }
-                        }
+                if (uidList.length > 0) {
+                    // The loop reads every message fetched and keeps the first whose own id is the one given.
+                    for await (const msg of client.fetch(uidList, { envelope: true, source: true }, { uid: true })) {
+                        if (source === undefined && (0, messageHeaders_js_1.messageIdIn)(msg.envelope?.messageId) === wanted)
+                            source = msg.source?.toString() ?? '';
                     }
-                    return { codes: [...new Set(codes)], messageId };
                 }
             }
             finally {
                 lock.release();
             }
-            return { codes: [], messageId };
+            if (source === undefined)
+                return { codes: [], messageId };
+            const bodyText = this.extractPlainText(source);
+            const htmlBody = this.extractHtmlBody(source);
+            const fullText = bodyText + ' ' + htmlBody;
+            // Apply custom or default code extraction patterns
+            const regex = pattern
+                ? new RegExp(pattern, 'g')
+                : /\b(\d{4,8})\b/g;
+            const codes = [];
+            let match;
+            while ((match = regex.exec(fullText)) !== null) {
+                codes.push(match[1] ?? match[0]);
+            }
+            // Also look for common verification code patterns
+            const verifyPatterns = [
+                /(?:code|verification|OTP|pin)\s*(?:is|:)\s*(\w{4,8})/gi,
+                /(\d{6})\s*(?:is your|to verify)/gi,
+                /(?:enter|use)\s+(\w{4,8})\s+(?:to|as|for)/gi,
+            ];
+            for (const vp of verifyPatterns) {
+                while ((match = vp.exec(fullText)) !== null) {
+                    const code = match[1];
+                    if (code && !codes.includes(code)) {
+                        codes.push(code);
+                    }
+                }
+            }
+            return { codes: [...new Set(codes)], messageId };
         }
         finally {
             await client.logout();
@@ -329,12 +371,24 @@ class EmailService {
     }
     // ── Reply to Email ──
     /**
-     * Replies to the message whose Message-ID is `messageId`, reading its sender, subject and References through IMAP,
-     * and sends `body` with `html`, when given, through the transport that sends, threaded with `In-Reply-To` and
-     * `References`. `messageId` and `body` must be strings, and `html` a string when it is given (`null` sends no HTML
-     * part): any other value throws a `TypeError` naming the field, never its value, before the original is read or
-     * anything is sent. Besides the bodies' files and addresses (see `sendEmail`), an object message id marked `prepared`
-     * would be written into the `In-Reply-To` header as it is.
+     * Replies to the INBOX message whose Message-ID is `messageId`, given with or without its angle brackets, and sends
+     * `body` with `html`, when given, through the transport that sends. The original is searched for by the id in angle
+     * brackets and fetched by the UID the search answers; a search matches every Message-ID that holds the text, so the
+     * original is the message whose own id is the one given. The reply goes to the original's Reply-To, or its From when
+     * it names none (RFC 5322 section 3.6.2), under its subject with one `Re: ` before it unless it starts with one in any
+     * case, on one line. It is threaded as RFC 5322 section 3.6.4 has it: `In-Reply-To` names the original, and
+     * `References` lists the ids of the original's own References, or the one id of its In-Reply-To when its References
+     * lists none, then the original's id. Only fields of those very names are read, each whole however it is folded, and
+     * an id in them that holds a character outside printable US-ASCII, or that is too long for one line, is left out, so
+     * both transports send the same fields whatever the original holds.
+     *
+     * `messageId` and `body` must be strings, and `html` a string when it is given (`null` sends no HTML part): any other
+     * value throws a `TypeError` naming the field, never its value, before the original is read or anything is sent.
+     * Besides the bodies' files and addresses (see `sendEmail`), an object message id marked `prepared` would be written
+     * into the `In-Reply-To` header as it is. A message id that is not one id of printable US-ASCII with no space, or that
+     * is too long for one line of `In-Reply-To`, throws an `Error` before the original is read; no message with that id,
+     * or an original that names no address to reply to, throws an `Error` before anything is sent. None of these errors
+     * holds the id.
      */
     async replyToEmail(messageId, body, html) {
         this.requireRunning();
@@ -343,23 +397,26 @@ class EmailService {
         (0, messageText_js_1.requireText)('messageId', messageId);
         (0, messageText_js_1.requireText)('body', body);
         html = (0, messageText_js_1.optionalText)('html', html);
-        // Fetch the original message to get reply headers
+        // The original's id as In-Reply-To and the end of References carry it, through either transport.
+        const parent = (0, messageHeaders_js_1.requireMessageId)(messageId);
         const client = await this.getImapClient();
-        let originalFrom = '';
-        let originalSubject = '';
-        let previous = '';
+        let original;
         try {
             const lock = await client.getMailboxLock('INBOX');
             try {
-                const uids = await client.search({ header: { 'message-id': messageId } }, { uid: true });
+                const uids = await client.search({ header: { 'message-id': parent } }, { uid: true });
                 const uidList = Array.isArray(uids) ? uids : [];
                 if (uidList.length > 0) {
-                    for await (const msg of client.fetch(uidList, { envelope: true, headers: true })) {
-                        originalFrom = msg.envelope?.from?.[0]?.address ?? '';
-                        originalSubject = msg.envelope?.subject ?? '';
-                        const headersStr = msg.headers?.toString() ?? '';
-                        const refsMatch = headersStr.match(/References:\s*(.+)/i);
-                        previous = refsMatch ? refsMatch[1].trim() : '';
+                    // The loop reads every message fetched and keeps the first whose own id is the one given.
+                    for await (const msg of client.fetch(uidList, { envelope: true, headers: true }, { uid: true })) {
+                        if (original !== undefined || (0, messageHeaders_js_1.messageIdIn)(msg.envelope?.messageId) !== parent)
+                            continue;
+                        original = {
+                            // A server gives the From as the Reply-To of a message that names none (RFC 3501 section 7.4.2).
+                            to: firstAddress(msg.envelope?.replyTo) ?? firstAddress(msg.envelope?.from) ?? '',
+                            subject: (0, messageText_js_1.oneLine)(msg.envelope?.subject ?? ''),
+                            thread: (0, messageHeaders_js_1.threadOf)(msg.headers?.toString() ?? ''),
+                        };
                     }
                 }
             }
@@ -370,25 +427,31 @@ class EmailService {
         finally {
             await client.logout();
         }
-        const replySubject = originalSubject.startsWith('Re:') ? originalSubject : `Re: ${originalSubject}`;
-        const references = previous ? `${previous} ${messageId}` : messageId;
+        if (original === undefined)
+            throw new Error('The reply was refused: no message in the inbox has that message id');
+        if (original.to === '')
+            throw new Error('The reply was refused: the message names no address to reply to');
+        const replySubject = /^re:/i.test(original.subject) ? original.subject : `Re: ${original.subject}`;
+        const references = [...original.thread, parent].join(' ');
+        // Checked by the rules every added field meets, so both transports are given the same fields.
+        const thread = (0, messageHeaders_js_1.requireHeaders)({ 'In-Reply-To': parent, References: references });
         if (this.resend) {
             return this.resend.send({
                 from: this.config.from,
-                to: originalFrom,
+                to: original.to,
                 subject: replySubject,
                 text: body,
                 html,
-                headers: { 'In-Reply-To': messageId, References: references },
+                headers: thread,
             });
         }
         const info = await this.transporter.sendMail({
             from: this.config.from ?? this.config.smtp.user,
-            to: originalFrom,
+            to: original.to,
             subject: replySubject,
             text: body,
             html,
-            inReplyTo: messageId,
+            inReplyTo: parent,
             references,
         });
         return { messageId: info.messageId };