HDTenEightyP/NetNews huggingface dataset:
X-Envelope-to: nodmgt-l@bitnic.bitnet
Content-transfer-encoding: 7BIT
X-Mts: smtp
Newsgroups: bit.listserv.nodmgt-l
Date:         Wed, 2 Sep 1992 10:56:37 -0400
From:         Greg Smith <smith@HELIOTROPE.BUCKNELL.EDU>
Subject:      UPDATE@BITNIC doesn't
Comments: cc: weber@bucknell.edu

Well, it's September 2 and I figured that I'd be able to send my DELETE
NODE and DELETE MEMBER commands to remove Bucknell University from
BITNET.  We've already mailed in our paper resignation.  I got the
DELETE NODE commands to work, although, much to my surprise, they were
executed in verify mode only.  However, DELETE MEMBER MN_BUCKNELL just
generates an error telling me that I have to DELETE my NODEs first and
that my request was NOT executed.  However, I DID delete the NODEs
first and I even received an acknowledgment to that effect before the
DELETE MEMBER command was processed.  If UPDATE has to queue the
updates because of the lengthy synchronization process, then why
doesn't it also queue my DELETE MEMBER command.  I really don't want to
have to repeatedly try to DELETE my MEMBER until BITNIC gets finished
with the 9210 update cycle, which I would have thought would have
occurred by now.  What's the story, here?

Yes, I'm a bit frustrated right now, and I apologize for that.  I was
just hoping that following the directions in the DELETE NODE and DELETE
MEMBER files from BITNIC would be enough.  The fact that the automated
procedure via UPDATE@BITNIC has a locked database for the majority of
the days in every month just got to me this morning.

Greg Smith

======================================================================
Greg Smith, Systems Analyst                   Computer Services
Internet:   smith@bucknell.edu                Bucknell University
AT&Tnet:    (717) 524-1801                    Lewisburg PA  17837  USA
======================================================================
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.nodmgt-l
Date:         Wed, 2 Sep 1992 19:29:06 EDT
From:         "Andrew T. Robinson" <ROBINSON@BITNIC.BITNET>
Subject:      Re: UPDATE@BITNIC doesn't

>Sounds like the code needs fixing to me...the user should not be bothered
>with such issues.  Just my 0.5 cents.
>
  .5 cents?  You're right, the user should NOT be bothered with such
  issues--but while a solution is *programmable* it's not necessarily
  practical from a cost/benefit standpoint.  But if folks can convince
  Jim it's a priority I'm sure I can correct the problem.

  I personally don't think it's worth it, because there is a simple
  and documented workaround (submitted related commands in a single
  job).  On the other hand, an issue came up this month with topology
  changes submitted at the last minute--it was impossible for the
  responsible parties to approve them before they were automatically
  cancelled by the arrival of the cutoff date.  The two problems are
  sorta related, and since I think the latter will need to be solved, the
  former may get rolled up into that.  And as usual, I'm always open
  to technical suggestions as to how it may be accomplished.

  So, I think your comments are worth a full 2 cents! :-)

Andy
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.nodmgt-l
Date:         Thu, 3 Sep 1992 15:42:59 CDT
From:         "McMahon,Brian D" <MCMAHON@GRIN1.BITNET>
Subject:      Apology

Netfolk,

A stress-induced transient brain failure (read: stupidity) on my part
caused me to send the missing-student message to a wider audience than
intended.  I just noticed the error in reviewing my mail.  I sincerely
regret the mistake, and apologize for any inconvenience caused.  This is
not a good day on campus.

Terribly sorry.

Brian McMahon (BDM13)    <MCMAHON@GRIN1.BITNET>    <MCMAHON@AC.GRIN.EDU>
Postmaster / Acad. Software Support   Grinnell College Computer Services
Grinnell, Iowa 50112 USA   Voice: +1 515 269 4901   Fax: +1 515 269 4936
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.nodmgt-l
Date:         Wed, 2 Sep 1992 15:00:25 EDT
From:         Larry Snodgrass <SNODGRAS@BITNIC.BITNET>
Subject:      Re: UPDATE@BITNIC doesn't
              2 Sep 1992 10:56:37 -0400 from <smith@HELIOTROPE.BUCKNELL.EDU>

