Skip Navigational Links
LISTSERV email list manager
LISTSERV - COMMUNITY.EMAILOGY.COM
LISTSERV Menu
Log In
Log In
LISTSERV 17.5 Help - LSTSRV-L Archives
LISTSERV Archives
LISTSERV Archives
Search Archives
Search Archives
Register
Register
Log In
Log In

LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Menu
LISTSERV Archives LISTSERV Archives
LSTSRV-L Home LSTSRV-L Home

Log In Log In
Register Register

Subscribe or Unsubscribe Subscribe or Unsubscribe

Search Archives Search Archives
Options: Use Forum View

Use Monospaced Font
Show HTML Part by Default
Show All Mail Headers

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

Print Reply
Subject:
Re: Incorrect domain name substitution?
From:
"John F. Chandler" <[log in to unmask]>
Reply To:
Forum on LISTSERV release 1.7
Date:
Mon, 5 Apr 1993 15:02:00 EST
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
> Recently my server received a subscription request from a user at
> CUNYVM.  For reasons unrelated to this query, the subscription request
> bounced.  What I'm trying to understand is:  how did a real mail origin
> of CUNYVM become "CUNYVM.HARVARD.EDU"????
 
Unfortunately, it's easy and quite common.  You don't have enough
evidence in this case, though, to point the finger of blame.  The
basic scenario is this:  the mail originator was presumably sending
mail from one BITNET node to another (CUNYVM to HARVARDA), and the
addresses, therefore, should not have required any further qualification
than xxxx@CUNYVM and [log in to unmask]  In practice, there is a
mail "domain" called ".BITNET" even though it is not officially
recognized anywhere.  Still, since both sender and receiver were
in the same "domain", the ".BITNET" suffix would have been either
"illegal" (by the official view) or unnecessary (by the de facto view).
Unfortunately, the mail got mixed into a processing path somewhere
along the way including non-BITNET-only mail.  The exact point where
this occurred is not apparent from the evidence.  In this case, it
may actually have occurred at the point of origin (the sender may,
for example, have sent the mail to [log in to unmask]).
Alternatively, it might have occurred somewhere at Harvard.  In any case,
when the mail passed through some MTA at Harvard, the unqualified
name CUNYVM was interpreted in terms of Internet standards, i.e., the
local domain was assumed to be "HARVARD.EDU" rather than "BITNET".
                                       John

ATOM RSS1 RSS2

COMMUNITY.EMAILOGY.COM CataList Email List Search Powered by LISTSERV