Sorry.... my earlier statement: It looks like the problem is that gpg 1.20 is not setting "force-v3-sigs" when --pgp2 is specifed. If "force-v3-sigs" is specified, the example shown below works fine. ...seems to be false. gpg issues a warning message about not being able to encrypt/sign at the same time in --pgp2 mode, and the resulting file cannot be used by pgp. Apologies for the confusion....