On Wed, 2 Sep 1992 10:56:37 -0400 Greg Smith said:
>Well, it's September 2 and I figured that I'd be able to send my DELETE
>NODE and DELETE MEMBER commands to remove Bucknell University from
>BITNET.  We've already mailed in our paper resignation.  I got the
>DELETE NODE commands to work, although, much to my surprise, they were
>executed in verify mode only.  However, DELETE MEMBER MN_BUCKNELL just
>generates an error telling me that I have to DELETE my NODEs first and
>that my request was NOT executed.  However, I DID delete the NODEs
>first and I even received an acknowledgment to that effect before the
>DELETE MEMBER command was processed.  If UPDATE has to queue the
>updates because of the lengthy synchronization process, then why
>doesn't it also queue my DELETE MEMBER command.  I really don't want to
>have to repeatedly try to DELETE my MEMBER until BITNIC gets finished
>with the 9210 update cycle, which I would have thought would have
>occurred by now.  What's the story, here?

I'm sorry about the error you have encountered.  We will look into that
and get it fixed as soon as possible.

The synchronization of UPDATE cannot happen until the master BITEARN NODES
file is updated with the 9210 update which is due out this weekend and
usually comes out the first full weekend of each month.  That schedule has
been around as long as I remember and is well documented in the Update
Procedures document.

>Yes, I'm a bit frustrated right now, and I apologize for that.  I was
>just hoping that following the directions in the DELETE NODE and DELETE
>MEMBER files from BITNIC would be enough.  The fact that the automated
>procedure via UPDATE@BITNIC has a locked database for the majority of
>the days in every month just got to me this morning.
>
>Greg Smith

Any questions or problems regarding UPDATE@BITNIC can be sent to
UPD_INFO@BITNIC.

Larry Snodgrass
BINTIC
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.nodmgt-l
Date:         Wed, 2 Sep 1992 11:50:34 EDT
From:         Larry Snodgrass <SNODGRAS@BITNIC.BITNET>
Subject:      Re: MAILER NAMES file

On Tue, 1 Sep 1992 01:32:02 +0200 Eric Thomas said:
>>2) A  similar function to MAILER  NAMES can be accomplished  by adding a
>>   node to BITEARN NODES and specifying a :serversN tag.
>
>That much I don't understand. As far as  I can see, a mail only node is a
>node which is  not connected to BITNET  and should not be  in the routing
>tables, but  somehow gets mail  via some  gateway. There are  hundreds of
>thousands of  mail only nodes  served by MX records  and the like,  I see
>absolutely no reason to have a special mechanism for BITNET nowadays. And
>frankly, I doubt anyone is interested in a type of connectivity that only
>supports mail from BITNET.
>
>  Eric

I'll admit there aren't many but there are a few people interested in
this type of connectivity.

1)  An organization on both BITNET and the Internet decides to drop their
    BITNET connectivity but has lots of users who are on lots of mailing
    lists with their BITNET address and have lots of friends who know their
    BITNET address so they would like to continue their CREN membership and
    still receive mail addressed to their BITNET address.  So they find
    some site to forward their BITNET-addressed mail to their Internet
    address and keep a node entry in the database.  In most cases this need
    would eventually go away once everyone is known by their Internet address.

2)  An organization which has a host on BITNET would like their users on
    some other system or private local network be able to send and receive
    BITNET mail but they can only do it through their mail gateway on their
    BITNET host.

Based on the comments I've seen so far its not worth doing.
Thanks to everyone who responded.

Larry
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Resent-Date:  Thu, 27 Aug 92 16:23:08 EDT
X-Resent-From:  LISTSERV Manager <LISTMGR@BITNIC>
X-Resent-To:    Larry Snodgrass <SNODGRAS@BITNIC>
X-Resent-Date: Wed, 26 Aug 92 17:22:07 EDT
X-Resent-From: Network Mailer <MAILER@BITNIC>
X-Resent-To: LISTMGR@BITNIC
Newsgroups: bit.listserv.nodmgt-l
Date:         Mon, 31 Aug 1992 13:39:08 EDT
Comments:     Resent-From: Larry Snodgrass <SNODGRAS@BITNIC>
Comments:     Originally-From: Rick Broadhead <YSAR1111@VM1.YorkU.CA>
From:         Larry Snodgrass <SNODGRAS@BITNIC.BITNET>
Subject:      ISO Country Codes

