Re: [nmh-workers] Killing Content-MD5 support

2018-07-01 Thread Ken Hornstein
>> - Currently we only calculate it correctly if your CTE is quoted-printable
>>   (we may calculate it correctly for some other content types, but that
>>   is debatable).
>
>With -check, CTE is promoted to either quoted-printable (for text)
>or base64 (for application, except a special case of q-p for Postscript).

Whoops, I missed that; fair enough!

>> I propose it be removed and for the next release the -check/-nocheck
>> flags are turned into NOPs and removed some point later.
>
>Fine with me.  Should we consider not making them strict NOPs, but having
>them print out a warning?  That would encourage users to remove those
>switches from their profiles.

Nah, I know Ralph reads the mailing list :-)

--Ken

-- 
nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers


Re: [nmh-workers] Killing Content-MD5 support

2018-07-01 Thread David Levine
Ken wrote:

> - Currently we only calculate it correctly if your CTE is quoted-printable
>   (we may calculate it correctly for some other content types, but that
>   is debatable).

With -check, CTE is promoted to either quoted-printable (for text)
or base64 (for application, except a special case of q-p for Postscript).

> I propose it be removed and for the next release the -check/-nocheck
> flags are turned into NOPs and removed some point later.

Fine with me.  Should we consider not making them strict NOPs, but having
them print out a warning?  That would encourage users to remove those
switches from their profiles.

David

-- 
nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers