The use of a :newnode tag in  the entry of a node running LISTSERV causes
problems  with the  LISTSERV running  on  that system.  When support  for
:newnode was originally designed, this was not seen as a problem: the tag
is  supposed  to  be  inserted  with  the  update  cycle  preceding  your
disconnection from BITNET. At this point  you should also contact me, not
because of the tag but because I need to know when a LISTSERV site leaves
BITNET, and I would remove you from PEERS NAMES. In other words, there is
no problem when the tag is used for the purpose for which it was intended
(so your implied warranty doesn't apply ;-) ).
 
If on the other  hand you want to insert the tag a  long time in advance,
in anticipation of a decision to leave BITNET next July, you will have to
modify BITEARN NODES  every month to remove the tag  before feeding it to
LISTSERV. This will restore proper behaviour for things like transferring
files to  the postmaster  or checking for  postmaster privileges.  On the
other hand, it will  of course bypass the other side  effects of the tag,
as far as your server in concerned. It would not be easy to have the side
effects respected  for regular use, but  ignored where it could  hurt; in
fact, it  would be pretty much  like second guessing what  you meant when
you  issued the  command.  With LISTSERV-TCP/IP,  the NODE  configuration
variable contains  an Internet  hostname and  everything falls  in place.
With  LISTSERV-NJE, it  would  be a  series of  kludges  that would  only
benefit  those  sites  that  will never  purchase  service  licenses  for
LISTSERV-NJE, so L-Soft is not going to "fix" it. People dumping VM would
not buy  the new version, and  people leaving BITNET but  keeping VM will
need LISTSERV-TCP/IP anyway, where the problem is not applicable.
 
  Eric