Who maintains COUNTRY ISOCODES on NETSERV?  It has been brought to
my attention that COUNTRY ISOCODES is not current.
The mail below references COUNTRY CODES on LISTSERV@BITNIC but that
file is a duplicate of COUNTRY ISOCODES from NETSERV (don't ask me
why the name is slightly different, it was like that before I got here).

Anyway, I see that ISO 3166 has several new country codes.  Should they
be added to COUNTRY ISOCODES?

Larry
----------------------------Original message----------------------------
Dear Postmaster:

Could you please have the person who maintains the NETINFO Filelist on your
listserv contact me.  The file COUNTRY CODES is outdated, and does not
include new top-level domains such as LT.  I would like to get an
updated copy of this document.  Thanks.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.nodmgt-l
Date:         Tue, 25 Aug 1992 15:46:41 EDT
From:         Jim Conklin <CONKLIN@BITNIC.BITNET>
Subject:      Re: BITNET Postmasters' Guide for VAX/VMS Systems
              25 Aug 1992 13:26:32 -0400 from <gettes@PRINCETON.EDU>

On Tue, 25 Aug 1992 13:26:32 -0400 <gettes@PRINCETON.EDU> said:
>On Tue, 25 Aug 92 11:33:05 -0400 conklin@bitnic.bitnet said:
>>     If you need assistance, please send e-mail to INFO@BITNIC.  In
>> addition, BITNIC sponsors a mentoring service for CREN members, provided
>> on a volunteer basis by knowledgeable staff at member sites, and BITNIC
>> staff will be glad to find a mentor to assist you in managing your
>> BITNET node if you request mentoring in your message to INFO@BITNIC.
>
>This is the first I have heard of this service. I am interested in it.
>Can somebody provide information about it? What platforms are supported?
>Who are the mentors?
>
>/mrg

  The service was started at the suggestion of Terry Kennedy, I believe.
It has historically concentrated on support for VAX/VMS (now OpenVMS, I'm
told), because that's where the expertise of the volunteers was.
  We'd like to expand it to other systems, which requires people with the
relevant expertise.  Volunteers are neded in order for this to happen.
  The volunteers accept, as they are able, requests for help sent by CREN to
a list to which they subscribe.
                               Jim
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.nodmgt-l
Date:         Thu, 3 Sep 1992 00:57:22 +0200
From:         Eric Thomas <ERIC@SEARN.BITNET>
Subject:      Re: MAILER NAMES file
              2 Sep 1992 11:50:34 EDT from Node Management <NODMGT-L@UGA>

On Wed, 2 Sep 1992 11:50:34 EDT Larry Snodgrass <SNODGRAS@BITNIC> said:

>1) An organization on both BITNET and the Internet decides to drop their
>    BITNET connectivity but has lots of users who are on lots of mailing
>    lists with  their BITNET address and  have lots of friends  who know
>    their  BITNET address  so they  would  like to  continue their  CREN
>    membership and still receive mail addressed to their BITNET address.

a. Their problem for leaving BITNET, you can't have the cake and eat it.

b. They're no longer members of CREN,  why should they be allowed to have
   a node, mail-only or not mail-only?

c. That can be done with a regular NJE entry anyway.

>2) An organization which has a host  on BITNET would like their users on
>    some  other system  or private  local network  be able  to send  and
>    receive  BITNET mail  but they  can only  do it  through their  mail
>    gateway on their BITNET host.

Define an  NJE node  and REROUTE  incoming files to  the mailer,  or some
special virtual machine specially designed  for this. That is how Iceland
is dealt with at SEARN.

  Eric
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Delivery-Notice:  SMTP MAIL FROM does not correspond to sender.
Newsgroups: bit.listserv.nodmgt-l
Date:         Mon, 31 Aug 1992 15:24:18 EDT
From:         Tram Nguyen <TRAMNG@ACADVM1.UOTTAWA.CA>
Subject:      Network Management System

Hi,

