-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 On Wed, Jan 25, 2006 at 01:39:36 PM -0500, Charles Hallenbeck wrote: > Hi people, > > I have experienced the same failure to verify inline signatures on signed messages on the list as others have > experienced. Neither my Mutt nor my gnupg have changed to account for this. Nor my exim4 either, for that matter. It looks like the list software is changing the Content-Type: header. A message I received which verified corectly automatically had this: Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Mutt adds this automatically, but messages from the list have this: Content-Type: text/plain; charset="us-ascii" So that's what's happening. There are procmail rules you can use to add the x-action: part to the header based on whether the message has the - -----BEGIN PGP SIGNED MESSAGE----- line, but I am not using one, you can probably google for it and find it easily though. HTH - -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan Thomas Stivers e-mail: stivers_t at tomass.dyndns.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFD1/1b5JK61UXLur0RAxpTAJ9rkWA2zNyAfVVoH4h4imeYUDWzYwCfTvCt hUqmyScwr4T5MZt4KrYCtnY= =3/Cy -----END PGP SIGNATURE-----
