X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10aa15,9b42ba92ac36b511,start X-Google-Attributes: gid10aa15,public X-Google-ArrivalTime: 1994-11-07 07:46:00 PST Path: nntp.gmd.de!Germany.EU.net!EU.net!howland.reston.ans.net!quagga.ru.ac.za!ee.und.ac.za!ticsa.com!cstatd.cstat.co.za!cool!gaven.cohen From: gaven.cohen@cool.alt.za (Gaven Cohen) Newsgroups: alt.bbs.wildcat Subject: Lserv 1.00 released! )1/2 Date: Mon, 7 Nov 1994 15:46:00 GMT Message-ID: <941107175154235@cool.alt.za> Organization: Cool BBS, South Africa Distribution: world Lines: 96 Hi Guys, I am *PROUD* to release the initial release of the Lserv program, a listserver / mailing list program for WildCat! 4.01 or above. This has VAST improvements over the 0.99b beta, which will be mentioned below. Some feature highlights over the beta are cool new display screens, vast speed improvements and bug fixes, many more features, and other bits and pieces. Some general program highlights: ability to host multiple mailing lists, seamless invisible message pointer file, get request (sends file/s back UUencoded and ability for remote 'administrators' to get lists of the subscribers to particular groups. To beta users: This was actually a little rushed release... at least two of the mentioned 'upcoming features' were to be included in the initial release, but because of the fact that WC4.01 cannot use WC4.00 I released Lserv as soon as possible. Cheers, Gaven ** "Feature Section" and "Changes from 0.99b" follows... LSERV100.ZIP is available from Pete Dalinis' famous WildCat! FTP site. FTP to abailable from Pete Dalinis' famous WildCat! FTP site. FTP to nw.hamshack.com, cd to /sys/wc/wccode, and get LSERV100.ZIP -------------------------------------------------------------------------- "Feature Section" of Manual -------------------------------------------------------------------------- * ABLE TO HOST MULTIPLE INTERNET MAILING LISTS. * ALLOWS REMOTE USERS TO SUBSCRIBE VIA E-MAIL. Users can send an e-mail message to 'LISTSERV@YOUR.DOMAIN.NAME' and in the body of the message, can place commands such as subscribe, unsub, sub, unsubscribe, etc. * SENDS OPERATION REPLIES. Lserv will reply to each message it receives, with the success or un- success of the operations requested. Customizable messages are sent with successful SUBs and UNSUBs, and a customizable 'invalid requests' file is sent with unsuccessful. * NAME CHECKING. Lserv will not subscribe users to lists that do not exit and they will not be able to unsubscribe from lists that do not exist either. Users who are already subscribed can not subscribe again, and users who have not subscribed can not un-subscribe. * FOOL PROOF SEAMLESS POINTER FILE. Lserv makes use of the NETWORK field in WildCay! messages to differen- tiate between processed and unprocessed messages. Lserv *will* *not* reprocess processed messagers eliminating the need for an "MPF" or Msg Pointer File. However, (as I noticed in the beta release) this can be quite horrible with LARGE e-mail conferences, so, Lserv uses a Message Pointer File even though it does not need it,so it does not go through the entire message base again each time. Since Lserv does not re-pro- cess processed messages, you can freely run wcPACK without having to worry about all messages being processed and sent again. If Lserv de- tects that the conference's highest message is below the message numb. mentioned in the MPF,it will reset this to zero, meaning that, the MPF is seamless, fool proof, and practically INVISIBLE. * CONTINUOUS MODE. Lserv can be set to loop continuously without stopping, searching for un-processed messages. This way, you can dedicate an entire node just for Lserv, giving all new list and listserv messages instant handling. * LIST NAME FROM FIELD. Lserv will place the list name in the from field of all messages being sent to subscribers. This allows easy replying. It also supplies the name of the material originator. * CUSTOMIZABLE .SIG FILE. You can define customizable text that is sent with each list message. * GET REQUESTS Each listname can have it's own directory, and users can request files from this directory to be sent back UUencoded. Note though, that this does NOT use wcGATE's UUencode feature, so as to prevent the same file being attached over and over again to different messages. You *must* have the UUENCODE.EXE program in your path for this to work. -------------------------------------------------------------------------- Changes from Previous Versions -------------------------------------------------------------------------- v0.99 - First beta release. * Made some nifty display screens. ;) * Fixed the prob where listname would send a message to itself. The problem arised in copying a message to the listserver that began with TO: listname@whereever... this line would be copied (Continued to next message)