I've got a couple of questions about the example filter handling of composite MIME types:
/usr/share/doc/mimedefang/examples/suggested-minimum-filter-for-windows-clie nts According to RFC 2045, three composite message types exist: "message", "multipart", or "X-<Extension>" Question 1: Are all of these composite types handled by the filter_multipart() function? If not, how are the others handled? These composite types include one or more discrete types, such as "text", "image", "audio", etc. My observation is that when a file is attached to a message, it is added as a discrete type, such as "text", "image", "audio", etc., which is handled by the filter() function. So, my observation is that the multipart MIME part never has an associated filename. But the discrete part within the multipart message may have an associated filename. Question 2: In the example file, filter_multipart calls the filter_bad_filenames() function to check for bad filename extensions. I see the utility of this test in the filter() function. But does a multipart message ever really have an associated filename? If so, can you help me understand, perhaps with examples, when filter_multipart() would need to check filenames? Thanks, Michael _______________________________________________ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list [email protected] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
