LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Eric Thomas <[log in to unmask]>
Wed, 16 Sep 1992 23:18:28 +0200
text/plain (29 lines)
On Wed, 16 Sep 1992 16:24:20 EDT Greg Kroll <USDGK@VTVM1> said:
 
>Under 1.7c anyone  at Virginia Tech (*.vt.edu) could send  to a list set
>up as follows:
>
>Local= *.vt.edu
>Service= Local
>Send= Service
>
>My question is, why doesn't it work  the way it used to? LISTSERV should
>know that *.vt.edu is "local", however it treats it as if it is not. Any
>ideas?
 
When I converted  the code to PASCAL,  I saw that the local  NJE node was
always added to the "Local=" keyword.  I thought this was not logical, if
you override the definition of "localness" for a list you probably expect
your definition  to be  entirely respected. Furthermore  the domain-style
address was not local  - only the NJE one. This was  not consistent, so I
took it away.
 
But the root of your problem is different: the definition only contains a
domain-style  *wildcard*. While  LISTSERV  does know  that  any file  for
VTVM2.VT.EDU can be sent to the BITNET node VTVM2, it has never performed
mappings  in the  other  direction. This  definition  works for  commands
coming from VTVM2.VT.EDU but fails for commands sent via TELL from VTVM2.
It should work if you add VTVM1 and VTVM2 to the definition.
 
  Eric

ATOM RSS1 RSS2