I am looking for a network management system for our network here.
Our backbone network consists of VM mainframe, UNIX hosts, PCs and a
few LANs running Novell.  Did anyone have a chance to work with any
NMS that could be able to provide basic networking capabilities
and also  be able to manage as the network grows ?
Any info, advice or hints are greatly appreciated.

Tram Nguyen,
University of Ottawa.
From: schafer@is.rice.edu (Richard Alan Schafer)
Newsgroups: bit.listserv.nodmgt-l
Subject: Re:      MAILER NAMES file
Date: 31 Aug 1992 22:23:51 GMT
Organization: Rice University

Is there really any likelihood that a new flood of mail only nodes will appear
after several years of just dead ones in that file?  I see every reason to
retire MAILER NAMES; I see less reason to invent a new set of tags in 
BITEARN NODES to support a function no one is likely to use.

-- 
Richard
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: Arnold Consulting
X-Envelope-To: uga.BITNET!nodmgt-l
X-Vms-To: IN%"nodmgt-l@uga"
X-Vms-Cc: ARNOLD
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Newsgroups: bit.listserv.nodmgt-l
Date:         Tue, 1 Sep 1992 10:18:24 -0500
From:         "Stephen L. Arnold" <ARNOLD@ARNOLD.COM>
Subject:      Re: MAILER NAMES file

Regarding support of the :MSG.N tag:  Jnet never looks at BITEARN NODES,
only at the routing tables, so it would never attempt to send messages
to the proposed :TYPE.MAIL nodes, however...

Larry said:
>I propose that  no more nodes be  added to MAILER NAMES and  the file be
>abolished for two reasons.

I guess I'm forth to agree with this on this list.

>2) A  similar function to MAILER  NAMES can be accomplished  by adding a
>   node to BITEARN NODES and specifying a :serversN tag.

Like several others, I agree that this is a bad procedure.  Instead of
establishing an *NJE* name for the system, a *domain-style-name* (in a
new second-level domain, if necessary) should be established for the
system, and the domain should be registered in DOMAIN NAMES.  Then the
system can exchange mail with both BITNET and Internet users using only
a private link to a BITNET-only node (as long as the BITNET node is
running a mailer, as required since 1 January 1992!).  Better
connectivity and no new software to write!

"Steve"   Stephen L. Arnold, Ph.D., Principal, Arnold Consulting
Address   4138 Iroquois Drive, Madison, Wisconsin  53711-3701  U.S.A.
Telephone +1 (608) 238-7835             Pager +1 (608) 277-4053
Internet  Arnold@Arnold.Com             BITNET  ARNOLD@WISCPSL
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.nodmgt-l
Date:         Thu, 3 Sep 1992 12:50:06 CET
From:         Hans-Ulrich Giese <U001212@HEARN.BITNET>
Subject:      new/del nodes for 9210
Comments: To: xmailer@HEARN.BITNET

here comes the monthly list of new/del nodes for 9210 :

new nodes :

BRCETESB 0928 BR ANSP
BRPUCRS  0929 BR ANSP
UDEMAV01 1277 MX BITNET
ALBNERIC 0925 US BITNET
ASU      0926 US BITNET
PSUBEH2  1245 US BITNET
VDH      1313 US BITNET
WCHESTER 1482 US BITNET
WINGRA   1519 US BITNET
JPNTGU00 1149 JP CAREN
BANUIA61 0032 BE EARN
DMUMPIMV 0728 DE EARN
DMUMPINT 0626 DE EARN
DMUMPIWH 0260 DE EARN
HUBME51  0924 HU EARN
TRATAUNI 0923 TR EARN

delete nodes :
ALMCSVM1 ALMCSVM2  ALMCSVM6  ALMCSVS5  ALMVMB    ALMVMC    BBRBFU01
BLIULG13 BRUFMGEE  BUMETA    DMSWWU2B  HNYKUN12  POLYGRAF  POLYTECH
PUCE     TAMAIL    UCSG      UTCHPC    WUMS      WUMS2
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.nodmgt-l
Date:         Fri, 4 Sep 1992 15:41:41 +0200
From:         Eric Thomas <ERIC@SEARN.BITNET>
Subject:      Monthly list of LISTSERV sites with outdated BITEARN NODES files

