Re: pgg doesn't seem to like me

[jam@jamux.com (John A. Martin)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>>>> "Josh" == Josh Huber
>>>>> "Re: pgg doesn't seem to like me"
>>>>>  Tue, 01 Oct 2002 15:16:11 -0400

    Josh> jam@jamux.com (John A. Martin) writes:
    >> ISTM somewhat surprising that the default PGP/Mime (sign and)
    >> encrypt should be to sign and then encrypt rather than to sign
    >> and encrypt in one operation something like 'gpg -se' and
    >> whatever.

    Josh> You can adjust this using mml-signencrypt-style:

    Josh> (mml-signencrypt-style "pgpmime" 'combined)

Ok, did the above.  Decryption failed as before.

Running the mail through gpg on the command line gives

- -------------- cut here ---->8 ---< head
$ gpg --decrypt ~/Mail/t-test/43

You need a passphrase to unlock the secret key for
user: "John A. Martin <jam@jamux.com>"
1024-bit ELG-E key, ID 4FC125AD, created 1998-09-19 (main key ID BFE25F2F)

gpg: encrypted with 1024-bit ELG-E key, ID 4FC125AD, created 1998-09-19
      "John A. Martin <jam@jamux.com>"
Content-Transfer-Encoding: quoted-printable


=2D-=20
GNU GPL: "The Source shall be with you... always."
- ---- 8<------- cut here ----------> tail

while signing and encrypting at the command line and then decrypting
looks like this

- -------------- cut here ---->8 ---< head
$ gpg -seatr jam@jamux.com </dev/null|gpg>/dev/null

You need a passphrase to unlock the secret key for
user: "John A. Martin <jam@jamux.com>"
1024-bit DSA key, ID BFE25F2F, created 1998-09-19

gpg: jam@jamux.com: skipped: public key already present

You need a passphrase to unlock the secret key for
user: "John A. Martin <jam@jamux.com>"
1024-bit ELG-E key, ID 4FC125AD, created 1998-09-19 (main key ID BFE25F2F)

gpg: encrypted with 1024-bit ELG-E key, ID 4FC125AD, created 1998-09-19
      "John A. Martin <jam@jamux.com>"
gpg: Signature made Tue Oct  1 16:01:14 2002 EDT using DSA key ID BFE25F2F
gpg: Good signature from "John A. Martin <jam@jamux.com>"
gpg:                 aka "John A. Martin <jam@acm.org>"
- ---- 8<------- cut here ----------> tail

One wonders whether there is a trusted signature on the stuff in the
first example above which was encrypted with

        (("smime" separate) ("pgp" separate) ("pgpmime" combined))

    jam

-----BEGIN PGP SIGNATURE-----

iD8DBQE9mgFQUEvv1b/iXy8RAqRRAJwPC1PimMmbgCWCIVqdXGrgjnjvXACeP540
VIjekvADuyCARS/AKgZXxgI=
=5cJm
-----END PGP SIGNATURE-----