On Fri, Apr 19, 2024 at 09:05:23AM -0700, Will Yardley wrote: > It's odd to me that, since OpenPGP and S/MIME both support MIME > encapsulation that the draft standard wouldn't use a separate MIME part > to handle the protected headers vs. stuffing it at the top of the > message body, which just seems kind of kludgy at best.
This also seems like a perfectly cromulent approach, and again better than the proposed one which puts nonstandard headers in a place where no standard says they can be. [Or perhaps the correct wording would be, "...which nonstandardly puts standard headers in a place where no standard says they should be."] MIME header blocks are for MIME-specific metadata; even if no mail clients actually break due to this, it still feels gross. Yes, the MIME spec says other fields can appear there and should be ignored (so long as they don't start with "content-") but having standard message headers in multiple places unexpectedly still runs the risk that insufficiently carefully implemented clients will get confused. -- Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience.
signature.asc
Description: PGP signature
