This is a MIME-encapsulated message

--EAA21011.849381385/leaf.maple.or.jp

The original message was received at Sat, 30 Nov 1996 23:57:17 +0900 (JST)
from fcgate@localhost

   ----- The following addresses have delivery notifications -----
news@maple-gw.maple.or.jp  (transient failure)

   ----- Transcript of session follows -----
news@maple-gw.maple.or.jp... Deferred: Connection refused by maple-gw.maple.or.jp.
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old

--EAA21011.849381385/leaf.maple.or.jp
Content-Type: message/delivery-status

Reporting-MTA: dns; leaf.maple.or.jp
Arrival-Date: Sat, 30 Nov 1996 23:57:17 +0900 (JST)

Final-Recipient: RFC822; news@maple-gw.maple.or.jp
Action: delayed
Status: 4.2.0
Remote-MTA: DNS; maple-gw.maple.or.jp
Last-Attempt-Date: Sun, 1 Dec 1996 04:16:25 +0900 (JST)
Will-Retry-Until: Thu, 5 Dec 1996 23:57:17 +0900 (JST)

--EAA21011.849381385/leaf.maple.or.jp
Content-Type: message/rfc822

Date: Sat, 30 Nov 1996 23:57:17 +0900 (JST)
Message-Id: <199611301457.XAA24962@leaf.maple.or.jp>
From: Andrew Brennan <brennan@crashprone.allegheny.edu>
To: news@maple-gw.maple.or.jp
Subject: Re: news@leaf.maple.or.jp strikes again

On Sat, 30 Nov 1996, Stefan Schmiedl wrote:

> Could someone tell me, what the right procedure is for getting such a
> loop terminated as quickly as possible, once I have noticed it?

   The "right" way?  I think the most effective is to take advantage of
   an automatic list and forged an unsubscription for the offender, but
   I'm sure that isn't in the Emily Post article on 'netiquette'(sp?).

   andrew.  (brennan@allegheny.edu)



--EAA21011.849381385/leaf.maple.or.jp--