Looks like a possible bug in 2.0.8. When I get a chance, I'll test out a 2.0.8 site that I run and see if it does the same. If it does, I'll compare the code and see if I can isolate it...
There was a message about two weeks ago that outlined the use ~mailman/bin/withlist. You should be able to use this to remove the errant entry manually from the database. Frankly I think it's easier to startup Python, and do it that way (make a copy of the database first...). Good Luck - I'm off to a Christmas party! Jon Carnes ----- Original Message ----- From: "Richard Idalski" <[EMAIL PROTECTED]> To: "Dan Mick" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, December 13, 2001 3:58 PM Subject: RE: [Mailman-Users] Bouncing address problems.... > And My very grievous oversight becomes apparent... well aside from hanging > my head in embarrassment, I now see that the db is not corrupt after all: > > [root@lists bin]# ./check_db affiliates > /home/mailman/lists/affiliates/config.db is fine > /home/mailman/lists/affiliates/config.db.last is fine > > So, what could we be looking at then? a problem with my configuration? a > bug? any ideas? > > > Thanks, > > Richard Idalski > > -----Original Message----- > From: Dan Mick [mailto:[EMAIL PROTECTED]] > Sent: Thursday, December 13, 2001 3:51 PM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: RE: [Mailman-Users] Bouncing address problems.... > > > > > Whoa... me thinks you're on to something, I'm running v2.08 which I > upgraded > > a few days ago. when i run chec_db on that particular db I get : > > > > > > root@lists bin]# ./check_db ../lists/affiliates/config.db > > /home/mailman/lists/../lists/affiliates/config.db/config.db cannot be > > opened: > > Not a directory > > /home/mailman/lists/../lists/affiliates/config.db/config.db.last cannot be > > opened: > > Not a directory > > Doesn't the fact that it issues a message with config.db listed > twice make you a little curious? Ypu gave the wrong args to > check_db. > > check_db's usage message (also in the top of the script): > > Usage: %(PROGRAM)s [options] [listname [listname ...]] > > Try > > cd ~mailman > bin/check_db affiliates > > > > > > ***** ALERT ***** > > Both the original database file and the backup seem > > corrupted. You will probably need to recover both > > /home/mailman/lists/../lists/affiliates/config.db/config.db > > and > > /home/mailman/lists/../lists/affiliates/config.db/config.db.last > > from a system backup, or remove the list `../lists/affiliates/config.db' > and > > re-create it from scratch. > > > > So It looks like I'l be recreating the list after all. > > > > One other thing I'm wondering is that this address is getting these errors > > fro multiple lists that it's on. Could they all eb corrupt? If so what > could > > cause multiple lists to be corrupt? > > > > Thanks Again, > > > > Richard Idalski > > > > > > > > > > > > -----Original Message----- > > From: Jon Carnes [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, December 13, 2001 3:28 PM > > To: Richard Idalski; [EMAIL PROTECTED] > > Subject: Re: [Mailman-Users] Bouncing address problems.... > > > > > > This is either a bug or an error in your config file. What version of > > Mailman are your running? Have run > > ~mailman/bin/check_db ~mailman/lists/<listname>/config.db > > > > ??? > > > > Jon Carnes > > ----- Original Message ----- > > From: "Richard Idalski" <[EMAIL PROTECTED]> > > To: "Jon Carnes" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > Sent: Thursday, December 13, 2001 3:20 PM > > Subject: RE: [Mailman-Users] Bouncing address problems.... > > > > > > > Thanks for the idea, I tried that and after removing them from the list > > and > > > looking at the db dump, the addres is still in the bounce info section, > > but > > > not in the members section... I know you can't edit the db's dirctly, so > > how > > > would I go about taking this address out of the bounce info? > > > > > > Thanks, > > > > > > Richard Idalski > > > > > > -----Original Message----- > > > From: Jon Carnes [mailto:[EMAIL PROTECTED]] > > > Sent: Thursday, December 13, 2001 3:12 PM > > > To: Richard Idalski; [EMAIL PROTECTED] > > > Subject: Re: [Mailman-Users] Bouncing address problems.... > > > > > > > > > To stop sending mail to a bouncing address Mailman simply actives the > > nomail > > > option for the offending address; however, at that point Mailman *does > > not* > > > erase or zero out the bounces from the database. The bounce record is > > still > > > in the database in the bounce_info{ } section. So it is likely that one > > > more bounce and the user will again be moved over to nomail. > > > > > > Removing the user from the list however *does* remove the info from the > > > bounce_info section (I just checked, using Mailman version 2.06). > > > > > > You should check your database. Indeed you might need to recreate it. > > > > > > For now, look at the database using: > > > ~mailman/bin/dumpdb ~mailman/lists/<listname>/config.db |more > > > > > > and look for the user. You will find them under "bounce_ info". Now > > remove > > > the user (go to the web-admin / Membership management / and remove the > > first > > > check mark next to their name / click on the "Submit Your Changes" > button > > at > > > the bottom of the page). > > > > > > Now dumpout the database and look again. Is the user still in the > > > members{ } section? Are they still in the bounce_info{ } section? > > > > > > Hope this helps - Jon Carnes > > > ----- Original Message ----- > > > From: "Richard Idalski" <[EMAIL PROTECTED]> > > > To: <[EMAIL PROTECTED]> > > > Sent: Thursday, December 13, 2001 1:57 PM > > > Subject: [Mailman-Users] Bouncing address problems.... > > > > > > > > > > > > > > Alright, I've got a problem here with an email address bouncing that > > > > shouldn't be. > > > > Here are the results of the bounce log: > > > > > > > > > > > > Dec 13 10:35:49 2001 (7197) List-Name: [EMAIL PROTECTED] - > > exceeded > > > > limits > > > > Dec 13 10:35:49 2001 (7197) List-Name: already disabled > > > > [EMAIL PROTECTED] > > > > > > > > > > > > Alright now, I've looked in the membership managament section of the > UI, > > > > and the 'nomail' option is NOT checked for this address. > > > > > > > > I've tried unsubscribing this address and re-adding it to the lists, > all > > > to > > > > no avail, it comes back up with the exceeded limits error. Where can > I > > > > re-enable this account, my next step will be to completey delete and > > > > re-create the list, but short of this what can I do? > > > > > > > > > > > > -Richard Idalski > > > > > > > > > > > > ------------------------------------------------------ > > > > Mailman-Users maillist - [EMAIL PROTECTED] > > > > http://mail.python.org/mailman/listinfo/mailman-users > > > > > > > > > > > > ------------------------------------------------------ > > > Mailman-Users maillist - [EMAIL PROTECTED] > > > http://mail.python.org/mailman/listinfo/mailman-users > > > > > > > > ------------------------------------------------------ > > Mailman-Users maillist - [EMAIL PROTECTED] > > http://mail.python.org/mailman/listinfo/mailman-users > ------------------------------------------------------ Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
