Hello, everyone. I'm new here.
I operate several Mailman lists. I have lots of questions, but will start with the most pressing one.
It is cumbersome, with so many lists, to go in to each list's page of pending administrative requests to see what is waiting for me to act upon.
I just discovered withlist this morning. I think I can handle my shell for iterating through all of my lists.
Is there some way, possibly with withlist, for me to get a list of pending requests for a list. I don't need a lot of information about them. Maybe even just a number of pending requests. The results of the query on all lists would go to me in an email.
My users are getting annoyed when I get around to looking at their held messages and releasing them two weeks after they sent them. Maybe I'm just irresponsible, but it seems I should be able to know which lists have pending requests with just one click/cron/something.
Rex
Rex Goode wrote:
cron/checkdbs will mail to the ower of each list with outstanding requests a summary of thos requests. In a normal, complete installation this runs at 08:00 daily, but you can manually run it at any time or adjust the crontab to run it more frequently.
Or you could make a script based on it that would print the output instead of mailing it.
def count_requests(mlist): if mlist.NumRequestsPending(): print 'List: %s, Requests = %i' % (mlist.real_name, mlist.NumRequestsPending())
save that as bin/count_requests.py. Then run, e.g.
#!/bin/sh cd /path/to/mailman bin/withlist -a -r count_requests | mail -s "subj" you@example.com
It sounds like you haven't installed Mailman's crontab.
Also note, if you set General Options -> admin_immed_notify to Yes the list owner(s)/moderator(s) will receive email notice of each request as it is made.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
In looking at the output I may see the problem. I have been running Mailman and upgraded versions and moved Mailman from one server to another for years. Look at this output from my list wherein I see values like 'False' where the legals values are supposed to be either yes or no:
# When you scrub attachments, they are stored in archive area and links # are made in the message so that the member can access via web browser. # If you want the attachments totally disappear, you can use content # filter options. # # legal values are: # 0 = "No" # 1 = "Yes" scrub_nondigest = False
could this be the problem where an upgrade was not done properly where I have an old, out of date 'config' file whose values are unrecognized or ?
On 11/25/2009 10:26 Mark Sapiro <mark@[1]msapiro.net> wrote ..
If filter_content is no, Mailman should not be doing any content filtering or HTML to plain text conversion. I can make a guess. Perhaps the message is multipart/alternative with text/plain and text/html alternative parts and you are viewing the received message with an MUA (mail client) set to show you the plain text, or perhaps you are seeing a 'scrubbed' message in a digest or the archive or even the message from the list if Non-digest options -> scrub_nondigest is set to Yes. If you really want to look 'under the hood' look at the output from bin/config_list -o - LISTNAME or bin/dumpdb lists/LISTNAME/config.pck | grep filter_content
Christian Stalberg wrote:
This is not a problem. config_list says legal values are 0 and 1 for False/True settings to accommodate older Pythons that didn't define False and True, but False and True for these is actually fine.
Besides, if your issue were due to scrub_nondigest being True, you could tell as the HTML wouldn't just disappear, it would be replaced by a stanza saying "an HTML attachment has been scrubbed" with a link to wher the HTML was stored.
Do the messages from the list contain a
X-Content-Filtered-By: Mailman/MimeDel 2.1.x
header? If not, Mailman's content filtering hasn't changed them.
What is the exact MIME structure of an HTML message to the list and of the message received from the list?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I am using digests. here is the header of the digest I am receiving with the header of one of its messages:
From line From halliburtonwatch-bounces@halliburtonwatch.net Thu Nov 26 14:10:47 2009 Return-Path: <halliburtonwatch-bounces@halliburtonwatch.net> X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) onzarathustra.mitigation.com X-Spam-Level: X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failedversion=3.2.5 Received: from zarathustra.mitigation.com (wa1 [127.0.0.1])by zarathustra.mitigation.com (8.14.3/8.14.3) with ESMTP id nAQJAh11009279;Thu, 26 Nov 2009 14:10:46 -0500 From: halliburtonwatch-request@halliburtonwatch.net Subject: halliburtonwatch Digest, Vol 30, Issue 14 To: halliburtonwatch@halliburtonwatch.net Reply-To: halliburtonwatch@halliburtonwatch.net Date: Thu, 26 Nov 2009 14:10:35 -0500 Message-ID: <mailman.1.1259262635.9269.halliburtonwatch@halliburtonwatch.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-BeenThere: halliburtonwatch@halliburtonwatch.net X-Mailman-Version: 2.1.12 Precedence: list List-Id: halliburton Watch <halliburtonwatch.halliburtonwatch.net> List-Unsubscribe: <http://halliburtonwatch.net/mailman/options/halliburtonwatch>, <mailto:halliburtonwatch-request@halliburtonwatch.net?subject=unsubscri be> List-Archive: <http://halliburtonwatch.net/mailman/private/halliburtonwatch/> List-Post: <mailto:halliburtonwatch@halliburtonwatch.net> List-Help: <mailto:halliburtonwatch-request@halliburtonwatch.net?subject=help> List-Subscribe: <http://halliburtonwatch.net/mailman/listinfo/halliburtonwatch>, <mailto:halliburtonwatch-request@halliburtonwatch.net?subject=subscribe
Sender: halliburtonwatch-bounces@halliburtonwatch.net Errors-To: halliburtonwatch-bounces@halliburtonwatch.net Message contents Send halliburtonwatch mailing list submissions to halliburtonwatch@halliburtonwatch.net To subscribe or unsubscribe via the World Wide Web, visit http://halliburtonwatch.net/mailman/listinfo/halliburtonwatch or, via email, send a message with subject or body 'help' to halliburtonwatch-request@halliburtonwatch.net You can reach the person managing the list at halliburtonwatch-owner@halliburtonwatch.net When replying, please edit your Subject line so it is more specific than "Re: Contents of halliburtonwatch digest..." Today's Topics: 3. Lawyers: government misconduct in halliburton case (Admin)
Message: 3 Date: Thu, 26 Nov 2009 11:13:40 -0500 (EST) From: Admin <admin@halliburtonwatch.net> To: halliburtonwatch@halliburtonwatch.net Subject: [halliburtonwatch] Lawyers: government misconduct in halliburton case Message-ID: <1259252020.7133@halliburtonwatch.net> Content-Type: text/plain; charset="windows-1252" An HTML attachment was scrubbed... URL: <http://halliburtonwatch.net/mailman/private/halliburtonwatch/attachmen ts/20091126/a60933e9/attachment-0001.htm>
Christian Stalberg wrote:
I am using digests. here is the header of the digest I am receiving with the header of one of its messages:
In my original reply I wrote "perhaps you are seeing a 'scrubbed' message in a digest". That is the case here. HTML cannot be included in the plain text digest, so it is 'scrubbed' (i.e. stored aside and replaced by a link).
[...]
The HTML part was removed, stored aside and replaced by the above note and link. The link appears to be broken (it redirects to a page that says there is no website at that domain), but that is a separate issue.
[...]
Now here's the header of that same message sent to the list for distribution:
If you want to see the same thing in the digest as in the individual message, you must select MIME as your digest format.
The list admin can uncheck 'plain' on the Membership Management... -> Membership List page or the user can select MIME for "Get MIME or Plain Text Digests?" on the user's options page.
Also, the admin can set Digest options -> mime_is_default_digest to MIME to make MIME the default digest format for new list members.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Rex Goode wrote:
cron/checkdbs will mail to the ower of each list with outstanding requests a summary of thos requests. In a normal, complete installation this runs at 08:00 daily, but you can manually run it at any time or adjust the crontab to run it more frequently.
Or you could make a script based on it that would print the output instead of mailing it.
def count_requests(mlist): if mlist.NumRequestsPending(): print 'List: %s, Requests = %i' % (mlist.real_name, mlist.NumRequestsPending())
save that as bin/count_requests.py. Then run, e.g.
#!/bin/sh cd /path/to/mailman bin/withlist -a -r count_requests | mail -s "subj" you@example.com
It sounds like you haven't installed Mailman's crontab.
Also note, if you set General Options -> admin_immed_notify to Yes the list owner(s)/moderator(s) will receive email notice of each request as it is made.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
In looking at the output I may see the problem. I have been running Mailman and upgraded versions and moved Mailman from one server to another for years. Look at this output from my list wherein I see values like 'False' where the legals values are supposed to be either yes or no:
# When you scrub attachments, they are stored in archive area and links # are made in the message so that the member can access via web browser. # If you want the attachments totally disappear, you can use content # filter options. # # legal values are: # 0 = "No" # 1 = "Yes" scrub_nondigest = False
could this be the problem where an upgrade was not done properly where I have an old, out of date 'config' file whose values are unrecognized or ?
On 11/25/2009 10:26 Mark Sapiro <mark@[1]msapiro.net> wrote ..
If filter_content is no, Mailman should not be doing any content filtering or HTML to plain text conversion. I can make a guess. Perhaps the message is multipart/alternative with text/plain and text/html alternative parts and you are viewing the received message with an MUA (mail client) set to show you the plain text, or perhaps you are seeing a 'scrubbed' message in a digest or the archive or even the message from the list if Non-digest options -> scrub_nondigest is set to Yes. If you really want to look 'under the hood' look at the output from bin/config_list -o - LISTNAME or bin/dumpdb lists/LISTNAME/config.pck | grep filter_content
Christian Stalberg wrote:
This is not a problem. config_list says legal values are 0 and 1 for False/True settings to accommodate older Pythons that didn't define False and True, but False and True for these is actually fine.
Besides, if your issue were due to scrub_nondigest being True, you could tell as the HTML wouldn't just disappear, it would be replaced by a stanza saying "an HTML attachment has been scrubbed" with a link to wher the HTML was stored.
Do the messages from the list contain a
X-Content-Filtered-By: Mailman/MimeDel 2.1.x
header? If not, Mailman's content filtering hasn't changed them.
What is the exact MIME structure of an HTML message to the list and of the message received from the list?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I am using digests. here is the header of the digest I am receiving with the header of one of its messages:
From line From halliburtonwatch-bounces@halliburtonwatch.net Thu Nov 26 14:10:47 2009 Return-Path: <halliburtonwatch-bounces@halliburtonwatch.net> X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) onzarathustra.mitigation.com X-Spam-Level: X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failedversion=3.2.5 Received: from zarathustra.mitigation.com (wa1 [127.0.0.1])by zarathustra.mitigation.com (8.14.3/8.14.3) with ESMTP id nAQJAh11009279;Thu, 26 Nov 2009 14:10:46 -0500 From: halliburtonwatch-request@halliburtonwatch.net Subject: halliburtonwatch Digest, Vol 30, Issue 14 To: halliburtonwatch@halliburtonwatch.net Reply-To: halliburtonwatch@halliburtonwatch.net Date: Thu, 26 Nov 2009 14:10:35 -0500 Message-ID: <mailman.1.1259262635.9269.halliburtonwatch@halliburtonwatch.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-BeenThere: halliburtonwatch@halliburtonwatch.net X-Mailman-Version: 2.1.12 Precedence: list List-Id: halliburton Watch <halliburtonwatch.halliburtonwatch.net> List-Unsubscribe: <http://halliburtonwatch.net/mailman/options/halliburtonwatch>, <mailto:halliburtonwatch-request@halliburtonwatch.net?subject=unsubscri be> List-Archive: <http://halliburtonwatch.net/mailman/private/halliburtonwatch/> List-Post: <mailto:halliburtonwatch@halliburtonwatch.net> List-Help: <mailto:halliburtonwatch-request@halliburtonwatch.net?subject=help> List-Subscribe: <http://halliburtonwatch.net/mailman/listinfo/halliburtonwatch>, <mailto:halliburtonwatch-request@halliburtonwatch.net?subject=subscribe
Sender: halliburtonwatch-bounces@halliburtonwatch.net Errors-To: halliburtonwatch-bounces@halliburtonwatch.net Message contents Send halliburtonwatch mailing list submissions to halliburtonwatch@halliburtonwatch.net To subscribe or unsubscribe via the World Wide Web, visit http://halliburtonwatch.net/mailman/listinfo/halliburtonwatch or, via email, send a message with subject or body 'help' to halliburtonwatch-request@halliburtonwatch.net You can reach the person managing the list at halliburtonwatch-owner@halliburtonwatch.net When replying, please edit your Subject line so it is more specific than "Re: Contents of halliburtonwatch digest..." Today's Topics: 3. Lawyers: government misconduct in halliburton case (Admin)
Message: 3 Date: Thu, 26 Nov 2009 11:13:40 -0500 (EST) From: Admin <admin@halliburtonwatch.net> To: halliburtonwatch@halliburtonwatch.net Subject: [halliburtonwatch] Lawyers: government misconduct in halliburton case Message-ID: <1259252020.7133@halliburtonwatch.net> Content-Type: text/plain; charset="windows-1252" An HTML attachment was scrubbed... URL: <http://halliburtonwatch.net/mailman/private/halliburtonwatch/attachmen ts/20091126/a60933e9/attachment-0001.htm>
Christian Stalberg wrote:
I am using digests. here is the header of the digest I am receiving with the header of one of its messages:
In my original reply I wrote "perhaps you are seeing a 'scrubbed' message in a digest". That is the case here. HTML cannot be included in the plain text digest, so it is 'scrubbed' (i.e. stored aside and replaced by a link).
[...]
The HTML part was removed, stored aside and replaced by the above note and link. The link appears to be broken (it redirects to a page that says there is no website at that domain), but that is a separate issue.
[...]
Now here's the header of that same message sent to the list for distribution:
If you want to see the same thing in the digest as in the individual message, you must select MIME as your digest format.
The list admin can uncheck 'plain' on the Membership Management... -> Membership List page or the user can select MIME for "Get MIME or Plain Text Digests?" on the user's options page.
Also, the admin can set Digest options -> mime_is_default_digest to MIME to make MIME the default digest format for new list members.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Christian Stalberg -
Mark Sapiro -
Rex Goode