gpg usage w/ pine

Matthias Odisio
Mon Jun 2 15:03:02 2003

On Fri, 30 May 2003, Bob Holtzman wrote:

> Hi,
> I'm running gnupg-1.0.7-7 and pine-4.44-7.73.0 under RH7.3 and after
> setting:
>  [X]  compose-send-offers-first-filter
> in pine and noting that the gpg install seems to have created:
> display-filters    = "_LEADING(-----BEGIN PGP MESSAGE-----)_" 
> /usr/bin/gpg-check
>                      "_LEADING(-----BEGIN PGP SIGNED MESSAGE-----)_" 
> /usr/bin/gpg-check
> sending-filters     = /usr/bin/gpg-sign
>                       /usr/bin/gpg-encrypt _RECIPIENTS_
>                       /usr/bin/gpg-sign+encrypt _RECIPIENTS_
> no filters are offered when I try to send. No opportunity to encrypt, 
> sign, nothing.
> The only way I could get it to work was to install pgp4pine. This is an 
> acceptable
> solution but I can't see why it's neccessary. Is there any way to get away 
> from pgp4pine?
> I should mention that gpg works well as a stand alone. I can engrypt, 
> decrypt and sign indidual files.
> Any ideas or pointers appreciated. Thanks.

According to my .pinerc (pine 4.44 rh 1.70.0), you could try with this 
placement for quotes :

display-filters=_LEADING("-----BEGIN PGP MESSAGE-----")_ /usr/bin/gpg-check 
Check also that, for a next filter, a real tab is inserted after the CR.

You might also consider magicpgp