Re: [Mailman-Users] Trouble with some messages being scrubbed
Thanks for confirming Mark. I had read that this was a possible bug - so good to know that an upgrade/new install will likely cure it. Would the workaround you describe involve setting: convert_html_to_plaintext = 1 and filter_mime_types = [add html/text] ? One other question about upgrade/new install - I have read that upgrading an existing installation is rather difficult and might involve downtime, so the preferred method is to bring up a new server and move the lists over. Is that correct? Thanks again. Scott -Original Message- From: Mark Sapiro [mailto:m...@msapiro.net] Sent: Sunday, August 09, 2009 9:30 PM To: Scott Race; mailman-users@python.org Subject: Re: [Mailman-Users] Trouble with some messages being scrubbed Scott Race wrote: I am getting the following message in some of our posts, no content, just: Skipped content of type multipart/alternative-- next part -- This is a bug in your 2.1.5 version, long since fixed. A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 1994 bytes Desc: image003.gif There's a link to the attachment, image003.gif, which pulls up ok, but, no content is being delivered. The list settings have filter_content set to No. This is a scrubber issue. It is independent of content filtering except in that if you filtered the text/html part out of the multipart/alternative part leaving only the text/plain part, it would probably appear OK in the archive. I read in another post that scrub_nondigest might be set to Yes, but I can't find the setting for that. Because it doesn't exist in 2.1.5, and if it were set in your case, it would just break individual messages and mime digests as well as archives and plain digests. Mailman 2.1.5. If you are saying that this happens to individual messages and not to just plain digests and archives, then this is not 'standard' 2.1.5, and somehow Scrubber has been inserted into GLOBAL_PIPELINE either in Defaults.py or mm_cfg.py or in a pipeline attribute of the list. The real solution is to upgrade to a more recent Mailman that doesn't have this Scrubber bug. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org 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
Re: [Mailman-Users] Trouble with some messages being scrubbed
Scott Race wrote: Would the workaround you describe involve setting: convert_html_to_plaintext = 1 and filter_mime_types = [add html/text] ? Not exactly. the workaround may be to just add text/html to filter_mime_types, but it depends if there is anything in pass_mime_types. If you have the default setting of multipart/mixed multipart/alternative text/plain in pass_mime types, you will already remove everything that isn't text/plain if you just turn on content filtering. Also, in 2.1.5, even if both filter_mime_types and pass_mime_types are empty, meaning nothing gets removed, a multipart/alternative part will still get replaced by it's first alternative (this is a setting - collapse_alternatives - in later versions, but in 2.1.5 it is always done). Thus, to do the minimal filtering that will avoid this bug, set filter_content = 1 filter_mime_types = [] pass_mime_types = [] convert_html_to_plaintext = 0 One other question about upgrade/new install - I have read that upgrading an existing installation is rather difficult and might involve downtime, so the preferred method is to bring up a new server and move the lists over. Is that correct? Upgrading from 2.1.5 to any more recent version is easy. It is much easier than bringing up a new server and moving lists. There are potential caveats regarding Python versions. See the FAQ at http://wiki.list.org/x/pYA9. Other than that, it depends how your original Mailman was installed. If from source, the upgrade process is to run configure with the same options as before (can be found in config.log if you still have the original) and make. Then if all went OK, stop Mailman, backup your current installation just in case, run make install and start Mailman. I've done this dozens of times on a production system without problems. It only takes a few minutes. Upgrading from a packege should also be easy, but the details depend on the package. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org 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
Re: [Mailman-Users] Approved: password header!
On 8/6/09 9:08 PM, Mark Sapiro m...@msapiro.net wrote: Thus, the idea of allowing [Approved: password] in the subject header and removing only that text from the subject has appeal because it doesn't depend on any characteristics of the message body. Won't work in an environment in which the message arrives with a DKIM signature including the Subject: header and when enforces valid DKIM headers inbound. (Or for a list going to outside subscribers, if any of them insist on DKIM validation.) Of course, it's very unlikely that approved header as first line of first text part works in that environment either. But Mailman already (by common configuration) munges Subject: headers. When Office 2010 public beta arrives (or before if someone here has earlier access) it would be nice to check whether Outlook 2010 has learned a rational way to add custom headers. --John -- Mailman-Users mailing list Mailman-Users@python.org 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
[Mailman-Users] Corrupted archives ...
Hullo, I'm running mailman-2.1.12, with the htdig patches on FreeBSD 7.0 I have a list with archives that are about 10 years old. The archive mbox size is 175M. I was alerted by a subscriber that the August 2009 archives list 128 No subject emails that look funny. So I looked.. sure enough they're there. And they look something like this when I click on a single email listed in the archives: No subject Mon Aug 10 18:53:40 EDT 2009 * Previous message: [Redacted] Blah... * Next message: No subject * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Tue, 14 Dec 1999 23:27:19 PST X-Originating-IP: [63.11.227.157] From: redacted redacted_at... To: redacted Date: Tue, 14 Dec 1999 23:27:19 PST Mailing-List: contact redacted X-Mailing-List: redacted Precedence: bulk List-Help: http://www.example.com/redacted/info.html, mailto:redacted at example.com List-Unsubscribe: mailto:redacted-unsubscribe at example.com List-Archive: http://www.example.com/redacted/ Reply-To: redacted Subject: [Redacted] Redacted MIME-Version: 1.0 Content-Type: text/plain; format=flowed Content-Transfer-Encoding: 7bit Status: RO Content-Length: 7352 Lines: 174 (body of email starts here) From Redacted redacted at u... Wed Dec 15 00:40:19 1999 Delivered-To: redacted Received: (listserv 1.291); by f7; 15 Dec 1999 08:43:59 - Delivered-To: redacted Date: 15 Dec 99 03:44:15 EST From: Redacted redacted at u... To: redacted X-Mailing-List: redacted Precedence: bulk List-Help: http://www.example.com/redacted/info.html, mailto:redacted at example.com List-Unsubscribe: mailto:redacted-unsubscribe at example.com List-Archive: http://www.example.com/redacted/ Reply-To: redacted Subject: [Redacted] RedactedMIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable (body of email starts here...) (another email starts here, as above...) (end of example) Everything looks fine if I use mutt -f listname.mbox in the private archives directory for the list. Has anyone had problems like this? My GoogleFu is failing me, or at least isn't showing me anything like this. Thanks in advance! --Glenn -- Mailman-Users mailing list Mailman-Users@python.org 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
Re: [Mailman-Users] Corrupted archives ...
Glenn Sieb wrote: I have a list with archives that are about 10 years old. The archive mbox size is 175M. I was alerted by a subscriber that the August 2009 archives list 128 No subject emails that look funny. [snip] From: redacted redacted_at... To: redacted Date: Tue, 14 Dec 1999 23:27:19 PST (body of email starts here) From Redacted redacted at u... Wed Dec 15 00:40:19 1999 Delivered-To: redacted Have you tried running bin/cleanarch and then rerunning bin/arch to regenerate the messages? It's possible what you're seeing could be caused by messed up From lines in your old mbox file (used by the archiver to determine the start of messages). Mutt may just have a more forgiving parser. Be warned, though, if you regenerate the entire archive, then the links in your archive will change (i.e. old posts that people have linked will no longer be in the same spot). Terri -- Mailman-Users mailing list Mailman-Users@python.org 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
