Re: OFFTOPIC Re: [Mailman-Users] Archive URL in postings (2.1b3)

On Tue, 29 Oct 2002 13:33:08 -0600 John Buttery <john@io.com> wrote:
Because it's simply a lie. I got this mail with the headers:
sorry. don't agree.
Sure it is. You assuming a certain set of semantic connotations for the To: and Cc: headers and then inferentially assume that everybody else operates on the same understanding of those headers. The problem is that its just not true. Your assumptions are neither universal or necessarily shared.
One has a List-ID header, one doesn't.
One has an In-Reply-To that references my prior post, one doesn't.
Hint: you can't.
Sure I can.
Ignoring the aspects of etiquette in quoting a private email in a public forum, this is also not a problem for the same reasons as above.
--
J C Lawrence
---------(*) Satan, oscillate my metallic sonatas.
claw@kanga.nu He lived as a devil, eh?
http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

On Tue, Oct 29, 2002 at 07:51:03PM -0800, J C Lawrence wrote:
Try again. Your message included both
In-Reply-To: Message from John Buttery <john@io.com> of "Tue, 29 Oct 2002 13:33:08 CST." <20021029193308.GA25878@io.com>
and
List-Id: Mailman mailing list management users <mailman-users.python.org>
among its headers. Both would have the In-Reply-To: header, still leaving John without a way to determine whether a list message was sent only to the list or both to him directly and to the list.
-- When we reduce our own liberties to stop terrorism, the terrorists have already won. - reverius
Innocence is no protection when governments go bad. - Tom Swiss

- J C Lawrence <claw@kanga.nu> [2002-10-29 19:51:03 -0800]:
Thinking that the address in the To: field is an address that the sender originally targeted directly may not be universal, but I think it's pretty close. *shrug*
You're right about this, I hadn't fully thought things out before I said that. However, it doesn't solve the problem of not knowing whether one of these list postings is the first of two duplicates, or just a normal posting. Someone just posted something about the In-Reply-To: header that may or may not refute that part, but it's moot because your point stands on the List-ID: header alone.
True, and I take that statement back for the same reasons as above. :p And, of course, I was not encouraging people to post private emails on-list, which is a MASSIVE etiquette breach...I was just trying to point out a situation in which "information loss" would happen.
--
John Buttery (Web page temporarily unavailable)

On Tue, Oct 29, 2002 at 07:51:03PM -0800, J C Lawrence wrote:
Try again. Your message included both
In-Reply-To: Message from John Buttery <john@io.com> of "Tue, 29 Oct 2002 13:33:08 CST." <20021029193308.GA25878@io.com>
and
List-Id: Mailman mailing list management users <mailman-users.python.org>
among its headers. Both would have the In-Reply-To: header, still leaving John without a way to determine whether a list message was sent only to the list or both to him directly and to the list.
-- When we reduce our own liberties to stop terrorism, the terrorists have already won. - reverius
Innocence is no protection when governments go bad. - Tom Swiss

- J C Lawrence <claw@kanga.nu> [2002-10-29 19:51:03 -0800]:
Thinking that the address in the To: field is an address that the sender originally targeted directly may not be universal, but I think it's pretty close. *shrug*
You're right about this, I hadn't fully thought things out before I said that. However, it doesn't solve the problem of not knowing whether one of these list postings is the first of two duplicates, or just a normal posting. Someone just posted something about the In-Reply-To: header that may or may not refute that part, but it's moot because your point stands on the List-ID: header alone.
True, and I take that statement back for the same reasons as above. :p And, of course, I was not encouraging people to post private emails on-list, which is a MASSIVE etiquette breach...I was just trying to point out a situation in which "information loss" would happen.
--
John Buttery (Web page temporarily unavailable)
participants (3)
-
Dave Sherohman
-
J C Lawrence
-
John Buttery