--On March 19, 2007 6:19:00 PM -0700 Mark Sapiro <[EMAIL PROTECTED]> wrote:
> Presumably the new installation is a 2.1.x installation, not 2.0.x, so > you can't just move the queue entries because they're not compatible > (in 2.1 there is a single .pck file per msg as opposed to the 2.0 .db > and .msg files). IIRC, the incoming message is plain text in the .msg > file, so using bin/inject on the new system to inject these into the > 'in' queue for the list, although tedious, may be easier than anything > else. (with luck, the list is an addressee so you can get that from > the .msg without having to get it from the metadata in the associated > .db). To which I reply: It's interesting -- the old installation was a 2.1.4 install, so I don't know there are both a .db and a .msg file for each message. At any rate, when I looked just now, there were 150 pairs of .db and .msg files, and all but one had been flagged as SPAM, so I used bin/inject with the one .msg file, and sh*t-canned the rest of the files. Thanks for the confirmation that that was what I needed to do. -- Steve Burling <mailto:[EMAIL PROTECTED]> University of Michigan, ICPSR Voice: +1 734 615.3779 330 Packard Street FAX: +1 734 647.8700 Ann Arbor, MI 48104-2910 ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
