On Thu, 29 Apr 1999 12:59:56 -0500, "John R. Andrews" <[log in to unmask]> wrote: >I am trying to set up a list that will allow anyone in our local >service area, i.e., *.uic.edu to post, but off campus posts to go to a >moderator. We are running Listserv version 1.8c. > >On page 169 of the Site Manager's Operation Manual for Listserv 1.8c >it states that while the first editor must be a network address and >not an access-level, subsequent editors may be access-levels. The >following example is given: * Editor= [log in to unmask],(MYLIST-L) > >From this I concluded, I could specify "Service" as the second editor >entry; however, when I do, I receive the following error. > >* Editor= ...,SERVICE Error: Incorrect syntax. This parameter must be >a so called "monitoring address", such as "Owners", "Owner" (only the >first address in the list of owners), "Postmaster(s)", a valid RFC822 >address, and so on. The special keyword "quiet:" indicates that all >the addresses that follow should be ignored when sending unimportant >messages. > >However, Listserv will accept a (listname) editor entry, so I'm >guessing that only some of the access-levels are usable. > >Is there some other way to specify a service area as able to send but >not others? > >John Andrews >UIC I've wanted to do something similar. In general, I want to limit my list so that only subscribers can send to it. However, if a site takes responsibility for distributing the messages to everyone at that site, then I'd everyone at that site (= domain) to be able to send to my list. Like you, I also noticed that the second and subsequent editors can be an access level. So my idea was to set up a separate list (which would never be used for distributing messages) whose service area was defined as the set of domains that I wanted to be able to send to my list. I then set * Editor= My_Address,(MyList),Service(Separate_List) I exchanged mail with Eric and he said that he thought that this SHOULD work. I tried it and there were no syntax errors, but it doesn't seem to work the way I (and Eric?) thought it should. I never pursued it and hence I don't have a solution for you. I did want to pass on this idea and my experience. I also want to support the idea that this would be a useful facility to have. The following is an excerpt from my own "LISTSERV Wish List" document. Using <Area>s in the values of the Editor=, Review=, and Send= keywords I would like to be able to use <Area>s (as used with the Service= keyword, e.g. SITE.EDU,*.SITE.EDU) in the values of other keywords that control access to the list. In particular, I would like to be able to set any of the Review=, Send=, and Editor= (for the second and subsequent editors) keywords to "SITE.EDU,*.SITE.EDU" or to a combination of an access-level and an area. For example, "Send= Private,site.edu,*.site.edu" would mean anyone subscribed to the list OR in the site.edu domain could send to the list. Similarly, "Editor= UserID@Node,(MYLIST),site.edu,*.site.edu" would mean that either UserID@Node, anyone subscribed to the MYLIST list, OR anyone in the site.edu domain would be recognized as an editor of the list. Date: Sat, 4 Jan 1997 20:20:00 -0500 From: "David M. Rosenberg" <[log in to unmask]> Subject: Re: Defining additional service areas & uses of service areas I am a fan of LISTSERV. However, there are a few things that I think it should (and perhaps does) do, but I can't figure out how to make it to them. A recent message by Roger Fajman requests a feature related to a function that I want. I want to add my request to the same chain in the hope that a clever implementor can accommodate both requests with a single feature. (Eric, unless there already is some way to accomplish the function I'm requesting, I'd appreciate your adding it to the wishlist.) My request: I have a list with many individual subscribers and some "site" subscribers. By a "site subscriber" I mean a situation where there is one subscription for an institution and that institution takes responsibility for distributing the information to their members (through some method that they control, such as a bulletin board system, a sub-list, a communally-accessible database, paper printouts, etc.). I want to have a closed list (that is, * Send= Editor Editor= me@myhost,(listname) ), but I want to allow individuals at my site subscriber's institutions to be able to send to the list. I know that the normal way to handle this is to ask each of those individuals to subscribe personally and set his personal subscription to NOMAIL. Instead, I would like to, in effect, add (something like) a service area as an editor, either directly * Editor= me@host,(list),*@site1.edu,*@*.site1.edu,*@site2.edu,*@*.site2.edu or indirectly * Editor= me@host,(list),Service(dummy-list) (where dummy-list was another list defined to have as its service area the set of domains from which I wish to accept posts to my list) or any other way that accomplishes the effect described above (unfortunately, I have not been able to get either of the above methods to work). In Roger Fajman's message of Thu, 2 Jan 1997 17:50:07 EST, he made a proposal to ease having several service areas shared among many lists. He wanted a way to have one definition for each of several service areas and to use those service areas in a number of lists. The LOCAL service area gave him one. Roger suggested having a list that defined its service area and then being able to set up other lists so that they used the same service area, for example with a syntax like * Service= (xyz-l) or perhaps (this is my suggestion) * Service= Service(dummy-list) It has been suggested that the ".ik" (include keyword) mechanism might solve Roger's problem, but I don't see how it could solve mine. /David M. Rosenberg [log in to unmask] 1-617-253-8054 "Send=" restricted to area(s) plus specified users? Is "* Send= Service,[log in to unmask],[log in to unmask]" a valid list header keyword setting and does it have the effect that anyone with an address in the list's Service area and [log in to unmask] and [log in to unmask] may send messages to the list? If not, how could this effect be accomplished most easily? Is "* Send= Mysite.Edu,*.Mysite.Edu,[log in to unmask],[log in to unmask]" a valid list header keyword setting and does it have the effect that anyone with an address of the form *@Mysite.Edu or *@*.Mysite.Edu and [log in to unmask] and [log in to unmask] may send messages to the list? If not, how could this effect be accomplished most easily?