--=-=-= Content-Transfer-Encoding: quoted-printable "Jeff Crosby" <[EMAIL PROTECTED]> writes:
> Scott's mail arrives as an attachment as well. ATT00008.txt is the messa= ge > and AT00011.dat is his signature file. I don't know what you have > configured unless it's something on my end. Your client is to blame. PGP/MIME is an RFC standard and for some reason your client is not playing well with that standard. I'm using a completely different client from Matt but using the same standardized approach for signing (and encrypting if need be) messages. The message is indeed split into MIME components but most mailers recognize and parse it correctly rath= er than showing split attachments. One other possibility is that a virus/spam scanner or somesuch is messing up the MIME encoding in transit confusing your mail reader. =2D-=20 Scott Harney<[EMAIL PROTECTED]> "...and one script to rule them all." gpg key fingerprint=3D7125 0BD3 8EC4 08D7 321D CEE9 F024 7DA6 0BC7 94E5 --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD4DBQA+mydH8CR9pgvHlOURAkYiAJdlTYzxdVrT87VjYo/TazdRdAhgAJ9EdVQt FqaJhyhvgKR/H2kd+uHKOQ== =z/wS -----END PGP SIGNATURE----- --=-=-=--
