Re: [Mailman-Users] Mail going to qfiles/shunt

2005-05-08 Thread Tokio Kikuchi
Oh, Yes! The fix should appear soon in anonymous CVS and viewcvs. http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/ Brad Knowles wrote: > At 9:42 PM +0900 2005-05-08, Tokio Kikuchi wrote: > > >> I think I could track this down. I used Unicode{En|De}codeError but >> they are introduced in

Re: [Mailman-Users] Mail going to qfiles/shunt

2005-05-08 Thread Brad Knowles
At 9:42 PM +0900 2005-05-08, Tokio Kikuchi wrote: > I think I could track this down. I used Unicode{En|De}codeError but > they are introduced in Python2.3. It should be UnicodeError and this > catches both encode ande decode errots. I've updated CVS with this fix > for Decorate.py and cmd_s

Re: [Mailman-Users] Mail going to qfiles/shunt

2005-05-08 Thread Tokio Kikuchi
John W. Baxter wrote: > On 5/7/05 4:45 AM, "Brad Knowles" <[EMAIL PROTECTED]> wrote: > >>Mailman 2.1.5 required Python 2.3, but in theory this was >>supposed to be fixed in Mailman 2.1.6, easing the restriction back >>down to Python 2.1. > > Which would imply that Barry's new email module is goo

Re: [Mailman-Users] Mail going to qfiles/shunt

2005-05-07 Thread John W. Baxter
On 5/7/05 4:45 AM, "Brad Knowles" <[EMAIL PROTECTED]> wrote: > Mailman 2.1.5 required Python 2.3, but in theory this was > supposed to be fixed in Mailman 2.1.6, easing the restriction back > down to Python 2.1. Which would imply that Barry's new email module is good back at least to Python 2.1.

Re: [Mailman-Users] Mail going to qfiles/shunt

2005-05-07 Thread Larry Hansford
At 07:45 AM 5/7/2005, Brad Knowles wrote: At 11:49 PM -0400 2005-05-06, Larry Hansford wrote: I got it working. I upgraded from Python 2.2.3 to Python 2.3.5 and reinstalled Mailman, and it began working. Mailman 2.1.5 required Python 2.3, but in theory this was supposed to be fixed in M

Re: [Mailman-Users] Mail going to qfiles/shunt

2005-05-07 Thread Brad Knowles
At 11:49 PM -0400 2005-05-06, Larry Hansford wrote: > I got it working. I upgraded from Python 2.2.3 to Python 2.3.5 > and reinstalled Mailman, and it began working. Mailman 2.1.5 required Python 2.3, but in theory this was supposed to be fixed in Mailman 2.1.6, easing the restriction

Re: [Mailman-Users] Mail going to qfiles/shunt

2005-05-06 Thread Larry Hansford
At 04:57 PM 5/6/2005, Tokio Kikuchi wrote: Larry Hansford wrote: > I installed the Mailman 2.1.6rc3, and it tested okay. But, messages > sent to previously existing lists all go to /home/mailman/files/shunt, > and are not delivered. Is this a rights problem? I ran check_perms, > and it did not

Re: [Mailman-Users] Mail going to qfiles/shunt

2005-05-06 Thread Tokio Kikuchi
Larry Hansford wrote: > I installed the Mailman 2.1.6rc3, and it tested okay. But, messages > sent to previously existing lists all go to /home/mailman/files/shunt, > and are not delivered. Is this a rights problem? I ran check_perms, > and it did not find any errors. Hi, Since 2.1.6rc3 i

[Mailman-Users] Mail going to qfiles/shunt

2005-05-06 Thread Larry Hansford
I installed the Mailman 2.1.6rc3, and it tested okay. But, messages sent to previously existing lists all go to /home/mailman/files/shunt, and are not delivered. Is this a rights problem? I ran check_perms, and it did not find any errors. Thanks! Larry --