> No. What you'd want to do is to rename modified header field into some > sort of trace data and copy the original data in its place. Displaying > modification would then be up to the MUA which could display small > icon allowing user to see what the modification was as an option.
That's one approach, but hardly the only possible one. Most of the users I know would find it completely baffling if their mail program showed them multiple versions of headers and asked whether they liked them. > For most cases original value would be just fine ... Can you describe the algorithm to distinguish the cases where the original value is fine from the cases where it's not? I hope we agree that we do not want to spec a verification system that uses heuristics that vary from one implementation to another. Regards, John Levine, [EMAIL PROTECTED], Primary Perpetrator of "The Internet for Dummies", Information Superhighwayman wanna-be, http://www.johnlevine.com, Mayor "A book is a sneeze." - E.B. White, on the writing of Charlotte's Web _______________________________________________ NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html
