Re: p0.88 (and since time immemorial?) date-lapsed error

[Karl Kleinpaste <karl@justresearch.com>]

Karl Kleinpaste <karl@justresearch.com> writes:
>> With gnus-treat-date-lapsed set to 'head, received and Gcc'd forwarded
>> messages display such that *both* Date: headers are replaced with the
>> same X-Sent header.

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> I'm not sure I follow you here, but
> `gnus-article-date-lapsed-new-header' controls whether the Date header 
> is removed when looking at the lapsed header.

No, that's not what I meant.

When one forwards a message, both the new, enclosing message and the
contained message have Date: headers.  Setting gnus-treat-date-lapsed
results in displays of this flavor:
________________

	From: Karl Kleinpaste <karl@justresearch.com> 
	Subject: [Karl Kleinpaste <karl@justresearch.com>] test 
	To: karl@beaver.jprc.com 
»»-->	X-Sent: 1 week, 4 days, 18 hours, 20 minutes, 43 seconds ago 

	[1. text/plain] 
 
	enclosing text. 
 
	[2. message/rfc822] 
 
	From: Karl Kleinpaste <karl@justresearch.com> 
	Subject: test 
	To: karl@beaver.jprc.com 
»»-->	X-Sent: 1 week, 4 days, 18 hours, 20 minutes, 43 seconds ago 
 
	inner text. 
________________

The X-Sent: are identical, but in the original message file, they are:
	Date: 22 Jun 1999 17:00:38 -0400 
	Date: 22 Jun 1999 16:49:59 -0400 
The 2nd is not treated individually; the 1st is given "lapsed"
treatment, and that string is substituted for all Date: headers.