Received: from localhost (daemon@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id OAA02441; Fri, 22 Mar 1996 14:42:18 -0500 Received: by CS.UTK.EDU (bulk_mailer v1.4); Fri, 22 Mar 1996 14:41:41 -0500 Received: from jekyll.piermont.com (jekyll.piermont.com [206.1.51.15]) by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id OAA02221; Fri, 22 Mar 1996 14:41:35 -0500 Received: from localhost (perry@localhost) by jekyll.piermont.com (8.7.4/8.6.12) with SMTP id OAA23793; Fri, 22 Mar 1996 14:39:51 -0500 (EST) Message-Id: <199603221939.OAA23793@jekyll.piermont.com> X-Authentication-Warning: jekyll.piermont.com: Host perry@localhost didn't use HELO protocol To: djb@koobera.math.uic.edu (D. J. Bernstein) cc: drums@cs.utk.edu Subject: Re: Issues summary web page In-reply-to: Your message of "22 Mar 1996 18:52:17 GMT." <19960322185217.7222.qmail@koobera.math.uic.edu> Reply-To: perry@piermont.com X-Reposting-Policy: redistribute only with permission Date: Fri, 22 Mar 1996 14:39:50 -0500 From: "Perry E. Metzger" D. J. Bernstein writes: > > In fact, I certainly wish bounce messages would contain a reference to the > > bounced message in their header; > > You mean, a References line with the original Message-ID? I wouldn't do > that, because it requires putting an 822 parser into the MTA, where it > doesn't belong. > > Machine-readable bounce messages are a good thing, certainly. I still > don't see why they should have their own Message-IDs. Because bounce messages bounce? Because people want to trace bounce messages? Because they are very cheap to generate and very useful? Perry