Barry Warsaw wrote:
On Mon, 2003-03-17 at 15:15, Chuq Von Rospach wrote:
This gave me an idea, since I had a list with a binary email address
(how? add_members of a directory instead of a file in the directory.
oops).
Oh, I should point out one other thing. I fixed Mailman cvs so that it
wo
On Mon, 2003-03-17 at 15:15, Chuq Von Rospach wrote:
> This gave me an idea, since I had a list with a binary email address
> (how? add_members of a directory instead of a file in the directory.
> oops).
Oh, I should point out one other thing. I fixed Mailman cvs so that it
would reject non-a
On Mon, 2003-03-17 at 15:15, Chuq Von Rospach wrote:
> This gave me an idea, since I had a list with a binary email address
> (how? add_members of a directory instead of a file in the directory.
> oops).
Here's a thought: since find_members takes a regular expression, you
could do something li
This gave me an idea, since I had a list with a binary email address
(how? add_members of a directory instead of a file in the directory.
oops).
Here's what I did:
dumpdb config.db
this gave me the "\x00\x0c\x." version of the string.
I cut and pasted that into a quickie perl scr
Thanks, Jon. This worked (when I chose a character other than "X" which
apparently had special meaning in the pickle!).
Jon Carnes wrote:
The easiest way I've found to do this is to stop Mailman from running
and then use a hex editor to edit the binary directly (change the out of
range value to a
The easiest way I've found to do this is to stop Mailman from running
and then use a hex editor to edit the binary directly (change the out of
range value to an standard Ascii value). Note, that Mailman stores the
email names in several places within the database.
It would be great if someone wou
(Context: Mailman 2.1.1) I have a list with a single corrupt address in
it. The address string contains a \xa0 character. Routines which access
the address list fail with errors like
Traceback (most recent call last):
File "/var/mailman/bin/list_members", line 232, in ?
main()
File "/var
