-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stephen Gran wanted us to know:
>> Yes, inline signing would probably fix that issue. >In my last message, I see: >Content-Type: multipart/signed; micalg=pgp-sha1; Mime multipart is not inline signing. >It is an inline, gpg signed message. I had no idea how many broken This email that I'm sending is an inline signed message. Look at the difference in the headers of mine compared to the one you were looking at before. Blue skies... - -- Regards... Todd OS X: We've been fighting the "It's a mac" syndrome with upper management for years now. Lately we've taken to just referring to new mac installations as "Unix" installations when presenting proposals and updates. For some reason, they have no problem with that. -- /. Linux kernel 2.6.3-19mdkenterprise 2 users, load average: 0.07, 0.06, 0.02 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBdsQ0Y2VBGxIDMLwRAmDCAJ4zPVTyYV9RNnee64xfKUBGxsgN9wCcCP3U +gM+i+cN0Z6LqPIMQo8H6T4= =hnMi -----END PGP SIGNATURE----- _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
