Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!ctrsol!samsung!rex!wuarchive!texbell!attctc!vector!telecom-gateway From: dmr@csli.stanford.edu (Daniel M. Rosenberg) Newsgroups: comp.dcom.telecom Subject: Re: ATTMAIL Access? Message-ID: Date: 17 Nov 89 20:53:42 GMT Sender: news@vector.Dallas.TX.US Organization: Center for the Study of Language and Information, Stanford U. Lines: 23 Approved: telecom-request@vector.dallas.tx.us X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@vector.dallas.tx.us X-TELECOM-Digest: volume 9, issue 518, message 2 of 11 UCHUCK@unc.bitnet (Chuck Bennett (919)966-1134) writes: >My local email guru told me to try "sp3ba!wcseal@attmail.att.com", below >is the result of that attempt. > > The error message was: > > destination unknown or forwarding disallowed Stuff sent to host.att.com currently goes through att.arpa, aka research.att.com. Soon this will be inet.att.com. AT&T doesn't want to forward to machines outside of AT&T, and the error message you got here indicates that even for attmail, which is significantly enough outside of the AT&T machine network. I'd expect you could bounce this off of uunet: e.g., attmail!wcseal@ uunet.uu.net. So, with that answer, I have a question: just who the heck is UUNET and why do they let us bounce all our mail off of them? # Daniel M. Rosenberg // Stanford CSLI // Eat my opinions, not Stanford's. # dmr@csli.stanford.edu // decwrl!csli!dmr // dmr%csli@stanford.bitnet