On Sun, Feb 21 1999 at 19:23 -0500, Eric S. Raymond wrote: > > The binary fetchmail 4.7.7 rpm avaliable at your website does not behave > > as expected. Haven't checked the source rpm/build rules... > > I came in late. In what specific respect is the behavior unexpected? We were talking about the problem that fetchmail (even version 4.7.7(rpm)), in contrast to what the NEWS file and the man page say, *does* decode MIME by default unless 'no mimedecode' is explicitly specified in .fetchmailrc; this damages the PGP signatures, as you already know. Best regards -- 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