[Mailman-Users] problem after upgrading to 2.1

[Jon Carnes]

Have you tried a ~mailman/bin/dumpdb on the config.pck for the list.  It
would dump out the users - multiple times: once for language, once for
members, once for passwords, and once for user options.

You might even be able to pin-point the problem point.

Good Luck - Jon Carnes

On Wed, 2003-02-05 at 23:10, Scott R. Every wrote:
> 
> 
> --On Wednesday, February 5, 2003 10:41 PM -0500 Jon Carnes <jonc at nc.rr.com> 
> wrote:
> 
> > I suggest that you need to check the configuration of the file
> > (~mailman/bin/check_db). I believe the error indicates that while
> 
> this was done for both the original db and the newly imported db created 
> from the list_members program in 2.0.x.  Both checked out OK.
> 
> > reading the config.pck file (and dumping out the member names) that it
> > found values that are not Ascii.
> 
> How would one go about tracking this down?  i cannot really view the list 
> with the list_member tool and the web access is far too slow to be of use.
> 
> any python wizards out there who could shed more light on the error below?
> 
> 
> >
> > The list is large enough that you could have had a problem in the
> > upgrade.
> >
> > Good Luck - Jon Carnes
> 
> Thanks for the advice.
> 
> s
> 
> >
> > On Wed, 2003-02-05 at 11:59, Scott R. Every wrote:
> >> After upgrading, I am now getting the following error using list_members:
> >> Traceback (most recent call last):
> >>   File "./list_members", line 232, in ?
> >>     main()
> >>   File "./list_members", line 207, in main
> >>     s = formataddr((name, addr)).encode(enc, 'replace')
> >> UnicodeError: ASCII decoding error: ordinal not in range(128)
> >>
> >> This happens whether I use the existing config.db file or if I use
> >> list_members from 2.0.x to dump all the users, then use add_members to
> >> add  them to a new list.  Again, list_members works as expected under
> >> 2.0.x, but  not under 2.1.  Has anyone seen this before?  Does anyone
> >> know of any  workarounds?
> >>
> >> I need list_members to be working for arbitrary list splitting.
> >>
> >> The list has almost 600k members which may be causing the problem, but
> >> it  worked fine in 2.0.x.  Any help would be appreciated.
> >>
> >> Thanks
> >>
> >> s
> >>
> >> Scott R. Every   mailto:scott at blast.com
> >> Blast Inc.       http://www.blast.com
> >> 1-800-24-BLAST   ext 543
> >>
> >> ------------------------------------------------------
> >> Mailman-Users mailing list
> >> Mailman-Users at 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/
> >>
> >> This message was sent to: jonc at nc.rr.com
> >> Unsubscribe or change your options at
> >> http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com
> >
> 
>