On Sat, 28 Sep 2019 21:24:00 -0400, Ken Hornstein writes:
Oh, there is one additional bit of tooling I think is necessary: being able to specify the "raw" contents of a multipart part when CREATING a message.
yes.
# This is a hypothetical syntax for including "pre-formed" multipart content
echo '#!<' >> /tmp/newdraft.$$
cat /tmp/body.$$ >> /tmp/newdraft.$$
echo "#application/pkcs7-signature; name=smime.p7s {attachment;
filename=smime.p7s} /tmp/signdata.$$" >> /tmp/newdraft.$$
echo "#end" >> /tmp/newdraft.$$
i think telling mhbuild to ignore directives for pre-formed stuff will need need both 'start verbatim here' and 'stop verbatim here' markers, or you won't be able to attach the crypto signature or end the outermost multipart... maybe something like shell here document delimiters?
Does that make sense?
thanks, yes, that clarifies things.
What you would do with PGP/GPG is pretty close to that, I think.
the mime types are different but that's pretty much it. (i feel confident claiming that because i wrote an outgoing automatic signer-or-encrypter for pgp/mime a while ago; see http://snafu.priv.at/mystuff/kuvert/ for details) regards az -- Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + http://snafu.priv.at/ Commercial televsion is like deliberately sticking hat pins through your frontal lobes most of the time. -- Rebecca Ore
signature.asc
Description: Digital Signature
-- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers