[Mailman-Users] Ask create list question

Dear sir or madan, I just try to installthe mailman-2.1.9 and it looks work but when I want to creat a new list it alway show "Error: You are not authorized to create new mailing lists" I use the command "bin/mmsitepass xx" twice and creat the new list via web ui but it still shwo the same

[Mailman-Users] Mailman 2.2.x - If and When?

One last question :) I need to know whether to tell my Mailman server admins to apply the patch now or maybe hold out for 2.2.x. So is 2.2.x happening ( the site says it might not. ), and if so, whats the ETA for the release? Brandon ---Original Message--- [EMAIL PROTECTED] wrote: > >Is ther

Re: [Mailman-Users] Mailman 2.2.x - If and When?

At 5:08 AM -0800 12/13/06, <[EMAIL PROTECTED]> wrote: > I need to know whether to tell my Mailman server admins to apply the > patch now or maybe hold out for 2.2.x. So is 2.2.x happening ( the > site says it might not. ), and if so, whats the ETA for the release? I'm sure that 2.2.x will happ

Re: [Mailman-Users] Ask create list question

[EMAIL PROTECTED] wrote: >I just try to installthe mailman-2.1.9 and it looks work but when I want >to creat a new list >it alway show "Error: You are not authorized to create new mailing lists" > >I use the command "bin/mmsitepass xx" twice and creat the new list via >web ui but >it still

Re: [Mailman-Users] Mailman 2.2.x - If and When?

Brad Knowles wrote: >At 5:08 AM -0800 12/13/06, <[EMAIL PROTECTED]> wrote: > >> I need to know whether to tell my Mailman server admins to apply the >> patch now or maybe hold out for 2.2.x. So is 2.2.x happening ( the >> site says it might not. ), and if so, whats the ETA for the release? > >I

[Mailman-Users] Case-Sensitivity Problem?

To all, I recently had a member (an administrator and moderator, no less) whose message was bounced. Their moderation bit is not set, and in addition to being the list administrator, they are an undigested member. However, they recently had a message held for moderator approval. I cannot se

Re: [Mailman-Users] Case-Sensitivity Problem?

Quoting Ryan Steele ([EMAIL PROTECTED]): > From reading the docs, I thought that (for list membership purposes), > the email addresses were case insensitive, thus complying with RFC 822. RFC 822 says that the part before the @ sign *can* be case sensitive. So the behavour you're seeing is all

Re: [Mailman-Users] Case-Sensitivity Problem?

I think I've actually identified the problem. Here is an excerpt from the mail header: >Received: from [EMAIL PROTECTED] > by imo-m26.mx.aol.com (mail_out_v38_r7.6.) id e.cef.43ab224 (57293); > Wed, 13 Dec 2006 09:41:44 -0500 (EST) >From: [EMAIL PROTECTED] >Message-ID: <[EMAIL PR

Re: [Mailman-Users] Case-Sensitivity Problem?

Ryan Steele wrote: > >I recently had a member (an administrator and moderator, no less) whose >message was bounced. Their moderation bit is not set, and in addition >to being the list administrator, they are an undigested member. >However, they recently had a message held for moderator approva

Re: [Mailman-Users] Case-Sensitivity Problem?

At 2:00 PM -0500 12/13/06, Ryan Steele wrote: > Here is an excerpt from the mail header: > >> Received: from [EMAIL PROTECTED] >> by imo-m26.mx.aol.com (mail_out_v38_r7.6.) id e.cef.43ab224 (57293); >> Wed, 13 Dec 2006 09:41:44 -0500 (EST) >> From: [EMAIL PROTECTED] >> Messag

Re: [Mailman-Users] Case-Sensitivity Problem?

Ryan Steele wrote: >I think I've actually identified the problem. I don't think so. >Here is an excerpt from the mail header: > >>Received: from [EMAIL PROTECTED] >> by imo-m26.mx.aol.com (mail_out_v38_r7.6.) id e.cef.43ab224 (57293); >> Wed, 13 Dec 2006 09:41:44 -0500 (EST) >

[Mailman-Users] Mailman on Mac OS X Server 10.3: Outgoing messages stuck in qrunner/in folder

Hi, I am running Mailman on an Xserve running Mac OS X Server 10.3.9. The version of Mailman is the one included with Mac OS X Server 10.3.9. (It's 2.1.2.) I've just started experimenting with mailing lists on this server using Mailman. Things worked fine until I actually got to the stage

Re: [Mailman-Users] Mailman on Mac OS X Server 10.3: Outgoing messagesstuck in qrunner/in folder

Pierre Igot wrote: > >I am running Mailman on an Xserve running Mac OS X Server 10.3.9. The >version of Mailman is the one included with Mac OS X Server 10.3.9. >(It's 2.1.2.) See >I've just started experimenting with ma

Re: [Mailman-Users] Mailman on Mac OS X Server 10.3: Outgoing messagesstuck in qrunner/in folder

On 06-12-13, at 19:31, Mark Sapiro wrote: > Pierre Igot wrote: >> >> I am running Mailman on an Xserve running Mac OS X Server 10.3.9. The >> version of Mailman is the one included with Mac OS X Server 10.3.9. >> (It's 2.1.2.) > > > See >

[Mailman-Users] User unsubscribing

I'm still using mm 2.1.5, still trying to get my ISP to pay attention . . . Anyway: I can test my E-list in various ways, because I'm subscribed from a couple of addresses, in addition to adminning it from the E-address you're getting this from. So: this afternoon I unsubscribed myself, using lyn

Re: [Mailman-Users] User unsubscribing

At 6:35 PM -0500 12/13/06, Alan McConnell wrote: > But when I went back to check: there "I" am, still a member. > > My question: how can that happen? The web page may have been cached at a proxy between you and the server, or it may be cached internally to your web browser. Try doing a force

Re: [Mailman-Users] Mailman on Mac OS X Server 10.3: Outgoing messagesstuck in qrunner/in folder

Pierre Igot wrote: >On 06-12-13, at 19:31, Mark Sapiro wrote: > >> Pierre Igot wrote: >>> >>> I am running Mailman on an Xserve running Mac OS X Server 10.3.9. The >>> version of Mailman is the one included with Mac OS X Server 10.3.9. >>> (It's 2.1.2.) >> >> >> See >>

Re: [Mailman-Users] Mailman on Mac OS X Server 10.3: Outgoingmessagesstuck in qrunner/in folder

Mark Sapiro wrote: >Pierre Igot wrote: > >>On 06-12-13, at 19:31, Mark Sapiro wrote: >> >>> Pierre Igot wrote: I am running Mailman on an Xserve running Mac OS X Server 10.3.9. The version of Mailman is the one included with Mac OS X Server 10.3.9. (It's 2.1.2.) >>> >>> >>> See