On Wed, 7 Jul 1993 09:09:40 EDT Evan S. Davies said: >Do any of you list owners know of listserver software designed to run in a >unix environment? I would like to start a list, but it needs to run on an >RS-6000 running unix. Any help/suggestions will be appreciated. > > >-------------------------------- >Evan S. Davies >State Council of Higher Education for Virginia >[log in to unmask] Evan, I don't know much about the unix listserv software. but I'll pass on what I know--I had a user who was interested in joing a list we didn't realize it was unix. The only source we could find for further info on that list was the owner. FYI, i do subscribe to one unix listserv Net-Happenings which has lots of valuable info on it. But sure miss the various capabilities of bitnet listserv esp. archive searching and review. I have to admit I haven't had the time to explore unix listserv as I should. but perhaps this will help. If you decide to install & use, please send me a note re: your experience. Please send it directly to me, since unix listserv is not the topic of this listserv. I posting this note to the entire group since it's informational, and those not interested can simply ignore it. Diane Oerly, Univ. of Missouri Columbia ([log in to unmask]) ---first a note I rec'd when i checked into the list the user was interested in From: " Don Roper (303) 492-7466" <[log in to unmask]> Message-Id: <[log in to unmask]> To: [log in to unmask] Subject: unix-listserv i think there are somewhere between one and two hundred sites running unix-listserv. You can ftp into cs.bu.edu and get README and FAQ files as well as the source for version 6.0 which has lots of features. You can join the list, unix-listserv by sending a sub message to [log in to unmask] Start with help and check out the features. you can send 'index unix-listserv' to [log in to unmask] to see their previous mos of discussions. The code was, I'm pretty sure, written on a Sun but it's been ported to lots of other operating systems, such as AIX, but various people have had some difficulties with the ports -- getting it running on my NeXT wasn't trivial. The author, a computer scientist at BU isn't, I would say, the the best author of documentation. But he works hard to support it and i'm liking it. - - next the result of my help inquiry - - - - - - - - - - - - - - From: [log in to unmask] To: [log in to unmask] Subject: HELP X-Listserver-Version: 6.0 -- UNIX ListServer by Anastasios Kotsikonas X-Comment: InterNIC IS List Server UNIX ListServer 6.0 Here is a brief description of the set of requests recognized by UNIX ListServer. Everything appearing in [] below is optional; everything appearing in <> is mandatory; all arguments are case insensitive. The vertical bar ("|") is used as a logical OR operator between the arguments. Requests may be abbreviated, but you must specify at least the first three characters. Keep in mind that when referring to a <list>, that list may be of two kinds: local or remote, unless otherwise noted. When referring to a local list, your request will be immediately processed; when referring to a remote list (a list served by another ListServer which this system knows about), your request will be appropriately forwarded. Issue a 'lists' request to get a listing of all local and known remote lists to this ListServer. Recognized requests are: help [topic] -------------- Without arguments, this file. Otherwise get specific information on the selected topic. Topics may also refer to requests. To learn more about this system issue a 'help listserver' request. To get a listing of all available topics, generate an error message by sending a bogus request like 'help me'. set <list> [<option> <arg[s]>] ----------------------------- Without the optional arguments, get a list of all current settings for the specified list. Otherwise change the option to a new value for that list. Issue a 'help set' request for more information. subscribe <list> <your name> ---------------------------- The only way to subscribe to a list. unsubscribe <list> signoff <list> ------------------ Two ways of removing yourself from the specified list. recipients <list> review <list> ----------------- Get a listing of all non-concealed people subscribed to the specified list. information <list> ------------------ Get information about the specified list. statistics <list> {[subscriber email address(es)] | [-all]} ----------------------------------------------------------- Get a listing of non-concealed subscribers along with the number of messages each one of them has sent to the specified list. If the optional email addresses are given, then statistics will be collected for these users only. For example: stat foo user1@domain user2@domain will generate statistics about these two subscribers. "-all" lists statistics for all users that have posted on the list (whether currently subscribed ot not). run <list> [<password> <cmd [args]>] ------------------------------------- Run the specified command with the optional arguments and receive the output from stdout and/or stderr. To get a listing of all available commands to run, omit the arguments, i.e. issue a 'run <list>' request. You have to belong to the specified list, and must have obtained the password from the list's owner; the owner's address may be found in the Errors-To: header line of each delivered message. <list> may be local only. lists ----- Get a list of all local mailing lists that are served by this server, as well as of all known remote lists. index [archive | path-to-archive] [/password] [-all] ---------------------------------------------------- Get a list of files in the selected archive, or the master archive if no archive was specified. If an archive is private, you have to provide its password as well. get <archive | path-to-archive> <file> [/password] [parts] ---------------------------------------------------------- Get the requested file from the specified archive. Files are usually split in parts locally, and in such a case you will receive the file in multiple email messages -- an 'index' request tells you how many parts the file has been split into, and their sizes; if you need to obtain certain parts, specify them as optional arguments. If an archive is private, you have to provide its password as well. search <archive | path-to-archive>] [/password] [-all] <pattern> ---------------------------------------------------------------- Search all files of the specified archive (and all of its subarchives if -all is specified) for lines that match the pattern. The pattern can be an egrep(1)-style regular expression with support for the following additional operators: '~' (negation), '|' and '&' (logical OR and AND), '<' '>' (group regular expressions). The pattern may be enclosed in single or double quotes. Note: . matches any character including new line. fax <fax-number> <archive | path-to-archive> <file> [/password] [parts] ----------------------------------------------------------------------- Same as 'get', but it faxes you the files instead to the specified number. release ------- Get information about the current release of this ListServer system. which ----- Get a listing of local mailing lists to which you have subscribed.