X-Delivery-Notice:  SMTP MAIL FROM does not correspond to sender.
Newsgroups: bit.listserv.domain-l
Date:         Sun, 15 Nov 1992 15:58:08 IST
From:         Hank Nussbacher <HANK@VM.BIU.AC.IL>
Subject:      Re: Netdata field in DOMAIN NAMES

>Hank, It seems to me you have three classes of mailer addresses in DOMAIN
>NAMES:
>
>1. userid@node   where a matching userid@node mailer is defined in BITEARN
>                 NODES
>
>2. userid@node   where no matching mailer is defined
>
>3. SMTP@INTERBIT
>
>Class 1 can be labeled automatically (by using the format field of the
>MAIL servers tag.  If this field contains 'ND' then :netdata.YES should be
>supplied in DOMAIN NAMES. This would be preferable to having to submit two
>updates requests (even if it meant a months delay in propogation).

Ok.  I can do that.  But I am looking at the 6Oct1992 issue of the
NODES FILE FORMATS and CONTENTS doc and can't understand how to
properly parse a servers tag.  The following comes from PUCC:

servers1 VMMAIL@PUCC(MAIL,PU,M,BSMTP,P_JWAGNER)
servers2 VMMAILB@PUCC(MAIL,PU,M,OUTONLY,P_JWAGNER)
servers3 VMMAILT@PUCC(MAIL,ND PU,M,OUTONLY,P_JWAGNER)

#1 and #2 I follow, but #3 should be (MAIL,ND,M,OUTONLY...) ????

When I look at ANNENRES I see the servers tag as follows:
servers1 MAILER@ANNENRES(MAIL,ND,M,BSMTP,P_POST)

This more or less jives with what the formats and contents doc states,
but I may be misreading it.  When are spaces allowed within the
parenthesis and what is the proper format for the syntax to parse?

>
>Class 2 needs a manual update. Do you actually have any in this category? If
Quite a few.  Here is an exception report I just ran off comparing
the :gateway. in DOMAIN NAMES and the :servers. in BITEARN NODES:
------------------------------------
MAILER@AEARN:
servers1 MAILER@AWIUNI11(MAIL,PU,M,BSMTP,P_ATEADM)

SMTPUSER@EREVAX:  no definition

SMTP@UIUCVMD:
servers1 MAILER@UIUCVMD(MAIL,PU,M,BSMTP,P_00000001)

SMTP@CSEARN
servers1 MAILER@CSEARN(MAIL,PU,M,BSMTP,P_PKL)

SMTP@ALBNYVM1
servers1 MAILER@ALBNYVM1(MAIL,PU,M,BSMTP,P_RPFEIFFE)

SMTPUSER@AMHERST
servers1.MAILER@AMHERST(MAIL,,,,)

MAILER@APPSTATE: no definition

SMTPUSER@ARIZONA
servers1 SMTPUSER@ARIZONA(MAIL,ND PU,M,BSMTP,P_JTRUMBO)

SMTP@UBVM
servers1 MAILER@UBVM(MAIL,PU,M,BSMTP,P_UPOSTMAS)
servers2 MAILER_L@UBVM(MAIL,PU,M,BSMTP,P_UPOSTMAS)

MAILER@CITADEL: no definition

SMTPUSER@UPRENET: no definition

SMTP@CUNYVM
servers1 MAILER@CUNYVM(MAIL,PU,M,BSMTP,P_BYALOW)

SMTP@IUGATE
servers1 MAILER@IUGATE(MAIL,PU,M,BSMTP RFC822,P_RDAVILA)

SMTP@LATECH
servers1 MAILER@LATECH(MAIL,PU,M,BSMTP,P_GBANCKS)

SMTPUSER@LOYVAX: no definition

MAILER@LTUVAX: no definition

MAILER@MIDD: no definition

SMTPUSER@NUACC
servers1 MAILER@NUACC(MAIL,PU,M,BSMTP,P_RSAFIAN)

SMTP@NYUCCVM
servers1 MAILER@NYUCCVM(MAIL,PU,M,BSMTP,P_FHUBER)

SMTPUSER@OBERLIN
servers1 MAILER@OBERLIN(MAIL,ND PU,M,BSMTP,P_MGILBERT)

MAILER@PEPVAX: no definition

SMTPUSER@RHIT: no definition

SMTPUSER@SCU: no definition

MAILER@SLUVCA: no definition

SMTP@SMSVMA
servers1 MAILER@SMSVMA(MAIL,PU,M,BSMTP,P_MOGLESBY)

SMTP@SUVM
servers1 BITMAIL@SUVM(MAIL,PU,M,BSMTP,P_GMALLING)

MAILER@TCUAVMS
servers1 MAILER@TCUAVMS(MAIL,,,,P_POSTMAST)

MAILER@TUSK
servers1 MAILER@TUSK(MAIL,,,,P_POSTMAST)

SMTP@UCCVMA
servers1 MAILER@UCCVMA(MAIL,PU,M,BSMTP,P_RHINTZ)

SMTP@UIUCVMD
servers1 MAILER@UIUCVMD(MAIL,PU,M,BSMTP,P_00000001)

SMTP@USCVM
servers1 MAILER@USCVM(MAIL,PU,M,BSMTP,P_JRIEHL)

SMTPUSER@UVMVAX: no definition

SMTPUSER@VCURUBY
servers1 MAILER@VCURUBY(MAIL,PU,M,BSMTP,P_BLANGFOR)

SMTPUSER@WISCMAC3: no definition

SMTPUSER@WSU
servers1 MAILER@WSU(MAIL,PU,M,BSMTP,P_PVENDT)

SMTP@YALEVM
servers1 MAILER@YALEVM(MAIL,PU,M,BSMTP,P_POSTMAST)

MAILER@TECMTYVM
servers1.MAILER@TECMTYVM(MAIL,,,,)

SMTPNL@HEARN
servers1 MAILER@HEARN(MAIL,PU,M,BSMTP,P_NN)

SMTP@NJECNVM1
servers1 VMMAILER@NJECNVM1(MAIL,PU,M,BSMTP,P_NHAUSER)

SMTP@PTEARN
servers1 MAILER@PTEARN(MAIL,PU,M,OUTONLY,P_PAMORIM)

MAILER@UUCPGATE: no definition

------------------------------------

This report flags the following:
- Those nodes with a gateway defined in DOMAIN NAMES with no server
  tag in BITEARN NODES
- Those nodes with a gateway defined in DOMAIN NAMES with a server tag
  in BITEARN NODES but which does not define the :gateway. defined
  in DOMAIN NAMES
- Those nodes that have ND defined for their format and are recorded
  in DOMAIN NAMES as a gateway
- Those nodes that have empty fields in the their :servers. tag

If someone would care to define to me all the rules involved here I
will gladly write up the program to merge the info into DOMAIN NAMES
from the already existing BITEARN NODES.  I also agree to run the merge
program after every BITEARN NODES update but as John pointed out, that
would cause a slight (30 day) propogation delay in those updates.

>so, I would suggest having them add the mailer to their :servers information
>(you can specify more than one) and converting these addresses to class 1.
>
>Class 3 should always be :netdata.NO until support for NETDATA is made a
>requirement for being an interbit gateway.

Ok.

>
>   John

Hank

P.S. John, ain't MAILER@UUCPGATE your baby? :-)
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU