On Fri, Feb 19 1999 at 10:11 -0500, Eric S. Raymond wrote:
> > * Mimedecode default turned off pending a fix for the PGP-signature-
> > munging bug.
> >
> > There are no more recent entries regarding mimedecode, so it has
> > apparently not been fixed since. Is it possible that you (and
> > Vladimir) are using fetchmail with this mimedecode option switched
> > on?
>
> Note: this bug has been fixed recently (4.7.6).
The binary fetchmail 4.7.7 rpm avaliable at your website does not behave
as expected. Haven't checked the source rpm/build rules...
--
Boris Wesslowski
[EMAIL PROTECTED]
www.kyb.uni-stuttgart.de/boris
- Content type change corrupts PGP signature Boris Wesslowski
- Re: Content type change corrupts PGP signature Thomas Roessler
- Re: Content type change corrupts PGP signature Thomas Roessler
- Re: Content type change corrupts PGP signatu... Vladimir Sizikov
- Re: Content type change corrupts PGP signatu... Eric S. Raymond
- Re: Content type change corrupts PGP sig... Boris Wesslowski
- Re: Content type change corrupts PG... Eric S. Raymond
- Re: Content type change corrupt... Boris Wesslowski
- Re: Content type change cor... Eric S. Raymond
- Re: Content type change cor... Christian Schult
- Re: Content type change corrupts PGP signature Boris Wesslowski
