Benjamin Michotte muttered:
> In my .procmailrc, I've got
> 
> ##
> ## 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"
> }
> 
> :0 fBw
>       * ^-----BEGIN PGP PUBLIC KEY BLOCK-----
>       * ^-----END PGP PUBLIC KEY BLOCK-----
>       | formail -i "Content-Type: application/pgp-keys; format=text;"
> 
> But when I receive a signed mail, I've got a 
> [-- Attachment #1 --]
> [-- Type: text/plain, Encoding: quoted-printable, Size: 0.4K --]
> ....
> [-- Attachment #2 --]
> [-- Type: application/pgp-signature, Encoding: 7bit, Size: 0.2K --]
> 
> [-- application/pgp-signature is unsupported (use 'v' to view this part) --]
> 
> why?

Well, that's what is's suppsed to do, isn't it? Rewrite tradional PGP to
PGP/MIME!? 
If you're asking why application/pgp-signature is unsupported, my guess
that you didn't verify that signature. See pgp_verify_sig.
Be sure to have sourced a propper mutt-pgp.rc (check your docs for the
samples).

HTH,

Michael
-- 
"Whip me.  Beat me.  Make me maintain AIX."
(By Stephan Zielinski)

PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key

Reply via email to