application/pgp - in-line possible?

[3rd time's a charm.  %-/   That attachment might as well have
been mad of Teflon; it stuck about like it.  Sorry folks.]

I'm having trouble getting an application/pgp message to display
in-line.  I'm attaching the message I'm having trouble with.
When viewing the message I see

    This is a application/pgp
    It can be displayed with "gpg < /home/kevinc/.tmp/0.0=1.19155.exmh | metamail".	(Invoke menu with
right button.)
	charset = us-ascii
	x-action = pgp-signed
	disposition = inline
	format = text

Indeed, I get a pop-up window that shows the text when I do what's
recommended above.  I'd just prefer to see this in-line in the 
message.

FWIW, for encrypted messages, I get

    This is a text/x-pgp
    It might be displayable with metamail.	(Invoke menu with right button.)
    This is a GnuPG signed and encrypted message
     Decrypt and verify with GnuPG 
    This is a application/pgp
    It might be displayable with metamail.	(Invoke menu with right button.)
	x-action = encryptsign
	x-originator = D165C0CC
	x-recipients="D165C0CC, D165C0CC"
	format = text

Where "Decrypt and verify with GnuPG" is highlighted and clickable, 
and clicking will bring up a passphrase window.  After entering my 
passphrase, the message is decrypted in-line.

Thanks...

Hello!

The latest release from the development branch of GnuPG is ready for
public consumption.  This is a branch to create what will be GnuPG 1.4
someday.  It will change much more frequently than the 1.2.x "stable"
branch, which will mainly be updated for bug fix reasons.

The more GnuPG-familiar user is encouraged try this release (and the
ones that will follow in the 1.3.x branch), and report back any
problems to gnupg-devel <at> gnupg.org.  In return, you get the latest code
with the latest features.  However, it is always important to keep in
mind that this is still development code - please do not use it on
anything mission-critical.  Critical applications should always use
the 1.2.x stable branch.

You may notice the smaller tarball size for these development
releases.  This is due to the translations other than de being
removed.  You may also notice the smaller size of the compiled gpg
binary, and that is due to some of the keyserver modifications.  See
the list below for more changes.

The files are available from:

  ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-1.3.1.tar.gz       (1506k)
  ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-1.3.1.tar.gz.sig
  ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-1.3.0-1.3.1.diff.gz (167k)

MD5 checksums for the files are:

  bbfd0613a3309e10b2d8b9d7d08bbe8a  gnupg-1.3.1.tar.gz.sig
  eaf6fd07ca5088c3f1589c20718b81d7  gnupg-1.3.1.tar.gz
  55ef3ce7ae7532e5f377ea963b33d20e  gnupg-1.3.0-1.3.1.diff.gz

Noteworthy changes in version 1.3.1 (2002-11-12)
------------------------------------------------

    * Trust signature support.  This is based on the Maurer trust
      model where a user can specify the trust level along with the
      signature with multiple levels so users can delegate
      certification ability to other users, possibly restricted by a
      regular expression on the user ID.  Note that full trust
      signature support requires a regular expression parsing library.
      The regexp code from glibc 2.3.1 is included for those platforms
      that don't have working regexp functions available.  The
      configure option --disable-regex may be used to disable any
      regular expression code, which will make GnuPG ignore any trust
      signature with a regular expression included.

    * Two new commands --hidden-recipient (-R) and --hidden-encrypt-to
      encrypt to a user, but hide the identity of that user.  This is
      the same functionality as --throw-keyid, but can be used on a
      per-user basis.

    * Full algorithm names (e.g. "3DES", "SHA1", "ZIP") can now be
      used interchangeably with the short algorithm names (e.g. "S2",
      "H2", "Z1") anywhere algorithm names are used in GnuPG.

Happy Hacking,

  The GnuPG team (David, Stefan, Timo and Werner)