From owner-freebsd-chat  Tue Jul 14 21:43:32 1998
Return-Path: <owner-freebsd-chat@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA14940
          for freebsd-chat-outgoing; Tue, 14 Jul 1998 21:43:32 -0700 (PDT)
          (envelope-from owner-freebsd-chat@FreeBSD.ORG)
Received: from www.video-collage.com (root@www.video-collage.com [206.15.171.132])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14935
          for <chat@freebsd.org>; Tue, 14 Jul 1998 21:43:30 -0700 (PDT)
          (envelope-from mi@xxx.video-collage.com)
Received: from xxx.video-collage.com (mi@xxx.video-collage.com [199.232.254.68])
	by www.video-collage.com (8.8.5/8.8.5) with ESMTP id AAA10600
	for <chat@freebsd.org>; Wed, 15 Jul 1998 00:44:25 -0400 (EDT)
Received: (from mi@localhost)
	by xxx.video-collage.com (8.8.8/8.8.7) id AAA16033
	for chat@freebsd.org; Wed, 15 Jul 1998 00:43:19 -0400 (EDT)
	(envelope-from mi)
From: Mikhail Teterin <mi@video-collage.com>
Message-Id: <199807150443.AAA16033@xxx.video-collage.com>
Subject: Re: STOP THE BLOODY CROSS POSTING!
In-Reply-To: <Pine.BSF.3.96.980714214233.4031A-100000@localhost> from Tim Vanderhoek at "Jul 14, 98 09:59:04 pm"
To: 
Date: Wed, 15 Jul 1998 00:43:19 -0400 (EDT)
X-Face: 
	%UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
		 hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
		 y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL35 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-chat@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Tim Vanderhoek once stated:

=> IMHO, this should be handled by mailing list software. Make sure
=> no-one gets the same message ID twice is rather simple, since all
=
=This is easy.  If you only want to "get" the same message ID
=once, then filter your own messages based on message ID.  Goto
=line 320 or so of procmailex(5). 

Yes, but by then the message already ate up twice or more of the
Internet bandwidth then it had to...

=Even more importantly, if a message is cross-posted, then it
=SHOULD belong in all the -lists it is cross-posted to.

It does belong to. And so it says in all (almost all) the headers.
You just get one copy... If you wish to store it in several places,
your scripts will have plenty of data to select the proper folders.

=Consider: I may only scan the -current list today because I'm
=short on time.  Unfortunately an important notice was
=cross-posted to -announce and -current, but the stupid
=mailing-list software only sent me the copy that was posted to
=-current.

The message will not say it is only posted to current. It will list
all of the mailing lists. Now, my suggestion does not mean to
encourage crossposting. It will only make handling of crosspostings
more intelligent.

=Cross-posting merely encourages over-use of the mailing-lists, even
=with such mailing-list software as you envision. By encouraging
=cross-posting, your subscription to -current will slowly become a
[...]

Wait, wait. I did not suggest to _encourage_ crossposting... But
if something happens to belong (in poster's opinion) to -multimedia,
-mobile, and -current there should be a way to send it there without
annoying people who are subscribed to all three.

	-mi

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-chat" in the body of the message