Re: customizing debian apache
On Thu, 8 Nov 2001, Matt Hope wrote: fairly tidy. An alternative would be patching suexec to accept a run-time path (from what I gather, this is non-trivial) The apache-common package comes with some suexec source. But I am not sure why -- since it is unusable because it is missing several more headers. Anyways, I often use sed to patch suexec: $ cat -v sed.expression s/\/home\/httpd\/html/\/home^@^@^@^@^@^@^@^@^@^@^@/ Jeremy C. Reed .. ISP-FAQ.com -- find answers to your questions http://www.isp-faq.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mailing Lists
On Thu, Nov 08, 2001 at 01:59:51PM +, Martin WHEELER wrote:
On Thu, 8 Nov 2001, Andre Luis Lopes wrote:
Em Qui 08 Nov 2001 10:19, Craigsc escreveu:
We are wanting to set-up a mailing list for our clients and were
wondering which program(s) we should use. At present our mail is
handled by exim.
exim should be adequate for small-medium mail loads.
for larger mail loads, try something more robust scalable like
postfix.
I did it sometime ago and I've used mailman which is quite easy to
use and powerfull, but I'm not an ISP so people in the list would
help you best.
I *am* an ISP, and after messing around with quite a few list managers
eventually settled on mailman as being the best solution for my
situation. (Lazy admin with lots of lists :)
me too (that is, i work as senior system admin at an ISP), except i
settled on listar majordomo...not because they're great but because
they suck the least for my needs.
i'm also an even lazier admin because (following the perl truism that
Laziness is a Virtue) i wrote scripts to automate creation of lists so
that i don't have to work very hard to admin them. :)
a day of fairly interesting work writing scripts three years ago plus a
few days maintaining them and adding features since then has saved me
literally weeks of tedious boredom in manual administration of mailing
lists.
It's worth it for the web-based administration and archiving alone.
mailman's web based admin is fine if you like that kind of thing, and
it is a pretty good list manager in general, but its archiving really
sucks. it produces something that is *almost* an mbox file but is just
different enough that it can't be read or used by any tool that handles
mbox files, e.g. mailgrep, mutt, pine, elm, etc etc etc.
the really annoying thing about it is that a) it has been a known bug
for years, and b) it would be trivial to fix if they could be bothered.
the problem is in the From_ line, the pipermail script uses a bogus Date
format that confuses mbox-capable programs.
the correct date format IS documented...see the mbox(5) man page:
The date is expected to be formatted according to the fol
lowing syntax (represented in the augmented Backus-Naur
formalism used by RFC 822):
mbox-date= weekday month day time [ timezone ] year
weekday = Mon / Tue / Wed / Thu / Fri
/ Sat / Sun
month= Jan / Feb / Mar / Apr / May
/ Jun / Jul / Aug / Sep
/ Oct / Nov / Dec
day = 1*2DIGIT
time = 1*2DIGIT : 1*2DIGIT [ : 1*2DIGIT ]
timezone = ( + / - ) 4DIGIT
year = ( 4DIGIT / 2DIGIT )
For compatibility reasons with legacy software, two-digit
years greater than or equal to 70 should be interpreted as
the years 1970+, while two-digit years less than 70 should
be interpreted as the years 2000-2069.
anyway, i wrote the following little script to convert a downloaded
mailman/pipermail archive to a standard mbox format archive, so that i
can read the archive in mutt.
#! /usr/bin/perl -ni.bak
use Date::Parse ;
use Date::Format ;
$template = %a %b %d %R:%S %Y ;
if (/(^From )([^]*) (.*)/) {
$time = str2time($3) ;
$date = time2str($template, $time) ;
print $1$2 $date\n ;
} else {
print ;
} ;
craig
PS: i think i've tried all of the free list managers that are available,
and they all have something that sucks about them. i guess i dislike
listar the least (unless i'm running a list where PGP/GPG signatures
are needed, in which case it truly sucks because it mangles them...so
i use majordomo instead, which also sucks because it's so ancient and
crappy.).
of the major free list managers around, smartlist doesn't scale,
listar breaks signatures, mailman screws up archives and is written in
python (some might see that as a feature, but i don't), and majordomo
is...well...majordomo.
actually, if it wasn't for listar breaking signatures, i think it would
be almost perfect. that's it's only flaw...the trouble is that it's a
BIG flaw, and one which excludes it from serious use on geek mailing
lists.
however, the good thing about both listar and majordomo is that they
make it very easy to automate configuration of new lists.
pps: i archive lists in either one-message-per-file (listar) or one mbox
file per month (majordomo) formats, and use mhonarc and htdig to provide
searchable web archives. ignoring the mailman/pipermail bug mentioned
above, the archiving features are available in all list managers...the
trick is in using the available tools to automate the whole process of
creating mailing lists and archives.
i run about a dozen lists on my home mail server, and about 200
majordomo lists and 400 listar lists on my main servers at work (most of
the majordomo lists are legacy lists which can't be changed because the
list owners would
Re: customizing debian apache
Apparently the path is hardcoded into suexec for security reasons, so... Anyway, as Jeremy said (and much to our fustration) the suexec source included is missing critical files required for compilation, so we grab the apache source code and just build suexec (think i've mentioned this before... anyway). Sincerely, Jason Lim - Original Message - From: Jeremy C. Reed [EMAIL PROTECTED] To: Matt Hope [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, November 09, 2001 11:39 AM Subject: Re: customizing debian apache On Thu, 8 Nov 2001, Matt Hope wrote: fairly tidy. An alternative would be patching suexec to accept a run-time path (from what I gather, this is non-trivial) The apache-common package comes with some suexec source. But I am not sure why -- since it is unusable because it is missing several more headers. Anyways, I often use sed to patch suexec: $ cat -v sed.expression s/\/home\/httpd\/html/\/home^@^@^@^@^@^@^@^@^@^@^@/ Jeremy C. Reed .. ISP-FAQ.com -- find answers to your questions http://www.isp-faq.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] http://www.zentek-international.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Compressing Mail Transfer
On Thu, Nov 08, 2001 at 04:52:03PM +1100, Andrew Tait wrote: I was wondering if anyone has come across a way to compress the SMTP transfer of mail between two servers to reduce bandwidth usage. The situation we have is a mail server that is dialled into out network, and a mail server at our border connection. At the moment, the dial-up server is sending mail directly out. I would like the dial-up server to send the mail to our main mail server instead (as easy as pie to do!), but would like to compress the mail transfer between the two, as the dial-up server has a limited connection. there are several ways of doing this. including: 1. run a compressed tunnel between the two machines and set up the transport table and/or smarthost/relayhost configuration so that the smtp connection goes over the tunnel. there are several tunneling programs available. vtun is one of the better ones, it supports both encryption and compression of the tunnel's traffic, and it works with most unixes incl. linux, freebsd, and solaris. see http://vtun.sourceforge.net/ for details. 2. alternatively, use uucp (you can use stunnel openssl to ensure that the uucp connection is encrypted and compressed). 3. if you've got a good grasp of how internet mail works and how your MTA works then it's not that difficult to construct a custom batched-smtp scheme using ssh and some shell scripts. you can either use gzip to explicitly compress the mail batches (better compression) or simply rely on the compression built-in to ssh (slightly easier to implement). the drawback here is that this is, to some extent, re-inventing uucp. craig -- craig sanders [EMAIL PROTECTED] Fabricati Diem, PVNC. -- motto of the Ankh-Morpork City Watch
i815-based MBs, PXE and linux
Hello, I need to purchase several diskless workstations for use with linux, and I'm in process of choosing hardware for them. The biggest problem is motherboards since this is the only thing (except NIC) that can cause a lot of linux compatibility troubles. I'm considering to purchase MBs based on i815 chipset. Did anybody have any problems with them? I'm also considering these motherboards with NIC on the board (AFAIK only Intel 82562ET can be found on MBs with i815)? How well do these onboard NICs behave and how well do they work under linux (and which kernel supports them - 2.2.x, 2.4.x)? How are they compared to realtek8139-based standalone NICs? Also, since the boxes will be diskless, either standalone NICs should have a boot prom socket or BIOS have to support PXE. I would like to have PXE-enabled BIOS (only few cheap 100Mbs NICs have boot prom socket, and boot prom chip costs as much as floppy disk drive). My research tells that only AMI bios or phoenix bios supports PXE (the most widely spread Award BIOS doesn't support PXE). Question is: does these bioses support PXE *with* realtek8139 cards? One with PXE-enabled BIOS and realtek8139-based NIC can answer this question by going to BIOS setup and checking whether 'boot sequence' setting has an option 'boot from network' among choises (A,C, C,A etc). Thank you very much for the answers in advance. Best regards, -Vlad
Re: customizing debian apache
On Thu, 08 Nov 2001, Craig Sanders [EMAIL PROTECTED] wrote... : why? : : these are ALL run-time configuration directives. : : edit your apache config and forget about it. ... for all but the previously mentioned su-exec path, which is set at compile time in the suexec binary.
Re: customizing debian apache
On Wed, 07 Nov 2001, Cameron Moore [EMAIL PROTECTED] wrote...
: I am well aware that there are ten different ways to do this the hard
: way. I can build apache from the official apache source tarball, but
: I'd like to be able to install a customized deb package that's easy to
: maintain (ie. I don't want to have to go in and hack up the build
: scripts every time I upgrade).
My suggestion:
apt-get source apache
rename the package, to something like apache-cmore
edit the debian/control to have it Provide apache, and Conflicts
with apache.
Yes, this is still harder to maintain with new versions, but it is still
fairly tidy. An alternative would be patching suexec to accept a run-time
path (from what I gather, this is non-trivial)
\dopey{}
Mailing Lists
Hi scholars and gentlemen We are wanting to set-up a mailing list for our clients and were wondering which program(s) we should use. At present our mail is handled by exim. Any advised would be welcomed. ..Craig
stable vs testing
Hi All I have a need for glibc2.2 so I may have to use the testing/unstable distribution. This will be in a ISP environment but not as a public host. My question is what other experiences have others have running testing/unstable in a live environment with regards to both security and stability. Thanks in advance. Kind regards Glenn Hocking
RE: stable vs testing
Title: RE: stable vs testing I have two boxes running testing, and they rock!! But If you plan to use the box for production, I always recommend you the stable.think on security issues in the future. Un saludo. -Mensaje original- De: Glenn Hocking [mailto:[EMAIL PROTECTED]] Enviado el: jueves, 08 de noviembre de 2001 13:37 Para: debian-isp@lists.debian.org Asunto: stable vs testing Hi All I have a need for glibc2.2 so I may have to use the testing/unstable distribution. This will be in a ISP environment but not as a public host. My question is what other experiences have others have running testing/unstable in a live environment with regards to both security and stability. Thanks in advance. Kind regards Glenn Hocking -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mailing Lists
Em Qui 08 Nov 2001 10:19, Craigsc escreveu: Hi scholars and gentlemen We are wanting to set-up a mailing list for our clients and were wondering which program(s) we should use. At present our mail is handled by exim. Any advised would be welcomed. ..Craig I did it sometime ago and I've used mailman which is quite easy to use and powerfull, but I'm not an ISP so people in the list would help you best. -- André Luís Lopes andrelop at ig dot com dot br
Re: Mailing Lists
On Thu, Nov 08, 2001 at 02:19:47PM +0200, Craigsc wrote: Hi scholars and gentlemen We are wanting to set-up a mailing list for our clients and were wondering which program(s) we should use. At present our mail is handled by exim. Mailman. Smartlist is second choise. I have 7-8k users on one mailman list, and it performs well. For extreme speed though, use smartlist and zmailer on the box. Given a fast disk and enough RAM, this combo CRANKS. Tim -- Tim Sailer (at home) Coastal Internet, Inc. Network and Systems Operations PO Box 671 http://www.buoy.comRidge, NY 11961 [EMAIL PROTECTED]/[EMAIL PROTECTED] (631) 924-3728
Re: Mailing Lists
On Thu, 8 Nov 2001, Andre Luis Lopes wrote: Em Qui 08 Nov 2001 10:19, Craigsc escreveu: We are wanting to set-up a mailing list for our clients and were wondering which program(s) we should use. At present our mail is handled by exim. I did it sometime ago and I've used mailman which is quite easy to use and powerfull, but I'm not an ISP so people in the list would help you best. I *am* an ISP, and after messing around with quite a few list managers eventually settled on mailman as being the best solution for my situation. (Lazy admin with lots of lists :) It's worth it for the web-based administration and archiving alone. msw -- - Share your knowledge. It's a way to achieve immortality - [EMAIL PROTECTED] pub 1024D/01269BEB 2001-09-29 Martin Wheeler (personal key) Key fingerprint = 6CAD BFFB DB11 653E B1B7 C62B AC93 0ED8 0126 9BEB
Re: Mailing Lists
On Thu, 8 Nov 2001, Martin WHEELER wrote: On Thu, 8 Nov 2001, Andre Luis Lopes wrote: Em Qui 08 Nov 2001 10:19, Craigsc escreveu: We are wanting to set-up a mailing list for our clients and were wondering which program(s) we should use. At present our mail is handled by exim. I did it sometime ago and I've used mailman which is quite easy to use and powerfull, but I'm not an ISP so people in the list would help you best. I *am* an ISP, and after messing around with quite a few list managers eventually settled on mailman as being the best solution for my situation. (Lazy admin with lots of lists :) It's worth it for the web-based administration and archiving alone. msw I totally agree. At the ISP I work for we switched from majordomo to mailman some time ago, and it works perfectly. The web-based admin is great, both for us as admins and for our customers. Teun -- Teun Vink - [EMAIL PROTECTED] - icq: 15001247 - http://teun.moonblade.net
Traffic shaping
Hi again fellas Has anyone successfully implemented bandwidth shaping using debian ? If so what packages / kernel was used and how easy was it ? Any insight is welcome. ..Craig
Re: stable vs testing
Glenn Hocking wrote: My question is what other experiences have others have running testing/unstable in a live environment with regards to both security and stability. I use ONLY testing/unstable. Had never any problems with woody. I use widely known software like apache, bind, postfix so on. You can also experiment with Sid if you want. All software I mention above works stable. I expirienced some quota misbehavior and this is currently soft you can't rely on. -- Regards, Marek L. Kozak
Re: Traffic shaping
Hi again fellas Has anyone successfully implemented bandwidth shaping using debian ? If so what packages / kernel was used and how easy was it ? We are using the shaper module (shaper.o) from the 2.2 kernel with the debian shaper package for quite a while now and we are satisfied. We only perform simple shaping, the outgoing(!) traffic from one or more network adapters is limited. It's staightforward in its use: For an adapter (eth1, 64Kbit): shapecfg attach shaper0 eth1 shapecfg speed shaper0 64000 ifconfig shaper0 myhost netmask 255.255.255.240 broadcast 1.2.3.4.255 up route add -net some.network netmask a.b.c.d dev shaper0 Hope this helps, Bob van der Kamp Kern Automatiseringsdiensten Any insight is welcome. ..Craig -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- composed with SquirrelMail
Routing which depends on source address?
hi! I've the following problem: i have a private network with lets say two workstations an one router ws1 : 192.168.1.11 ws2 : 192.168.1.12 gw : 192.168.1.1 the gw is running debian. the goal is to use two different dialups depending on the source address, e.g use default route over ppp0 device when data comes from 192.168.1.11 and use default route over ppp0 device when data comes from 192.168.1.12. i heard that iptables can do this, examples? any further sugestions? cu markus -- --- Markus Garschaemail: [EMAIL PROTECTED] Hartmannstr. 129fon: 09131/626715 91058 Erlangen fax: +49 89 244356966 pgp-keyid: 0xEE18AF3B --- pgp4Bgz20FUUq.pgp Description: PGP signature
Mailing Lists, Deux
Ok, the last mailing list question prompted me to ask a mailing list question myself. Here's my setup--I've got Mailman managing a bunch of lists for an organization, and we have several lists set up to cascade to each other in the following fashion: Regional List -- Statewide List -- Chapter List +- Statewide List -- Chapter List +- Chapter List Now, most individuals don't subscribe to the Regional or Statewide lists, they subscribe to their Chapter's list. However, when someone wants to make a Region-wide announcement, they post it to the Region list. Since they're not usually a member of the region list, the message sits until I approve it. After that, however, comes the part I'd like to change: the message cascades down into the statewide lists, where it sits until someone approves it, and then it goes down to the chapter lists, where it sits until the moderators of THOSE approve it. What I'd like to do is have a message from the Region wide list automagically pass through the subordinate lists, without requiring everybody to be on every list (thus defeating the purpose of this list structure). I've thought about making posts to the various lists appear to come from the list itself (since then I could add the parent list as an authorized poster for it's child), but I like the idea of having the mail appear to come from the person originating the message. Any thoughts or suggestions are welcome. Thanks in advance! -packy -- Packy Anderson [EMAIL PROTECTED] At dinner yesterday, I tried to cut myself a slice of prime rib, but it was only divisible by itself and one.
Re: Routing which depends on source address?
ip rule add from 192.168.1.11 table 10 ip route add default via xxx.xxx.xxx.xxx table 10 ip rule add from 192.168.1.12 table 11 ip route add default via xxx.xxx.xxx.xxx table 11 pretty easy really. The ip command is in the iproute2 package. Markus Garscha wrote: hi! I've the following problem: i have a private network with lets say two workstations an one router ws1 : 192.168.1.11 ws2 : 192.168.1.12 gw : 192.168.1.1 the gw is running debian. the goal is to use two different dialups depending on the source address, e.g use default route over ppp0 device when data comes from 192.168.1.11 and use default route over ppp0 device when data comes from 192.168.1.12. i heard that iptables can do this, examples? any further sugestions? cu markus -- --- Markus Garschaemail: [EMAIL PROTECTED] Hartmannstr. 129fon: 09131/626715 91058 Erlangen fax: +49 89 244356966 pgp-keyid: 0xEE18AF3B --- -- Part 1.2Type: application/pgp-signature -- Regards, Robert Davidson. http://www.mlug.org.au/
Re: stable vs testing
On Thu, 8 Nov 2001, Glenn Hocking wrote: My question is what other experiences have others have running testing/unstable in a live environment with regards to both security and stability. unstable is very much a trust this and die environment. NOT recommended for a critically live installation. I run testing in a live environment -- BUT: I have *two* copies of the system software on the same machine (on different physical disks); one of which is always two-three days behind the other in terms of update/upgrade. So if tonight's upgrade makes something go bang, I can usually recover as soon as I notice. (Case in point: libexpat went agley on me a couple of weeks ago, but fortunately I was able to copy over a library file from one system to another to sort it.) HTH msw -- - Share your knowledge. It's a way to achieve immortality - [EMAIL PROTECTED] pub 1024D/01269BEB 2001-09-29 Martin Wheeler (personal key) Key fingerprint = 6CAD BFFB DB11 653E B1B7 C62B AC93 0ED8 0126 9BEB
FTP: symlinks, SITE commands
Hi! Two questions: Is there a possibility to upload/create a symlink with FTP? (proftpd) I searched the RFCs and haven't found anything, but I just want to make sure. How can I find out what SITE commands does proftpd support? This doesn't seem to be documented anywhere in /usr/doc/proftpd... regards Marcin -- Marcin Owsiany [EMAIL PROTECTED]
Re: tape drives
On Wednesday, November 7, 2001, at 05:56 PM, David Bishop wrote: As for the second part of my question, any recommendations on *what* my choice of backup software should be? ever hear of bru? it's not free (but there is a demo). My friend told me about it, so I bought it. It has worked wonderfully well, it can even back up to or from machines over the network. there are 2 licenses, personal and commercial. it is also extremely easy, which is a plus. just my 2¢ -chris zubrzycki Security Is A Series Of Well-Defined Steps... chmod -R 0 / ; and smile :)
Re: FTP: symlinks, SITE commands
On Thu, Nov 08, 2001 at 07:52:33PM +0100, Marcin Owsiany wrote: Hi! Two questions: Is there a possibility to upload/create a symlink with FTP? (proftpd) I searched the RFCs and haven't found anything, but I just want to make sure. How can I find out what SITE commands does proftpd support? This doesn't seem to be documented anywhere in /usr/doc/proftpd... try typing `site help' in a command line ftp client -- ,---. Name: Alson van der Meulen Personal:[EMAIL PROTECTED] School: [EMAIL PROTECTED] `---' Just add yourself to the password file and make a directory... -
Re: customizing debian apache
On Thu, 8 Nov 2001, Matt Hope wrote: fairly tidy. An alternative would be patching suexec to accept a run-time path (from what I gather, this is non-trivial) The apache-common package comes with some suexec source. But I am not sure why -- since it is unusable because it is missing several more headers. Anyways, I often use sed to patch suexec: $ cat -v sed.expression s/\/home\/httpd\/html/\/[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@^@/ Jeremy C. Reed .. ISP-FAQ.com -- find answers to your questions http://www.isp-faq.com/
Re: Mailing Lists
On Thu, Nov 08, 2001 at 01:59:51PM +, Martin WHEELER wrote:
On Thu, 8 Nov 2001, Andre Luis Lopes wrote:
Em Qui 08 Nov 2001 10:19, Craigsc escreveu:
We are wanting to set-up a mailing list for our clients and were
wondering which program(s) we should use. At present our mail is
handled by exim.
exim should be adequate for small-medium mail loads.
for larger mail loads, try something more robust scalable like
postfix.
I did it sometime ago and I've used mailman which is quite easy to
use and powerfull, but I'm not an ISP so people in the list would
help you best.
I *am* an ISP, and after messing around with quite a few list managers
eventually settled on mailman as being the best solution for my
situation. (Lazy admin with lots of lists :)
me too (that is, i work as senior system admin at an ISP), except i
settled on listar majordomo...not because they're great but because
they suck the least for my needs.
i'm also an even lazier admin because (following the perl truism that
Laziness is a Virtue) i wrote scripts to automate creation of lists so
that i don't have to work very hard to admin them. :)
a day of fairly interesting work writing scripts three years ago plus a
few days maintaining them and adding features since then has saved me
literally weeks of tedious boredom in manual administration of mailing
lists.
It's worth it for the web-based administration and archiving alone.
mailman's web based admin is fine if you like that kind of thing, and
it is a pretty good list manager in general, but its archiving really
sucks. it produces something that is *almost* an mbox file but is just
different enough that it can't be read or used by any tool that handles
mbox files, e.g. mailgrep, mutt, pine, elm, etc etc etc.
the really annoying thing about it is that a) it has been a known bug
for years, and b) it would be trivial to fix if they could be bothered.
the problem is in the From_ line, the pipermail script uses a bogus Date
format that confuses mbox-capable programs.
the correct date format IS documented...see the mbox(5) man page:
The date is expected to be formatted according to the fol
lowing syntax (represented in the augmented Backus-Naur
formalism used by RFC 822):
mbox-date= weekday month day time [ timezone ] year
weekday = Mon / Tue / Wed / Thu / Fri
/ Sat / Sun
month= Jan / Feb / Mar / Apr / May
/ Jun / Jul / Aug / Sep
/ Oct / Nov / Dec
day = 1*2DIGIT
time = 1*2DIGIT : 1*2DIGIT [ : 1*2DIGIT ]
timezone = ( + / - ) 4DIGIT
year = ( 4DIGIT / 2DIGIT )
For compatibility reasons with legacy software, two-digit
years greater than or equal to 70 should be interpreted as
the years 1970+, while two-digit years less than 70 should
be interpreted as the years 2000-2069.
anyway, i wrote the following little script to convert a downloaded
mailman/pipermail archive to a standard mbox format archive, so that i
can read the archive in mutt.
#! /usr/bin/perl -ni.bak
use Date::Parse ;
use Date::Format ;
$template = %a %b %d %R:%S %Y ;
if (/(^From )([^]*) (.*)/) {
$time = str2time($3) ;
$date = time2str($template, $time) ;
print $1$2 $date\n ;
} else {
print ;
} ;
craig
PS: i think i've tried all of the free list managers that are available,
and they all have something that sucks about them. i guess i dislike
listar the least (unless i'm running a list where PGP/GPG signatures
are needed, in which case it truly sucks because it mangles them...so
i use majordomo instead, which also sucks because it's so ancient and
crappy.).
of the major free list managers around, smartlist doesn't scale,
listar breaks signatures, mailman screws up archives and is written in
python (some might see that as a feature, but i don't), and majordomo
is...well...majordomo.
actually, if it wasn't for listar breaking signatures, i think it would
be almost perfect. that's it's only flaw...the trouble is that it's a
BIG flaw, and one which excludes it from serious use on geek mailing
lists.
however, the good thing about both listar and majordomo is that they
make it very easy to automate configuration of new lists.
pps: i archive lists in either one-message-per-file (listar) or one mbox
file per month (majordomo) formats, and use mhonarc and htdig to provide
searchable web archives. ignoring the mailman/pipermail bug mentioned
above, the archiving features are available in all list managers...the
trick is in using the available tools to automate the whole process of
creating mailing lists and archives.
i run about a dozen lists on my home mail server, and about 200
majordomo lists and 400 listar lists on my main servers at work (most of
the majordomo lists are legacy lists which can't be changed because the
list owners would
Re: customizing debian apache
Apparently the path is hardcoded into suexec for security reasons, so... Anyway, as Jeremy said (and much to our fustration) the suexec source included is missing critical files required for compilation, so we grab the apache source code and just build suexec (think i've mentioned this before... anyway). Sincerely, Jason Lim - Original Message - From: Jeremy C. Reed [EMAIL PROTECTED] To: Matt Hope [EMAIL PROTECTED] Cc: debian-isp@lists.debian.org Sent: Friday, November 09, 2001 11:39 AM Subject: Re: customizing debian apache On Thu, 8 Nov 2001, Matt Hope wrote: fairly tidy. An alternative would be patching suexec to accept a run-time path (from what I gather, this is non-trivial) The apache-common package comes with some suexec source. But I am not sure why -- since it is unusable because it is missing several more headers. Anyways, I often use sed to patch suexec: $ cat -v sed.expression s/\/home\/httpd\/html/\/[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@^@/ Jeremy C. Reed .. ISP-FAQ.com -- find answers to your questions http://www.isp-faq.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] http://www.zentek-international.com
