Hi,
mhbuild(1)'s `-check' adds a `Content-MD5' header to each part.
Consider it's run by whatnow(1) due to `mime', and that's followed by an
`edit', allowing the user to actually edit what's covered by the digest.
I think the addition of `Content-MD5' should be in the outgoing pipeline
once the c
Ralph wrote:
> mhbuild(1)'s `-check' adds a `Content-MD5' header to each part.
> Consider it's run by whatnow(1) due to `mime', and that's followed by an
> `edit', allowing the user to actually edit what's covered by the digest.
I agree with Ken's comments here:
https://lists.gnu.org/archive/htm
>mhbuild(1)'s `-check' adds a `Content-MD5' header to each part.
>Consider it's run by whatnow(1) due to `mime', and that's followed by an
>`edit', allowing the user to actually edit what's covered by the digest.
>
>I think the addition of `Content-MD5' should be in the outgoing pipeline
>once the
>Honestly, if I ever get around to doing a rewrite of the MIME handling
>I'm certainly wasn't planning on keeping support for it so we should
>really decide if Content-MD5 is something we want to invest time and
>energy into.
Obviously I'm not a fan of Content-MD5, but I took a look at our
impleme
