Python mailing list vs. References: (was Re: My quarterly question on Design by Contract in Python...)

[Aahz Maruch]

In article <000301be9ea7$a798f960$159e2299 at tim>,
Tim Peters <tim_one at email.msn.com> wrote:
>
>I believe Aahz is suggesting:
>
>1. Never change a References header if there is one.
>2, Never change a In-Reply-To header if there is one.
>3. Never create a In-Reply-To header if there isn't one.
>4. If there isn't a References header, but there is a In-Reply-To that
>   appears to hold a sensible msg ID, then-- and only then --synthesize
>   a References header from that.

5. Only do this from mail to news, not the other direction.

(I think it was Lars who pointed out that RFC-822 specifically allows
both References and In-Reply-To, but I did some more digging and
verified that RFC-1036 permits only References; this to me implies that
unidirectional munging is acceptable and appropriate.)

((As Barry requested, I have moved the main line of discussion to the
mailman-developers list.))
-- 
                      --- Aahz (@netcom.com)

Hugs and backrubs -- I break Rule 6       <*>      http://www.rahul.net/aahz/
Androgynous poly kinky vanilla queer het

'It's odd, and a little unsettling, to reflect upon the fact that English is 
the only major language in which "I" is capitalized; in many other languages 
"You" is capitalized and the "i" is lower case.'  -- Sydney J. Harris