Re: mutt signatures (was Re: Volume on -devel) [ot]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Yes, it's a standard. RFC 2015. There is no particular reason a mail
> program should not support it. You mentioned elisp; the latest version of
> VM might, if I understood the upstream announcement correctly.
that's the problem with mh-e and especially tm-mh-e... it seems to be
so out of date. i think i may volunteer as an upstream maintainer, or
at least make an updated one my first debian package. (just as soon as
you guys finish the gpg switch, that is. i am not a huge fanatic about
freeness, and have very few qualms about using non-free software so
long as it's good enough, but i do refuse to use patented algorithms
when an almost-as-good free one is available.)
- --phouchg
"Reasoning is partly insane" --Rush, "Anagram (for Mongo)"
PGP 5.0 key (0xE024447449) at http://cif.rochester.edu/~phouchg/pgpkey.txt
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
Comment: Processed by Mailcrypt 3.5.1, an Emacs/PGP interface
Charset: noconv
iQA/AwUBNvKpmZ49M+7gJHRJEQLHXwCePCb9kir3gKhqMgNmeZLR3Qx3R5YAoOqp
sVCf7lAxRJ9thPK8K897eeOg
=4121
-----END PGP SIGNATURE-----
Reply to: