Re: [Mailman-Users] Deleting old msgs?
You did the work, so I'll just thank you very, very much!! Have a merry Christmas or Hanukkah or . Thank you, Frank Bell Application Systems Admin Information Systems and Services Washburn University Topeka, KS 66621 785-670-2334 On 12/2/2011 5:25 PM, Mark Sapiro wrote: Frank Bell wrote: Is there any easier way? I just took over our mailman server and we have several years worth of messages in 190+ mboxs totaling approx 130 gig and a few 100K msgs. You inspired me. I've created a script for pruning archives. See NOTE ON PRUNING OLD MESSAGES: in the FAQ athttp://wiki.list.org/x/2YA9 for links. Since this is a brand new process, I suggest you make backup copies of the LISTNAME.mbox files before starting. The script has a --backup option, but I would make separate backups to be sure until you've run the script successfully. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Changes to CookHeaders.py stop working for SOME lists!?
Folks -- OS: Red Hat Linux OS Version: RHEL 5.6 MailTransfer Agent (MTA): postfix MTA Version: 2.3.3-2.1 Mailman Version: 2.1.9 release 6.el5 (yikes!) Over a year ago, I added some code to CookHeaders.py to add a custom header of my choosing to all messages on all lists for this installation, and all was well. Right now, some of the lists apply the custom header, and just a few (but more than one), do NOT. I don't think that should even be possible, but it certainly is happening. Any ideas on how this could be happening and how to fix it? Additional information: About a month ago, the custom header disappeared completely from everywhere, and when I looked at the files somehow CookHeaders.py had been reverted to an earlier state that did not contain my changes. So, I overwrote that configuration with the backup of my version and ran /bin/restart. Everything worked just fine on ALL lists for a couple of weeks, and then this strange problem came up. I've checked CookHeaders.py, and it contains the desired changes. I've since run /bin/restart and /bin/stop with /bin/start, but the problem persists. I have complete sudo access to this virtual machine, so there should be no restrictions on what I can do; but I'm a novice when it come to linux usage. Any help is appreciated, Drew Tenenholz -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] MIME digests problem?
could the following be directly related to the toggle between MIME digests and plain-text ones? (herewith the question) I've been using mailman for a very long time, since I migrated from SmartList maybe 12 years ago. I have a multi-question topic that takes a few questions and combines them into a cohesive whole. This is what I'd like to ask: 1) My main mailinglist runs to about 2000 subscribers. I would say perhaps it's evenly split between those who would like to have something more blog-ish (web-based) and those who would like to have it remain email-based. However, I've just noticed something on a user's cellphone-based email and their web-based email; this is one of the people who would like me to move the whole interface to Facebook. (and I have spent years developing the wiki associated with this mailinglist!). (see http://www.colorist.org/wiki ) Now I think FB has its place, but this is a professional forum where almost instantaneous answers that come from mailman's email-based design are very valuable to that half of the community who use it for asking important questions that are answered in literally, a moment or two. Yet I just looked at this particular user's celphone (Android) message queue, (he subscribes to the digest) and saw that the digests he's getting are empty attachments indicating 2k in leng th (I forced one out that is about 8 pages to test). Then he also complained that on Earthlink's Webmail he gets his digests not with concatenated text like I'm used to seeing, but with no text in the message and instead, an Attachments header that lists each message (horizontally) as Forwarded message Forwarded message etc. (which when clicked, show the messages, supposedly). He hates this of course. For what it's worth, he says Outlook exhibits the same behavior as Earthlink's Webmail. So I'm wondering, has something changed in the way the RFCs are not being honored; are digests not 'homogenous' across platforms any more; is there a way to fix this behavior which may be affecting others? Thank you to Barry, et al., for maintaining Mailman. btw I'm running 2.1.12 on CentOS. Rob Lingelbach r...@colorist.org -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] MIME digests problem?
Rob Lingelbach wrote: could the following be directly related to the toggle between MIME digests and plain-text ones? It almost certainly is. 1) Yet I just looked at this particular user's celphone (Android) message queue, (he subscribes to the digest) and saw that the digests he's getting are empty attachments indicating 2k in length (I forced one out that is about 8 pages to test). I use K-9 mail on an Android phone, and it's handling of MIME format digests is a disaster. See http://code.google.com/p/k9mail/issues/detail?id=2017. I think there may be similar issues with the Android native mail client. I don't know about iPhones. Then he also complained that on Earthlink's Webmail he gets his digests not with concatenated text like I'm used to seeing, but with no text in the message and instead, an Attachments header that lists each message (horizontally) as Forwarded message Forwarded message etc. (which when clicked, show the messages, supposedly). He hates this of course. For what it's worth, he says Outlook exhibits the same behavior as Earthlink's Webmail. So both Earthlink web mail and Outlook do not render a MIME digest very well. So I'm wondering, has something changed in the way the RFCs are not being honored; are digests not 'homogenous' across platforms any more; is there a way to fix this behavior which may be affecting others? Have your user switch to plain digests. For a long time, Mailman digest subscribers have had a choice between MIME format and 'plain' format digests. The MIME format digest is fully conformant with the MIME RFCs, but not all MUAs deal with it well. The plain format digest is (mostly) RFC 1153 compliant, but compliance only matters to digest exploder software. Virtually all MUAs should be able to properly render it, but non-plain text message parts get replaced by short blurbs containing a URL to where they can be found, and one can't directly reply to an individual message, at least without an 'exploder'. Thus, each user gets to choose which format better suits their needs. -- 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 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Changes to CookHeaders.py stop working for SOMElists!?
Drew Tenenholz wrote:
OS: Red Hat Linux
OS Version: RHEL 5.6
MailTransfer Agent (MTA): postfix
MTA Version: 2.3.3-2.1
Mailman Version: 2.1.9 release 6.el5 (yikes!)
Over a year ago, I added some code to CookHeaders.py to add a custom header of
my choosing to all messages on all lists for this installation, and all was
well. Right now, some of the lists apply the custom header, and just a few
(but more than one), do NOT. I don't think that should even be possible, but
it certainly is happening.
Any ideas on how this could be happening and how to fix it?
What is your change to CookHeaders? I.e., I would need to see the exact
change to know whether it is somewhere that is conditionally executed
based on list settings.
Is either include_rfc2369_headers or include_list_post_header set to No
for the affected lists (those that don't apply the header)?
Do the affected lists have a lists/LISTNAME/extend.py file or a
'pipeline' attribute?
/usr/lib/mailman/bin/dumpdb /var/lib/mailman/lists/LISTNAME/config.pck \
| grep pipeline
Additional information: About a month ago, the custom header disappeared
completely from everywhere, and when I looked at the files somehow
CookHeaders.py had been reverted to an earlier state that did not contain my
changes.
yum probably 'upgraded' Mailman.
So, I overwrote that configuration with the backup of my version and ran
/bin/restart.
Do you mean /usr/lib/mailman/bin/mailmanctl restart?
Everything worked just fine on ALL lists for a couple of weeks, and
then this strange problem came up. I've checked CookHeaders.py, and
it contains the desired changes. I've since run /bin/restart and
/bin/stop with /bin/start, but the problem persists.
If you don't mean 'mailmanctl {stop|start|restart}, what are these
things.
In any case, if you didn't restart Mailman after your changes, no lists
would have your change.
--
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
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
