From owner-freebsd-security Sat Jul 29 16: 2:23 2000 Delivered-To: freebsd-security@freebsd.org Received: from dfw-smtpout2.email.verio.net (dfw-smtpout2.email.verio.net [129.250.36.42]) by hub.freebsd.org (Postfix) with ESMTP id 7FCDE37B621 for ; Sat, 29 Jul 2000 16:02:20 -0700 (PDT) (envelope-from bokr@accessone.com) Received: from [129.250.38.63] (helo=dfw-mmp3.email.verio.net) by dfw-smtpout2.email.verio.net with esmtp (Exim 3.12 #7) id 13IfcZ-0004ST-00; Sat, 29 Jul 2000 23:02:19 +0000 Received: from [204.250.68.168] (helo=gazelle) by dfw-mmp3.email.verio.net with smtp (Exim 3.15 #4) id 13IfcY-0001M3-00; Sat, 29 Jul 2000 23:02:18 +0000 Message-Id: <3.0.5.32.20000729160602.00914500@mail.accessone.com> X-Sender: bokr@mail.accessone.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sat, 29 Jul 2000 16:06:02 -0700 To: Mitch Collinsworth From: Bengt Richter Subject: Re: ? Cc: freebsd-security@freebsd.org In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 07:41 2000-07-28 -0400 Mitch Collinsworth wrote: >What's going on here is that this guy is creating local newsgroups to >distribute these lists into. Unfortunately his news <---> mail gateway >is running in both directions, so anything sent to the gateway e-mail >address is getting fed back into the list posting address and we're all >seeing it. Whether this is acceptable practice is a policy question for >the freebsd lists administrator to deal with. In the mean time I would >suggest addressing any complaints to the lists admin and to the address >in his X-Complaints-To: header, usenet@news.kharkiv.net. > >-Mitch > Maybe there is a win-win possibility after the initial annoyance. The "arkiv" in kharkiv.net sugggests the idea that they're subscribing to various lists to do automatic archiving. I would like access to that, especially with search capability. BUT ... not at the cost of seeing a kind of cross-post spam in freebsd-security. I don't think newsgroup (if that's what it's about) posts should automatically be passed through to mailing lists. For one thing, many news reader programs blindly copy the cross-posting info such that even experienced users may accidentally spam unintentionally in sending a quick reply. To have that kind of traffic into freebsd-security (and the other lists I haven't Cc'd) would be disruptive. If that is what's coming, I would vote for blocking their incoming traffic. I would hope it's just a temporary configuration error of some kind, to give them the benefit of the doubt. An unmoderated newsgroup connected as feared would amount to a spam pass-through. There's enough already directly. However, they may well be doing a valuable service for a group of people (potentially including us) by passively taking a single feed from freebsd-security@freebsd.org and publishing it in a context of their own (guessing that is their intent). Just so their subscribers have to take an "opt-in" action (like filling in Cc:) _each time_ in order to post to a mailing list, not an "opt-out" each time to override auto-spam. Regards, Bengt Richter P.S. Could we filter to exclude non-subscribers and have a category of listen-only subscribers to deal with the current issue, if necessary? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message