Jon Carnes wrote:
Hmmm.... Now that is a good question!Yes I did try that, and no it didn't work.
I assume you tried copying the heldmsg files back into the data
directory and then running the web-admindb (and that didn't work?)
If so then try sending a message to the list that would be held forThat doesn't work either. My messages still appear in the admindb webpage and get approved rather than the ones in the data directory that I replaced.
moderation and then replace the heldmsg-...pck file that is created with
one of the ones you copied off (just renaming it). Then approve the
moderated message and see if that does the job proper.
If that doesn't work, you can use the strings command to find who sentHad to resort to this one, unfortunately.
the message and drop them a note asking them to resend the message.
Cheers, Stephan
Good Luck (and let us know what happens!)
On Fri, 2003-02-21 at 18:53, Stephan Spencer wrote:
Thanks for that, Jon.
I am indeed running 2.1.
I tried deleting held messages but that didn't work. I'm still getting a low-level error:
Feb 21 17:38:44 2003 admin(32190): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
admin(32190): [----- Mailman Version: 2.1 -----]
admin(32190): [----- Traceback ------]
admin(32190): Traceback (most recent call last):
admin(32190): File "/usr/local/mailman/scripts/driver", line 87, in run_main
I deleted request.db and it works fine now. I've made backups of the 15 or so legitimate held messages (heldmsg-bnb-list-xxx.pck).
How do I get those back into request.db?
Thanks, Stephan
On Saturday, February 22, 2003, at 04:54 AM, Jon Carnes wrote:
What version of Mailman are you using? (it looks like one of the 2.1.x versions).
Hope you have already fixed this by now, but just in case, here is
something you can try. Look in the data directory for Mailman - this is
where the held messages are stored. You can actually scan the heldmsg
files manually and delete ones that might be overly large.
cd /usr/local/mailman/data ls -l
The default message format in version 2.1 is pickle (instead of text), but you can still easily look at each held message by using the strings command ("strings" is a utility that used to be loaded by default, if you don't have it loaded it's very easy to find).
strings heldmsg-b2b-list-1.pck
Deleting the heldmsg's here does not delete them from your lists "request.db" file, but when you run admindb for the list, that will compare the heldmsg files to the ones in request.db and then update request.db (the handling of the request.db file is a lot smarter in version 2.1 of Mailman).
In other words,once you launch the Web-admindb everything should sync up
and you will just see the messages you left that need approving. It
*should* work at this point. <assuming that problem was a bad email and
you deleted the bad email>
If not, I recommend removing that lists request.db file: /usr/local/mailman/lists/b2b-list/request.db
Just rename the file to something else and then try launching the web-admindb again.
Good Luck - Jon Carnes
------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
