Am I the only listowner getting this? What is/has been done? Is this a tamu problem or a netcom problem? Blaine Co-Owner - Sex-L Owner - Grunge-L, MUD-L, Astros, autos-l, Reds, Devilrays, and Brewers ---------- Forwarded message ---------- Date: Wed, 19 Jun 1996 09:49:37 -0600 From: L-Soft list server at Texas A&M (1.8b) <[log in to unmask]> To: Blaine Thompson <[log in to unmask]> Subject: SEX-L: error report from POSTAL.TAMU.EDU The enclosed message, found in the SEX-L mailbox and shown under the spool ID 3189 in the system log, has been identified as a possible delivery error notice for the following reason: "X-Report-Type:" field found in the mail header. ------------------------ Message in error (189 lines) ------------------------- Return-Path: <> Received: from TAMVM1.TAMU.EDU (NJE origin LISTSERV@TAMVM1) by TAMVM1.TAMU.EDU (LMail V1.2a/1.8a) with BSMTP id 0131; Wed, 19 Jun 1996 09:42:00 -0600 Received: from TAMVM1 (NJE origin SMTPH@TAMVM1) by TAMVM1.TAMU.EDU (LMail V1.2a/1.8a) with BSMTP id 0119; Wed, 19 Jun 1996 09:41:52 -0600 Received: from postal.tamu.edu by tamvm1.tamu.edu (IBM VM SMTP V2R2) with TCP; Wed, 19 Jun 96 09:41:50 CST Received: from localhost (localhost) by postal.tamu.edu (8.7.5/8.7.3) with internal id BDV03291; Wed, 19 Jun 1996 09:10:30 -0500 (CDT) Date: Wed, 19 Jun 1996 09:10:30 -0500 (CDT) From: Mail Delivery Subsystem <[log in to unmask]> Subject: Warning: could not send message for past 12 hours Message-Id: <[log in to unmask]> To: <[log in to unmask]> MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary="BDV03291.835193430/postal.tamu.edu" Auto-Submitted: auto-generated (warning-timeout) This is a MIME-encapsulated message --BDV03291.835193430/postal.tamu.edu ********************************************** ** THIS IS A WARNING MESSAGE ONLY ** ** YOU DO NOT NEED TO RESEND YOUR MESSAGE ** ********************************************** The original message was received at Tue, 18 Jun 1996 17:45:01 -0500 (CDT) from postal.tamu.edu [128.194.103.24] ----- The following addresses have delivery notifications ----- <[log in to unmask]> (transient failure) <[log in to unmask]> (transient failure) <[log in to unmask]> (transient failure) <[log in to unmask]> (transient failure) <[log in to unmask]> (transient failure) <[log in to unmask]> (transient failure) <[log in to unmask]> (transient failure) <[log in to unmask]> (transient failure) <[log in to unmask]> (transient failure) <[log in to unmask]> (transient failure) <[log in to unmask]> (transient failure) <[log in to unmask]> (transient failure) ----- Transcript of session follows ----- 451 <[log in to unmask]>... IX.NETCOM.COM: Name server timeout 451 <[log in to unmask]>... IX.NETCOM.COM: Name server timeout 451 <[log in to unmask]>... IX.NETCOM.COM: Name server timeout 451 <[log in to unmask]>... IX.NETCOM.COM: Name server timeout 451 <[log in to unmask]>... IX.NETCOM.COM: Name server timeout 451 <[log in to unmask]>... IX.NETCOM.COM: Name server timeout 451 <[log in to unmask]>... IX.NETCOM.COM: Name server timeout 451 <[log in to unmask]>... IX.NETCOM.COM: Name server timeout 451 <[log in to unmask]>... IX.NETCOM.COM: Name server timeout 451 <[log in to unmask]>... IX.NETCOM.COM: Name server timeout 451 <[log in to unmask]>... IX.NETCOM.COM: Name server timeout 451 <[log in to unmask]>... IX.NETCOM.COM: Name server timeout Warning: message still undelivered after 12 hours Will keep trying until message is 3 days old --BDV03291.835193430/postal.tamu.edu Content-Type: message/delivery-status Reporting-MTA: dns; postal.tamu.edu Arrival-Date: Tue, 18 Jun 1996 17:45:01 -0500 (CDT) Final-Recipient: RFC822; [log in to unmask] Action: delayed Status: 4.4.3 Last-Attempt-Date: Wed, 19 Jun 1996 09:10:30 -0500 (CDT) Will-Retry-Until: Fri, 21 Jun 1996 17:45:01 -0500 (CDT) Final-Recipient: RFC822; [log in to unmask] Action: delayed Status: 4.4.3 Last-Attempt-Date: Wed, 19 Jun 1996 09:10:30 -0500 (CDT) Will-Retry-Until: Fri, 21 Jun 1996 17:45:01 -0500 (CDT) Final-Recipient: RFC822; [log in to unmask] Action: delayed Status: 4.4.3 Last-Attempt-Date: Wed, 19 Jun 1996 09:10:30 -0500 (CDT) Will-Retry-Until: Fri, 21 Jun 1996 17:45:01 -0500 (CDT) Final-Recipient: RFC822; [log in to unmask] Action: delayed Status: 4.4.3 Last-Attempt-Date: Wed, 19 Jun 1996 09:10:30 -0500 (CDT) Will-Retry-Until: Fri, 21 Jun 1996 17:45:01 -0500 (CDT) Final-Recipient: RFC822; [log in to unmask] Action: delayed Status: 4.4.3 Last-Attempt-Date: Wed, 19 Jun 1996 09:10:30 -0500 (CDT) Will-Retry-Until: Fri, 21 Jun 1996 17:45:01 -0500 (CDT) Final-Recipient: RFC822; [log in to unmask] Action: delayed Status: 4.4.3 Last-Attempt-Date: Wed, 19 Jun 1996 09:10:30 -0500 (CDT) Will-Retry-Until: Fri, 21 Jun 1996 17:45:01 -0500 (CDT) Final-Recipient: RFC822; [log in to unmask] Action: delayed Status: 4.4.3 Last-Attempt-Date: Wed, 19 Jun 1996 09:10:30 -0500 (CDT) Will-Retry-Until: Fri, 21 Jun 1996 17:45:01 -0500 (CDT) Final-Recipient: RFC822; [log in to unmask] Action: delayed Status: 4.4.3 Last-Attempt-Date: Wed, 19 Jun 1996 09:10:30 -0500 (CDT) Will-Retry-Until: Fri, 21 Jun 1996 17:45:01 -0500 (CDT) Final-Recipient: RFC822; [log in to unmask] Action: delayed Status: 4.4.3 Last-Attempt-Date: Wed, 19 Jun 1996 09:10:30 -0500 (CDT) Will-Retry-Until: Fri, 21 Jun 1996 17:45:01 -0500 (CDT) Final-Recipient: RFC822; [log in to unmask] Action: delayed Status: 4.4.3 Last-Attempt-Date: Wed, 19 Jun 1996 09:10:30 -0500 (CDT) Will-Retry-Until: Fri, 21 Jun 1996 17:45:01 -0500 (CDT) Final-Recipient: RFC822; [log in to unmask] Action: delayed Status: 4.4.3 Last-Attempt-Date: Wed, 19 Jun 1996 09:10:30 -0500 (CDT) Will-Retry-Until: Fri, 21 Jun 1996 17:45:01 -0500 (CDT) Final-Recipient: RFC822; [log in to unmask] Action: delayed Status: 4.4.3 Last-Attempt-Date: Wed, 19 Jun 1996 09:10:30 -0500 (CDT) Will-Retry-Until: Fri, 21 Jun 1996 17:45:01 -0500 (CDT) --BDV03291.835193430/postal.tamu.edu