[Gllug] mutt/gpg

[gllug at uncertainty.org.uk]

Hi,
   I've missed the earlier mails in this thread ... but

mutt and gpg work out of the box for me...

(using the RH 7.1 rpms)

- although I did have to create my own key and edit the gpg/options file
to set a keyserver that I use.

I don't use gpg.rc - my muttrc was created by the muttrc builder (but I 
think that really just set up where to collect mail from) all pgp related entries are commented out!

but.. there is an interesting dicusiion going on on the mutt-users mailing
list at the moment. It seems like mutt uses the latest standard (mime/pgp)
but most other mail clients use pgp/cleartext which is an old and apparenltly
broken standard (content is labeled as plain text when it is better labeled as
pgp text and the system doesn't work for non-ascii text)

there are variuos threads that you could look at 
http://www.mail-archive.com/mutt-users@mutt.org/msg19618.html
http://www.mail-archive.com/mutt-users@mutt.org/msg19459.html
http://www.mail-archive.com/mutt-users@mutt.org/msg19456.html

or from the mutt faq
-------------

Why can't Mutt decode this PGP mail sent with Pine/ELMme/etc?
Because this PGP mail does not say it is a PGP mail in the header, and Mutt only scans the header of mails. This is a feature!

Well, there is a solution for your problem, if you use procmail. Add these lines to your .procmailrc:

 
# Add a "Content-Type: application/pgp" header so Mutt will know the
# mail is encrypted.
:0 fBw
* ^-----BEGIN PGP MESSAGE-----
* !Content-type: multipart
| formail -i "Content-Type: application/pgp; format=text; x-action=encryptsign"

# Add a "Content-Type: application/pgp" header so Mutt will know the
# mail is signed.
:0 fBw
* ^-----BEGIN PGP SIGNED MESSAGE-----
* !Content-type: multipart
| formail -i "Content-Type: application/pgp; format=text; x-action=sign"
---------------------




On Thu, Oct 11, 2001 at 10:04:59AM +0100, Paul Brazier wrote:
> I'm slowly getting somewhere - I managed to decrypt an email in mutt.
> I do need the gpg.rc file included in my .muttrc it seems.
> Then I was getting the message mixed up with the gpg keyring output but
> half readable.
> I had several files called mutt* in the /tmp directory and deleting
> these seemed to cure this problem - they must have been lock files of
> some sort.
> 
> Encypting still isn't working yet - it can't seem to find the public
> keys on my keyring.
> 
> I've just used a sample .muttrc and gpg.rc that came with the mutt rpm
> and tweaked them slightly.
> 
> 
> 
> 
> 
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the originator.
> 
> This footnote also confirms that this email message has been checked
> for the presence of computer viruses.
> 
> **********************************************************************
> 
> 
> -- 
> Gllug mailing list  -  Gllug at linux.co.uk
> http://list.ftech.net/mailman/listinfo/gllug
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 274 bytes
Desc: not available
URL: <http://mailman.lug.org.uk/pipermail/gllug/attachments/20011011/b67fb5b5/attachment.pgp>