From: Harald.T.Alvestrand@uninett.no
To: drums@cs.utk.edu
Subject: Re: other Message-ID applications
In-reply-to: <19970911170023.5795.qmail@koobera.math.uic.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <22489.874102091.1@dale.uninett.no>
Date: Sat, 13 Sep 1997 00:08:13 +0200
Message-ID: <22491.874102093@dale.uninett.no>
Sender: hta@dale.uninett.no

Dan Bernstein said:
>This is irrelevant for a message that (1) starts a new thread, (2) is
>sent to a single recipient, and (3) is not saved by the sender. The
>recipient can make up his own Message-ID for the message if he's
>desperate to thread it. Standard example: bounce messages.

This of course assumes that the sender can know that the recipient is
a single recipient, or that the various recipients have no need to
communicate with each other about the message.

This is probably true >90% of the time for MTA-level bounce messages
(Delivery Status Notifications), since few people indulge in pointing
the envelope FROM address at a mailing list or multiperson alias.

              Harald A