Delivery-Date: Sat Apr 06 15:09:45 2002
Date: Sat, 6 Apr 2002 10:09:29 -0500 (EST)
From: Mail Delivery Subsystem <MAILER-IMP@seas.upenn.edu>
Message-Id: <200204061509.g36F9Tbd020533@heyday.seas.upenn.edu>
To: <mjd@seas.upenn.edu>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
	boundary="g36F9Tbd020533.1018105769/heyday.seas.upenn.edu"
Subject: Returned mail: see transcript for details
Auto-Submitted: auto-generated (failure)

This is a MIME-encapsulated message

--g36F9Tbd020533.1018105769/heyday.seas.upenn.edu

The original message was received at Sat, 6 Apr 2002 10:09:28 -0500 (EST)
from mjd@RED.SEAS.UPENN.EDU [158.130.64.176]

   ----- The following addresses had permanent fatal errors -----
<postmaster@wt.net>
    (reason: 554 Kmail ESMTP v2.4.1 ready)
<kushner@wt.net>
    (reason: 554 Kmail ESMTP v2.4.1 ready)

   ----- Transcript of session follows -----
... while talking to mp.hou.wt.net.:
<<< 554 Kmail ESMTP v2.4.1 ready
554 5.0.0 Service unavailable

--g36F9Tbd020533.1018105769/heyday.seas.upenn.edu
Content-Type: message/delivery-status

Reporting-MTA: dns; heyday.seas.upenn.edu
Received-From-MTA: DNS; RED.SEAS.UPENN.EDU
Arrival-Date: Sat, 6 Apr 2002 10:09:28 -0500 (EST)

Final-Recipient: RFC822; postmaster@wt.net
Action: failed
Status: 5.5.0
Diagnostic-Code: SMTP; 554 Kmail ESMTP v2.4.1 ready
Last-Attempt-Date: Sat, 6 Apr 2002 10:09:29 -0500 (EST)

Final-Recipient: RFC822; kushner@wt.net
Action: failed
Status: 5.5.0
Diagnostic-Code: SMTP; 554 Kmail ESMTP v2.4.1 ready
Last-Attempt-Date: Sat, 6 Apr 2002 10:09:29 -0500 (EST)

--g36F9Tbd020533.1018105769/heyday.seas.upenn.edu
Content-Type: message/rfc822

Return-Path: <mjd@red.seas.upenn.edu>
Received: from red.seas.upenn.edu (mjd@RED.SEAS.UPENN.EDU [158.130.64.176])
	by heyday.seas.upenn.edu (8.12.2/8.12.2) with ESMTP id g36F9Sbd020531;
	Sat, 6 Apr 2002 10:09:28 -0500 (EST)
Received: from red.seas.upenn.edu (mjd@localhost)
	by red.seas.upenn.edu (8.10.1/8.10.1) with ESMTP id g36F9RW05742;
	Sat, 6 Apr 2002 10:09:28 -0500 (EST)
Message-Id: <200204061509.g36F9RW05742@red.seas.upenn.edu>
To: kushner@wt.net (James Kushner)
cc: mjd@seas.upenn.edu, postmaster@wt.net
Subject: Re: Mail to wt.net
Date: Sat, 06 Apr 2002 10:09:27 -0500
From: Mark-Jason Dominus <mjd@seas.upenn.edu>


> How recent is that development? 

The first record I can find of it occurring is yesterday at 17:48.

> I got some messages today from the fictionary list, which of course
> is refracted through plover.com.

I hadn't realized that any mail was going through to you.  Looking
over the records, I see that no mail was delivered to either you or
Nova between 17:48 yesterday and 02:49 this morning.  At 02:49,
advocacy-419, which was originally sent out at 01:49, was
delivered to Nova,after several intervening refusals.  At the exact
same time, wt.net refused the copy that plover was was trying to send
to you.

wt.net then refused several more delivery attempts of other messages,
until 04:36, when it finally allowed plover to deliver advocacy-419 to
you.  It then immediately resumed refusing messages and hasn't
accepted anything else until now, despite several attempts.

Messages I have for you and Nova that are still pending:

	artichoke-244  (5 April 17:20)  (you only)
	fictionary-622 (6 April 00:26)
	advocacy-418   (6 April 00:39)
	
	
You'll note that I said that the problem started at 17:48, but
artichoke-244 was sent at 17:20.  That delivery failed for a
different, but probably related reason: wt.net's mail server failed
completely without even sending a response.


--g36F9Tbd020533.1018105769/heyday.seas.upenn.edu--