Re: [Evolution] Sending of GPG-encrypted mail.

[Jeffrey Stedfast <fejj ximian com>]

This has been reported a few times and I have yet to figure out the
problem. I've emailed Werner Koch (of gpg fame) and asked if the
command-line Evolution is sending to encrypt a message is correct, and
he replied that it was indeed correct so I'm not sure what the problem
is.

You can check the command-line yourself in
camel/camel-pgp-context.c::pgp_encrypt() (by sticking a printf or
something in there), but it should be:

gpg --verbose --yes --batch --armor -r r1 -r r2 ... -r rn --output -
--encrypt

if you turn on "encrypt to self", then r1 is your key and r2 is your
first recipient, otherwise r1 is your first recipient on down the line.

Jeff

On Tue, 2001-08-28 at 22:36, Chris Ball wrote:
> Hi,
>
> Apologies if this is somehow redundant, or more related to gpg than
> evolution. As I can encrypt mail directly with gpg and pipe it to mail,
> I think I'm right in asking here. But we'll see. :)
>
> I have no problem receiving encrypted e-mail with evolution, but sending
> it seems to result in the mail being transparently encrypted with /my/
> private key rather than the public key of the recipient. I've tried with
> more than one recipient, and in both cases their key was aleady imported
> into my keyring as well as available on a defined nameserver. The
> recipient receives the following error from gpg:
>
> gpg: encrypted with ELG-E key, I'D 9C76F617 # my private key.
> gpg: decryption failed: secret key not available
> gpg: [don't know]: invalid packet (ctb=7c)
>
> Any ideas on how to get Evolution to handle encrypting with an external
> public key?
>
> ~C.