Path: utzoo!utgpu!watserv1!watmath!att!rutgers!usc!samsung!uunet!intercon!news
From: amanda@mermaid.intercon.com (Amanda Walker)
Newsgroups: comp.mail.uucp
Subject: Re: Paths and Precedence (Re: Question about From: lines)
Message-ID: <26A1F43B.1039@intercon.com>
Date: 16 Jul 90 17:07:06 GMT
References: <++J4QGC@xds13.ferranti.com> <KARL.90Jul10093842@giza.cis.ohio-state.edu> <3RK4TQE@xds13.ferranti.com> <269B6560.3F1E@intercon.com> <S2M4Q11@xds13.ferranti.com> <269D048B.5A0C@intercon.com> <T:M4WO4@xds13.ferranti.com> <269FEC7D.40E@intercon.com> <UBP4EI9
Sender: usenet@intercon.com (USENET The Magnificent)
Reply-To: amanda@mermaid.intercon.com (Amanda Walker)
Organization: InterCon Systems Corporation, Herndon, VA
Lines: 20

In article <UBP4EI9@ggpc2.ferranti.com>, peter@ficc.ferranti.com (Peter da
Silva) writes:
> I don't suppose it might be because someone between you and them decided to
> block source routing... as you originally implied you were doing?

No, it's because the host in question (let's call it XXX.COM) **requires**
source routing for mail going into the organization, and then, as far as
I can tell, breaks any mail coming in from the outside world, however it's
addressed.  Occasionally, I will get a piece of mail that has managed to
escape with a domain address, and I get hopeful, but evidently subdomains
of XXX.COM are supposed to be secret, and XXX.COM itself will bounce my
replies back.

Argh.

Sound familiar, anyone...?

--
Amanda Walker <amanda@intercon.com>
InterCon Systems Corporation