Shadow Members on List DB file

Bug #265706 reported by Vtkstef
2
Affects Status Importance Assigned to Milestone
GNU Mailman
Fix Released
Medium
Unassigned

Bug Description

I cannot list shadow members that exist on the DB file, and for
this reason I don't know how to remove them

I got this from the bounce log

Aug 01 05:41:01 2002 (6459) ICB: <email address hidden> -
first
Aug 01 07:11:02 2002 (6694) ICB: <email address hidden> - first
Aug 01 08:51:00 2002 (7070) ICB:
<email address hidden> - first
Aug 01 09:07:02 2002 (7127) ICB: <email address hidden> -
first
Aug 01 11:11:01 2002 (7862) Announce:
<email address hidden> - first
Aug 01 11:12:02 2002 (7867) announce: address
<email address hidden> not a member.

I looked for <email address hidden> using find_member and
list_members and I could not find it. I ran the list DB file through
the unix strings command, and I could see the addresses. I tried
looking for it using Mailman.MailList class using both
GetDelivery[Digest]Members and Get[Digest]Members methods,
and again I could not find them.

Please tell me how I can remove them!

Stefano

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

Revision history for this message
Vtkstef (vtkstef) wrote :
Revision history for this message
Dmick (dmick) wrote :

Bounces don't always come back with the subscriber's
subscribed address. You can use the regular-expression
search in the
membership-management web page to find an address that's
likely to be them, or you can use MM 2.1 to implement
VERP-style addressing, which can help find them.

My bounces are a lot more reliable now that I've hacked MM
to request VERP addressing from postfix; mis-labeled bounces
are unfortunately a fact of life in today's complex and
badly-administered email world.

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

We really need to know what version of Mailman you're
running. Some of the older 2.0.x series versions didn't
properly maintain consistency in the various member oriented
dictionaries. Your config.db file wasn't readable, so I
can't tell if that was your problem or not.

Revision history for this message
Vtkstef (vtkstef) wrote :

I am using version 2.0.5

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

That's fairly well out of date. I suggest upgrading to
MM2.0.13 and seeing if the problem persists.

Moving this to Pending to wait for an update.

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.