From List-Managers-Owner Mon Apr 12 01:23:43 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-921015) id AA29530; Mon, 12 Apr 93 01:23:43 GMT Received: from POBOX.UCS.UMASS.EDU by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-921015) id AA29523; Sun, 11 Apr 93 18:23:36 PDT Received: from titan.ucs.umass.edu by POBOX.UCS.UMASS.EDU (PMDF #2573 ) id <01GWWE17G61C007WEB@POBOX.UCS.UMASS.EDU>; Sun, 11 Apr 1993 21:24:23 -0500 Received: by titan.ucs.umass.edu (5.65/DEC-Ultrix/4.3) id AA14519; Sun, 11 Apr 1993 21:24:21 -0400 Date: 11 Apr 1993 21:24:20 -0400 (EDT) From: Pres Smith Subject: Archives Chopper To: List-Managers@GreatCircle.COM Message-Id: <9304120124.AA14519@titan.ucs.umass.edu> Content-Type: text Content-Transfer-Encoding: 7BIT X-Mailer: ELM [version 2.4 PL21] Content-Length: 659 Sender: List-Managers-Owner@GreatCircle.COM Precedence: bulk Is there a sub-program for chopping up archives into "byte"-sized chunks of about 100K automatically for Anastasios Kotsikonas' unix list server program? Any program? It takes too much time for systems people to do this by "hand" now. Also, are such archives searchable by LDbase rules? It's taking me too much time to retrieve old files at subscriber requests by "memory" and I don't have a large enough hard disk to hold my own "saves" of old posts for use of some file search program. If I did, what do listowners use--Ask Sam? Zyindex? WordCruncher? Fgrep? Thanks Prescott Smith, listowner, Ednet pgsmith@educ.umass.edu From List-Managers-Owner Mon Apr 12 22:50:09 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-921015) id AA06122; Mon, 12 Apr 93 22:50:09 GMT Received: from uu3.psi.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-921015) id AA06113; Mon, 12 Apr 93 15:50:00 PDT Received: from stormking.com!dropzone!dropzone.stormking.com by uu3.psi.com (5.65b/4.0.071791-PSI/PSINet) via UUCP; id AA09974 for ; Mon, 12 Apr 93 18:34:21 -0400 Received: from dropzone.UUCP by stormking.com with UUCP id AA15314 (5.65c/IDA-1.4.4 for list-managers@greatcircle.com); Mon, 12 Apr 1993 18:14:47 -0400 Received: by dropzone.stormking.com (UUPC/extended 1.11x); Mon, 12 Apr 1993 17:55:28 edt Date: Mon, 12 Apr 1993 17:55:26 edt From: "Scott J. Ellentuch" Message-Id: <2bca0173.dropzone@dropzone.stormking.com> Organization: The Telecom Security Group DropZone Reply-To: "Scott J. Ellentuch" To: list-managers@GreatCircle.COM Subject: Re: Archives Chopper Sender: List-Managers-Owner@GreatCircle.COM Precedence: bulk On 11 Apr 1993 21:24:20 -0400 (EDT), "Pres Smith" wrote: > > Is there a sub-program for chopping up archives into "byte"-sized > chunks of about 100K automatically for Anastasios Kotsikonas' unix > list server program? Any program? It takes too much time for systems > people to do this by "hand" now. > At the current time I do not think this is implemented for archives. It IS available when archiving using the "farch" command. I will make sure that Tasos puts it on the "To: do" list. > > Also, are such archives searchable by LDbase rules? > The "search" command was added in ListServer 6.0, and a copy of the "help search" is included at the end of this message. Tasos will have to clear this up, and he's on vacation. > > It's taking me too much time to retrieve old files at subscriber > requests by "memory" and I don't have a large enough hard disk to hold > my own "saves" of old posts for use of some file search program. If I > did, what do listowners use--Ask Sam? Zyindex? WordCruncher? Fgrep? > > Thanks Prescott Smith, listowner, Ednet pgsmith@educ.umass.edu > > Syntax: search ] [/password] [-all] 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: '~', if leading the regular expression it reverses its meaning; '|' and '&' separate multiple regular expressions (logical OR and AND); '<' '>' group regular expressions (we preserve the meaning of the parentheses from ed(1), and remove the meaning of < and > from ed(1) since in the ListServer context they are either the default, or inappropriate). These can be used literally by escaping them with '\'. In addition, the following characters should be defined in matched pairs: (), <>, []. The pattern may be enclosed in single or double quotes. Pattern matching is case insensitive. Certain archives may be private, and in this case you have to specify a password for accessing them. The slash is required. Different archives may have different passwords. The archiving system is hierarchical. Therefore subarchives may have the same names; they can be distinguished by the path (the branch in the hierarchy) to them. For example, the archives unix and pub/unix are distinct. 'path-to-archive' is a UNIX style path (such as pub/unix) -- i.e. a '/' is used to move through the branches of the hierarchy. An 'index' request always reports paths to archives for your convinience. Examples: search listserver -all "|.*andarin[sz]?" search iul '\|.*\|.$' Notes: - . matches ANY character including newline, so to find all lines that contain a newline only, one should use '^.$' instead of '^$' - If you do not quote your pattern, it will include any blanks you may have appended after it by mistake, and it will not include any blanks that may start the regular expression. From List-Managers-Owner Mon Apr 19 17:14:29 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-921015) id AA01881; Mon, 19 Apr 93 17:14:29 GMT Received: from cheviot.ncl.ac.uk by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-921015) id AA01874; Mon, 19 Apr 93 10:13:29 PDT Received: from turing.ncl.ac.uk by cheviot.ncl.ac.uk id (5.65cVUW/NCL-CMA.1.35 for ) with SMTP; Mon, 19 Apr 1993 18:14:01 +0100 From: "John Martin" Message-Id: Subject: Gopher Service for Mailbase To: nisp-all@mailbase.ac.uk, owners-unique@mailbase.ac.uk (owners-unique list), iuic-infs@mailbase.ac.uk, uk-gopher-managers@mailbase.ac.uk, lis-link@mailbase.ac.uk, list-managers@GreatCircle.COM Date: Mon, 19 Apr 93 18:13:57 WET DST X-Mailer: ELM [version 2.3 PL11] Sender: List-Managers-Owner@GreatCircle.COM Precedence: bulk Hello, The Mailbase service is pleased to announce a Gopher interface to its mailing list archives. Name=Mailbase Gopher Type=1 Host=mailbase.ac.uk Port=70 Path= Current features: - You can browse/retrieve all publicly available information and Mailbase documents. - Mail archives appear as an index of subjects so that individual messages may be retrieved/browsed. - You can browse/retrieve a list's membership/ownership. Coming soon: - A 'gopher' login for those of you who don't have clients. - Searching for relevant files. Please try this out and send any comments to mailbase-helpline@mailbase.ac.uk Cheers, John -- AKA: postmaster@mailbase.ac.uk ------------------------------------------------------------------- John Martin Computing Laboratory 091 222 8087 University of Newcastle upon Tyne John.Martin@newcastle.ac.uk Newcastle upon Tyne, UK. ------------------------------------------------------------------- From List-Managers-Owner Wed Apr 28 22:35:29 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-921015) id AA02442; Thu, 29 Apr 93 04:44:22 GMT Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-921015) id AA02268; Thu, 29 Apr 93 04:34:06 GMT Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-921015) id AA02261; Wed, 28 Apr 93 21:34:02 PDT Date: Wed, 28 Apr 93 21:34:02 PDT Message-Id: <9304290434.AA02261@mycroft.GreatCircle.COM> From: Brent@GreatCircle.COM (Brent Chapman) To: Brent@GreatCircle.COM (Brent Chapman) Subject: Mail lost through crash of Mycroft.GreatCircle.COM Reply-To: Brent@GreatCircle.COM (Brent Chapman) Sender: List-Managers-Owner@GreatCircle.COM Precedence: bulk Mycroft.GreatCircle.COM (aka FTP.GreatCircle.COM and GreatCircle.COM) suffered a major disk crash on Monday night, 26 April 93. The machine was returned to service on Wednesday night, 28 April 93. The machine was restored to its state as of 0130 PDT Sunday 25 April 93 (0830 GMT), which means that everything done on the machine Sunday and Monday was lost. Any mail sent to or through GreatCircle.COM between 0130 PDT Sunday 25 April 93 (0830 GMT Sunday 25 April 93) and about 2330 PDT Monday 26 April 93 (0630 GMT Tuesday 27 April 93) has been lost. Any mail sent to or through GreatCircle.COM after about 2330 PDT Monday 26 April 93 (0630 GMT Tuesday 27 April 93) should be OK, and will be processed over the next day or so as things get caught up around here. If you sent mail to me personally (Brent@GreatCircle.COM) on Sunday or Monday, I may or may not have seen it before the crash. If I saw it, I I probably replied to it before the crash, but I've lost both your original and my reply. I'd appreciate it if you could resend any mail you sent to me during that period, even if I already replied to it, so that I have a record (if you could also send me a copy of my own reply to you, that would be fantastic). If you sent mail to Majordomo@GreatCircle.COM on Sunday or Monday, you'll need to send it again, even if you got back a confirmation from Majordomo that it had been processed. The mailing lists were on the disk that died, so they're back to where there were as of 0130 PDT Sunday 25 April 93. If you sent mail to one of the mailing lists here (Firewalls, List-Managers, Majordomo-Users, and PhoneStation) on Sunday or Monday, it may or may not have been forwarded to the list, but it's missing from the archives. I don't remember anything earth-shaking being posted during that period, but I could be mistaken. If you got a copy of your message back from the list, then everybody else did too, and there's no need to resend it. If you sent something and haven't gotten a copy back, or if you sent something and did get a copy back but you think it's critical that it make it into the archives, you should send it again. Sorry for the inconvenience. My apologies if you end up getting multiple copies of this; it's going out to several mailing lists. Thanks for your help! -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From List-Managers-Owner Thu Apr 29 12:47:58 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-921015) id AA04562; Thu, 29 Apr 93 12:47:58 GMT Received: from amber.me.fau.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-921015) id AA04555; Thu, 29 Apr 93 05:47:49 PDT Received: by amber.me.fau.edu id AA04814 (5.65a/IDA-1.4.2 for List-Managers-Digest@greatcircle.com); Thu, 29 Apr 93 08:35:42 -0400 Date: Thu, 29 Apr 93 08:35:42 -0400 From: "N. Saravanan" Message-Id: <9304291235.AA04814@amber.me.fau.edu> To: List-Managers@GreatCircle.COM Cc: List-Managers-Digest@GreatCircle.COM Subject: Help in setting up a list. Sender: List-Managers-Owner@GreatCircle.COM Precedence: bulk Hello subscribers: I know this is a very stupid question and I am not even sure if I should waste your time by asking this. I have been given the responsibility of setting up a mailing list. It needs to meet the following requirements: (1) It has to be in a digest form. (Similar to list-managers-digest). (2) It has to be moderated. (3) It has to run on a Sun Sparc. I have downloaded the listserver6.0 software and compiled it. I would like to have a format for the digest as follows: ---------------------------------------------------------------------------- Some announcements if any go here. Then followed by actual e-mail from subscribers after they have been moderated. ----------------------------------------------------------------------------- I have tried setting up the "config" file in the listserver software as follows: list EVOL-PROG evol-prog@magenta.me.fau.edu owner@magenta.me.fau.edu password nothing -M -m 50 -e With this set up I do the following: ----------------------------------- Each time a subscriber sends an e-mail to the list, it is send to the list owner. Since the list owner wants to moderate the list and make it into a digest, he saves it into a file. After a certain number of messages have been saved in the file, the owner edits this file and then forwards it to the list. At this point I have a number of problems. (1) The moderated, digestified list keeps coming back to the owner for moderation again. (2) Can I set it up in such a way that the list forwards to the owner only after it has received a certain number of messages and has put it in a digest form . Possibly with the format described above. (3) Am I using the wrong software package? (4) Any other useful suggestions and ideas arewelcome. If you think replying to the list is a waste of bandwidth, please e-mail your suggestions and comments to me at: saravan@amber.me.fau.edu Thanks in advance. Saravan *************************************************************************************** * N.Saravan * Part-time Engineer and Full-Time Fisherman ---------* * saravan@amber.me.fau.edu *-----------------------------------------------------* * saravan@cse.fau.edu * Live SIMPLY,so that others may simply LIVE ---------* *************************************************************************************** From List-Managers-Owner Thu Apr 29 11:37:43 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-921015) id AA05811; Thu, 29 Apr 93 18:27:57 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-921015) id AA05779; Thu, 29 Apr 93 11:25:29 PDT Message-Id: <9304291825.AA05779@mycroft.GreatCircle.COM> To: "N. Saravanan" Cc: List-Managers@GreatCircle.COM Subject: Re: Help in setting up a list. In-Reply-To: Your message of Thu, 29 Apr 93 08:35:42 -0400 Date: Thu, 29 Apr 93 11:24:58 -0700 From: Brent Chapman Sender: List-Managers-Owner@GreatCircle.COM Precedence: bulk # Hello subscribers: # # I know this is a very stupid question and I am not even sure if I should waste # your time by asking this. # # I have been given the responsibility of setting up a mailing list. It needs # to meet the following requirements: # # (1) It has to be in a digest form. (Similar to list-managers-digest). # (2) It has to be moderated. # (3) It has to run on a Sun Sparc. I have downloaded the listserver6.0 software # and compiled it. # # I would like to have a format for the digest as follows: # ---------------------------------------------------------------------------- # # # Some announcements if any go here. # # # Then followed by actual e-mail from subscribers after they have been moderated. # # ----------------------------------------------------------------------------- RFC1153 defines how digests are supposed to look. If you don't follow the spec, lots of "undigestify" programs will break. I'd use "digest" (available for anonymous FTP from FTP.GreatCircle.COM, file pub/list-managers/tools/digest.shar) for this. "digest" spools articles as they come in, then creates and sends digests later. I normally run a "cron" job to create the digests, but there's no reason you couldn't edit the files (the moderation you want) then run "digest" by hand instead. There's one feature of "digest" that you'd need to bypass: it automatically creates and sends digests when they grow past a certain size. If you want a chance to moderate the messages first, you'd need to disable that (easiest way is probably to set the size parameter that controls this behavior to some insanely big (effectively infinite) size; this is configurable on a per-list basis). Here are the relevant aliases for a digest called "Sample-Digest": sample-digest: "|/usr/local/mail/majordomo/wrapper digest -r -c /usr/local/mail/digest/sample-digest.cf" sample-digest-send: "|/usr/local/mail/majordomo/wrapper resend -p bulk -l Sample-Digest -f Sample-Digest-Owner -h GreatCircle.COM -s sample-digest-outgoing" sample-digest-outgoing: :include:/usr/local/mail/lists/sample-digest sample-digest-owner: brent owner-sample-digest: sample-digest-owner owner-sample-digestify: sample-digest-owner owner-sample-digest-send: sample-digest-owner owner-sample-digest-outgoing: sample-digest-owner owner-sample-digest-owner: brent Mail sent to "sample-digest" is spooled for later processing by "digest -r". When the "digest" program creates a digest, it sends it to "sample-digest-send" (although the headers say it was sent to "sample-digest"; the headers lie), which sends it out to the members of the list. The "sample-digest.cf" configuration file would contain all the configuration info for "Sample-Digest" that will be used by the "digest" program. It specifies the name of the digest, what the addresses in the header should be, the names of the files containing the volume number, issue number, header data (announcements, etc.), and trailer data, and so forth. -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041