It appears that Alessandro Vesely <[email protected]> said: >On Mon 20/May/2024 20:10:44 +0200 John Levine wrote: >> It appears that Jeremy Harris <[email protected]> said: >>>On 20/05/2024 09:06, Alessandro Vesely wrote: >>>> Content-Type: is a technical field >>> >>>Not a term I've met before. Is there a formal definition? >> >> As Dave said, no. There isn't even an informal definition. > >Informally, I think it's quite straightforward to distinguish between >technical >versus semantic fields.
I still have no idea what headers you'd consider to be technical. Message-ID? Expires? (Don't tell me, it's not helpful.) >I'd be curious to learn why. A mailing list might change it from > > Content-type: text/plain; charset=utf-8 >to > Content-Type: text/plain; charset="utf-8" I have trouble imagining that many mailing lists would make that change and only that change and would otherwise leave the messasge untouched. In any event, as we've now said several times, the Content-Type attack is specifically described in RFC 6376. I see that the perl and python DKIM modules sign the content-* headers by default. R's, John _______________________________________________ Ietf-dkim mailing list -- [email protected] To unsubscribe send an email to [email protected]
