Eric S. Raymond wrote: > > 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. > > That's bad news; the author of the feature thought he'd fixed this problem. > I've copied this to him. I'm using fetchmail 4.6.0. Mimedecode is off on default in this version. christian -- PGP public key by "Subject: send pgp-key" or from public key server. fingerprint: 06 3A 6D 67 8A 8A 2E C7 10 83 22 BD DC D7 39 9D
- 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