[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Mutt and inline gpg



On Thu, 09 Aug 2001, Marc Leeman <Marc.Leeman@esat.kuleuven.ac.be> wrote...

: kmail sends the gpg messages inline, and upon arrival decodes them
: immediately. In my config, mutt sends them as attachments.
: When I get a kmail message, I have to save it to file and manually
: decode it (not that difficult, but annoying). Mutt doesn't recognise
: the inline format of kmail.
: When my friends (2 differnt ones, one of which is planning to switch
: to mutt) get the mails, they get it in an attachment, have to save it
: and decode it manually (apparently kmail is expecting inline messages).
: Obviously, mutt/mutt and kmail/kmail messages are working perfectly.
`-

I've seen a few procmail recipes around which remedy this.


# Convert old-style PGP messages to MIME
:0
* !^Content-Type: multipart/
* !^Content-Type: application/pgp
{
    :0 fBw
        * ^-----BEGIN PGP MESSAGE-----
        * ^-----END PGP MESSAGE-----
        | formail -i "Content-Type: application/pgp; format=text; x-action=encrypt"

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


I cant take credit for this, its part of a procmail file I've put together
from multiple sources.


[----------------------------------------------------------------------]
  Matt 'Dopey' Hope                              matth@cse.unsw.edu.au

Attachment: pgp_tGRAPHMcR.pgp
Description: PGP signature


Reply to: