Peter J. Holzer wrote:
On 2006-01-18 21:04:08 +1100, Andrew Pam wrote:
On Wed, Jan 18, 2006 at 04:12:49AM -0500, Bob Dodds wrote:
list threading depends on keeping "old" message id in some
header. At the moment I can't remember how I reconcile
that, but it's possible. Maybe the old id gets bumped into
an X header. I can't remember but I had to fix that to please
a listserver administrator(to preserve threading).
If you resend a message, you make the old Message-ID header into a
Resent-Message-ID header. (Likewise the Date and From headers become
Resent-Date and Resent-From headers.)
No. You keep the old Message-ID, and generate a
new unique Resent-Message-ID. Likewise, you keep Date and From and
generate Resent-Date and Resent-From to document when and by whom the
message was resent. See RFC 2822, section 3.6.6.
hp
I think a good mua handles that aspect, and all I have to do
is not mess it up. A lower level system message would not
have the benefit of mua's capabilities but then a system
notification would never be resending a message, either.
Do you know of any mua's that fail to handle that?
-Bob