The following 26 servers (10%) use an outdated BITEARN NODES file:

 BRUFPB   VERS9208
 CFRVM    VERS9207
 EB0UB012 VERS9208
 EMUVM1   VERS9208
 FRSAC12  VERS9208
 FRULM11  VERS9010
 HASARA11 VERS9208
 INDYCMS  VERS9208 (backbone server)
 JHUHYG   VERS9208 (backbone server)
 JPNCUN10 VERS9207
 KRSNUCC1 VERS9208
 LMUACAD  VERS9208
 MIAMIU   VERS9208
 NASVM    VERS9208
 NUSVM    VERS9208 (backbone server)
 RITVM    VERS9208 (backbone server)
 TSCVM    VERS8904
 TTUVM1   VERS9208
 UMDSCVM  VERS9208
 UMSSMDVM VERS9108
 UNALCOL  VERS9207
 UNAMVM1  VERS9208 (backbone server)
 UNCCVM   VERS9208
 UREGINA1 VERS9208 (backbone server)
 VILLVM   VERS9207 (backbone server)
 VTVM2    VERS9208 (backbone server)

The following servers have been unreachable for more than 7 days:

 BRUFMS     FRECP12    SAMFORD    UCHDCI01   UDESVM     VMNMDSC
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.nodmgt-l
Date:         Mon, 31 Aug 1992 14:33:09 EDT
From:         Larry Snodgrass <SNODGRAS@BITNIC.BITNET>
Subject:      MAILER NAMES file
Comments: To: technews@BITNIC.BITNET, crentac@BITNIC.BITNET

The next version of MAILER NAMES (9209) that I store on NETSERV and
LISTSERV@BITNIC will not have any entries, only comments.  I have
contacted someone for each entry that was in that file and confirmed
that each node no longer exists.  This was a suggestion made at the
February Pre-SHARE Bittech meeting.

MAILER NAMES historically has been used to identify mail-only
BITNET hosts (hosts without true NJE connectivity but can have
mail gatewayed to them through some other BITNET node).  MAILER
NAMES is used in the configuration process of the VM Network
Mailer to add entries to its BITNET node table.

I propose that no more nodes be added to MAILER NAMES and the file
be abolished for two reasons.

1) As far as I know MAILER NAMES is only used by the VM Network Mailer
   and not by other mailers on BITNET.  This means only sites with
   the VM Network Mailer can send mail to the nodes in MAILER NAMES.

2) A similar function to MAILER NAMES can be accomplished by adding
   a node to BITEARN NODES and specifying a :serversN tag.

The advantage to #2 is that these nodes will appear in XMAILER
NAMES and mailers other than the VM Network Mailer will then know
about them and be able to send mail to them.

If the node is truely a mail-only node then the disadvantage to
#2 is that the node would show up in the routing tables and any
files sent to that node would build up at the node to which it is
connected (messages could be disabled with a :msg.N tag in the entry).

In reality many sites have already implemented the #2 solution.

I would like to see some discussion on NODMGT-L on the following
proposal.

Allow a ":type.MAIL" entry in BITEARN NODES which has the same
requirements as a ":type.NJE" entry except for the following:

1) Contains a ":type.MAIL" tag.
2) Ignored by the routing table generators so that the node
   does not appear in the routing tables.  (I believe the
   routing table generators only look at :type.NJE entries so
   this is not an issue.)
3) Must contain a :serversN tag to specify the mail gateway.
4) Must not contain any :linksN tags.

These :type.MAIL entries could then be included in XMAILER NAMES and would
be known to all mailers on the network but would not show up in the
routing tables.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.nodmgt-l
Date:         Mon, 31 Aug 1992 17:02:21 CDT
From:         Barry Finkel <B19141@ANLVM.CTD.ANL.GOV>
Subject:      COUNTRY ISOCODES

>Who maintains COUNTRY ISOCODES on NETSERV?  It has been brought to
>my attention that COUNTRY ISOCODES is not current.
>The mail below references COUNTRY CODES on LISTSERV@BITNIC but that
>file is a duplicate of COUNTRY ISOCODES from NETSERV (don't ask me
>why the name is slightly different, it was like that before I got here).

