OK,

I've got another problem with Qmail/Plesk/Mailman (same customer,
rebuilt server). Plesk is 7.5.4 reloaded.

Mail delivered fails with "need GID 110 got 101" error. I set up the
brute-force wrapper to deliver with GID 110, and set the permissions
correctly for it to work. Now, I'm getting the following (broken up
into multiple lines for courtesy):

qmail: 1157518628.995172 delivery 726: success:
group_mismatch_error._Mailman_expected_the_mail_wrapper_script_to_be/
executed_as_one_of_the_following_groups:/[mail,_nobody,_mailman],/
but_the_system's_mail_server_executed_the_mail_script_as_group:_"popuser"./
Try_tweaking_the_mail_server_to_run_the_script_as_one_of_these_groups:/
[mail,_nobody,_mailman],/or_re-run_configure_providing_the_
command_line_option:/'--with-mail-gid=popuser'./Failed_to_start_
/usr/lib/mailman/mail/mailman./did_0+0+1/

I'm about ready to pull my hair out. I even added the popuser user to
the mailman group in /etc/passwd.

So, that being said, are there any ideas out there? I have been
messing with this for a week, and have not come up with anything else
to do.

--
Douglas G. Phillips
Simple Business Solutions

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Search Discussions

  • Douglas G. Phillips at Sep 7, 2006 at 6:36 am
    Prequalification: This may not work for everyone. What I suspected is
    that something in the mailman config was corrupted, or when the server
    backups were restored, something was configured for the old server,
    and was therefore different with the new one. However, I noticed in
    my research on this problem that there were a number of individuals
    with strange issues like this, so hopefully this helps someone.

    What I did:
    Get a fresh copy of mailman (stock version), and compiled it, with the
    expected mail gid and cgi gid used in this installation. I then
    installed it into a different working directory (/usr/local/mailman),
    and copied the list configs and archives into this directory space.
    Finally, I moved the plesk installation (/usr/lib/mailman) to a
    different name and symlinked /usr/local/mailman to /usr/lib/mailman.

    Everything is working fine now, including the plesk control panel.

    So, at this point, I'm not sure whether plesk's version modifies
    anything in mailman, or if they just have a front-end that manipulates
    things somehow, but since it's [plesk] compiled PHP code, I won't find
    out that way. But the customer is very happy, and at the moment,
    that's all I am worried about... (And finally getting some sleep)
    ----- Original Message -----
    From: "Douglas G. Phillips" <doug at sbscomp.net>
    To: <mailman-users at python.org>
    Sent: Wednesday, September 06, 2006 12:05 AM
    Subject: [Mailman-Users] Mailman/Qmail/Plesk Problem


    OK,

    I've got another problem with Qmail/Plesk/Mailman (same customer,
    rebuilt server). Plesk is 7.5.4 reloaded.

    Mail delivered fails with "need GID 110 got 101" error. I set up the
    brute-force wrapper to deliver with GID 110, and set the permissions
    correctly for it to work. Now, I'm getting the following (broken up
    into multiple lines for courtesy):

    qmail: 1157518628.995172 delivery 726: success:
    group_mismatch_error._Mailman_expected_the_mail_wrapper_script_to_be/
    executed_as_one_of_the_following_groups:/[mail,_nobody,_mailman],/
    but_the_system's_mail_server_executed_the_mail_script_as_group:_"popus
    er"./
    Try_tweaking_the_mail_server_to_run_the_script_as_one_of_these_groups:
    /
    [mail,_nobody,_mailman],/or_re-run_configure_providing_the_
    command_line_option:/'--with-mail-gid=popuser'./Failed_to_start_
    /usr/lib/mailman/mail/mailman./did_0+0+1/

    I'm about ready to pull my hair out. I even added the popuser user to
    the mailman group in /etc/passwd.

    So, that being said, are there any ideas out there? I have been
    messing with this for a week, and have not come up with anything else
    to do.

    --
    Douglas G. Phillips
    Simple Business Solutions

    ----------------------------------------------------------------
    This message was sent using IMP, the Internet Messaging Program.
  • Liste yoneticisi at Oct 4, 2007 at 2:16 pm
    I configured the list and default values accourding to the following
    values.

    I filled the filter_filename_extensions and pass_filename_extensions
    parameters for filtering attachments.

    the values are listed below:
    filter_filename_extensions = """exe
    bat
    cmd
    com
    pif
    scr
    vbs
    cpl"""

    pass_filename_extensions = """doc
    xls
    xml
    xlw
    ppt
    pps
    pdf
    php
    gz
    gif
    jpg
    jpeg
    bmp
    png
    htm
    html
    txt
    rtf
    rar
    zip"""

    But i have a problem, if someone sends a document with file name qwe.JPG
    mailman doesn't send the attachment.
    I couldn't add the Capital letter extensions. Mailman converts them to
    lower letter.

    Do you have any advise about it?
  • Mark Sapiro at Oct 5, 2007 at 1:11 am

    liste yoneticisi wrote:
    pass_filename_extensions = """doc
    xls
    xml
    xlw
    ppt
    pps
    pdf
    php
    gz
    gif
    jpg
    jpeg
    bmp
    png
    htm
    html
    txt
    rtf
    rar
    zip"""

    But i have a problem, if someone sends a document with file name qwe.JPG
    mailman doesn't send the attachment.
    I couldn't add the Capital letter extensions. Mailman converts them to
    lower letter.

    The conversion of *_filename_extensions to lower case is intentional,
    but we neglected to convert the actual extension in the message to
    lower case for comparison.

    The following patch will be in Mailman 2.1.10 and will fix the problem.

    --- Mailman/Handlers/MimeDel.py 2005-12-30 18:50:08 +0000
    +++ Mailman/Handlers/MimeDel.py 2007-10-05 01:01:24 +0000
    @@ -256,4 +256,4 @@
    fext = fext[1:]
    else:
    fext = ''
    - return fext
    + return fext.lower()

    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Liste yoneticisi at Mar 7, 2008 at 12:54 pm
    Hi;

    Is there a patch that giving information for filtered extension.

    I mean i am filtering *.mpg for example.
    If someone sends an attachment with mpg extension, e-mail is delivered
    without attachment and without any information about filtering.

    But if sender doesn't know about it, (or if not
    remember) he may say "i sent such a movie about blah blah."

    is it possible to add a sentence like below:
    "the attachment is filtered due to "list_name" content-filtering
    configuration"
  • Mark Sapiro at Mar 7, 2008 at 9:24 pm
    liste yoneticisi <listeyon at metu.edu.tr>
    Date: Fri, 7 Mar 2008 14:54:17 +0200 (WET)
    To: Mailman Users ML <mailman-users at python.org>
    Hi;

    Is there a patch that giving information for filtered extension.

    I mean i am filtering *.mpg for example.
    If someone sends an attachment with mpg extension, e-mail is delivered
    without attachment and without any information about filtering.

    But if sender doesn't know about it, (or if not
    remember) he may say "i sent such a movie about blah blah."

    is it possible to add a sentence like below:
    "the attachment is filtered due to "list_name" content-filtering
    configuration"

    It is certainly possible, but as far as I know, there is no published
    patch for it.

    Of course, there is the

    X-Content-Filtered-By: Mailman/MimeDel 2.1.x

    header that is added whenever anything is removed, but I expect you
    want something more visible than that.

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Brad Knowles at Mar 8, 2008 at 2:06 am

    On 3/7/08, Mark Sapiro quoted liste yoneticisi <listeyon at metu.edu.tr>:

    Is there a patch that giving information for filtered extension.

    I mean i am filtering *.mpg for example.
    If someone sends an attachment with mpg extension, e-mail is delivered
    without attachment and without any information about filtering.
    [ ... deletia ... ]
    It is certainly possible, but as far as I know, there is no published
    patch for it.
    What about scrub_nondigest? Wouldn't that do what the OP was asking for?

    --
    Brad Knowles <brad at shub-internet.org>
    LinkedIn Profile: <http://tinyurl.com/y8kpxu>
  • Mark Sapiro at Mar 8, 2008 at 3:42 am

    Brad Knowles wrote:
    On 3/7/08, Mark Sapiro quoted liste yoneticisi <listeyon at metu.edu.tr>:
    Is there a patch that giving information for filtered extension.

    I mean i am filtering *.mpg for example.
    If someone sends an attachment with mpg extension, e-mail is delivered
    without attachment and without any information about filtering.
    [ ... deletia ... ]
    It is certainly possible, but as far as I know, there is no published
    patch for it.
    What about scrub_nondigest? Wouldn't that do what the OP was asking for?

    Possibly. If the OP is willing to turn off content filtering or limit
    it to collapse_alternatives and then have all non-text/plain and
    characterset unknown parts stored and replaced with hyperlinks in the
    delivered posts, then yes, scrub_nondigest would do it.

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Liste yoneticisi at Mar 10, 2008 at 7:48 am
    On Fri, 7 Mar 2008, Mark Sapiro wrote:

    Brad Knowles wrote:
    On 3/7/08, Mark Sapiro quoted liste yoneticisi <listeyon at metu.edu.tr>:
    Is there a patch that giving information for filtered extension.

    I mean i am filtering *.mpg for example.
    If someone sends an attachment with mpg extension, e-mail is delivered
    without attachment and without any information about filtering.
    [ ... deletia ... ]
    It is certainly possible, but as far as I know, there is no published
    patch for it.
    What about scrub_nondigest? Wouldn't that do what the OP was asking for?
    Possibly. If the OP is willing to turn off content filtering or limit
    it to collapse_alternatives and then have all non-text/plain and
    characterset unknown parts stored and replaced with hyperlinks in the
    delivered posts, then yes, scrub_nondigest would do it.
    Actually I just want a vissible message for deleted/filtered attachments.

    You once sent a patch cok uppercase attachments.(I copied below) Is it
    possible to add a command in order to add message (or information) to a
    suitable part of this file??

    But i don't know the the programming language for mailman.

    Thank you fot your consideration and cooperation.

    """
    The conversion of *_filename_extensions to lower case is intentional,
    but we neglected to convert the actual extension in the message to
    lower case for comparison.

    The following patch will be in Mailman 2.1.10 and will fix the problem.

    --- Mailman/Handlers/MimeDel.py 2005-12-30 18:50:08 +0000
    +++ Mailman/Handlers/MimeDel.py 2007-10-05 01:01:24 +0000
    @@ -256,4 +256,4 @@
    fext = fext[1:]
    else:
    fext = ''
    - return fext
    + return fext.lower()

    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
    """
  • Mark Sapiro at Mar 15, 2008 at 4:10 am

    liste yoneticisi wrote:
    Actually I just want a vissible message for deleted/filtered attachments.

    Actually, given the current architecture of content filtering, this
    turns out to be not at all easy to do in any reasonable way. About the
    best that could be done without too much difficulty is content
    filtering could prepare a report along the lines of

    text/html part removed by content filtering
    image/jpeg part removed by content filtering
    application/msword part removed by content filtering

    and add it to the message similarly to the way msg_footer is added.

    In any case, this is not likely to be done before Mailman 2.2 if then.

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Liste yoneticisi at Nov 12, 2007 at 9:18 am
    Hello;

    The owner of one of our lists face with a problem.

    When she tries to unsubscribe one of the member from the list,
    (checks the unsub column, and pushes submit your changes button)

    the following page occurs.
    "
    Bug in Mailman version 2.1.9

    We're sorry, we hit a bug!
    Please inform the webmaster for this site of this problem. Printing of
    traceback and other system information has been explicitly inhibited, but
    the webmaster can find this information in the Mailman error logs.
    "

    There is no problem for other lists.

    When I checked error log,
    there was some lines about this list such as following.

    "
    admin(12323): PATH_INFO: /engelsiz-uni/members/list
    admin(12323): HTTP_REFERER:
    http://mailman.metu.edu.tr/mailman/admin/engelsiz-uni/members/list
    admin(12323): PATH_TRANSLATED:
    /cwis/htdocs/mailman/engelsiz-uni/members/list
    admin(12323): REQUEST_URI: /mailman/admin/engelsiz-uni/members/list
    admin(15609): HTTP_COOKIE:
    engelsiz-uni+admin(020000006929103847732800000030313065653535393561663537623235393632376361336138383761333066346336316663623635;
    __utma 3322125.419203040.1165843329.1165843329.1165843329.1
    admin(15609): PATH_INFO: /engelsiz-uni/members
    admin(15609): HTTP_REFERER:
    http://mailman.metu.edu.tr/mailman/admin/engelsiz-uni/members
    admin(15609): PATH_TRANSLATED: /cwis/htdocs/mailman/engelsiz-uni/members
    admin(15609): REQUEST_URI: /mailman/admin/engelsiz-uni/members
    "

    Could you please tell me how can I solve the problem?

    regards.

    ----------------
    Liste Yoneticisi
    http://e-list.cc.metu.edu.tr
    http://e-liste.bidb.odtu.edu.tr
  • Mark Sapiro at Nov 12, 2007 at 3:42 pm

    liste yoneticisi wrote:
    When she tries to unsubscribe one of the member from the list,
    (checks the unsub column, and pushes submit your changes button)

    the following page occurs.
    "
    Bug in Mailman version 2.1.9

    We're sorry, we hit a bug!
    Please inform the webmaster for this site of this problem. Printing of
    traceback and other system information has been explicitly inhibited, but
    the webmaster can find this information in the Mailman error logs.
    "

    There is no problem for other lists.

    When I checked error log,
    there was some lines about this list such as following.

    "
    admin(12323): PATH_INFO: /engelsiz-uni/members/list
    admin(12323): HTTP_REFERER:
    http://mailman.metu.edu.tr/mailman/admin/engelsiz-uni/members/list
    admin(12323): PATH_TRANSLATED:
    /cwis/htdocs/mailman/engelsiz-uni/members/list
    admin(12323): REQUEST_URI: /mailman/admin/engelsiz-uni/members/list
    admin(15609): HTTP_COOKIE:
    engelsiz-uni+admin(020000006929103847732800000030313065653535393561663537623235393632376361336138383761333066346336316663623635;
    __utma 3322125.419203040.1165843329.1165843329.1165843329.1
    admin(15609): PATH_INFO: /engelsiz-uni/members
    admin(15609): HTTP_REFERER:
    http://mailman.metu.edu.tr/mailman/admin/engelsiz-uni/members
    admin(15609): PATH_TRANSLATED: /cwis/htdocs/mailman/engelsiz-uni/members
    admin(15609): REQUEST_URI: /mailman/admin/engelsiz-uni/members
    "

    Could you please tell me how can I solve the problem?

    Post the entire section of the error log from the time in question. You
    have omitted all the information that would help diagnose this
    problem. The most important part is the Python traceback.

    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Liste yoneticisi at Nov 13, 2007 at 12:45 pm
    ----------------
    Liste Yoneticisi
    http://e-list.cc.metu.edu.tr
    http://e-liste.bidb.odtu.edu.tr

    On Mon, 12 Nov 2007, Mark Sapiro wrote:

    liste yoneticisi wrote:
    When she tries to unsubscribe one of the member from the list,
    (checks the unsub column, and pushes submit your changes button)

    the following page occurs.
    "
    Bug in Mailman version 2.1.9

    We're sorry, we hit a bug!
    Please inform the webmaster for this site of this problem. Printing of
    traceback and other system information has been explicitly inhibited, but
    the webmaster can find this information in the Mailman error logs.
    "

    There is no problem for other lists.

    When I checked error log,
    there was some lines about this list such as following.

    "
    admin(12323): PATH_INFO: /engelsiz-uni/members/list
    admin(12323): HTTP_REFERER:
    http://mailman.metu.edu.tr/mailman/admin/engelsiz-uni/members/list
    admin(12323): PATH_TRANSLATED:
    /cwis/htdocs/mailman/engelsiz-uni/members/list
    admin(12323): REQUEST_URI: /mailman/admin/engelsiz-uni/members/list
    admin(15609): HTTP_COOKIE:
    engelsiz-uni+admin(020000006929103847732800000030313065653535393561663537623235393632376361336138383761333066346336316663623635;
    __utma 3322125.419203040.1165843329.1165843329.1165843329.1
    admin(15609): PATH_INFO: /engelsiz-uni/members
    admin(15609): HTTP_REFERER:
    http://mailman.metu.edu.tr/mailman/admin/engelsiz-uni/members
    admin(15609): PATH_TRANSLATED: /cwis/htdocs/mailman/engelsiz-uni/members
    admin(15609): REQUEST_URI: /mailman/admin/engelsiz-uni/members
    "

    Could you please tell me how can I solve the problem?

    Post the entire section of the error log from the time in question. You
    have omitted all the information that would help diagnose this
    problem. The most important part is the Python traceback.
    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
    ----------
    The whole section is copied below:
    "
    admin(2745): HTTP_COOKIE:
    engelsiz-uni+admin(0200000069cb563747732800000061373462616233393830346232666366376163663863623563333565663162303161616538663163
    admin(2745): HTTP_REFERER:
    http://mailman.metu.edu.tr/mailman/admin/engelsiz-uni/members/list
    admin(2745): PATH_TRANSLATED:
    /cwis/htdocs/mailman/engelsiz-uni/members/list
    admin(2745): REQUEST_URI: /mailman/admin/engelsiz-uni/members/list
    admin(2745): PATH_INFO: /engelsiz-uni/members/list
    admin(8881): HTTP_COOKIE:
    engelsiz-uni+admin(0200000069ce0f3847732800000065363039633637306537333533383866303363316138386461366239333837626636666133626166
    admin(8881): PATH_INFO: /engelsiz-uni/members/list
    admin(8881): HTTP_REFERER:
    http://mailman.metu.edu.tr/mailman/admin/engelsiz-uni/members/list
    admin(8881): PATH_TRANSLATED:
    /cwis/htdocs/mailman/engelsiz-uni/members/list
    admin(8881): REQUEST_URI: /mailman/admin/engelsiz-uni/members/list
    admin(9327): HTTP_COOKIE:
    engelsiz-uni+admin(020000006929103847732800000030313065653535393561663537623235393632376361336138383761333066346336316663623635;
    __utma 3322125.419203040.1165843329.1165843329.1165843329.1
    admin(9327): PATH_INFO: /engelsiz-uni/members
    admin(9327): HTTP_REFERER:
    http://mailman.metu.edu.tr/mailman/admin/engelsiz-uni/members
    admin(9327): PATH_TRANSLATED: /cwis/htdocs/mailman/engelsiz-uni/members
    admin(9327): REQUEST_URI: /mailman/admin/engelsiz-uni/members
    admin(9407): HTTP_COOKIE:
    engelsiz-uni+admin(020000006929103847732800000030313065653535393561663537623235393632376361336138383761333066346336316663623635;
    __utma 3322125.419203040.1165843329.1165843329.1165843329.1
    admin(9407): PATH_INFO: /engelsiz-uni/members
    admin(9407): HTTP_REFERER:
    http://mailman.metu.edu.tr/mailman/admin/engelsiz-uni/members
    admin(9407): PATH_TRANSLATED: /cwis/htdocs/mailman/engelsiz-uni/members
    admin(9407): REQUEST_URI: /mailman/admin/engelsiz-uni/members
    admin(11017): HTTP_COOKIE:
    engelsiz-uni+admin(020000006929103847732800000030313065653535393561663537623235393632376361336138383761333066346336316663623635;
    __utma 3322125.419203040.1165843329.1165843329.1165843329.1
    admin(11017): PATH_INFO: /engelsiz-uni/members/list
    admin(11017): HTTP_REFERER:
    http://mailman.metu.edu.tr/mailman/admin/engelsiz-uni/members/list
    admin(11017): PATH_TRANSLATED:
    /cwis/htdocs/mailman/engelsiz-uni/members/list
    admin(11017): REQUEST_URI: /mailman/admin/engelsiz-uni/members/list
    admin(12323): HTTP_COOKIE:
    engelsiz-uni+admin(020000006929103847732800000030313065653535393561663537623235393632376361336138383761333066346336316663623635;
    __utma 3322125.419203040.1165843329.1165843329.1165843329.1
    admin(12323): PATH_INFO: /engelsiz-uni/members/list
    admin(12323): HTTP_REFERER:
    http://mailman.metu.edu.tr/mailman/admin/engelsiz-uni/members/list
    admin(12323): PATH_TRANSLATED:
    /cwis/htdocs/mailman/engelsiz-uni/members/list
    admin(12323): REQUEST_URI: /mailman/admin/engelsiz-uni/members/list
    admin(15609): HTTP_COOKIE:
    engelsiz-uni+admin(020000006929103847732800000030313065653535393561663537623235393632376361336138383761333066346336316663623635;
    __utma 3322125.419203040.1165843329.1165843329.1165843329.1
    admin(15609): PATH_INFO: /engelsiz-uni/members
    admin(15609): HTTP_REFERER:
    http://mailman.metu.edu.tr/mailman/admin/engelsiz-uni/members
    admin(15609): PATH_TRANSLATED: /cwis/htdocs/mailman/engelsiz-uni/members
    admin(15609): REQUEST_URI: /mailman/admin/engelsiz-uni/members

    "
    By the way I still wonder why this problem occured, but i performed a
    quick ans dirty solution, I removed the list without deleting
    archives after listing the subscribers and opened again. subscribed
    subscribers, archive was OK.
    But I don't know whether this problem occurs again or not.
  • Mark Sapiro at Nov 14, 2007 at 5:02 am

    liste yoneticisi wrote:
    The whole section is copied below:
    "
    admin(2745): HTTP_COOKIE:
    engelsiz-uni+admin(0200000069cb563747732800000061373462616233393830346232666366376163663863623563333565663162303161616538663163
    admin(2745): HTTP_REFERER:
    http://mailman.metu.edu.tr/mailman/admin/engelsiz-uni/members/list
    admin(2745): PATH_TRANSLATED:
    /cwis/htdocs/mailman/engelsiz-uni/members/list
    admin(2745): REQUEST_URI: /mailman/admin/engelsiz-uni/members/list
    admin(2745): PATH_INFO: /engelsiz-uni/members/list
    admin(8881): HTTP_COOKIE:
    engelsiz-uni+admin(0200000069ce0f3847732800000065363039633637306537333533383866303363316138386461366239333837626636666133626166
    admin(8881): PATH_INFO: /engelsiz-uni/members/list
    admin(8881): HTTP_REFERER:
    http://mailman.metu.edu.tr/mailman/admin/engelsiz-uni/members/list
    admin(8881): PATH_TRANSLATED:
    /cwis/htdocs/mailman/engelsiz-uni/members/list
    admin(8881): REQUEST_URI: /mailman/admin/engelsiz-uni/members/list
    admin(9327): HTTP_COOKIE:
    engelsiz-uni+admin(020000006929103847732800000030313065653535393561663537623235393632376361336138383761333066346336316663623635;
    __utma 3322125.419203040.1165843329.1165843329.1165843329.1
    admin(9327): PATH_INFO: /engelsiz-uni/members
    admin(9327): HTTP_REFERER:
    http://mailman.metu.edu.tr/mailman/admin/engelsiz-uni/members
    admin(9327): PATH_TRANSLATED: /cwis/htdocs/mailman/engelsiz-uni/members
    admin(9327): REQUEST_URI: /mailman/admin/engelsiz-uni/members
    admin(9407): HTTP_COOKIE:
    engelsiz-uni+admin(020000006929103847732800000030313065653535393561663537623235393632376361336138383761333066346336316663623635;
    __utma 3322125.419203040.1165843329.1165843329.1165843329.1
    admin(9407): PATH_INFO: /engelsiz-uni/members
    admin(9407): HTTP_REFERER:
    http://mailman.metu.edu.tr/mailman/admin/engelsiz-uni/members
    admin(9407): PATH_TRANSLATED: /cwis/htdocs/mailman/engelsiz-uni/members
    admin(9407): REQUEST_URI: /mailman/admin/engelsiz-uni/members
    admin(11017): HTTP_COOKIE:
    engelsiz-uni+admin(020000006929103847732800000030313065653535393561663537623235393632376361336138383761333066346336316663623635;
    __utma 3322125.419203040.1165843329.1165843329.1165843329.1
    admin(11017): PATH_INFO: /engelsiz-uni/members/list
    admin(11017): HTTP_REFERER:
    http://mailman.metu.edu.tr/mailman/admin/engelsiz-uni/members/list
    admin(11017): PATH_TRANSLATED:
    /cwis/htdocs/mailman/engelsiz-uni/members/list
    admin(11017): REQUEST_URI: /mailman/admin/engelsiz-uni/members/list
    admin(12323): HTTP_COOKIE:
    engelsiz-uni+admin(020000006929103847732800000030313065653535393561663537623235393632376361336138383761333066346336316663623635;
    __utma 3322125.419203040.1165843329.1165843329.1165843329.1
    admin(12323): PATH_INFO: /engelsiz-uni/members/list
    admin(12323): HTTP_REFERER:
    http://mailman.metu.edu.tr/mailman/admin/engelsiz-uni/members/list
    admin(12323): PATH_TRANSLATED:
    /cwis/htdocs/mailman/engelsiz-uni/members/list
    admin(12323): REQUEST_URI: /mailman/admin/engelsiz-uni/members/list
    admin(15609): HTTP_COOKIE:
    engelsiz-uni+admin(020000006929103847732800000030313065653535393561663537623235393632376361336138383761333066346336316663623635;
    __utma 3322125.419203040.1165843329.1165843329.1165843329.1
    admin(15609): PATH_INFO: /engelsiz-uni/members
    admin(15609): HTTP_REFERER:
    http://mailman.metu.edu.tr/mailman/admin/engelsiz-uni/members
    admin(15609): PATH_TRANSLATED: /cwis/htdocs/mailman/engelsiz-uni/members
    admin(15609): REQUEST_URI: /mailman/admin/engelsiz-uni/members

    Is this all that's there? What I expect to see for one specific error
    is something like the following although with different specifics.

    Nov 13 20:45:08 2007 admin(1656):
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    admin(1656): [----- Mailman Version: 2.1.10a0 -----]
    admin(1656): [----- Traceback ------]
    admin(1656): Traceback (most recent call last):
    admin(1656): File "/cygdrive/f/test-mailman/scripts/driver", line
    101, in run_
    main
    admin(1656): main()
    admin(1656): File "/cygdrive/f/test-mailman/Mailman/Cgi/admin.py",
    line 197, i
    n main
    admin(1656): show_results(mlist, doc, category, subcat, cgidata)
    admin(1656): File "/cygdrive/f/test-mailman/Mailman/Cgi/admin.py",
    line 522, i
    n show_results
    admin(1656): form.AddItem(show_variables(mlist, category, subcat,
    cgidata, d
    oc))
    admin(1656): File "/cygdrive/f/test-mailman/Mailman/Cgi/admin.py",
    line 571, i
    n show_variables
    admin(1656): add_options_table_item(mlist, category, subcat, table,
    item)
    admin(1656): File "/cygdrive/f/test-mailman/Mailman/Cgi/admin.py",
    line 586, i
    n add_options_table_item
    admin(1656): val = get_item_gui_value(mlist, category, kind,
    varname, params
    , extra)
    admin(1656): File "/cygdrive/f/test-mailman/Mailman/Cgi/admin.py",
    line 617, i
    n get_item_gui_value
    admin(1656): raise "bogus error"
    admin(1656): bogus error
    admin(1656): [----- Python Information -----]
    admin(1656): sys.version = 2.5.1 (r251:54863, May 7 2007,
    17:32:04)
    [GCC 3.4.4 (cygming special) (gdc 0.12, using dmd 0.125)]
    admin(1656): sys.executable = /usr/bin/python
    admin(1656): sys.prefix = /usr
    admin(1656): sys.exec_prefix = /usr
    admin(1656): sys.path = /usr
    admin(1656): sys.platform = cygwin
    admin(1656): [----- Environment Variables -----]
    admin(1656): HTTP_REFERER: http://msapiro.net/mailman/admin/list1
    admin(1656): SERVER_SOFTWARE: Apache/1.3.33 (Cygwin)
    admin(1656): SCRIPT_NAME: /mailman/admin
    admin(1656): SERVER_SIGNATURE: <ADDRESS>Apache/1.3.33 Server at
    msapiro Port
    80</ADDRESS>
    admin(1656):
    admin(1656): REQUEST_METHOD: POST
    admin(1656): HTTP_KEEP_ALIVE: 300
    admin(1656): SERVER_PROTOCOL: HTTP/1.1
    admin(1656): QUERY_STRING:
    admin(1656): SYSTEMROOT: C:\WINDOWS
    admin(1656): CONTENT_LENGTH: 34
    admin(1656): HTTP_ACCEPT_CHARSET: ISO-8859-1,utf-8;q=0.7,*;q=0.7
    admin(1656): HTTP_USER_AGENT: Mozilla/5.0 (Windows; U; Windows NT
    5.1; en-US;
    rv:1.7.5) Gecko/20070321 Netscape/8.1.3
    admin(1656): TZ: PST8PDT7,M3.2.0/2,M11.1.0/2
    admin(1656): SERVER_NAME: msapiro
    admin(1656): REMOTE_PORT: 1133
    admin(1656): PATH_TRANSLATED: /var/www/htdocs/list1
    admin(1656): SERVER_PORT: 80
    admin(1656): SERVER_ADDR: 192.168.0.4
    admin(1656): DOCUMENT_ROOT: /var/www/htdocs
    admin(1656): PYTHONPATH: /cygdrive/f/test-mailman
    admin(1656): SCRIPT_FILENAME: /cygdrive/f/test-mailman/cgi-bin/admin
    admin(1656): SERVER_ADMIN: msapiro at value.net
    admin(1656): HTTP_HOST: msapiro.net
    admin(1656): HTTP_CONNECTION: keep-alive
    admin(1656): REQUEST_URI: /mailman/admin/list1
    admin(1656): HTTP_ACCEPT:
    application/x-shockwave-flash,text/xml,application/
    xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
    admin(1656): WINDIR: C:\WINDOWS
    admin(1656): GATEWAY_INTERFACE: CGI/1.1
    admin(1656): REMOTE_ADDR: 68.183.193.239
    admin(1656): HTTP_ACCEPT_LANGUAGE: en-us,en;q=0.5
    admin(1656): CONTENT_TYPE: application/x-www-form-urlencoded
    admin(1656): HTTP_ACCEPT_ENCODING: gzip,deflate
    admin(1656): UNIQUE_ID: Rzp9UsCoAAQAAAFgNu8
    admin(1656): PATH_INFO: /list1

    Do you not have something like this in the error log?


    By the way I still wonder why this problem occured, but i performed a
    quick ans dirty solution, I removed the list without deleting
    archives after listing the subscribers and opened again. subscribed
    subscribers, archive was OK.
    But I don't know whether this problem occurs again or not.

    Since the problem was with one list only, it was probably related to
    something in that list's configuration (config.pck) file. Now that you
    have removed and recreated the list, the problem no longer exists.

    The only hope for knowing what the problem was at this point is the
    error log information, assuming you have a complete log entry like the
    example above.

    If for some reason, your error log is missing the 90% of each log entry
    that you didn't include, then there is a problem with the logging some
    how, and we'll probably never know what the problem with the list was.

    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Liste yoneticisi at Feb 26, 2008 at 3:33 pm
    Hello;

    How can i divide the file "listname.mbox" in the directory
    "listname.mbox/" by day.

    I heard that it is possible as configuring listserver. But i couldn't find
    it.
    Can you help me?

    Thank you.

    Evrim AKMAN

    # The archive file structure by default is:
    #
    # archives/
    # private/
    # listname.mbox/
    # listname.mbox
    # listname/
    # lots-of-pipermail-stuff
    # public/
    # listname.mbox@ -> ../private/listname.mbox
    # listname@ -> ../private/listname



    ----------------
    Liste Yoneticisi
    http://e-list.cc.metu.edu.tr
    http://e-liste.bidb.odtu.edu.tr
  • Mark Sapiro at Feb 26, 2008 at 4:24 pm

    liste yoneticisi wrote:
    How can i divide the file "listname.mbox" in the directory
    "listname.mbox/" by day.

    Set up a cron job to run at daily at 23:59 and do something like

    #!/bin/bash
    suffix=`date +%Y%m%d`
    sleep 60
    if [[ -f /path/to/archives/private/listname.mbox/listname.mbox ]]
    then mv /path/to/archives/private/listname.mbox/listname.mbox \
    /path/to/archives/private/listname.mbox/listname.mbox.$suffix
    fi

    Although you'd probably want to break it into subdirectories by month
    and possibly year so as not to accumulate too many files in one
    directory.

    Moving the file aside is not a problem for the archiver which will just
    create a new one the next time it archives a message.

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Mark Sapiro at Feb 26, 2008 at 4:39 pm

    Mark Sapiro wrote:
    liste yoneticisi wrote:
    How can i divide the file "listname.mbox" in the directory
    "listname.mbox/" by day.

    Set up a cron job to run at daily at 23:59 and do something like

    #!/bin/bash
    suffix=`date +%Y%m%d`
    sleep 60
    if [[ -f /path/to/archives/private/listname.mbox/listname.mbox ]]
    then mv /path/to/archives/private/listname.mbox/listname.mbox \
    /path/to/archives/private/listname.mbox/listname.mbox.$suffix
    fi

    Although you'd probably want to break it into subdirectories by month
    and possibly year so as not to accumulate too many files in one
    directory.

    Moving the file aside is not a problem for the archiver which will just
    create a new one the next time it archives a message.

    I neglected to address
    I heard that it is possible as configuring listserver. But i couldn't find
    it.

    There is no configuration option for this. Perhaps you are thinking of
    the list's archive_volume_frequency which can be set to 'Daily' to
    create a new archive index and pseudo mbox .txt file on a daily basis.

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Liste yoneticisi at Feb 27, 2008 at 7:24 am
    On Tue, 26 Feb 2008, Mark Sapiro wrote:

    Mark Sapiro wrote:
    liste yoneticisi wrote:
    How can i divide the file "listname.mbox" in the directory
    "listname.mbox/" by day.

    Set up a cron job to run at daily at 23:59 and do something like

    #!/bin/bash
    suffix=`date +%Y%m%d`
    sleep 60
    if [[ -f /path/to/archives/private/listname.mbox/listname.mbox ]]
    then mv /path/to/archives/private/listname.mbox/listname.mbox \
    /path/to/archives/private/listname.mbox/listname.mbox.$suffix
    fi

    Although you'd probably want to break it into subdirectories by month
    and possibly year so as not to accumulate too many files in one
    directory.

    Moving the file aside is not a problem for the archiver which will just
    create a new one the next time it archives a message.

    I neglected to address
    I heard that it is possible as configuring listserver. But i couldn't find
    it.
    There is no configuration option for this. Perhaps you are thinking of
    the list's archive_volume_frequency which can be set to 'Daily' to
    create a new archive index and pseudo mbox .txt file on a daily basis.
    Thank you, you're right, that option divides

    /path/to/archives/private/listname/<TIME RELATED DIRECTORY>

    part. We configured as monthly, and using monarch.

    We are trying to use htdig in order to archive search, but for a long time
    (about months) we are unable to use it,

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Mark Sapiro at Feb 27, 2008 at 3:00 pm

    liste yoneticisi wrote:
    We configured as monthly, and using monarch.

    We are trying to use htdig in order to archive search, but for a long time
    (about months) we are unable to use it,

    Have you seen the various patches for Mailman/htDig integration and
    Mailman/MHonArc integration at <http://www.openinfo.co.uk/mm/>?

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Jim Popovitch at Feb 27, 2008 at 3:57 am

    On Tue, Feb 26, 2008 at 10:33 AM, liste yoneticisi wrote:
    Hello;

    How can i divide the file "listname.mbox" in the directory
    "listname.mbox/" by day.
    http://www.openinfo.co.uk/mm/patches/dailymbox/index.html

    hth,

    -Jim P.
  • Liste yoneticisi at Jul 20, 2009 at 10:26 am
    Hello;

    I have two main questions.

    First; We once asked about adding password reminder to private archive
    login page. We tried some modifications but couldn't succeed. I copied the
    previous correspondence below.

    """
    Can I put the password reminder on private archive login page? So that,
    list members who want to see the archive, but do not remember their
    passwords, can quickly learn their passwords. Otherwise, password
    reminder is too hard to find using the links on general list info page..

    This is a good idea. I think I'll implement it for Mailman 2.2.

    What needs to be done is the reminder button has to be added to the
    private.html archive login template and code needs to be added to
    Mailman/Cgi/private.py to recognize the button and send the reminder.

    You can look at Mailman/Cgi/options.py for how it's done there.
    """


    I have added the following lines to
    PATH/mailman/Mailman/Cgi/private.py

    "
    print Utils.maketext(
    'private.html',
    {'action' : Utils.websafe(action),
    'realname': mlist.real_name,
    'message' : message,
    }, mlist=mlist)
    return

    ### My Lines 7/4/2009 Eklenti baslangic

    if cgidata.has_key('emailpw'):
    mlist.MailUserPassword(user)
    options_page(
    mlist, doc, user, cpuser, userlang,
    _('A reminder of your password has been emailed to you.'))
    print doc.Format()
    return
    ### My Lines 7/4/2009 Eklenti bitis


    lang = mlist.getMemberLanguage(username)
    i18n.set_language(lang)
    doc.set_language(lang)

    # Authorization confirmed... output the desired file
    try:
    ctype, enc = guess_type(path, strict=0)

    "

    But nothing changed.:-(

    What else can we do about it?
    Mailman version is 2.1.9

    --------------------

    The second question is about vesion upgrade.

    Mailman, in our system, is running on Debian.
    Python version is 2.4.4

    I heard that 2.1.12 doesn't work properly on 2.4.4 but I am informed that
    the newer version of Python doesn't exist on Debian Package.
    It seems difficult to upgrade under these circumstances.

    What are the major differences between the Mailman versions 2.1.9 and
    2.1.12 with regard to security, usability?

    Thanks...
  • Mark Sapiro at Jul 21, 2009 at 3:20 am

    liste yoneticisi wrote:
    I have two main questions.

    First; We once asked about adding password reminder to private archive
    login page. We tried some modifications but couldn't succeed. I copied the
    previous correspondence below.

    """
    Can I put the password reminder on private archive login page? So that,
    list members who want to see the archive, but do not remember their
    passwords, can quickly learn their passwords. Otherwise, password
    reminder is too hard to find using the links on general list info page..

    This is a good idea. I think I'll implement it for Mailman 2.2.

    What needs to be done is the reminder button has to be added to the
    private.html archive login template and code needs to be added to
    Mailman/Cgi/private.py to recognize the button and send the reminder.

    You can look at Mailman/Cgi/options.py for how it's done there.
    """


    I have added the following lines to
    PATH/mailman/Mailman/Cgi/private.py

    "
    print Utils.maketext(
    'private.html',
    {'action' : Utils.websafe(action),
    'realname': mlist.real_name,
    'message' : message,
    }, mlist=mlist)
    return

    ### My Lines 7/4/2009 Eklenti baslangic

    if cgidata.has_key('emailpw'):
    mlist.MailUserPassword(user)
    options_page(
    mlist, doc, user, cpuser, userlang,
    _('A reminder of your password has been emailed to you.'))
    print doc.Format()
    return
    ### My Lines 7/4/2009 Eklenti bitis


    lang = mlist.getMemberLanguage(username)
    i18n.set_language(lang)
    doc.set_language(lang)

    # Authorization confirmed... output the desired file
    try:
    ctype, enc = guess_type(path, strict=0)

    "

    But nothing changed.:-(

    There are several things wrong with the above.

    You have copied the wrong code from options.py. That code processes the
    reminder button from the logged-in options page (I'm not sure why
    there is a reminder there, but the list admin could use it to send a
    reminder to the user). You want the code that follows the comment

    # Are we processing a password reminder from the login screen?

    but if you copy it verbatim as you did with the other, you'll have the
    problem that it calls the function loginpage() just as the above calls
    options_page() and those functions are local to the options.py module
    and undefined in private.py. You don't want to call either of those.

    The final problem is you've inserted your code in the wrong place. You
    put it where it is only reached if the user is already authenticated
    or provided a valid authentication.

    What else can we do about it?

    Find someone who knows some Python to do this for you.


    You can try the insert in the attached reminder.txt file, but note that
    this is untested and may cause problems.

    Mailman version is 2.1.9

    --------------------

    The second question is about vesion upgrade.

    Mailman, in our system, is running on Debian.
    Python version is 2.4.4

    I heard that 2.1.12 doesn't work properly on 2.4.4 but I am informed that
    the newer version of Python doesn't exist on Debian Package.
    It seems difficult to upgrade under these circumstances.

    What are the major differences between the Mailman versions 2.1.9 and
    2.1.12 with regard to security, usability?

    See
    <http://bazaar.launchpad.net/%7Emailman-coders/mailman/2.1/annotate/head%3A/NEWS>

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

    -------------- next part --------------
    An embedded and charset-unspecified text was scrubbed...
    Name: reminder.txt
    URL: <http://mail.python.org/pipermail/mailman-users/attachments/20090720/47ea6b2d/attachment-0001.txt>
  • Liste yoneticisi at Jul 23, 2009 at 11:37 am
    Dear Mr. Sapiro;

    Thank you very much for your quick response.

    Few months ago we made a list based modification in our "test" list.

    It can be seen here:
    http://mailman.metu.edu.tr/mailman/private/test
    -------------------------------------------------------------
    I am not very good at object oriented programming, and can hardly
    understand python
    scripts.

    But I am trying to understand the commands.
    I tried the text in the attachment also but as you warned, it didn't
    work.:-(

    -----------------------------------
    The final problem is you've inserted your code in the wrong place. You
    put it where it is only reached if the user is already authenticated
    or provided a valid authentication.
    -----------------------------------

    Actually if someone reached to the archive (in order to see attachments,
    messages for example) he probably had not logged into list archives
    page yet. He is asked to enter his e-mail and corresponding password.

    After submitting both correctly, the html form runs "private" script.
    <FORM METHOD=POST ACTION="$HOST/mailman/private/$LISTNAME"

    But as you mentioned;
    For the reminder form the necessary form action lines should be as
    follows:

    <FORM action="$HOST/mailman/options/$LISTNAME" method="POST" >
    <INPUT name="email" type="TEXT"> (*)
    <INPUT name="login-remind" type="SUBMIT" value="Remind" >

    There are three submit buttons in options page but the necessary one is
    named "login-remind".

    (*) It may not be necessary, since it is already written in archive
    authentication form. But the "private" script is reading the variables
    "username and password", but "option" script is reading the
    variable "email".

    -----------------------
    What needs to be done is the reminder button has to be added to the
    private.html archive login template and code needs to be added to
    Mailman/Cgi/private.py to recognize the button and send the reminder.
    -----------------------

    You also suggested that a remind button could be added to
    generic "private.html" externally.

    I tried that also (but the Turkish version.
    $MAILMAN_PATH/mailman/templates/tr/private.html)

    But it didn't have any effect.


    By the way;
    from the file "Mailman/Cgi/options.py"
    I copied the necessary lines as follows.

    # Password reminder section
    actionurl = mlist.GetScriptURL('options')

    form = Form(actionurl)
    table = Table(width='100%', border=0, cellspacing=4, cellpadding=5)

    table.AddRow([Center(Header(2, _('Password reminder')))])

    table.AddCellInfo(table.GetCurrentRowIndex(), 0,
    bgcolor=mm_cfg.WEB_HEADER_COLOR)

    table.AddRow([Label(_('Email address:')),
    TextBox('email', size )])

    table.AddRow([_("""By clicking on the <em>Remind</em> button, your
    password will be emailed to you.""")])

    table.AddRow([Center(SubmitButton('login-remind', _('Remind')))])
    # Finish up glomming together the login page

    -------------
    Do these lines work?
    Is it necessary to add html code to template/private.html also?

    Regards...
    ----------------
    Liste Yoneticisi
    http://e-list.cc.metu.edu.tr
    http://e-liste.bidb.odtu.edu.tr

    On Mon, 20 Jul 2009, Mark Sapiro wrote:

    Date: Mon, 20 Jul 2009 20:20:22 -0700
    From: Mark Sapiro <mark at msapiro.net>
    To: liste yoneticisi <listeyon at metu.edu.tr>,
    Mailman Users ML <mailman-users at python.org>
    Subject: Re: [Mailman-Users] Password reminder on private archive login page

    liste yoneticisi wrote:
    I have two main questions.

    First; We once asked about adding password reminder to private archive
    login page. We tried some modifications but couldn't succeed. I copied the
    previous correspondence below.

    """
    Can I put the password reminder on private archive login page? So that,
    list members who want to see the archive, but do not remember their
    passwords, can quickly learn their passwords. Otherwise, password
    reminder is too hard to find using the links on general list info page..

    This is a good idea. I think I'll implement it for Mailman 2.2.

    What needs to be done is the reminder button has to be added to the
    private.html archive login template and code needs to be added to
    Mailman/Cgi/private.py to recognize the button and send the reminder.

    You can look at Mailman/Cgi/options.py for how it's done there.
    """


    I have added the following lines to
    PATH/mailman/Mailman/Cgi/private.py

    "
    print Utils.maketext(
    'private.html',
    {'action' : Utils.websafe(action),
    'realname': mlist.real_name,
    'message' : message,
    }, mlist=mlist)
    return

    ### My Lines 7/4/2009 Eklenti baslangic

    if cgidata.has_key('emailpw'):
    mlist.MailUserPassword(user)
    options_page(
    mlist, doc, user, cpuser, userlang,
    _('A reminder of your password has been emailed to you.'))
    print doc.Format()
    return
    ### My Lines 7/4/2009 Eklenti bitis


    lang = mlist.getMemberLanguage(username)
    i18n.set_language(lang)
    doc.set_language(lang)

    # Authorization confirmed... output the desired file
    try:
    ctype, enc = guess_type(path, strict=0)

    "

    But nothing changed.:-(

    There are several things wrong with the above.

    You have copied the wrong code from options.py. That code processes the
    reminder button from the logged-in options page (I'm not sure why
    there is a reminder there, but the list admin could use it to send a
    reminder to the user). You want the code that follows the comment

    # Are we processing a password reminder from the login screen?

    but if you copy it verbatim as you did with the other, you'll have the
    problem that it calls the function loginpage() just as the above calls
    options_page() and those functions are local to the options.py module
    and undefined in private.py. You don't want to call either of those.

    The final problem is you've inserted your code in the wrong place. You
    put it where it is only reached if the user is already authenticated
    or provided a valid authentication.
  • Mark Sapiro at Jul 23, 2009 at 10:20 pm

    liste yoneticisi wrote:
    But I am trying to understand the commands.
    I tried the text in the attachment also but as you warned, it didn't
    work.:-(

    Yes, It had a few problems :(

    -----------------------------------
    The final problem is you've inserted your code in the wrong place. You
    put it where it is only reached if the user is already authenticated
    or provided a valid authentication.
    -----------------------------------

    Actually if someone reached to the archive (in order to see attachments,
    messages for example) he probably had not logged into list archives
    page yet. He is asked to enter his e-mail and corresponding password.

    My remark above referred to where in the logical flow of the private.py
    module you had put your code. It was not about how a user would arrive
    at the page.

    Since I had planned to look into this for Mailman 2.2 anyway, I have
    made a first cut at implementing this feature. The attached
    privatepw.patch.txt contains patches to Mailman/Cgi/private.py and
    templates/en/private.html to implement this feature. I have tested
    them and they seem OK.

    You're on your own for the Turkish version of the private.html template.

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

    -------------- next part --------------
    An embedded and charset-unspecified text was scrubbed...
    Name: privatepw.patch.txt
    URL: <http://mail.python.org/pipermail/mailman-users/attachments/20090723/ae8f994d/attachment.txt>
  • Liste yoneticisi at Jul 24, 2009 at 8:11 am
    Dear Mr Sapiro;

    Thank you very much, It worked for English archive interfaces.
    But it doesn't work for Turkish Interface.

    Altough I made completely the same modifications as English one.
    Is there another area to enforce the changes for international files?

    ----------------
    Liste Yoneticisi
    http://e-list.cc.metu.edu.tr
    http://e-liste.bidb.odtu.edu.tr

    On Thu, 23 Jul 2009, Mark Sapiro wrote:

    Date: Thu, 23 Jul 2009 15:20:41 -0700
    From: Mark Sapiro <mark at msapiro.net>
    To: liste yoneticisi <listeyon at metu.edu.tr>, mailman-users at python.org
    Subject: Re: Password reminder on private archive login page

    liste yoneticisi wrote:
    But I am trying to understand the commands.
    I tried the text in the attachment also but as you warned, it didn't
    work.:-(

    Yes, It had a few problems :(

    -----------------------------------
    The final problem is you've inserted your code in the wrong place. You
    put it where it is only reached if the user is already authenticated
    or provided a valid authentication.
    -----------------------------------

    Actually if someone reached to the archive (in order to see attachments,
    messages for example) he probably had not logged into list archives
    page yet. He is asked to enter his e-mail and corresponding password.

    My remark above referred to where in the logical flow of the private.py
    module you had put your code. It was not about how a user would arrive
    at the page.

    Since I had planned to look into this for Mailman 2.2 anyway, I have
    made a first cut at implementing this feature. The attached
    privatepw.patch.txt contains patches to Mailman/Cgi/private.py and
    templates/en/private.html to implement this feature. I have tested
    them and they seem OK.

    You're on your own for the Turkish version of the private.html template.

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Liste yoneticisi at Jul 24, 2009 at 8:42 am
    On Fri, 24 Jul 2009, liste yoneticisi wrote:

    Date: Fri, 24 Jul 2009 11:11:28 +0300 (WET)
    From: liste yoneticisi <listeyon at metu.edu.tr>
    To: Mark Sapiro <mark at msapiro.net>
    Cc: mailman-users at python.org
    Subject: Re: [Mailman-Users] Password reminder on private archive login page

    Dear Mr Sapiro;

    Thank you very much, It worked for English archive interfaces.
    But it doesn't work for Turkish Interface.

    Altough I made completely the same modifications as English one.
    Is there another area to enforce the changes for international files?

    Ooops. I made the changes in $PATH/templates/site/tr/private.html
    and it worked.
    I made the changes /template/tr/private.html

    It's mu fault.

    Thank you very much for your cooperation.


    ----------------
    http://e-list.cc.metu.edu.tr
    http://e-liste.bidb.odtu.edu.tr

    On Thu, 23 Jul 2009, Mark Sapiro wrote:

    Date: Thu, 23 Jul 2009 15:20:41 -0700
    From: Mark Sapiro <mark at msapiro.net>
    To: liste yoneticisi <listeyon at metu.edu.tr>, mailman-users at python.org
    Subject: Re: Password reminder on private archive login page

    liste yoneticisi wrote:
    But I am trying to understand the commands.
    I tried the text in the attachment also but as you warned, it didn't
    work.:-(

    Yes, It had a few problems :(

    -----------------------------------
    The final problem is you've inserted your code in the wrong place. You
    put it where it is only reached if the user is already authenticated
    or provided a valid authentication.
    -----------------------------------

    Actually if someone reached to the archive (in order to see attachments,
    messages for example) he probably had not logged into list archives
    page yet. He is asked to enter his e-mail and corresponding password.

    My remark above referred to where in the logical flow of the private.py
    module you had put your code. It was not about how a user would arrive
    at the page.

    Since I had planned to look into this for Mailman 2.2 anyway, I have
    made a first cut at implementing this feature. The attached
    privatepw.patch.txt contains patches to Mailman/Cgi/private.py and
    templates/en/private.html to implement this feature. I have tested
    them and they seem OK.

    You're on your own for the Turkish version of the private.html template.

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

    ------------------------------------------------------
    Mailman-Users mailing list
    Mailman-Users at 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/listeyon%40metu.edu.tr

    Security Policy: http://wiki.list.org/x/QIA9
  • Mark Sapiro at Jul 21, 2009 at 3:51 am

    liste yoneticisi wrote:
    I heard that 2.1.12 doesn't work properly on 2.4.4 but I am informed that
    the newer version of Python doesn't exist on Debian Package.
    It seems difficult to upgrade under these circumstances.

    There is a simple patch to the Python 2.4.4 lib/email/Charset.py at
    <http://launchpadlibrarian.net/23670138/Charset.py.patch> that will
    fix it for Mailman.

    Also see the comment thread at
    <https://bugs.launchpad.net/mailman/+bug/328353>.

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Gerrat Rickert at Jun 24, 2009 at 1:47 pm
    Recently, and in the past, when posting to a python mailing list (not
    this one specifically), my message has been indented and placed under
    the last message (of a completely unrelated post).
    -ie. it looks like I've hijacked a thread.

    I didn't however - I created a brand new email message (from scratch)
    and sent it to the list.
    Any ideas on how or why it would appear like I was responding to a
    completely unrelated post? (there was actually nothing I could even
    find in common on my subject line and the subject of the post where my
    message appeared indented under.)

    After reading the FAQ, and searching the archives, I couldn't find
    anything related to this, so I'll ask here.
    I would like to determine if this is a mailman-related issue in general,
    something specific with some mailman-run mailing lists that I post to,
    or a problem specifically related to our Outlook or Outlook Exchange
    setup.
    (...I was hoping for a different answer than the obvious "don't use
    Outlook")

    ...maybe, If I'm lucky, this message will hijack a thread, and the
    answer will be obvious to "the-powers-that-be".

    Thanks for any help
    Gerrat
  • Mark Sapiro at Jun 25, 2009 at 3:56 pm

    Gerrat Rickert wrote:
    Recently, and in the past, when posting to a python mailing list (not
    this one specifically), my message has been indented and placed under
    the last message (of a completely unrelated post).
    -ie. it looks like I've hijacked a thread.

    I assume you are talking about your message in the pipermail archive.
    If so, can you point at one such in the archives of a list?

    If you're talking about threading in your own MUA (mail client) that
    doesn't appear that way in the archive, then I don't think we can help.

    I didn't however - I created a brand new email message (from scratch)
    and sent it to the list.
    Any ideas on how or why it would appear like I was responding to a
    completely unrelated post? (there was actually nothing I could even
    find in common on my subject line and the subject of the post where my
    message appeared indented under.)

    Threading in the pipermail archive has nothing to do with the Subject:
    header. It is based on In-Reply-To: and/or References: headers.

    After reading the FAQ, and searching the archives, I couldn't find
    anything related to this, so I'll ask here.
    I would like to determine if this is a mailman-related issue in general,
    something specific with some mailman-run mailing lists that I post to,
    or a problem specifically related to our Outlook or Outlook Exchange
    setup.
    (...I was hoping for a different answer than the obvious "don't use
    Outlook")

    I'm not aware of any such issue in Mailman.

    ...maybe, If I'm lucky, this message will hijack a thread, and the
    answer will be obvious to "the-powers-that-be".

    Sorry, not in the list archive anyway. If there is an example in a
    public archive, please point to it.

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Gerrat Rickert at Jun 25, 2009 at 5:26 pm

    -----Original Message-----
    From: Mark Sapiro [mailto:mark at msapiro.net]
    Sent: Thursday, June 25, 2009 11:56 AM
    To: Gerrat Rickert; mailman-users at python.org
    Subject: Re: [Mailman-Users] Outlook Indenting messages

    Gerrat Rickert wrote:
    Recently, and in the past, when posting to a python mailing list (not
    this one specifically), my message has been indented and placed under
    the last message (of a completely unrelated post).
    -ie. it looks like I've hijacked a thread.

    I assume you are talking about your message in the pipermail archive.
    If so, can you point at one such in the archives of a list?
    <snip>

    Yes, this message:
    http://twistedmatrix.com/pipermail/twisted-python/2009-June/019859.html


    Thanks,
    Gerrat
  • Mark Sapiro at Jun 25, 2009 at 7:00 pm

    Gerrat Rickert wrote:

    -----Original Message-----
    From: Mark Sapiro [mailto:mark at msapiro.net]
    Sent: Thursday, June 25, 2009 11:56 AM
    To: Gerrat Rickert; mailman-users at python.org
    Subject: Re: [Mailman-Users] Outlook Indenting messages

    Gerrat Rickert wrote:
    Recently, and in the past, when posting to a python mailing list (not
    this one specifically), my message has been indented and placed under
    the last message (of a completely unrelated post).
    -ie. it looks like I've hijacked a thread.

    I assume you are talking about your message in the pipermail archive.
    If so, can you point at one such in the archives of a list?
    <snip>

    Yes, this message:
    http://twistedmatrix.com/pipermail/twisted-python/2009-June/019859.html

    I see the incorrect threading of the above message in the index
    <http://twistedmatrix.com/pipermail/twisted-python/2009-June>. I also
    see other threading anomalies in the same index.

    I downloaded the twisted-python.mbox/twisted-python.mbox file from
    twistedmatrix.com and built the May and June archive from it in a test
    2.1.9 Mailman. For example at the end of
    <http://twistedmatrix.com/pipermail/twisted-python/2009-June> I see

    ---------------------------------------------------------------
    # [Twisted-Python] untwisting twistd Jared Gisin
    + [Twisted-Python] untwisting twistd Phil Christensen
    + [Twisted-Python] untwisting twistd glyph at
    divmod.com
    + [Twisted-Python] untwisting twistd Phil Christensen
    * [Twisted-Python] untwisting twistd Alex Clemesha
    o [Twisted-Python] untwisting twistd Jared Gisin
    + [Twisted-Python] untwisting twistd Phil Christensen
    + [Twisted-Python] untwisting twistd Johan Rydberg
    # [Twisted-Python] twisted.web2 only can serve one connection at the
    same time when using scgi? Chris
    # [Twisted-Python] Fwd: SerialPort.loseConnection() in Win32,
    workaround biziap biziap
    * [Twisted-Python] Twisted Trial Gerrat Rickert
    o [Twisted-Python] Twisted Trial glyph at divmod.com
    + [Twisted-Python] Twisted Trial Gerrat Rickert
    # [Twisted-Python] adbapi and multiple queries in single transaction.
    Vishal Shetye
    + [Twisted-Python] adbapi and multiple queries in
    single transaction. Phil Christensen
    # [Twisted-Python] adbapi and multiple queries in single Vishal Shetye
    # [Twisted-Python] [ANN] Foolscap-0.4.2 released Brian Warner
    # [Twisted-Python] How to disable XMLRPC logging Dustin Land
    * [Twisted-Python] How to disable XMLRPC logging Jean-Paul
    Calderone
    ---------------------------------------------------------------

    and in the archive I built from the .mbox

    ---------------------------------------------------------------
    # [Twisted-Python] untwisting twistd Jared Gisin
    * [Twisted-Python] untwisting twistd Phil Christensen
    o [Twisted-Python] untwisting twistd glyph at divmod.com
    + [Twisted-Python] untwisting twistd Phil Christensen
    * [Twisted-Python] untwisting twistd Alex Clemesha
    o [Twisted-Python] untwisting twistd Jared Gisin
    + [Twisted-Python] untwisting twistd Phil Christensen
    * [Twisted-Python] untwisting twistd Johan Rydberg
    # [Twisted-Python] twisted.web2 only can serve one connection at the
    same time when using scgi? Chris
    # [Twisted-Python] Fwd: SerialPort.loseConnection() in Win32,
    workaround biziap biziap
    # [Twisted-Python] Twisted Trial Gerrat Rickert
    * [Twisted-Python] Twisted Trial glyph at divmod.com
    o [Twisted-Python] Twisted Trial Gerrat Rickert
    # [Twisted-Python] adbapi and multiple queries in single transaction.
    Vishal Shetye
    * [Twisted-Python] adbapi and multiple queries in single
    transaction. Phil Christensen
    # [Twisted-Python] adbapi and multiple queries in single Vishal Shetye
    # [Twisted-Python] [ANN] Foolscap-0.4.2 released Brian Warner
    # [Twisted-Python] How to disable XMLRPC logging Dustin Land
    * [Twisted-Python] How to disable XMLRPC logging Jean-Paul
    Calderone
    ---------------------------------------------------------------

    You can see in the twistedmatrix.com index two cases where the second
    post in a thread is indented to level 3 instead of level 1 which is
    clearly wrong. You can also see that in the archive I built, your
    thread starts at level 0 as it should.

    Also note that this apparently has nothing to do with Outlook.. There
    is a similarly indented post in early June -

    [Twisted-Python] Application Design help - Concurrent but not Protocols
    based. Senthil Kumaran

    and the posting MUA in that case was Mutt.

    Also see
    <http://twistedmatrix.com/pipermail/glyph-discuss/2009-May/thread.html>
    where the only two posts (spam) are both indented to level 1.

    Does this occur only on twistedmatrix.com lists? There is clearly
    something wrong with the archiving process on that site, but I can't
    duplicate it in a stock 2.1.9 environment.

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Gerrat Rickert at Jun 25, 2009 at 7:17 pm

    -----Original Message-----
    From: Mark Sapiro [mailto:mark at msapiro.net]
    Sent: Thursday, June 25, 2009 3:01 PM
    To: Gerrat Rickert; mailman-users at python.org
    Subject: RE: [Mailman-Users] Outlook Indenting messages

    Gerrat Rickert wrote:
    -----Original Message-----
    From: Mark Sapiro [mailto:mark at msapiro.net]
    Sent: Thursday, June 25, 2009 11:56 AM
    To: Gerrat Rickert; mailman-users at python.org
    Subject: Re: [Mailman-Users] Outlook Indenting messages

    Gerrat Rickert wrote:
    Recently, and in the past, when posting to a python mailing list
    (not
    this one specifically), my message has been indented and placed
    under
    the last message (of a completely unrelated post).
    -ie. it looks like I've hijacked a thread.

    I assume you are talking about your message in the pipermail archive.
    If so, can you point at one such in the archives of a list?
    <snip>

    Yes, this message:
    http://twistedmatrix.com/pipermail/twisted-python/2009-June/019859.htm
    l

    I see the incorrect threading of the above message in the index
    <http://twistedmatrix.com/pipermail/twisted-python/2009-June>. I also
    see other threading anomalies in the same index.

    I downloaded the twisted-python.mbox/twisted-python.mbox file from
    twistedmatrix.com and built the May and June archive from it in a test
    2.1.9 Mailman. For example at the end of
    <http://twistedmatrix.com/pipermail/twisted-python/2009-June> I see <snip>
    ---------------------------------------------------------------

    You can see in the twistedmatrix.com index two cases where the second
    post in a thread is indented to level 3 instead of level 1 which is
    clearly wrong. You can also see that in the archive I built, your
    thread starts at level 0 as it should.

    Also note that this apparently has nothing to do with Outlook.. There
    is a similarly indented post in early June -

    [Twisted-Python] Application Design help - Concurrent but not Protocols
    based. Senthil Kumaran

    and the posting MUA in that case was Mutt.

    Also see
    <http://twistedmatrix.com/pipermail/glyph-discuss/2009-May/thread.html>
    where the only two posts (spam) are both indented to level 1.

    Does this occur only on twistedmatrix.com lists? There is clearly
    something wrong with the archiving process on that site, but I can't
    duplicate it in a stock 2.1.9 environment.

    Thanks for your detailed investigation, Mark.
    I may have misremembered how a previous posting of mine was mis-indented
    (...postings were from a few years back, and it may have just been that
    my replies were shown at the top level instead of indented - I believe
    this may have been an old bug with Outlook specifically).

    I don't have any other examples from other mailing lists, so let's
    assume it's just the twistedmatrix.com list for now.
    I'll forward this thread to their mailing list administrator to
    investigate.

    Thanks again for your help.
    Regards,
    Gerrat
  • Grant Taylor at Jun 26, 2009 at 3:28 am

    Gerrat Rickert wrote:
    I may have misremembered how a previous posting of mine was
    mis-indented (...postings were from a few years back, and it may have
    just been that my replies were shown at the top level instead of
    indented - I believe this may have been an old bug with Outlook
    specifically).
    I don't know if it is related or not, but I have noticed a similar
    problem with my Mail <-> News gateway (included with Mailman).
    Specifically messages that I reply to the mailing list seem to loose the
    message ID of the immediate parent message and what should look like this:

    - first message
    + second message
    + third message

    Often

    - first message
    + second message
    + third message

    I have attributed this to the fact that Mailman either munges or out and
    out replaces the Message-ID.

    However, none of this is a hijacked thread as the Gerrat indicated.



    Grant. . . .
  • Mark Sapiro at Jun 26, 2009 at 3:18 pm

    Grant Taylor wrote:
    Gerrat Rickert wrote:
    I may have misremembered how a previous posting of mine was
    mis-indented (...postings were from a few years back, and it may have
    just been that my replies were shown at the top level instead of
    indented - I believe this may have been an old bug with Outlook
    specifically).
    I don't know if it is related or not, but I have noticed a similar
    problem with my Mail <-> News gateway (included with Mailman).
    Specifically messages that I reply to the mailing list seem to loose the
    message ID of the immediate parent message and what should look like this:

    - first message
    + second message
    + third message

    Often

    - first message
    + second message
    + third message

    I have attributed this to the fact that Mailman either munges or out and
    out replaces the Message-ID.

    I think this is unrelated to any of Gerrat's issues. Mailman does
    replace the Message-ID header in messages gated from a list to usenet.
    The reason for this is if a message is cross-posted to two Mailman
    lists, both of which gateway to usenet groups, the messages will be
    separately gated to the nntp server, and if they have the same
    Message-ID, the nntp server will ignore the second one it receives.

    This can lead to the issue above because messages posted to a list will
    have one Message-ID in the list archive and a different Message-ID on
    usenet. Suppose 'second message' above is a reply to 'first message'
    from the list. Its In-Reply-To: and References: headers reference the
    list Message-ID of 'first message and it is properly threaded in the
    list archive. Then 'third message' is a usenet reply to 'second
    message'. Since it is a usenet reply, its In-Reply-To: references the
    usenet Message-ID of 'second message' which is unknown to the list
    archive. Its References: header will reference the usnet Message-ID of
    'second message' and the list Message-ID of 'first message' from the
    References: header of 'second message'. Thus, when it gets archived,
    it is threaded as a reply to 'first message' since that is the only
    referenced Message-ID known to the archiver.

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Gerrat Rickert at Jul 27, 2009 at 3:22 pm

    -----Original Message-----
    From: Mark Sapiro [mailto:mark at msapiro.net]
    Sent: Thursday, June 25, 2009 11:56 AM
    To: Gerrat Rickert; mailman-users at python.org
    Subject: Re: [Mailman-Users] Outlook Indenting messages

    Gerrat Rickert wrote:
    Recently, and in the past, when posting to a python mailing list
    (not
    this one specifically), my message has been indented and placed
    under
    the last message (of a completely unrelated post).
    -ie. it looks like I've hijacked a thread.

    I assume you are talking about your message in the pipermail
    archive.
    If so, can you point at one such in the archives of a list?
    <snip>

    Yes, this message:
    http://twistedmatrix.com/pipermail/twisted-python/2009-June/019859.ht
    m
    l

    I see the incorrect threading of the above message in the index
    <http://twistedmatrix.com/pipermail/twisted-python/2009-June>. I also
    see other threading anomalies in the same index.

    I downloaded the twisted-python.mbox/twisted-python.mbox file from
    twistedmatrix.com and built the May and June archive from it in a test
    2.1.9 Mailman. For example at the end of
    <http://twistedmatrix.com/pipermail/twisted-python/2009-June> I see <snip>
    ---------------------------------------------------------------

    You can see in the twistedmatrix.com index two cases where the second
    post in a thread is indented to level 3 instead of level 1 which is
    clearly wrong. You can also see that in the archive I built, your
    thread starts at level 0 as it should.

    Also note that this apparently has nothing to do with Outlook.. There
    is a similarly indented post in early June -

    [Twisted-Python] Application Design help - Concurrent but not
    Protocols
    based. Senthil Kumaran

    and the posting MUA in that case was Mutt.

    Also see
    <http://twistedmatrix.com/pipermail/glyph-discuss/2009-May/thread.html
    where the only two posts (spam) are both indented to level 1.

    Does this occur only on twistedmatrix.com lists? There is clearly
    something wrong with the archiving process on that site, but I can't
    duplicate it in a stock 2.1.9 environment.

    Thanks for your detailed investigation, Mark.
    I may have misremembered how a previous posting of mine was
    mis-indented
    (...postings were from a few years back, and it may have just been that
    my replies were shown at the top level instead of indented - I believe
    this may have been an old bug with Outlook specifically).

    I don't have any other examples from other mailing lists, so let's
    assume it's just the twistedmatrix.com list for now.
    I'll forward this thread to their mailing list administrator to
    investigate.

    Thanks again for your help.
    Regards,
    Gerrat
    I have (a little) more info about this now, Mark (another list that this

    type of thing is happening on).

    This was a posting on the twisted-python mailing list (on which I had
    the
    indentation issue):
    I was reminded of this thread when I came across what appears to be the
    same bug on the Tahoe list:

    http://allmydata.org/pipermail/tahoe-dev/2009-July/thread.html

    Notice multiple posts in threads they don't look like they belong to, as
    well as many threads which have nonsensical levels of indentation.

    I'm not sure if anyone ever answered your question about twisted-
    python's mailman installation being "stock" or not. If not, then I
    think I can confirm that it is. There is also no configuration that
    would alter this behavior, as far as I know. We've probably set a few
    options via the admin interface, but I don't think any of those should
    affect this behavior.

    Jean-Paul
    The twisted python mailing list is running on:
    "unmodified mailman 1:2.1.9-9ubuntu1 install", and the
    Tahoe list is using: "2.1.9-4ubuntu1"

    Could this be an ubuntu-specific issue?

    Thanks,
    Gerrat
  • Mark Sapiro at Jul 27, 2009 at 6:40 pm
    This thread began in June at
    <http://mail.python.org/pipermail/mailman-users/2009-June/066410.html>
    and continued at
    <http://mail.python.org/pipermail/mailman-users/2009-June/066415.html>

    Gerrat Rickert wrote:
    I have (a little) more info about this now, Mark (another list that this
    type of thing is happening on).

    This was a posting on the twisted-python mailing list (on which I had
    the
    indentation issue):
    I was reminded of this thread when I came across what appears to be the
    same bug on the Tahoe list:

    http://allmydata.org/pipermail/tahoe-dev/2009-July/thread.html

    Notice multiple posts in threads they don't look like they belong to, as
    well as many threads which have nonsensical levels of indentation.

    I'm not sure if anyone ever answered your question about twisted-
    python's mailman installation being "stock" or not. If not, then I
    think I can confirm that it is. There is also no configuration that
    would alter this behavior, as far as I know. We've probably set a few
    options via the admin interface, but I don't think any of those should
    affect this behavior.

    Jean-Paul
    The twisted python mailing list is running on:
    "unmodified mailman 1:2.1.9-9ubuntu1 install", and the
    Tahoe list is using: "2.1.9-4ubuntu1"

    Could this be an ubuntu-specific issue?

    Ubuntu is based on Debian.

    I have just confirmed by testing that this problem is caused by the
    Debian Mailman patch "30_pipermail_threads.patch".

    This patch can be found by following the links from
    <http://patch-tracking.debian.net/package/mailman> (I don't want to
    give a more specific URL because the URLs below this level are
    unstable).

    Thus, the problem potentially exists in all Debian/Ubuntu Mailman
    packages. The patch attempts to fix Debian bug #167758
    <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug7758>, and it may
    do that, but it clearly breaks this.

    I'll try to report this to Debian.

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Barry Finkel at Jul 21, 2009 at 3:05 pm

    When I go to that URL I get a message:

    Internal Server Error


    ----------------------------------------------------------------------
    Barry S. Finkel
    Computing and Information Systems Division
    Argonne National Laboratory Phone: +1 (630) 252-7277
    9700 South Cass Avenue Facsimile:+1 (630) 252-4601
    Building 222, Room D209 Internet: BSFinkel at anl.gov
    Argonne, IL 60439-4828 IBMMAIL: I1004994
  • Mark Sapiro at Jul 21, 2009 at 3:41 pm

    Barry Finkel wrote:
    Mark wrote:
    When I go to that URL I get a message:

    Internal Server Error

    So do I. This is a Launchpad issue, and I was hoping it would work by
    the time anyone tried it. These things are usually transient.

    You can go to
    <http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/files> and
    click the 'download' icon at the far right of the 'NEWS' line to
    download the raw file. That at least seems to work.

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Barry Finkel at Jul 27, 2009 at 8:20 pm

    Mark Sapiro wrote:
    Ubuntu is based on Debian.

    I have just confirmed by testing that this problem is caused by the
    Debian Mailman patch "30_pipermail_threads.patch".

    This patch can be found by following the links from
    <http://patch-tracking.debian.net/package/mailman> (I don't want to
    give a more specific URL because the URLs below this level are
    unstable).

    Thus, the problem potentially exists in all Debian/Ubuntu Mailman
    packages. The patch attempts to fix Debian bug #167758
    <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug7758>, and it may
    do that, but it clearly breaks this.

    I'll try to report this to Debian.
    The bug report (dated 4 Nov 2002) states:

    Hi, pipermail screws up threading in case that two messages
    which were sent at the same time both start a new thread.
    New messages to either thread are then only listed below.

    The problem is that threadKey in a thread starting message
    is only a function of message Date, nothing else.

    It may not happen that often in human communication that
    two messages are written at the very same time, but it
    happens with a lot of cron generated output here.

    Does this problem exists in the SourceForge distribution?
    ----------------------------------------------------------------------
    Barry S. Finkel
    Computing and Information Systems Division
    Argonne National Laboratory Phone: +1 (630) 252-7277
    9700 South Cass Avenue Facsimile:+1 (630) 252-4601
    Building 222, Room D209 Internet: BSFinkel at anl.gov
    Argonne, IL 60439-4828 IBMMAIL: I1004994
  • Mark Sapiro at Jul 27, 2009 at 8:35 pm

    Barry Finkel wrote:
    The bug report (dated 4 Nov 2002) states:

    Hi, pipermail screws up threading in case that two messages
    which were sent at the same time both start a new thread.
    New messages to either thread are then only listed below.

    The problem is that threadKey in a thread starting message
    is only a function of message Date, nothing else.

    It may not happen that often in human communication that
    two messages are written at the very same time, but it
    happens with a lot of cron generated output here.

    Does this problem exists in the SourceForge distribution?

    Debian bug #167758 quoted above does exist in the SourceForge
    distribution, and the Debian patch 'fixes' it, but the cure may be
    worse than the disease.

    I will be looking at finding a fix that doesn't mess up indentation.

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Barry Finkel at Jul 28, 2009 at 3:31 pm

    "Gerrat Rickert" wrote:

    The twisted python mailing list is running on:
    "unmodified mailman 1:2.1.9-9ubuntu1 install", and the
    Tahoe list is using: "2.1.9-4ubuntu1"

    Could this be an ubuntu-specific issue?
    I have not included the initial part of this thread, as my reply
    is "generic". I have looked at Debian/Ubuntu packaging, and there
    are a large number of patches included in any Debian/Ubuntu Mailman
    package. There are fewer for 2.1.12 than for previous releases.

    A 2.1.9 package has 43 patches. A 2.1.5 package has 47 patches.
    When I was building my own Ubuntu package from the SourceForge source,
    I looked at each one of these patches. Most were undocumented; there
    was no reference to a Debian/Ubuntu bug number.
    The only one I kept was one that placed files in the "proper"
    directories for Ubuntu. When I looked at three security patches, I
    found that two matched the SourceForge code, but one differed.
    ----------------------------------------------------------------------
    Barry S. Finkel
    Computing and Information Systems Division
    Argonne National Laboratory Phone: +1 (630) 252-7277
    9700 South Cass Avenue Facsimile:+1 (630) 252-4601
    Building 222, Room D209 Internet: BSFinkel at anl.gov
    Argonne, IL 60439-4828 IBMMAIL: I1004994

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmailman-users @
categoriespython
postedSep 6, '06 at 5:05a
activeJul 28, '09 at 3:31p
posts41
users9
websitelist.org

People

Translate

site design / logo © 2022 Grokbase