bounce_info corrupt

Bug #265569 reported by Bug Importer
2
Affects Status Importance Assigned to Milestone
GNU Mailman
Invalid
Medium
Unassigned

Bug Description

I am running Mailman 2.0.6 on a Compaq Tru64 UNIX 5.1
system.

I created a list, ms-adm, which seemed to go fine.

When I tried to add a list of users on the adminstrator
membership management page, while the users were
subscribed, eg. list admins received a subscription
notification mail message, and the users show us as
members using the list_members command, they never got
a welcome message with their password.

This problem seems to be intermittent, I added two
users at the outset and they got a welcome message with
their password, but when I entered a larger group (17
users) they seemed to be added, but never got the
welcome message.

In addition, when I do a dumpdb, I see entries foreach
of this second group of users which look like:

'bounce_info': { '<email address hidden>':
[1004707923.71, 2.0, 2.0],
                       '<email address hidden>':
[1004707923.17, 2.0, 2.0],...

One of the users I added was <email address hidden>, another
was <email address hidden>.

During list adminstration, I never changed any of the
bounce options.

Also, if these users go to the listinfo page
enter their address, <email address hidden> for instance, and
click "edit options" they see <email address hidden>,
rather than <email address hidden>.

This is the _only_ list I'm having problems with.

It seems I should only have the list administrators in
the bounce_info variables, or is that an incorrect
assumption? How can I fix the database?
I am unsure of the python syntax.

Any suggestions?

-- Bob Benites

[http://sourceforge.net/tracker/index.php?func=detail&aid=477529&group_id=103&atid=100103]

Revision history for this message
Bug Importer (bug-importer) wrote :

When I tried to enter my E-mail address, my browser crashed.
The above post was made by <email address hidden>

Revision history for this message
Barry Warsaw (barry) wrote :

All this has been significantly rewritten for MM2.1, so I'm
closing this bug as out-of-date.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.