From my NODMGT-L NOTEBOOK:
>Date:         Tue, 10 Mar 1992 11:44:33 +0100
>Reply-To:     Node Management Discussion <NODMGT-L@BITNIC.BITNET>
>Sender:       Node Management Discussion <NODMGT-L@BITNIC.BITNET>
>From:         "Alain FONTAINE (Postmaster - UCL)" <fontaine@SRI.UCL.AC.BE>
>Subject:      Re: New/Updated version of COUNTRY ISOCODES
>To:           Multiple recipients of list NODMGT-L <NODMGT-L@BITNIC>
>In-Reply-To:  Message of Mon, 9 Mar 92 19:25:26 CST from <COURCOUL@VMTECQRO>
>
>I am maintaining COUNTRY ISOCODES on NETSERV. The way it works : I receive
>the official announcements from the DIN secretariat (which maintains ISO 3166
>on behalf of ISO). When I get an update, it is included in the file on the
>same day (OK, week). I did not receive anything yet on those new independent
>countries. Well, I guess ISO must be very careful with such heavily politi-
>cally loaded matters.                                       /AF
----------------------------------------------------------------------------
Barry S. Finkel
Computing and Telecommunications Division
Argonne National Laboratory               BITNET:   B19141@ANLVM
9700 South Cass Avenue                    Internet: B19141@ANLVM.CTD.ANL.GOV
Building 221, Room B223                   Phone:    (708) 252-7277
Argonne, IL   60439-4844                  Facsimile:(708) 252-5983
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.nodmgt-l
Date:         Thu, 3 Sep 1992 11:53:18 EDT
From:         Larry Snodgrass <SNODGRAS@BITNIC.BITNET>
Subject:      Re: MAILER NAMES file

On Thu, 3 Sep 1992 00:57:22 +0200 Eric Thomas said:
>On Wed, 2 Sep 1992 11:50:34 EDT Larry Snodgrass <SNODGRAS@BITNIC> said:
>
>>1) An organization on both BITNET and the Internet decides to drop their
>>    BITNET connectivity but has lots of users who are on lots of mailing
>>    lists with  their BITNET address and  have lots of friends  who know
>>    their  BITNET address  so they  would  like to  continue their  CREN
>>    membership and still receive mail addressed to their BITNET address.
>
>a. Their problem for leaving BITNET, you can't have the cake and eat it.
>
>b. They're no longer members of CREN,  why should they be allowed to have
>   a node, mail-only or not mail-only?

But they are still members of CREN.  The paragraph above says
"they would like to continue their CREN membership."
In exchange for their CREN membership they would like to receive this mail
mail forwarding service.

>c. That can be done with a regular NJE entry anyway.

I agree.  As I said in my original mail, it is already being done with the
current spec.  And will continue to be done that way given the opposition.

An interesting note though, in section 1.2 of NEWTAGS DESCRIPT a :type.MAIL
entry is referenced and defined but "MAIL" is not included in section 2.3.34
where the values of the :type tag are defined.

Larry
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.nodmgt-l
Date:         Tue, 1 Sep 1992 01:32:02 +0200
From:         Eric Thomas <ERIC@SEARN.BITNET>
Subject:      Re: MAILER NAMES file
              31 Aug 1992 14:33:09 EDT from Node Management <NODMGT-L@UGA>

On Mon, 31 Aug 1992 14:33:09 EDT Larry Snodgrass <SNODGRAS@BITNIC> said:

>I propose that  no more nodes be  added to MAILER NAMES and  the file be
>abolished for two reasons.

I concur.

>2) A  similar function to MAILER  NAMES can be accomplished  by adding a
>   node to BITEARN NODES and specifying a :serversN tag.

That much I don't understand. As far as  I can see, a mail only node is a
node which is  not connected to BITNET  and should not be  in the routing
tables, but  somehow gets mail  via some  gateway. There are  hundreds of
thousands of  mail only nodes  served by MX records  and the like,  I see
absolutely no reason to have a special mechanism for BITNET nowadays. And
frankly, I doubt anyone is interested in a type of connectivity that only
supports mail from BITNET.

  Eric
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU