FAQ
Hi all

When a user wants to subscribe to my mailinglist, the user gets the
confirmation mail, to confirm the subscription.

Then, when the user just replies to the mail (using thunderbird), the
list administrator (me) gets a mail that says, a new user subscribed to
the mailing list, but when I go to the backend (administration), the
user is not in the list of recipients!

If the user clicks on the link in the confirmation mail and confirms the
subscription in the web form, he appears in the recipients list!

I didn't find any report in the web about users having the same problem..

can someone help me?

best regards
Till

PS: I had the same problem subscribing to this mailing list, may be it's
me.. :-/ when I replied to the message nothing happened, and when I
confirmed on the webpage, I got the confirmation back immediately..

Search Discussions

  • Mark Sapiro at May 9, 2010 at 9:58 pm

    Till Kleisli wrote:
    When a user wants to subscribe to my mailinglist, the user gets the
    confirmation mail, to confirm the subscription.

    Then, when the user just replies to the mail (using thunderbird), the
    list administrator (me) gets a mail that says, a new user subscribed to
    the mailing list, but when I go to the backend (administration), the
    user is not in the list of recipients!

    Prior to Mailman 2.1.10, there was a bug in cmd_confirm.py that could
    throw a UnicodeError exception in processing a confirmation email. It
    would confirm the subscription which sends the admin notice and then
    throw the exception in scanning the message body. This would cause
    CommandRunner to not save the updated list.

    You should find errors and tracebacks in Mailman's error log.

    If this is the problem, this patch (or upgrading Mailman) will fix it.

    --- Mailman/Commands/cmd_confirm.py 2005-12-30 18:50:08 +0000
    +++ Mailman/Commands/cmd_confirm.py 2008-02-18 18:48:16 +0000
    @@ -90,8 +90,11 @@
    match = 'confirm ' + cookie
    unprocessed = []
    for line in res.commands:
    - if line.lstrip() == match:
    - continue
    + try:
    + if line.lstrip() == match:
    + continue
    + except UnicodeError:
    + pass
    unprocessed.append(line)
    res.commands = unprocessed
    # Process just one confirmation string per message


    PS: I had the same problem subscribing to this mailing list, may be it's
    me.. :-/ when I replied to the message nothing happened, and when I
    confirmed on the webpage, I got the confirmation back immediately..

    I just successfully subscribed and confirmed a subscription to this
    list by email, so I don't see a problem there.

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Till Kleisli at May 14, 2010 at 11:17 am
    Hi Mark

    Thank you for the hint.

    I informed my hosting provider about this and hope, he will update
    mailman, at the moment he's still running 2.1.5...

    Unfortunately I can't do it by myself.

    About the registration to this list, everything went fine, the mail just
    had some delay.. :)

    Till
    On 09.05.2010 23:58, Mark Sapiro wrote:
    Till Kleisli wrote:
    When a user wants to subscribe to my mailinglist, the user gets the
    confirmation mail, to confirm the subscription.

    Then, when the user just replies to the mail (using thunderbird), the
    list administrator (me) gets a mail that says, a new user subscribed to
    the mailing list, but when I go to the backend (administration), the
    user is not in the list of recipients!

    Prior to Mailman 2.1.10, there was a bug in cmd_confirm.py that could
    throw a UnicodeError exception in processing a confirmation email. It
    would confirm the subscription which sends the admin notice and then
    throw the exception in scanning the message body. This would cause
    CommandRunner to not save the updated list.

    You should find errors and tracebacks in Mailman's error log.

    If this is the problem, this patch (or upgrading Mailman) will fix it.

    --- Mailman/Commands/cmd_confirm.py 2005-12-30 18:50:08 +0000
    +++ Mailman/Commands/cmd_confirm.py 2008-02-18 18:48:16 +0000
    @@ -90,8 +90,11 @@
    match = 'confirm ' + cookie
    unprocessed = []
    for line in res.commands:
    - if line.lstrip() == match:
    - continue
    + try:
    + if line.lstrip() == match:
    + continue
    + except UnicodeError:
    + pass
    unprocessed.append(line)
    res.commands = unprocessed
    # Process just one confirmation string per message


    PS: I had the same problem subscribing to this mailing list, may be it's
    me.. :-/ when I replied to the message nothing happened, and when I
    confirmed on the webpage, I got the confirmation back immediately..

    I just successfully subscribed and confirmed a subscription to this
    list by email, so I don't see a problem there.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmailman-users @
categoriespython
postedMay 8, '10 at 10:57p
activeMay 14, '10 at 11:17a
posts3
users2
websitelist.org

2 users in discussion

Till Kleisli: 2 posts Mark Sapiro: 1 post

People

Translate

site design / logo © 2022 Grokbase