using a key without self-signature

[Calum Selkirk]

--FkmkrVfFsRoUs1wW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

* David T-G [davidtg-gnupg@justpickone.org] [2002-05-15 11:12 -0500]:

> > On Wed, May 15, 2002 at 05:27:31PM +0200, Jeroen Valcke wrote:
> >
> > The new way is to leave headers alone and use mutt's
> > check-traditional-pgp function, which can detect PGP messages at
> > run-time, and adjust content-types.
>
> Right.  Folks used to use procmail to tweak the headers, but that isn't
> infallible.

David pretty much covers the mutt specific aspects of this problem.
Basically mutt isn't seeing these messages as signed/encrypted etc
is due to the content headers. My ~/.procmailrc reads:

## Convert old-style PGP messages to MIME

:0
* !^Content-Type: message/
* !^Content-Type: multipart/
* !^Content-Type: application/pgp
{
    :0 fBw
    * ^-----BEGIN PGP MESSAGE-----
    * ^-----END PGP MESSAGE-----
    | formail -i "Content-Type: application/pgp; format=3Dtext; x-action=encrypt"

    :0 fBw
    * ^-----BEGIN PGP SIGNED MESSAGE-----
    * ^-----BEGIN PGP SIGNATURE-----
    * ^-----END PGP SIGNATURE-----
    | formail -i "Content-Type: application/pgp; format=3Dtext; x-action=sign"
}

:0 fBw
* ^-----BEGIN PGP PUBLIC KEY BLOCK-----
* ^-----END PGP PUBLIC KEY BLOCK-----
| formail -i "Content-type: application/pgp; format=3Dtext; "

As David points out mutt can be patched to create_pgp_traditional (using
David's mutt patch coctail is one soluton). You would then be able to add a
message-hook to set mutt to send traditional/inline signed/encrypted messages
to outlook-user@address.org or ~h "^X-Mailer: Microsoft Outlook Express".
Again this is covered in detail in the mutt-users list archive:

<http://marc.theaimsgroup.com/?l=3Dmutt-users&r=3D1&w=3D2>

HTH

cal


--FkmkrVfFsRoUs1wW
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE847EmCnVTDMCvVYgRAp7HAJ4kh8cRKEodmtbBEJZ3egO2WSNmOACfbpCM
fRfVjhsyLv6LDPU/iAgCHwY=
=rSmt
-----END PGP SIGNATURE-----

--FkmkrVfFsRoUs1wW--