Found in a UI pass against Stalwart 1.0: opening any message failed with Email/get: invalidArguments - Invalid property ... List-Unsubscribe ... form: Text.
List-Unsubscribe is an RFC 2369 header, and RFC 8621 4.1.2.3 allows asText only for headers outside RFC 5322 and RFC 2369. Stalwart 0.16 answered it anyway; 1.0 refuses the whole call. header:List-Unsubscribe:asURLs returns the list the reader was extracting by regex, and gives the same result on 0.16.27 and 1.0.0.
Of the 17 header properties ihasmail names, 1.0 refuses three: this one, plus Return-Path:asText and Received:asText:all, which were only typings and never requested. Those are dropped.
Checked: typecheck, 1549 web + 257 server tests, build; on a local Stalwart 1.0 with 10,000 migrated messages, threads open, attachments list, send delivers.
Found in a UI pass against Stalwart 1.0: opening any message failed with `Email/get: invalidArguments - Invalid property ... List-Unsubscribe ... form: Text`.
List-Unsubscribe is an RFC 2369 header, and RFC 8621 4.1.2.3 allows `asText` only for headers outside RFC 5322 and RFC 2369. Stalwart 0.16 answered it anyway; 1.0 refuses the whole call. `header:List-Unsubscribe:asURLs` returns the list the reader was extracting by regex, and gives the same result on 0.16.27 and 1.0.0.
Of the 17 header properties ihasmail names, 1.0 refuses three: this one, plus `Return-Path:asText` and `Received:asText:all`, which were only typings and never requested. Those are dropped.
Checked: typecheck, 1549 web + 257 server tests, build; on a local Stalwart 1.0 with 10,000 migrated messages, threads open, attachments list, send delivers.
List-Unsubscribe is an RFC 2369 header, and RFC 8621 4.1.2.3 allows the
Text form only for headers outside RFC 5322 and RFC 2369. Stalwart 0.16
answered it anyway; Stalwart 1.0 refuses the whole Email/get with
invalidArguments, so no message could be opened. asURLs returns the list the
reader was extracting by hand, on both versions.
Also drops the unused Return-Path and Received asText typings, which 1.0
refuses for the same reason.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found in a UI pass against Stalwart 1.0: opening any message failed with
Email/get: invalidArguments - Invalid property ... List-Unsubscribe ... form: Text.List-Unsubscribe is an RFC 2369 header, and RFC 8621 4.1.2.3 allows
asTextonly for headers outside RFC 5322 and RFC 2369. Stalwart 0.16 answered it anyway; 1.0 refuses the whole call.header:List-Unsubscribe:asURLsreturns the list the reader was extracting by regex, and gives the same result on 0.16.27 and 1.0.0.Of the 17 header properties ihasmail names, 1.0 refuses three: this one, plus
Return-Path:asTextandReceived:asText:all, which were only typings and never requested. Those are dropped.Checked: typecheck, 1549 web + 257 server tests, build; on a local Stalwart 1.0 with 10,000 migrated messages, threads open, attachments list, send delivers.