-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 19 May 2004 9:14 am, Karthik Poobalasubramanian wrote: > On Wed, 19 May 2004, Bryce T. Pier wrote: > > It's been a while since I used mutt. Don't you need to add some hooks > > based on the text of a gpg-signed message. I remember doing a lot of > > tweaking to my muttrc to get auto-verify and auto-key-retrieve to work. > > Googling for muttrc and gpg I found this: > > http://www.dotfiles.com/files/27/319_muttrc.txt > > and several others. > > > > I know it's possible as I used mutt that way for at least 2-3 years and > > it worked wonderfully. > > Bryce, > Actually you I don't think you have to specify anything in your .muttrc. > I have keyserver-options auto-key-retrieve in gpg.conf and retreving > keys works great. Its just that it doesn't recognize signed(or > encrypted) email from Kmail(i haven't tried with any other client). I am > mutt-users list and i could verify all signatures that were sent on the > list.
It still sounds like your missing a hook in your muttrc that will detect kmail signed or encrypted email. It would make sense that all the people using the mutt-users list were actually sending their mail with mutt so your muttrc hooks were detecting the gpg pieces and handling them correctly. As I said, I'm certain it will work you just need to figure out the correct hook based on what is different about the raw emails from the different mailers. The only differences I see in your emails vs. mine are: mine: Content-Type: Text/Plain; charset="iso-8859-1" yours: Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed and my ----BEGIN etc. lines are prefaced with "=2D". Kory's have this as well. - -- Bryce T. Pier [EMAIL PROTECTED] We are dreamers, shapers, singers and makers. We study the mysteries of laser and circuit, crystal and scanner, holographic demons and invocations of equations. These are tools we employ and we know many things. -Elric, Babylon5 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAq5MMoNTOIKp/8CURAgLfAJ9rBkb/yKsqau3zJSMcr3qo9BpXWwCghPLo rfE7xUDv3Tdtxgi4KEcs4+0= =IChW -----END PGP SIGNATURE-----
