FAQ

LuKreme wrote:
I THINK that the "No" really means that it is not possible.

Not without modifying the source code.

The Digest messages are sent out as multi-part mime messages. Each message in the digest is a separate mime part. The text of the actual message is the thing that appears to be a 'header' to your and your user, but it is not the header, it is the body of the message.

This is true of the MIME format digests, but list members can chose a
plain text digest which is a single text/plain part containing the
masthead, the table of contents and the (scrubbed) messages, and which
in a default installation with default list settings is the default
digest format.

What I would recommend is making sure your client understands the mime digest format and can properly 'explode' it into individual messages. This way you never have to worry about the 'header'

And list owners and other list members would never have to deal with
posts with Subject: Re: listname Digest, Vol nn, Issue nn and bodies
consisting of "Yeah, me too" followed by a quote of the entire digest.

</rant>

--
Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan

Search Discussions

  • LuKreme at Nov 24, 2009 at 12:56 am

    On 23-Nov-2009, at 17:53, Mark Sapiro wrote:

    And list owners and other list members would never have to deal with
    posts with Subject: Re: listname Digest, Vol nn, Issue nn and bodies
    consisting of "Yeah, me too" followed by a quote of the entire digest.

    </rant>

    I'm hoping that in MM3 when someone does this a couple of things happen:

    1) the message is not posted
    2) they get a note from the list saying don't do that
    3) their mod bit is enabled.

    --
    You know, Rick, I have many a friend in Casablanca, but somehow,
    just because you despise me, you are the only one I trust.
  • Christian stalberg at Nov 24, 2009 at 11:52 am
    Why would HTML messages sent to the list be chanegd to plain text when I
    have content filtering turned off via the GUI? Is it possible the GUI switch
    is not working? If yes, how can I check 'under the hood'? Thank you in
    advance.
  • Mark Sapiro at Nov 25, 2009 at 3:14 am

    christian stalberg wrote:
    Why would HTML messages sent to the list be chanegd to plain text when I
    have content filtering turned off via the GUI? Is it possible the GUI switch
    is not working? If yes, how can I check 'under the hood'? Thank you in
    advance.

    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

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Rex Goode at Nov 26, 2009 at 3:26 pm
    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
  • Mark Sapiro at Nov 27, 2009 at 2:01 am

    Rex Goode wrote:
    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.

    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.

    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.

    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 at example.com
    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.

    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 at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Christian Stalberg at Nov 27, 2009 at 1:29 pm
    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
  • Mark Sapiro at Nov 27, 2009 at 3:23 pm

    Christian Stalberg wrote:
    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 ?

    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 at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Christian Stalberg at Nov 28, 2009 at 2:22 pm
    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 at halliburtonwatch.net Thu
    Nov 26 14:10:47 2009
    Return-Path: <halliburtonwatch-bounces at 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 at halliburtonwatch.net
    Subject: halliburtonwatch Digest, Vol 30, Issue 14
    To: halliburtonwatch at halliburtonwatch.net
    Reply-To: halliburtonwatch at halliburtonwatch.net
    Date: Thu, 26 Nov 2009 14:10:35 -0500
    Message-ID:
    <mailman.1.1259262635.9269.halliburtonwatch at halliburtonwatch.net>
    MIME-Version: 1.0
    Content-Type: text/plain; charset="us-ascii"
    Content-Transfer-Encoding: 7bit
    X-BeenThere: halliburtonwatch at 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 at halliburtonwatch.net?subject=unsubscri
    be>
    List-Archive:
    <http://halliburtonwatch.net/mailman/private/halliburtonwatch/>
    List-Post: <mailto:halliburtonwatch at halliburtonwatch.net>
    List-Help:
    <mailto:halliburtonwatch-request at halliburtonwatch.net?subject=help>
    List-Subscribe:
    <http://halliburtonwatch.net/mailman/listinfo/halliburtonwatch>,
    <mailto:halliburtonwatch-request at halliburtonwatch.net?subject=subscribe
    >
    Sender: halliburtonwatch-bounces at halliburtonwatch.net
    Errors-To: halliburtonwatch-bounces at halliburtonwatch.net
    Message contents
    Send halliburtonwatch mailing list submissions to
    halliburtonwatch at 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 at halliburtonwatch.net
    You can reach the person managing the list at
    halliburtonwatch-owner at 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 at halliburtonwatch.net>
    To: halliburtonwatch at halliburtonwatch.net
    Subject: [halliburtonwatch] Lawyers: government misconduct in
    halliburton case
    Message-ID: <1259252020.7133 at 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>
    -------------- next part --------------
    Lawyers: government misconduct in halliburton case
    By PETE YOST (AP) 1 hour ago

    http://www.google.com/hostednews/ap/article/ALeqM5gEkqkbr5Pndf7Tzj86eSq
    aSbPHSAD9C79K601
    WASHINGTON Defense lawyers are...
    ++++++
    Now here's the header of that same message sent to the list for
    distribution:

    From line From admin at halliburtonwatch.net Thu Nov 26 11:13:42 2009
    From: Admin <admin at halliburtonwatch.net>
    Subject: Lawyers: government misconduct in halliburton case
    To: halliburtonwatch at halliburtonwatch.net
    Cc:
    Bcc:
    Message-Id: <1259252020.7133 at halliburtonwatch.net>
    X-Originating-IP: 24.7.1.30
    X-Mailer: Usermin 1.420
    Date: Thu, 26 Nov 2009 11:13:40 -0500 (EST)
    MIME-Version: 1.0
    Content-Type: multipart/mixed; boundary="bound1259252022"
    Message contents View as text
    Lawyers: government misconduct in halliburton case
    By PETE YOST (AP) 1 hour ago

    On 11/27/2009 10:23 Mark Sapiro <mark at msapiro.net> wrote ..
    Christian Stalberg wrote:
    > >
    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 ?
    >
    >
    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 The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B.
    Dylan
  • Mark Sapiro at Nov 28, 2009 at 3:52 pm

    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).


    [...]
    ----------------------------------------------------------------------
    Message: 3
    Date: Thu, 26 Nov 2009 11:13:40 -0500 (EST)
    From: Admin <admin at halliburtonwatch.net>
    To: halliburtonwatch at halliburtonwatch.net
    Subject: [halliburtonwatch] Lawyers: government misconduct in
    halliburton case
    Message-ID: <1259252020.7133 at halliburtonwatch.net>
    Content-Type: text/plain; charset="windows-1252"
    An HTML attachment was scrubbed...
    URL:
    <http://halliburtonwatch.net/mailman/private/halliburtonwatch/attachments/20091126/a60933e9/attachment-0001.htm>

    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 at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmailman-users @
categoriespython
postedNov 24, '09 at 12:53a
activeNov 28, '09 at 3:52p
posts10
users4
websitelist.org

People

Translate

site design / logo © 2022 Grokbase