On Wed, 17 May 89 14:04:10 EDT Harold Pritchett said: >Sure. Just code: > >* Local= UGA*,USCN,GIT*,GTRI01 Well, not quite. The LOCAL keyword doesn't honor wild cards (the UGA* thing), and only controls the for of mail sent from the list. Subscribers on "local" nodes receive separate copies of the mail, with only their own address in the To: line. >* Service= LOCAL Coding "Service= UGA*,USCN,GIT*,GTRI01" will do what Harold intended. The rule for coding the SERVICE keyword is "Service= <pattern>,<pattern>,...", where <pattern> is either <ISO-2-char-country-id>, <nodename>, or <prefix>*<middle>*<suffix>. Any of the three pattern pieces can be ommitted, and "**" can be coded as "*". So "Service= US,PUCC,RUT*,*VM,NJ*VS,U*NJ*VS,*NY*VAX,*VX*" is an all-inclusive example. It should be pointed out there is no law preventing Rutgers, for example, from registering a node named UGAMUGA (a Sesame Street reference, I believe), which would match Harold's UGA* pattern. If you're concerned that the list be strictly internal, don't use wild cards in the SERVICE keyword. If you're just trying to keep the list from becoming universally known, it's fine. >Then no one can sign up, unless they are at one of these nodes. Also, if >I am going to do this, I should also add: > >* Confidential= Service > >Now, the list will only appear to people who can subscribe when they do a >LIST command to LISTSERV, and it will not appear in the LIST GLOBAL command. Yup. Definitely a good idea for an internal-only list. Ross Patterson Rutgers University Subject: Re: multi-node local lists? X-LSVRepTo: X-LSVopts: NOACK Org=LSTSRV-L@RUTVM1 X-LSVvia: LSTSRV-L@RUTVM1 LSTSRV-L@POLYGRAF To: $PEER$ <LSTSRV-L@CEARN> In-Reply-To: Message of Wed, 17 May 89 14:04:10 EDT from <[log in to unmask]> On Wed, 17 May 89 14:04:10 EDT Harold Pritchett said: >Sure. Just code: > >* Local= UGA*,USCN,GIT*,GTRI01 Well, not quite. The LOCAL keyword doesn't honor wild cards (the UGA* thing), and only controls the for of mail sent from the list. Subscribers on "local" nodes receive separate copies of the mail, with only their own address in the To: line. >* Service= LOCAL Coding "Service= UGA*,USCN,GIT*,GTRI01" will do what Harold intended. The rule for coding the SERVICE keyword is "Service= <pattern>,<pattern>,...", where <pattern> is either <ISO-2-char-country-id>, <nodename>, or <prefix>*<middle>*<suffix>. Any of the three pattern pieces can be ommitted, and "**" can be coded as "*". So "Service= US,PUCC,RUT*,*VM,NJ*VS,U*NJ*VS,*NY*VAX,*VX*" is an all-inclusive example. It should be pointed out there is no law preventing Rutgers, for example, from registering a node named UGAMUGA (a Sesame Street reference, I believe), which would match Harold's UGA* pattern. If you're concerned that the list be strictly internal, don't use wild cards in the SERVICE keyword. If you're just trying to keep the list from becoming universally known, it's fine. Received: from graf.poly.edu by CEARN.cern.ch (Mailer R2.03B) with BSMTP id 4147; Thu, 18 May 89 21:09:19 GVA Received: by POLYGRAF (Mailer R2.03B) id 2889; Thu, 18 May 89 14:42:34 EDT Received: from RUTVM1.RUTGERS.EDU by graf.poly.edu (Mailer R2.03B) with BSMTP id 2875; Thu, 18 May 89 14:40:15 EDT Received: by RUTVM1 (Mailer R2.03BRU) id 4596; Thu, 18 May 89 14:39:26 EDT Received: by RUTVM1 (Mailer R2.03BRU) id 4591; Thu, 18 May 89 14:38:34 EDT Message-ID: <LSTSRV-L%89051814392288@RUTVM1> Newsgroups: bit.listserv.lstsrv-l Date: Thu, 18 May 89 14:17:41 EDT Reply-To: Revised LISTSERV forum <LSTSRV-L@POLYGRAF> Sender: Revised LISTSERV forum <LSTSRV-L@POLYGRAF> From: Ross Patterson <A024012@RUTVM1> Subject: Re: multi-node local lists? X-LSVRepTo: X-LSVopts: NOACK Org=LSTSRV-L@RUTVM1 X-LSVvia: LSTSRV-L@RUTVM1 LSTSRV-L@POLYGRAF To: $PEER$ <LSTSRV-L@CEARN> In-Reply-To: Message of Wed, 17 May 89 14:04:10 EDT from <[log in to unmask]> On Wed, 17 May 89 14:04:10 EDT Harold Pritchett said: >Sure. Just code: > >* Local= UGA*,USCN,GIT*,GTRI01 Well, not quite. The LOCAL keyword doesn't honor wild cards (the UGA* thing), and only controls the for of mail sent from the list. Subscribers on "local" nodes receive separate copies of the mail, with only their own address in the To: line. >* Service= LOCAL Coding "Service= UGA*,USCN,GIT*,GTRI01" will do what Harold intended. The rule for coding the SERVICE keyword is "Service= <pattern>,<pattern>,...", where <pattern> is either <ISO-2-char-country-id>, <nodename>, or <prefix>*<middle>*<suffix>. Any of the three pattern pieces can be ommitted, and "**" can be coded as "*". So "Service= US,PUCC,RUT*,*VM,NJ*VS,U*NJ*VS,*NY*VAX,*VX*" is an all-inclusive example. It should be pointed out there is no law preventing Rutgers, for example, from registering a node named UGAMUGA (a Sesame Street reference, I believe), which would match Harold's UGA* pattern. If you're concerned that the list be strictly internal, don't use wild cards in the SERVICE keyword. If you're just trying to keep the list from becoming universally known, it's fine. >Then no one can sign up, unless they are at one of these nodes. Also, if >I am going to do this, I should also add: > >* Confidential= Service > >Now, the list will only appear to people who can subscribe when they do a >LIST command to LISTSERV, and it will not appear in the LIST GLOBAL command. Yup. Definitely a good idea for an internal-only list. Ross Patterson Rutgers University