[ mailman-Bugs-714156 ] list_members fails on addresses with high-bit (?) characters

[SourceForge.net]

Bugs item #714156, was opened at 2003-04-02 15:18
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=714156&group_id=103

Category: command line scripts
Group: 2.1 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Cabel Sasser (cabelsa)
Assigned to: Nobody/Anonymous (nobody)
Summary: list_members fails on addresses with high-bit (?) characters

Initial Comment:
Version: Mailman 2.1.1

Dear Brilliant Mailman People,

I'm somewhat urgently trying to export lists from our old machine 
(which shuts down at the end of the week) to a brand new server.

I've created the lists on the new machine, and am trying to use 
list_members to export the people, so I can re-import them on 
the new box.

However, list_members is apparently failing on any address with 
high-bit ("funky") characters, and it appears we have quite a few 
out of our 100,000+ addresses.

Here's the error:

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)

Knowing absolutely nothing about Python, I put an extra "print" in 
that function to see what address it was dying on. Here it is:

[root at posh bin]# ./list_members transmit-e
000049941552520092563390-0001 at t-online.de
000049941552520092563390-0001 at t-online.de
007-orange at hanmail.net
007-orange at hanmail.net
[...]
1999818 at hitel.net
1999818 at hitel.net
1 at 1.com
1 at 1.com
1 at 1.ä??
Traceback (most recent call last):
  File "./list_members", line 234, in ?
    main()
  File "./list_members", line 209, in main
    s = formataddr((name, addr)).encode(enc, 'replace')
UnicodeError: ASCII decoding error: ordinal not in range(128)

So it looks like 1 at 1.ä[something] at least one problem address.

Is there any way I can work around this bug until an official 
update? 

Just deleting the problem members isn't as easy as it seems (the 
list is hardcoded to 'www.panic.com', and all the admin forms are 
pointing to that, but www.panic.com is now the new machine...)

Thanks for looking at this!

----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-04-03 00:40

Message:
Logged In: YES 
user_id=12800

Actually, I don't think this one's a duplicate.  660675
talks about "funny" characters in realnames, which should be
perfectly legal and Mailman should not choke on.  But your
message is about funny characters in email addresses, which
is not legal.

I don't know how, but it appears as though Mailman allowed
such bogus addresses into its member database.  This will
cause you pain, and such addresses should not be allowed. 
MM2.1.2 will disallow such addresses, but won't clean up
your existing member database.  Here's an article that might
help you with that:

http://article.gmane.org/gmane.mail.mailman.user/8487/match=find+members

----------------------------------------------------------------------

Comment By: Cabel Sasser (cabelsa)
Date: 2003-04-02 15:19

Message:
Logged In: YES 
user_id=665207

I apologize. This is a duplicate of bug #660675.

Search before you post a bug, Cabel. Jeez.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=714156&group_id=103