[comp.sys.apple] Finding crash

SEWALL@UCONNVM.BITNET (Murph Sewall) (05/10/88)

>Your letter expressing your difficulty in locating crash came through just
>fine.  Things when through a new system this time, though: MITVMA.

All our mail to INET goes through MITVMA (it's our regional gateway, some
other bitnet sites use CUNYVM, CORNELLA, or some other regional gate).
What is new is I reached you via mit.edu to trout.nosc.mil to UUCP -
trout.nosc is milnet's gate to UUCP, apparently our "official" gateway
at psuvax1 is no longer finding you all (UUCP is still UUCP).

>It's too bad BITNET sights have so much trouble: routing in and out of
>UUCP/ARPA, EBCDIC character munging, non-standard headers, etc.  People seem
>to have reversed the problem with respect to mailing to ProLine systems.  I've
>seen a lot of "dammit!  I can't access ProLine's" or, "I've never had so much
>trouble try to reach a ProLine", when the problem clearly is not a ProLine
>issue.  On this side of the net, we have no trouble whatsoever reaching UUCP,
>BITNET, ARPA, INTERNET, MILNET, JUNET, JANET, or whatever.  Of course, our
>springboard is UUCP.

Bitnet sites have no trouble at all reaching the internet (arpa, mil, janet,
junet, etc.), and methinks it's clearly not the Proline's fault; if I can
get UUCP to send to crash I CAN reach you.  You do seem to have less
trouble getting out than Larry Virden has from n8emr (UUCP seems to be able
to cause trouble from either direction).

Your "MX" records are (were?) at uiuc which (until recently) was the ONLY
mailer in christendom that recognized pro-name.cts.com, although psuvax1
would deliver mail addressed only to pro-name (by routing it to uiuc).
Recently, psuvax1's pathdata for the Prolines changed, and subsequent
experience indicates that the path psuvax1 is using doesn't work. Uiuc
still seems to know where you are, but for more than two weeks that
mailer has been bouncing stuff back to me, Chris Chung <CHRIS@BROWNVM>,
Brint Cooper <abc@brl.arpa> (I suppose anyone else who's sent mail
that way) with the message that it "can't reach crash."  I suppose that
means whatever "authority" sends out new pathdata has bunged up gateway
mailers all over everywhere.

Crash clearly is (has been) there or none of the Prolines would be sending
mail out as your "springboard" goes through crash on the way to the
rest of the world.  Anyway, for now everyone can send those "I can't
seem to get through to you guys" message to:
crash!pne01!pro-whichever!person@trout.nosc.mil as trout and crash seem
to speak.

>ARPA: crash!pnet01!pro-sol!mdavis@nosc.mil
>INET: mdavis@pro-sol.cts.com

As I understand it Internet INCLUDES arpa (and mil, janet, edu, etc.).
The arpa address above seems to work (your return address sometimes shows
as "nosc" and sometimes as "trout.nosc"  I'll stick with the latter as
that seems to be working.  The "INET" address bounces from edu (also
part of INET), maybe mdavis%pro-sol.cts.com@trout.nosc.mil works (one of
these days I'll try it).  That's not Proline's fault either; full domain
addressing isn't what it's cracked up to be (not yet anyway).

---------------------
Disclaimer: The "look and feel" of this message is exclusively MINE!
            (subject to change without notice; void where prohibited)

ARPA:   sewall%uconnvm.bitnet@mitvma.mit.edu       Murphy A. Sewall
BITNET: SEWALL@UCONNVM                          School of Business Admin.
UUCP:   ...ihnp4!psuvax1!UCONNVM.BITNET!SEWALL  University of Connecticut
Acknowledge-To: <SEWALL@UCONNVM>

lwv@n8emr.UUCP (Larry W. Virden) (05/14/88)

from what I can tell, the problems come in when mail hits what is known
in uucp/usenet as the backbone sites.  For instance, when I send out mail
here, it typically goes to osu-cis who forwards it either via internet or
uucp.  If uucp, it typically goes to the att backbone.  Now att decides that
he is so smart, he will modify my to addresses so that the mail will get
to the intended addressee in the shortest amount of time.  If that short
amount of time means passing thru rutgers, then the real problems starts.
What seems to be happening is that there are several interpretations of
the paths that are being generated.  One backbone says 'oh, @ before ! except
after %" (or something like that) and another may say "no, ! before @ except
between %" :-) - since it is like talking two different dialects, interesting
/ exasperating things result.

-- 
Larry W. Virden	 75046,606 (CIS)
674 Falls Place, Reynoldsburg, OH 43068 (614) 864-8817
osu-cis!n8emr!lwv (UUCP)	osu-cis!n8emr!lwv@TUT.CIS.OHIO-STATE.EDU (BITNET)
We haven't inherited the world from our parents, but borrowed it from our children.