@bumail/smtp 0.10.0 → 0.11.0

package/docs/troubleshooting.md

@@ -1157,7 +1157,8 @@ a token`; `orcpt.address of <address> must be a non-empty string`; `orcpt of
 <address> is over 500 characters once encoded`.
 
 **Why**: RFC 3461 §4.4 and §4.2 cap the parameters as sent, so a character that
-xtext writes as `+XX` counts three.
+xtext writes as `+XX` counts three (for a `utf-8` `orcpt`, the unitext form:
+raw UTF-8 octets, `\x{HH}` = 6; for another type, the type, the `;` and the xtext form).
 
 **Fix**: shorten the value, or give the type as letters, digits and hyphens.
 
@@ -1171,18 +1172,24 @@ await sendMail(message, { host, from, to, envid: 'q-1042' }); // not 'q 1042 …
 than `FULL` or `HDRS`; `ENVID` empty, longer than 100 characters as sent,
 not printable ASCII or not xtext; `NOTIFY` mixing `NEVER` with another
 event, naming an event twice or an unknown one; `ORCPT` with no
-`addr-type;` prefix, an address that is not xtext, or more than 500
-characters as sent (RFC 3461 §4.2).
+`addr-type;` prefix, an address that does not decode (not xtext for
+`rfc822`; for `utf-8`, RFC 6533's `\x{HEX}` form, with raw UTF-8 only when
+the transaction used `SMTPUTF8`), or more than 500 characters as sent (RFC
+3461 §4.2).
 
 **Why**: RFC 3461 §4. The server refuses the command rather than hand a
 wrong value to `onData`.
 
 **Fix**, as a client: encode the value as xtext (`+` and `=`, spaces and
-non-ASCII bytes as `+XX`), and send `NOTIFY=NEVER` alone.
+non-ASCII bytes as `+XX`), and send `NOTIFY=NEVER` alone. For
+`ORCPT=utf-8;` use RFC 6533 instead: `\x{E9}` for `é`, and `\x{2B}` for `+`
+(not `+2B`), or raw UTF-8 after `MAIL FROM … SMTPUTF8`.
 
 ```text
 C: RCPT TO:<bob@example.com> NOTIFY=SUCCESS,FAILURE ORCPT=rfc822;bob+2Btag@example.com
 S: 250 2.1.5 OK
+C: RCPT TO:<bob@example.com> ORCPT=utf-8;\x{E9}l\x{E8}ve@example.com
+S: 250 2.1.5 OK
 ```
 
 ### `501 5.5.4 … given twice`

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@bumail/smtp",
-	"version": "0.10.0",
+	"version": "0.11.0",
 	"description": "An SMTP server on Bun.listen — RFC 5321 with PIPELINING, SIZE, 8BITMIME, SMTPUTF8, STARTTLS and AUTH after TLS, policy hooks, and no open relay — and a client that delivers a message to a smarthost or by MX",
 	"license": "MIT",
 	"type": "module",