| Darxus on Wed, 24 Apr 2002 18:38:55 -0400 |
|
If you must use pine, and want to be able to do encryption with people who use rfc compliant mail clients, use the procmail recipe to convert them to what pine can read (http://www.washington.edu/pine/pine-info/2001.10/msg00028.html), or consider using mutt with the stuff that makes it work like pine (http://www.netmeister.org/apps/pine2mutt/). Mutt is *much* more powerful than Pine. Complaining that others do the right thing (RFC2015) just because Pine doesn't know how to handle it properly, or forcing your users to use old/pine style non-standard encryption just because pine can't handle it, is dumb. Honestly, I really do think it's best for people to use whatever they like. But the amount of annoyance pine has caused by 1) Not implimenting rfc compliant support for signing and encryption 2) Releasing it under a restrictive license that doesn't allow anybody else to fix this problem ..just bugs the hell out of me. FYI, I didn't know those urls or the rfc number, I pulled them out of this thread. -- "The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man." - George Bernard Shaw http://www.ChaosReigns.com Attachment:
pgp5nkZWImy7h.pgp
|
|