> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > Behalf Of Alberto Monteiro
... > What do you mean by "behave better"? Will it bar html messages, > or transform them into plain text? > > [anything else is **not** behave better] There are actually two problems. One is easy; messages that are just text/html. Those are converted to text, if the software doesn't barf on bad HTML. Mailman uses Lynx to do this, I believe. Second problem is when a message is encoded as MIME, such as the especially evil multipart/mixed, which can carry along binaries that have no business being sent to the list. Somewhere in there may be some HTML that might be convertable to text, but there seem to be no end of strange things that mailers do. On the other hand, multipart/alternative is usually easy to take apart because it usually consists of text/html and text/plain, so Mailman can just grab the text/plain version. So... if all that makes any sense... The list is set to drop any attachments that have a type of multipart. That's what stops *all* attachments that could be evil. Then it only lets through parts that are multipart/mixed, multipart/alternative or text/plain. Then it converts any text/html to text, using Lynx. The old problem that BZ and others encountered was that AOL was sending multipart messages in which (IIRC) any text was buried inside multipart attachments, so they were stripped off, nothing was left, and Mailman wasn't kind enough to bother to notify the sender. Now, it notifies. Is your head spinning now? MIME gets confusing, what with messages, attachments, parts, etc. I'm dealing with it in my analytical software, too. What a small nightmare it can be. Nick _______________________________________________ http://www.mccmedia.com/mailman/listinfo/brin-l
