Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][tlug] Re: Followup on mutt and gpg
- Date: Tue, 3 Sep 2002 14:53:10 +0200
- From: Tobias Diedrich <td@example.com>
- Subject: [tlug] Re: Followup on mutt and gpg
- References: <20020903012221.GD28108@example.com> <20020903040011.GC1996@example.com> <20020903053854.GC5943@example.com> <20020903142533.4085d3b9.simon@example.com>
- User-agent: Mutt/1.4i
simon colston wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > I am using Sylpheed 0.8.2. Scott, since you applied the OE patch > Sylpheed no longer recognises your mail as being digitally signed but > puts crap like the above in the body. It already is in the body, so it's not Sylpheed at fault :-) I have the following procmail recipies to handle this stuff (out of the mutt FAQ IIRC): # # PGP # :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=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" } -- Tobias PGP: 0x9AC7E0BC This mail is made of 100% recycled bits
- References:
- [tlug] Followup on mutt and gpg
- From: Scott Robbins
- Re: [tlug] Followup on mutt and gpg
- From: Jonathan Byrne
- Re: [tlug] Followup on mutt and gpg
- From: Scott Robbins
- Re: [tlug] Followup on mutt and gpg
- From: simon colston
Home | Main Index | Thread Index
- Prev by Date: [tlug] Re: Draft: Quickie Guide to GPG
- Next by Date: Re: [tlug] Followup on mutt and gpg
- Previous by thread: Re: [tlug] Followup on mutt and gpg
- Next by thread: Re: [tlug] Followup on mutt and gpg
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links