Date: Wed, 15 Jul 1998 12:55:00 -0400 (EDT) From: Mikhail Teterin <mi@aldan.algebra.com> To: chat@FreeBSD.ORG Subject: Re: Stopping the bloody cross posting. Message-ID: <199807151655.MAA00679@rtfm.ziplink.net> In-Reply-To: <Pine.BSF.3.96.980714230751.4031G-100000@localhost> from "Tim Vanderhoek" at "Jul 14, 98 11:26:17 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Tim Vanderhoek once stated: => First, I do not see anything wrong with Sender listing multiples. => Second, what's wrong with relying on To: and/or Cc:? = =Well, for starters because your message that I'm responding to =right now does not include any To: or Cc: headers. No To:-header? So, majordomo removed it? Can you verify? I did not put anything into CC figuring you are subscribed to -chat. (I'm not, btw -- your CC are apreciated). Besides, a special X-Whatever header can contain anything that's neccessary. For example, "X-Majordomo-Lists: freebsd-chat openbsd-mobile" -- an artificical example where openbsd and freebsd lists are handled by the same server. This header will also contain only "official" list names, for your convinience. =Consider a message x-posted to -chat and -alpha. I am not =subscribed to -alpha, however, my filter sees -alpha in the Cc: =header. Since my filter automatically recognizes new (FreeBSD) =mailing-lists and performs certain actions based on this, it will =think I've subscribed to -alpha. Not Good. Even worse if =someone Cc:'s a mythical mailing list. Then your filter is broken -- it tries to archive anything (or anything coming from freebsd.org). Let's not discuss actual implementation, unless you are trying to prove making such a filter is _impossible_. BTW, AFAIK, this is how alt.* news groups are created -- anyone can make a new one by including it into Newsgroups header :) =This is still going to screw people who subscribe each -list to a =different address. Eg. -hackers to freebsd-hackers@time.cdrom.com. This can, actually, be used to force hub to send copies -- for those who want it and are willing to waste some (cheap) local storage. =Finally, those headers are not altogether reliable. Well, I'm not sure what you mean by this. => I just find it silly to duplicate messages on the hub, when they can => easily be replicated by the receiver (if he/she wants to) for some => sort of archiving. The Internet gets plenty of traffic from dummies => already... [...] =Really, your argument about resources is bogus. The only way that =this becomes an issue is if cross-posting becomes rampant, and if =cross-posting becomes rampant [...] It is a _problem_ only when it's rampant. But it is always an anoyance. And resource-consuming. Not just hub's CPU, but the Internet bandwidth, people's disks, people's modems, and people's time too. -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199807151655.MAA00679>