Subject: Re: pgp4pine + gpg + sigdashes: who's to blame?

From: Jeff Franklin <[email-masked]>
Date: Wed, 6 Mar 2002 17:53:47 -0800 (Pacific Standard Time)

On Wed, 6 Feb 2002, Joel Boonstra wrote:

> So, where is that extra space getting stripped out?  My hunch is that it's
> not pine -- perhaps gpg eliminates all whitespace immediately preceding a
> newline.  However, perhaps when pine sends its data to the filter (i.e.,
> to pgp4pine), it strips out the space.  I doubt this, but it could be the
> case.  Or, perhaps pgp4pine munges the data as it's passing it through to
> gpg.  Again, unlikely, but it seems that one of those is happening, since
> sigdashes don't work for encrypted messages.
>
> So, here are my questions:
>
> * Can anyone else reproduce this?  Both me and my co-worker are using:
>
>   RH 7.1/7.2
>   pine 4.44
>   gpg (GnuPG) 1.0.4 (at least)
>   pgp4pine 1.75-6
>
> * If it's reproducible, how can I trace where the space is being stripped
> out?
>
> * Or, am I being silly, and missing something obvious?

Hi Joel,

In my tests of sending-filters, it looks to me like pine does correctly
preserve the white space.  My guess is the problem lies in some
interaction between pgp4pine and gpg.  If you wanted to test this
hypothesis more, I would try the sending filter manually with some example
text.  Then, you could try the same text with gpg, with whatever args
pgp4pine passes it.

Good luck!
Jeff

-- 
Jeff Franklin <[email-masked]>
Networks and Distributed Computing   University of Washington