Cor blimey, guvners, how do you do it? :-) Unpack. Edit Makefile. Build. Install files into a home directory.
Ecartis Setup Process Ecartis needs its own user and group. Ecartis will try to lose root privileges if it has them. Otherwise, it has no idea what user or group to use. Use the setuid and setgid bits on the ecartis binary and change ownership on all Ecartis files, including the binary, so that they are ecartis user and group owned. I don't know if this actually makes any difference, but set the Ecartis user's home directory to the Ecartis root. Make everything except the Ecartis directory and the ecartis binary unreadable to anybody but Ecartis. Let everybody have read-execute on those two only. Mind the log - if you put it there, create it first, then set its permissions so Ecartis won't create a new, world-readable one (if you're really this paranoid, that is). If you'll use PantoMIME, create your web directory and give it traverse-read by your webserver and read-write-traverse by Ecartis. Cron can safely run a script as root to invoke /opt/ecartis/ecartis (or whatever) with the -procbounce and then the -procdigest (not both at the same time) options, once daily. Use "-help" for a full list of options. Use "-cheatsheet sheetfile.html" for a comprehensive summary of every single configuration option and its applicability in each configuration file. Create a shell script in your webserver's cgi-bin directory called lsg2.cgi that simply does "exec /opt/ecartis/ecartis -lsg2" (change as needed). In your Ecartis directory, create a directory named "SITEDATA" beneath the lists directory. Now you can support site passwords if desired and can configure lists from the web. Now you can create any lists you need with the -newlist parameter and set up the necessary aliases as directed. If you're using smrsh, go through the necessary contortions (namely, create a wrapper shell script to invoke Ecartis with all given options that is reachable by smrsh - don't try a symlink, it won't work). It'll be like: #!/bin/sh exec /opt/ecartis/ecartis $@ Configure Ecartis by mucking about with the various files. I'm sure you know how it's done. Use your cheatsheet to guide you, and make use of the handy-dandy LSG2 configuration Edit List Config page from your web browser. Watch out for "choice" options - the only easy way to discover those is using the web, because the config file generator doesn't enumerate them (unfortunately). Bug? There's always the source, which anyway you want to spend some time reading to understand how stuff works in case of question. Test! You should now be able to ask [EMAIL PROTECTED] for "help" (subject or body, one command in the subject only and body ignored, or multiple in body). You can post to your list(s). You can browse to LSG2. Security: not foolproof, but it's the best you'll find for this kind of setup, and it's practical for most purposes. In particular, normal users could make new lists - not that that's going to hurt you or anything, not unless they're really determined to muck you up. The authentication mechanism is good! Performance: it's the MTA's problem. Tweak that. Postfix is generally accepted as the current Unix speed crown, though Xmailer is clearly faster. Enjoy your lean-'n'-mean Ecartis experience! Suggestions? If we can make this into a howto for beginners, I'm all for it. Cheers, Sabahattin -- [email protected] mailing list Send administrative requests (subscribe, unsubscribe, change options) to: [EMAIL PROTECTED] (use "help" in the Subject line for a summary of common options) You can also use the web interface at: https://sabahattin-gucukoglu.com/cgi-bin/lsg2.cgi For assistance, contact: [EMAIL PROTECTED]
