-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It would appear that on Sep 11, Alexandre Oliva did say: > On Sep 11, 2004, "Joe(theWordy)Philbrook" <jtwdyp@xxxxxxxx> wrote: > > > This is an experimental posting: A gpg clearsign text document > > containing the actual message, has been attached to this email via mime > > encoding. If you desire to verify the gpg sig you may need to save the > > attachment to disk with any standard mail client and use a gpg utility > > on it... If this method is bothersome, please let me know why. > > Yuck. At least mark the mime part with disposition inline instead of > attachment. > I agrees with you about "yuck"... (Hmmmnnn "mark the mime part with 'disposition inline'" Well perhaps I would if I knew how to get pine to do that.) Well as it is, since the correct word is "YUCK" I'm going back to relying on the message body inlined ascii armored text. So there shouldn't be any more like that one. ################################################################# # gpg sig for: Joe (theWordy) Philbrook <JtWdyP@xxxxxxxx> (:-0% # # You can find my public gpg key at http://pgpkeys.mit.edu/ # ################################################################# -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBQ8iQRZ/61mwhY94RAiRlAJ9XKwpVeYPWMXXnxZk/fC8ZLXB0wgCgmm+R 4yZDT0bObYy+fRHzlXZwqKQ= =B1zI -----END PGP SIGNATURE----- -- | ^^^ ^^^ | <o> <o> Joe (theWordy) Philbrook | ^ J(tWdy)P | ___ <<jtwdyp@xxxxxxxx>> | | <sigh>
