From owner-freebsd-hackers Thu Nov 2 9:11:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-c.mdsn1.wi.home.com [24.183.3.139]) by hub.freebsd.org (Postfix) with ESMTP id 087A137B4E5 for ; Thu, 2 Nov 2000 09:11:33 -0800 (PST) Received: (qmail 32098 invoked by uid 1000); 2 Nov 2000 17:11:32 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 2 Nov 2000 17:11:32 -0000 Date: Thu, 2 Nov 2000 11:11:32 -0600 (CST) From: Mike Silbersack To: Alex Belits Cc: Greg Black , hackers@FreeBSD.org Subject: Re: Time to close the list? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 2 Nov 2000, Alex Belits wrote: > On Thu, 2 Nov 2000, Mike Silbersack wrote: > > > Just having the list ensure that it was in the To: or Cc: header would be > > sufficient in this case. Such a change would block relay spam as well. > > Some places with not-so-nice connectivity to the rest of the Internet > use local lists to distribute this list among users -- this is why there > are messages with no to:/cc: hackers@freebsd.org in the first place. And > it will do nothing for autoresponders because autoresponder may happen to > be subscribed directly just like anything else. So, real solutions are: I'm confused. Some people can't send mail to the lists directly? And it would fix the auto-responder problem, since auto-responders tend to answer to the From: field, which would never be the mailing list's name. > 2. close the list, as it was proposed. If the icky freebsd@whatever.de address was subscribed, it would've still gotten onto the list (though I suppose the virus scan response would've been stopped.) Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message