Re: Content-MD5 header and gateways

I would prefer not to make either Harald's change or your change for two
reasons: first, it changes the philosophy of the document which is that
Content-MD5: is an end-to-end thing; second, it reduces the simplicity
of the document.  Content-MD5: is advisory, if you really care about
integrity, etc., then you should probably be using PEM with MIME and
use the MIME/X.400 mapping document to preserve the semantics.

/mtr