On 1/13/06, Robert Citek <[EMAIL PROTECTED]> wrote: > On Jan 12, 2006, at 9:28 PM, David Dooling wrote: > > Perhaps the lack of having a multipart/mixed MIME wrapped around the > > HTML is causing it to match ``the cwe-lug mailing list's content > > filtering rules and was prevented from being forwarded on to the list > > membership.'' > > It would be nice if mailman told me which rule matched. Anyone know > if that possible?
There are only two content filtering rules in Mailman: filter_mime_types and pass_mime_types. They are processed in that order. If any part of the message matches the any of the types in the filter_mime_types, it is discarded. Next, if any part of the message does not match the pass_mime_types, it is discarded. Then empty multipart sections are removed, then empty messages are discarded. In a previous email, you said: > in the Mailman configuration I have the following for pass_mime_types: > > multipart/mixed > multipart/alternative > text/plain > message/rfc822 The message he sent that got bounced was: Content-Type: text/html; charset=ISO-8859-1 So it looks like it failed to pass_mime_types, since text/html is not in the pass_mime_types list. The message/rfc822 Content-Type header at the top of ``his message'': --===============0953172244== Content-Type: message/rfc822 MIME-Version: 1.0 was not from his message, but was from the Mailman bounce message. That Content-Type header declared the type of that part of the multipart message Mailman sent. In other words, to allow his original bounced message, you would have to add ``text/html'' to the pass_mime_types. You might also want to enable convert_html_to_plaintext if you do this. dd -- David Dooling _______________________________________________ CWE-LUG mailing list [email protected] http://www.cwelug.org/ http://www.cwelug.org/archives/ http://www.cwelug.org/mailinglist/
