Re: Crypto-MIME in GNUS

[Simon Josefsson <simon@josefsson.org>]

"Georg C. F. Greve" <greve@gnu.org> writes:

> The biggest problem was that the gnus crypto function didn't work
> since it gave mailcrypt the buffer to encrypt that didn't contain
> headers so mailcrypt had no way to determine who to encrypt it
> for.

Weird, this is definitely not the case for me.  Could you tell why
`message-options-set-recipient' function fail to figure out
recipients?  Or if there's some problem in mml2015 when mailcrypt is
given the information snarfed from the *mail* buffer?

> Also when I got it to work half-way I realized that CC and BCC
> were ignored.

Right, `message-options-set-recipient' only look at the To: header.

> Also I wanted a nice way to determine whether to encrypt or sign that
> I could toggle while composing the mail.

Hm, `C-c RET s p' or `C-c RET c p'?

> What is also nice is an easy way to include public keys into the mail
> with correct MIME type. The solution I have is ugly but I didn't have
> time to think about something better and for now it works.

Ah, this is really useful.  Is there a MIME type for pgp public keys?
Cool.  I'm still using the mailcrypt default bindings which gets me a
nice menu where I can choice to insert my public key as a block.