So, I reviewed every setting that I can think of which I have listed below that would be involved with the problem that I have on the attachments being scrubbed. filter_content = no pass_mime_types =blank pass_filename_extensions=blank collapse_alternatives=yes convert_html_to_plaintext=no nondigestable=no scrub_nondigest=no digest_is_default = yes mime_is_default_digest=mime Still is scrubbing the attachments. I am stumped. Any ideas, besides canning our Groupwise e-mail system which we will be come Summer. Thanks for all the suggestions though. Appreciate the help Gary
>>> On 2/3/2009 at 11:02 AM, in message <[email protected]>, >>> "Gary Moore" <[email protected]> wrote: Grant, I actually just checked and I have the setting edit_filter_content set to "no" and the pass_mime_types was blank. Gary Gary Moore, CISSP Assistant Dean for Information Systems Hofstra University School of Law [email protected] (516) 463-6067 >>> On 2/3/2009 at 10:38 AM, in message <[email protected]>, >>> Grant Taylor <[email protected]> wrote: On 02/02/09 13:57, Gary Moore wrote: > My apologies if this has been on the list before. I have a mailman > listserv that I have setup to digest. The messages are forwarded > from our blog to a general resource account which sends them out to > the listserv. When the digest is sent out (see attached), each of > the digested messages has a "message scrubbed". How can I solve this > problem. Thanks in advance. I'm just guessing here, but I'm betting that you are sending your digest out with the actual messages as MIME attachments rather than textual copy in a new message. (Note: I think this is a good thing, so keep it up.) However I'm betting that Mailman is seeing the individual messages as attachments and is scrubbing them because it does not know about the MIME type, or more likely it is not an allowed MIME type. Go to Content Filtering -> pass_mime_types and make sure that multipart/digest, message/rfc822 and possibly text/rfc822-headers are included in the list. message/rfc822 is the standard attachment like you would receive if I forwarded a message to you (as an attachment). (Please refer to section 5.1.5 of RFC 2046 for more information.) I don't know if this will solve your problem or not, but at least it's a direction to look in to. Please let us know if this solves the problem as if it does, I propose that multipart/digest and message/rfc822 get added to the default allowed MIME types. Grant. . . . ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/gary.p.moore%40hofstra.edu Security Policy: http://wiki.list.org/x/QIA9 ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/gary.p.moore%40hofstra.edu Security Policy: http://wiki.list.org/x/QIA9 ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
