-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>>>> "Michael" == Michael T Babcock <mbabcock@xxxxxxxxxxxxxx> writes: >> > Yes, actually, his message was perfectly MIME compliant. Read the >> > source. <snip> >> >> OK, please show me the RFC that defines application/ms-tnef :-) Michael> You might want to be silent instead of sounding foolish. Michael> application/ms-tnef is the type of data within a segment of the Michael> MIME message. The message is MIME compliant -- perfectly so. RFC2046, section 6 (Experimental Media Type Values): ,---- | Any format without a rigorous and public definition must be named with | an "X-" prefix... `---- I believe that is what Marc was referring to. So the MIME type should have been called "application/x-ms-tnef". - -- Hubert Chan <hackerhue@xxxxxxxx> - http://www.geocities.com/hubertchan/ PGP/GnuPG key: 1024D/651854DF71FDA37F Fingerprint: 6CC5 822D 2E55 494C 81DD 6F2C 6518 54DF 71FD A37F Key available at wwwkeys.pgp.net. Please encrypt *all* e-mail to me. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7aat0ZRhU33H9o38RAtdOAJ9laphseoBHYDi7UPw9NafTWbTvWACfbeiu PzFOo7zoCfxNc8GFKm+jRFI= =AoYo -----END PGP SIGNATURE----- Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
