savanna wrote:
> In the FAQ there's a procmail recipe for converting old style pgp
> signatures to new style multi-part mime. The very first line should
> indicate that it's a filter recipe, not a delivery recipe:
>
> ie
>
> :0 f
>
> and not
>
> :0
>
> In this way all messages can be filtered before passing onto other
> recipes. I've attached my .procmail so you can see it in context.
>
> # convert old-style pgp to multipart-mime
> # notice f at start - filter
> :0 f
> * !^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"
> }
I personally do not use this recipe, but I wouldn't think the 'f' flag
on the top-level recipe would matter since the action is not a pipe.
There is nothing in the man page that I can see that says what the 'f'
flag does when applied to a grouping recipe. Does it really not work
for you when you use it as documented in PGP-Notes.txt?
