> A problem with including a public key with every plaintext message is that
> it isn't very discreet - actually looks kind of ugly in some peoples's
> email clients.
You could use a separate PGP/MIME bodypart...
> Come to think of it, there are some tricky issues with regards to crypto
> on mailing lists, it might make sense to have a
> X-crypto-originator [EMAIL PROTECTED] line in the headers to specify that the
> crypto information contained in that piece of mail applies to the address
> [EMAIL PROTECTED] - otherwise there's no clear way of unraveling all the
> possible mixes of from, to, and reply-to headers which could possibly be
> sent to a mailing list.
The recipient would probably ignore the mail headers and use the userID(s)
in the public key certificate included in the message.
Ian :0)
