At 1:27 AM +0200 2003/07/31, Brad Knowles wrote:
For example, if a message is PGP signed, the "Content-Type:" header might be "multipart/signed", "multipart/mixed", or there might be no MIME headers or formatting at all, and the message is in plain ASCII with internal formatting that PGP understands. If the message is in HTML, the value for this header might be "multipart/alternative".
Oh, and I forgot uuencode -- using this tool, the message will
likely appear to be in plain ASCII, but most MUAs will display the encoded part as an attachment. Do you want to ban them, too? If so, that's a lot more work.
My point is that this is not a simple process. You need to be
specific about what you want to eliminate, or what you want to allow. If you can provide that level of detail, then there should be existing tools that you can use to implement your choices, and we can help you find them.
But there isn't any "Big Red Switch", nor is there ever likely to be one.
-- Brad Knowles, <brad.knowles@skynet.be>
"They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania.
GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)