On 8/3/2018 10:30 AM, Brandon Long wrote:
I remember code which strips all of the Content-* foo headers for a part
when modifying that part. I assume that's generally fine if everything
is being messed with.
My interest was in preservation of unknown content-* fields when the
body-part is being tranfered (relayed or whatever).
If the content itself is being messed with, I'd assume all bets are off
for its associated meta-data in content-* fields, since really the
body-part will now be a different object...
Our s/mime code also does specially handling of all content-* headers
when signing/encrypting, so a "new" one is safe there as well.
thanks!
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp