On Thu, 16 May 2019 20:56:28 -0400, Ken Hornstein said: > It occur to me that this might still be useful, but making this switch > on a component is obviously wrong, and it should really be a function > escape. So I propose we switch all of the default scan formats from > using %{encrypted} to a yet-to-be-written function escape %(encrypted). > Since we don't really support encrypted email yet, this would always > return false for now, but this would be a much better solution for future > support rather than relying on a nonexistent header.
Probably need to be a bit more ambitious than that, and MIME-compliant. What I have in my own scan file: %(void{content-type})\ %<(match text/plain) \ %?(match text/html)H\ %?(match multipart/signed)S\ %?(match multipart/encrypted)E\ %|%<{content-type}M%|?%>%> \ although now that the vast majority of stuff is multipart/alternative with a text/plain and text/html, retiring the M may make sense. I'm amazed at how often I still see an 'H' or a '?' though. :)
pgpONYhqhoXYG.pgp
Description: PGP signature
-- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers