Bug 4933

Summary: Unable to subscribe to openicc list more mailman brokeness
Product: freedesktop.org Reporter: P Linnell <mrdocs>
Component: Mailing listsAssignee: fd.o Admin Massive <sitewranglers>
Status: CLOSED FIXED QA Contact:
Severity: major    
Priority: high    
Version: unspecified   
Hardware: x86 (IA32)   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description P Linnell 2005-10-31 07:40:42 UTC
Mails below copied:

I seem to be having trouble subscribing to the OpenICC mailing list.  I replied
to the confirmation email last week, but haven't received any mailing list
emails yet.  So, I tried subscribing again today, and used the HTML confirmation
link, but hit this bug:

Bug in Mailman version 2.1.5
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.


===========================================
Second mail received:


-------- Original Message --------
Subject: 	The results of your email commands
Date: 	Mon, 31 Oct 2005 06:35:18 -0800
From: 	openicc-bounces@lists.freedesktop.org
To: 	jefrey_c@airpost.net


The results of your email command are provided below. Attached is your
original message.

- Results:
    Ignoring non-text/plain MIME parts
    Invalid confirmation string.  Note that confirmation strings expire
approximately 3 days after the initial subscription request.  If your
confirmation has expired, please try to re-submit your original request or
message.

- Unprocessed:

    openicc-request@lists.freedesktop.org wrote:
    >Mailing list subscription confirmation notice for mailing list openicc
    >
    >We have received a request from 69.25.74.30 for subscription of your
    >email address, "jefrey_c@airpost.net", to the
    >openicc@lists.freedesktop.org mailing list.  To confirm that you want
    >to be added to this mailing list, simply reply to this message,
    >keeping the Subject: header intact.  Or visit this web page:
    >
    >   
http://lists.freedesktop.org/mailman/confirm/openicc/4f67af7544801ba8e2ae25a8c8ee9c280dfeb72a
    >
    >
    >Or include the following line -- and only the following line -- in a
    >message to openicc-request@lists.freedesktop.org:
    >
    >    confirm 4f67af7544801ba8e2ae25a8c8ee9c280dfeb72a
    >
    >Note that simply sending a `reply' to this message should work from
    >most mail readers, since that usually leaves the Subject: line in the
    >right form (additional "Re:" text in the Subject: is okay).
    >
    >If you do not wish to be subscribed to this list, please simply

- Ignored:
    >disregard this message.  If you think you are being maliciously
    >subscribed to the list, or have any other questions, send them to
    >openicc-owner@lists.freedesktop.org.
    >  
    >

- Done.

I have tested and confirm it happens to me too.
Comment 1 Stanislav Brabec 2005-11-28 21:30:57 UTC
Today I have experienced the same behavior.
Comment 2 Daniel Stone 2006-03-05 07:52:52 UTC
is this still going on?
Comment 3 Stanislav Brabec 2006-03-05 08:15:13 UTC
I don't know. My welcome mail from 2005-11-28 contains following text:

Manually added, as there is still something not right in mailman.
Comment 4 P Linnell 2006-03-05 09:21:15 UTC
Just retested. Still there. 


Bug in Mailman version 2.1.5

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. 
Comment 5 jimo 2006-03-18 12:11:26 UTC
Fwiw, I experienced the problem (unable to sub to openicc list) 
on March 15, 2006.  First time I've had a problem with Mailman. 
Comment 6 Daniel Stone 2006-03-19 10:21:06 UTC
fixified
Comment 7 P Linnell 2006-03-20 21:08:16 UTC
Thanks for the fix. Its working now.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.