Received: from localhost (daemon@localhost) 
        by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id NAA27745; Sat, 1 Jun 1996 13:46:27 -0400
Received: by CS.UTK.EDU (bulk_mailer v1.6); Sat, 1 Jun 1996 13:45:38 -0400
Received: from koobera.math.uic.edu (qmailr@KOOBERA.MATH.UIC.EDU [128.248.178.247]) 
        by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id NAA27670; Sat, 1 Jun 1996 13:45:33 -0400
Received: (qmail-queue invoked by uid 666); 1 Jun 1996 17:48:42 -0000
Date: 1 Jun 1996 17:48:42 -0000
Message-ID: <19960601174842.27929.qmail@koobera.math.uic.edu>
From: djb@koobera.math.uic.edu (D. J. Bernstein)
To: drums@cs.utk.edu
Subject: Re: 821bis outstanding issues list

> Only a limited set of mail exploders do actions where it makes
> sense to look for a delivered-to: in the headers they create.

All 1123-style aliases and mailing lists. This handles most loops.

> - Vacation programs
> - Nondelivery reports

Use the <> mechanism. (And, for mailing lists, don't replace <> with
<foo-owner>.)

> - Mail responders

A responder is a fancy mailing list: leave the header basically intact
(plus Delivered-To, of course), and insert responses into the body.
Alternatively, use the <> mechanism.

> - Digested mailing lists (ok, these are slow)

Yeah, if the second week's digest includes an entire copy of the first
week's digest, you should be able to fix it by the third week. :-)

---Dan