[Mailman-Users] List Copy

I need to move 1 list from one server to another server. Which files do I need to copy, I already have mailman setup and running on the new server. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/

Re: [Mailman-Users] Enable moderated list to always accept someemails?

Matt England wrote: >At 8/11/2006 08:57 PM, Brad Knowles wrote: >> >>You could have the mail2forum software add an appropriate "Approved:" >>header to the message, and that would go through. > >Ok, so I've researched how to do this (and it appears as simple as adding >an "Approved: " header to th

Re: [Mailman-Users] Message IDs & Security

At 10:23 PM + 2006-08-23, Jon Loose wrote: > On looking at the downloadable archives, the message ids are very long > indeed (over 100 characters). I took a look at the same file for this > list, and the ids seem shorter. Is there any way to get shorter message > ids? Not without changi

Re: [Mailman-Users] Spam avoidance, revisited: best practices?

At 11:52 AM -0500 2006-08-23, Patrick Bogen wrote: > I think he meant: auto-moderate new users, and unmoderate them after > some amount of time has passed (e.g., after a day or after a week) No, there is no built-in automated method of doing that. You could configure the list so that new subs

Re: [Mailman-Users] Enable moderated list to always accept some emails?

At 8/11/2006 08:57 PM, Brad Knowles wrote: >At 5:57 PM -0500 2006-08-11, Matt England wrote: > > > I want to enable a moderated list (that moderates emails from non > > subscribers) to always accept email that comes with a certain header > > attached (in this case, a header appended by http://ma

Re: [Mailman-Users] Spam avoidance, revisited: best practices?

At 8/23/2006 11:20 AM, Brad Knowles wrote: >At 11:20 PM -0500 2006-08-22, Matt England wrote: > > > This is the best email I have yet to find describing how mail.python.org > > proactive kills spam: > > > > http://mail.python.org/pipermail/python-list/2006-March/332443.html > >I've also got an a

Re: [Mailman-Users] Message IDs & Security

Jon Loose wrote: > >On looking at the downloadable archives, the message ids are very long indeed >(over 100 characters). I took a look at the same file for this list, and the >ids seem shorter. Is there any way to get shorter message ids? (This is just >a cosmetic issue as regards reading th

Re: [Mailman-Users] Spam avoidance, revisited: best practices?

On 8/23/06 1:18 PM, "Dragon" <[EMAIL PROTECTED]> wrote: > Matt England sent the message below at 12:14 8/23/2006: >> At 8/23/2006 11:52 AM, Patrick Bogen wrote: >> >>> I think he meant: auto-moderate new users, and unmoderate them after >>> some amount of time has passed (e.g., after a day or aft

Re: [Mailman-Users] setting moderator password with command line

Alan Holmes wrote: >Is there a way to set the moderator password with one of the command line >tools, or by setting an option in a config file and using the config_list >-i. See . You could also create a withlist script for

Re: [Mailman-Users] Miscreant "moderator request(s) waiting" messages

Mark Sapiro wrote: >> The next day, I got the same message - 77 moderator request(s) >> waiting. Go to the moderator webpage, no outstanding requests. > > Short answer - You have two different crontabs running cron/checkdbs > from two different mailman installations. [EMAIL PROTECTED]:/home/list

Re: [Mailman-Users] Miscreant "moderator request(s) waiting" messages

Craig Box wrote: > >The next day, I got the same message - 77 moderator request(s) waiting. >Go to the moderator webpage, no outstanding requests. Short answer - You have two different crontabs running cron/checkdbs from two different mailman installations. -- Mark Sapiro <[EMAIL PROTECTED]>

Re: [Mailman-Users] How to set moderator passwd via 'config_list'?

Matt England wrote: >Is there a way to set a list's moderator password via the 'config_list -i' >command? My mailman admin has yet to see a reference in the 'config_list >-o' output. Yes and no. You can set any list attribute via input to config_list. For example your input file could contai

Re: [Mailman-Users] Message IDs & Security

On Wed, Aug 23, 2006 at 10:23:08PM +, Jon Loose wrote: > I have just set up a new mailman list, which is working well. Thanks > to the developers for this software. Very useful indeed. > > On looking at the downloadable archives, the message ids are very long > indeed (over 100 characters).

[Mailman-Users] Message IDs & Security

I have just set up a new mailman list, which is working well. Thanks to the developers for this software. Very useful indeed. On looking at the downloadable archives, the message ids are very long indeed (over 100 characters). I took a look at the same file for this list, and the ids seem sh

[Mailman-Users] setting moderator password with command line

Is there a way to set the moderator password with one of the command line tools, or by setting an option in a config file and using the config_list -i. I basically want to set the moderator password without having to go into the web interface. Alan --

[Mailman-Users] setting moderator password with command line

Is there a way to set the moderator password with one of the command line tools? -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Sea

[Mailman-Users] Miscreant "moderator request(s) waiting" messages

I've just migrated a Mailman list from one host to another, by copying the data, archives and lists dir as suggested in the FAQ section 3.4. There were some configuration problems with the last machine, so I didn't get a lot of messages to -owner, and a lot of bounce messages. When I ended up with

Re: [Mailman-Users] Client wants unique archiving method

On Aug 23, 2006, at 4:02 PM, Dragon wrote: > They are on crack. And you really don't want to get into this can > of worms. I'm not saying it couldn't be done, but it is not > something that would be easy nor reliable. See below for the full > explanation. Thanks for the quick and (very) de

Re: [Mailman-Users] Spam avoidance, revisited: best practices?

Matt England sent the message below at 12:14 8/23/2006: >At 8/23/2006 11:52 AM, Patrick Bogen wrote: > > >I think he meant: auto-moderate new users, and unmoderate them after > >some amount of time has passed (e.g., after a day or after a week) > >Yes, that's correct. > >Can Mailman do the above (a

Re: [Mailman-Users] Client wants unique archiving method

Andrew Jones sent the message below at 11:23 8/23/2006: >I just moved a client to Dreamhost from another provider where they >also had a Mailman discussion list. > >Everything is working at Dreamhost, but they have a strange request. >They want all original posts to go to all subscribers as normal.

Re: [Mailman-Users] Spam avoidance, revisited: best practices?

At 8/23/2006 11:52 AM, Patrick Bogen wrote: >I think he meant: auto-moderate new users, and unmoderate them after >some amount of time has passed (e.g., after a day or after a week) Yes, that's correct. Can Mailman do the above (auto-moderate new users, and then automatically un-moderate them a

Re: [Mailman-Users] Spam avoidance, revisited: best practices?

* Matt England: > I'm also considering adding these capabilities (which may or may not be > implicit in the above description) to combat spam: > > * Don't allow email from non-subscribers > * Moderate email from new subscribers some period of time (probably a day > to a week) I've compiled a fe

[Mailman-Users] Mailman extension - Web compsition and templates

Are there any know ways to extend mailman to add ConstantContact.Com type features such as Browser based email composition, Newsletter Templates, View Tracking, etc.? Thank you, -Steve -- Mailman-Users mailing list Mailman-Users@python.org ht

[Mailman-Users] Client wants unique archiving method

I just moved a client to Dreamhost from another provider where they also had a Mailman discussion list. Everything is working at Dreamhost, but they have a strange request. They want all original posts to go to all subscribers as normal. BUT, they want all replies to ONLY go to the original

Re: [Mailman-Users] Spam avoidance, revisited: best practices?

On 8/23/06, Brad Knowles <[EMAIL PROTECTED]> wrote: > > I'm also considering adding these capabilities (which may or may not be > > implicit in the above description) to combat spam: > > > > * Don't allow email from non-subscribers > > * Moderate email from new subscribers some period of time (

[Mailman-Users] How to set moderator passwd via 'config_list'?

Is there a way to set a list's moderator password via the 'config_list -i' command? My mailman admin has yet to see a reference in the 'config_list -o' output. We basically want to set the moderator password without having to go into the web interface. -Matt -

Re: [Mailman-Users] Spam avoidance, revisited: best practices?

At 11:20 PM -0500 2006-08-22, Matt England wrote: > This is the best email I have yet to find describing how mail.python.org > proactive kills spam: > > http://mail.python.org/pipermail/python-list/2006-March/332443.html I've also got an article that will be going up soon on the LOPSA.org web

Re: [Mailman-Users] Spam avoidance, revisited: best practices?

Matt England wrote: > At 8/23/2006 06:43 AM, Oleg D. wrote: > >>> This is the best email I have yet to find describing how >>> mail.python.org proactive kills spam: >>> >>> http://mail.python.org/pipermail/python-list/2006-March/332443.html >>> >>> I'm also considering adding these capabilities (

Re: [Mailman-Users] Spam avoidance, revisited: best practices?

>This is the best email I have yet to find describing how mail.python.org >proactive kills spam: > >http://mail.python.org/pipermail/python-list/2006-March/332443.html > >I'm also considering adding these capabilities (which may or may not be >implicit in the above description) to combat spam: >

Re: [Mailman-Users] Spam avoidance, revisited: best practices?

At 8/23/2006 06:43 AM, Oleg D. wrote: >>This is the best email I have yet to find describing how mail.python.org >>proactive kills spam: >> >>http://mail.python.org/pipermail/python-list/2006-March/332443.html >> >>I'm also considering adding these capabilities (which may or may not be >>implici