Re: [Mailman-Users] Scheduled Administrative Option
At 10:46 PM -0400 2005-07-12, LifeTrek Coaching wrote: When will you add a Schedule feature to the Tend to Pending Moderator Requests sections? Right now there are only 4 options (Defer, Accept, Reject, Discard). There should be 5 (Defer, Accept, Reject, Discard, Schedule). The Schedule feature would enable you to Schedule the distribution of a post for a specific date and time. This would be an enormous improvement to the list functionality. Let me know. Thanks. That sounds like a good idea. Please feel free to file a Request For Enhancement at http://sourceforge.net/tracker/?group_id=103atid=350103. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Duplicate Unsubscribe Notifications
At 10:47 PM -0400 2005-07-12, LifeTrek Coaching wrote: When Mailman automatically removes a name from the list, I (as list owner and moderator) and receiving either 3 or 4 notices for each name that is removed. What is causing these multiple notices? How can I resolve the issue? Let me know. Thanks. It's hard to say. What's in your bounce and subscribe logs for these users? Have you looked closely at the headers of the duplicate messages you've received to see if they have the same Message-ID: header? Have you looked at the Received: headers on these duplicate messages, to see if they might have obviously been split and duplicated at some point? What's in your MTA logs? -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] How to search private archives
At 12:37 AM -0700 2005-07-13, Skip Taylor wrote: I understand there's a patch to allow searching private archives. The system I'm using has 2.1.5p1 I think. Can someone tell me where to find the patch(es)? Did you go to the Mailman FAQ Wizard at http://www.python.org/cgi-bin/faqw-mm.py and search for search? While you're at it, please check out http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq01.022.htp. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Emails Not Delivered, But Show Up In Archives
At 9:29 PM -0700 2005-07-12, Bradford Chang wrote: I'm having trouble narrowing down the source of this problem. But as of a couple days ago, all of the emails sent to my list have been showing up in the archives, but none of them have been delivered to the list members. Anyone have any ideas as far as what I should check... or maybe even a flat-out solution? :) Have you followed the guidance at http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.014.htp, or otherwise searched the Mailman FAQ Wizard for answers? -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Scheduled Administrative Option
Hi, Brad Knowles wrote: At 10:46 PM -0400 2005-07-12, LifeTrek Coaching wrote: When will you add a Schedule feature to the Tend to Pending Moderator Requests sections? Right now there are only 4 options (Defer, Accept, Reject, Discard). There should be 5 (Defer, Accept, Reject, Discard, Schedule). The Schedule feature would enable you to Schedule the distribution of a post for a specific date and time. This would be an enormous improvement to the list functionality. Let me know. Thanks. That sounds like a good idea. Please feel free to file a Request For Enhancement at http://sourceforge.net/tracker/?group_id=103atid=350103. Remember that current structure of mailman is not good at arbitrary scheduling. You may have to run a scheduling script every hour or so. It would be easier to use your PC (Windows or Linux) to send a message in a scheduled time. May be you can send a message with an Approved header and a confirm command with the confirmation string in the hold notice. Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Scheduled Administrative Option
My large list (40,000 names) is announcement only and all posts are held (to prevent the possibility of a spammer hijacking the list). So the Schedule option is the only one that would work. Simply scheduling when I send the post would not resolve the problem. May you be filled with goodness, peace, and joy. Bob Tschannen-Moran, Founder President LifeTrek Coaching International 121 Will Scarlet Lane Williamsburg, VA 23185-5043 Phone: (757) 345-3452 Fax: (772) 382-3258 Web: http://www.LifeTrekCoaching.com -Original Message- From: Tokio Kikuchi [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 13, 2005 7:13 AM To: Brad Knowles Cc: LifeTrek Coaching; mailman-users@python.org Subject: Re: [Mailman-Users] Scheduled Administrative Option Hi, Brad Knowles wrote: At 10:46 PM -0400 2005-07-12, LifeTrek Coaching wrote: When will you add a Schedule feature to the Tend to Pending Moderator Requests sections? Right now there are only 4 options (Defer, Accept, Reject, Discard). There should be 5 (Defer, Accept, Reject, Discard, Schedule). The Schedule feature would enable you to Schedule the distribution of a post for a specific date and time. This would be an enormous improvement to the list functionality. Let me know. Thanks. That sounds like a good idea. Please feel free to file a Request For Enhancement at http://sourceforge.net/tracker/?group_id=103atid=350103. Remember that current structure of mailman is not good at arbitrary scheduling. You may have to run a scheduling script every hour or so. It would be easier to use your PC (Windows or Linux) to send a message in a scheduled time. May be you can send a message with an Approved header and a confirm command with the confirmation string in the hold notice. Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Scheduled Administrative Option
In a flurry of recycled electrons, Tokio Kikuchi wrote: Remember that current structure of mailman is not good at arbitrary scheduling. You may have to run a scheduling script every hour or so. Seems like this already exists with qrunner. [knowing nothing about the internals..] If a message is 'scehduled' toss it into a different dierctory. At the same time, drop in a small file containing the time to send (a separate file should be lower overhead to open, and should have very little data.) Periodically check all these time-to-send files. Ought to be fairly trivial to impliment the sending portion. Don't know about the web pages, though. z! -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] List performance and server size
Hi everyone, I'm considering Mailman and I have been reading the FAQ and archives in search of an answer to my questions. I didn't have much luck and thought I would ask here. I have a client who needs to send out about 50,000 emails once a month via a one-way list. I'm considering installing Mailman on a Dell server with a 2.8 ghz Xeon processor, 1 GB ram and one 160 GB SATA IDE Hard drive. The OS would be FreeBSD. I'm not terribly strong in 'nix but I do have some experience with OpenBSD and I'm generally good at figuring out new things. Does anyone foresee any performance problems with my configuration? Will I have a lot of trouble installing Mailman on FreeBSD versus some other OS? Thanks for your help! -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] List performance and server size
At 11:03 AM -0500 2005-07-13, Dave Beckstrom wrote: I'm considering Mailman and I have been reading the FAQ and archives in search of an answer to my questions. I didn't have much luck and thought I would ask here. Hmm. That's a bad sign. Did you search the Mailman FAQ Wizard for performance? I have a client who needs to send out about 50,000 emails once a month via a one-way list. I'm considering installing Mailman on a Dell server with a 2.8 ghz Xeon processor, 1 GB ram and one 160 GB SATA IDE Hard drive. The OS would be FreeBSD. I'm not terribly strong in 'nix but I do have some experience with OpenBSD and I'm generally good at figuring out new things. Does anyone foresee any performance problems with my configuration? Will I have a lot of trouble installing Mailman on FreeBSD versus some other OS? For large mailing lists, RAM is a critical limiting factor, to a point. Whether or not your system will have enough RAM is hard to say. I'd be inclined to start with more, if possible. But it may turn out that you don't need all that RAM. This is one of those things where you take a guess (and you usually try to guess conservatively), and if things are obviously too bad then you revise the system configuration upward from there. After RAM, the next most important limiting factor is the disk I/O subsystem. On a busy server, ATA or EIDE drives do not cut the mustard -- not even SATA is good enough. You need SCSI. Not even with an intelligent drive controller will ATA or EIDE cut the mustard -- you need SCSI. An intelligent SCSI controller will be an improvement over standard SCSI drives, especially if you can configure it for a large amount of battery-backed write-back cache, and the drive array itself in a striped/striped or plaid RAID-1+0 configuration. The only question here is whether or not your system will be so busy that the ATA drives hurt you by so much that you are forced to replace them. It's impossible to answer that question a priori -- you may have to try it and find out. If at all possible, I would recommend replacing the drives in this configuration with SCSI, but that may not be possible. You're also going to need an improved filesystem, and FreeBSD is a good choice here, with more recent versions having soft updates enabled by default. You also need an MTA configured for maximum performance. It is possible to configure sendmail to extremely high levels of performance, but it takes a lot of work to do, and takes a fair amount of management to keep it there. Postfix works pretty well out-of-the-box for small to medium size lists, and there are a lot of knobs you can tune for further performance on larger lists. Operating system wise, I believe that FreeBSD is a good choice. It is my preferred choice, but of course that's a personal preference. One thing you generally don't need on a large mailing list server is CPU. Boxes with very slow CPUs but well-designed I/O subsystems will run circles around boxes with much faster CPUs but less well designed I/O subsystems. The problem is that pretty much all this information is already in the FAQ, with further information in the archives. So, if you searched for performance and you didn't find it then there is a bigger problem. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Scheduled Administrative Option
Carl Zwanzig said: In a flurry of recycled electrons, Tokio Kikuchi wrote: Remember that current structure of mailman is not good at arbitrary scheduling. You may have to run a scheduling script every hour or so. Seems like this already exists with qrunner. [knowing nothing about the internals..] If a message is 'scehduled' toss it into a different dierctory. At the same time, drop in a small file containing the time to send (a separate file should be lower overhead to open, and should have very little data.) Periodically check all these time-to-send files. Ought to be fairly trivial to impliment the sending portion. Don't know about the web pages, though. Wouldn't this be similiar in spirit to a monthly reminder email? (Set per-list, like some other list management software has--so moderators can send out, automagically, list-rules, etc. Right now, mailman doesn't have that feature.) --- The original portions of this message are the copyright of the author (c)1998-2004 Glenn E. Sieb.ICQ UIN: 300395IRC Nick: Rainbear All acts of Love and Pleasure are Her rituals-Charge of the Goddess -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] List performance and server size
Dave Beckstrom wrote: I have a client who needs to send out about 50,000 emails once a month via a one-way list. The unmentioned things here are, how fast to the emails have to leave the server and reach the users and how large are the emails? If the emails are relatively small, even a DSL line could get the emails out in a reasonable time frame. If they are large, and you have to get them out quickly, you could have some bandwidth issues. While 50,000 emails sounds like a lot, the fact you're only sending one email a month means you are probably wasting money throwing a mega server at it. I'm considering installing Mailman on a Dell server with a 2.8 ghz Xeon processor, 1 GB ram and one 160 GB SATA IDE Hard drive. The OS would be FreeBSD. At this time, I'm using a 733 pentium III with a 40gig ATA drive and 384 megs of ram. Its running FreeBSD 4.8, and it is running IPFW, NATD, DHCPD, NTPD, Squid, Apache, Postfix, and Mailman. It's hosting about 12 web sites (some of which are pretty active) and 15 mailing lists ranging from small to large (about 1,000), with activity all over the place. Most of the lists are interactive, not announcement lists. No performance issues. 15 mb of ram is still free, and only 147K of swap space has ever been used. We're using a slow 256kbps DSL line. The big hit is when on the first of the month all our subscribers get their Mailman reminders. The queue is clear before I get into the office at 8:00 AM. Mailman and Postfix installed pretty cleanly from the ports collection. I think in your shoes, I'd do a test run on a more modest server and see what the performance is like, and then look at where the actual bottlenecks are. FreeBSD is pretty friendly about being moved from one machine to another... just put your hard drive into a faster machine, make sure they have the same NIC and you can probably be running without having to change anything. I honestly suspect that your real performance hit will be list aging. From what I've read and seen, most lists, if they aren't maintained, have about 10% of their addresses go stale every month. That means you'll get about 5,000 bounces the first month. And handling bounces is a waste of bandwidth and system resources. I'd make sure you turn on VERP and prune aggressively. With only one mail going out a month, you have to use fairly aggressive pruning settings or the bad addresses will never age out. Look at the FAQs to see how to make Mailman work with your MTA and VERP. It took me about 1/2 a day with Postfix. (Because the system works so well, I don't have to tweak it often, so, despite using FreeBSD for years and years and the Mailman/Postfix combination for years, I'm still a perpetual newbie in FreeBSD, Mailman, and Postfix.) Mike -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Changing the path of cgi-bin
I've been asked to change the path from ~mailman/cgi-bin to ~mailman/something-else, the claim being security (and avoiding skript kiddies).Though, with the directory aliasing, I don't see where that makes a bit of difference. In my application, the httpd.conf is embedded such that it's run only to serve Mailman (stripped down). If you have /mailman aliased to /mailman/cgi-bin, then renaming it to something else doesn't seem like it will make any difference at all. But alas, I figured I'd ask and get some opinions first. Thanks -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Changing the path of cgi-bin
Forrest Aldrich said: I've been asked to change the path from ~mailman/cgi-bin to ~mailman/something-else, the claim being security (and avoiding skript kiddies).Though, with the directory aliasing, I don't see where that makes a bit of difference. I think what they're trying to avoid are scripts that search for a cgi-bin directory. If the directory is not cgi-bin, then their scripts will fail. My mailman scripts, for instance, live in /cgi-bin/mailman. ~P -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Changing the path of cgi-bin
Right, exactly. But what' the best way to do this with Mailman. Poster wrote: Forrest Aldrich said: I've been asked to change the path from ~mailman/cgi-bin to ~mailman/something-else, the claim being security (and avoiding skript kiddies).Though, with the directory aliasing, I don't see where that makes a bit of difference. I think what they're trying to avoid are scripts that search for a cgi-bin directory. If the directory is not cgi-bin, then their scripts will fail. My mailman scripts, for instance, live in /cgi-bin/mailman. ~P -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/forrie%40forrie.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Scheduled Administrative Option
Carl Zwanzig wrote: In a flurry of recycled electrons, Tokio Kikuchi wrote: Remember that current structure of mailman is not good at arbitrary scheduling. You may have to run a scheduling script every hour or so. Seems like this already exists with qrunner. [knowing nothing about the internals..] If a message is 'scehduled' toss it into a different dierctory. At the same time, drop in a small file containing the time to send (a separate file should be lower overhead to open, and should have very little data.) Periodically check all these time-to-send files. Ought to be fairly trivial to impliment the sending portion. Don't know about the web pages, though. z! Hi, Then you should do it for Mr. LifeTrek Coaching. ;-) I only wanted to say that my (or developers') priority would be lowest if an RFE is submitted in SF and it might be better to seek alternative solutions. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Changing the path of cgi-bin
On Wed, 2005-07-13 at 14:42 -0400, Forrest Aldrich wrote: Right, exactly. But what' the best way to do this with Mailman. Pick a new location of your chosing, move the cgi-bin directory to it, then edit your httpd ScriptAlias entry for mailman. -- John Dennis [EMAIL PROTECTED] -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Changing the path of cgi-bin
Are there any hard-coded dependencies upon the ~mailman/cgi-bin struct. John Dennis wrote: On Wed, 2005-07-13 at 14:42 -0400, Forrest Aldrich wrote: Right, exactly. But what' the best way to do this with Mailman. Pick a new location of your chosing, move the cgi-bin directory to it, then edit your httpd ScriptAlias entry for mailman. -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
