samitha@matt.ksu.ksu.edu (Samitha Amarasiri) (11/28/90)
I remember reading here about people having problems sending mail to AT&T. A local user got the following error message trying to send mail to AT&T. Any hints as to what could be wrong, and possible solutions are welcome. Please e-mail your responses since I do not read this group regularly. (Please note that he is replying to mail, hence it cannot be a mistyped address.) >======================================================================== >Received: by KSUVM (Mailer R2.07) id 3552; Mon, 26 Nov 90 08:18:38 CST >Date: Mon, 26 Nov 90 08:16:00 CST >Sender: KSU Consulting Group <CONSULT@KSUVM.BITNET> >From: sundar <SUNDAR@KSUVM.BITNET> >Subject: help >To: Samitha Amarasiri <SAMITHA@KSUVM.BITNET> > >Hi, I sent a mail and got the foll. warning message. I >Received: from KSUVM by KSUVM.KSU.EDU (Mailer R2.07) with BSMTP id 8705; Sun, > 25 Nov 90 17:07:06 CST >Received: from att.att.com by KSUVM.KSU.EDU (IBM VM SMTP R1.2.2MX) with TCP; > Sun, 25 Nov 90 17:07:04 CST >From: uucp@att.att.com >Date: Sun, 25 Nov 90 08:05:50 EST >To: SUNDAR@KSUVM.KSU.EDU >Subject: Warning From uucp > >We have been unable to contact machine 'att-mh' since you queued your job. >The following file have not been delivered. > > att-mh!mail likewise!polymer!sundar (Date 11/21) > >The job will be deleted in several days if the problem is not corrected. >If you care to kill the job, execute the following command: >Note: this command can only be executed on machine (att): > > uustat -katt-mhZf4c9 > > Sincerely, > att!uucp > >############################################# >##### Data File: ############################ >From KSUVM.KSU.EDU!SUNDAR Wed Nov 21 12:55 CST 1990 remote from att >Received: by att.att.com; Wed Nov 21 14:10:38 1990 >Received: from KSUVM.KSU.EDU by KSUVM.KSU.EDU (IBM VM SMTP R1.2.2MX) with BSMTP > id 5638; Wed, 21 Nov 90 14:48:00 CST >Received: by KSUVM (Mailer R2.07) id 1793; Wed, 21 Nov 90 13:01:42 CST >Date: Wed, 21 Nov 90 12:55 CST >From: sundar <SUNDAR@KSUVM.KSU.EDU> >To: <polymer!sundar@likewise.att.com> >In-Reply-To: Your message of Mon 19 Nov 90 10:03:39 EST > > > [...] > > > -- Samitha Amarasiri |BITNET :samitha@ksuvm |KSU Computing Activities| |INTERNET:samitha@matt.ksu.ksu.edu |Cardwell Hall, Manhattan| |PHONE :(913) 532-6311 |KS 66506 |
mark@cbnewsb.cb.att.com (Mark Horton) (11/28/90)
In article <1990Nov28.145114.29683@maverick.ksu.ksu.edu>, samitha@matt.ksu.ksu.edu (Samitha Amarasiri) writes: > > I remember reading here about people having problems sending mail to > AT&T. A local user got the following error message trying to send > mail to AT&T. Any hints as to what could be wrong, and possible > solutions are welcome. Please e-mail your responses since I do not > read this group regularly. (Please note that he is replying to mail, > hence it cannot be a mistyped address.) Please report problems about Email into AT&T to postmaster@att.com, since there is no reason for the AT&T Postmaster to read this newsgroup regularly either. I will mail a copy of this to the sender as well. > >We have been unable to contact machine 'att-mh' since you queued your job. The AT&T Internet gateway chose Thanksgiving weekend to get stuck, and a sizable backlog of incoming email accumulated. The warning you got is just that, a warning that your mail had not yet been delivered. The backlog has since been cleared out and all mail is functioning normally. Mark Horton