-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 One more thing. For those of us using pine, the ascii armor approach is the only option we have, unlike you mutt users. The reason for that is that pine will not permit attachments to be specified which do not yet exist, and the signature file, if prepared as a separate binary attachment, is not ready when pine needs it. If it by chance DOES exist, it is the wrong file, from an earlier message, and that won't do either. So for pine users, the only option is to use the older method of ascii armoring. Chuck - -- The Moon is Waxing Crescent (19% of Full) In a world without Fences or Walls no one needs Windows or Gates. My home page is now at http://www.mhcable.com/~chuckh -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iQCVAwUBQGK3ljVdG8M9x9tGAQLZRgQAgnDhHdh3kSOZrhhxv9vP5OwtQHesyenh QGb5JTSWm6Xshoa5It/Wmv/gXoOWVeb69Ivg+jhA8JQ567tNd5fCzINghaoOmv7h 8NB2NVaFksjTqrxkSxR2OvnKVBfjJWEG1wopMgmPmsDIuJFoSBBhIu5/xJb3Nu0Y PFreV0k4nSo= =4Lp8 -----END PGP SIGNATURE-----
