From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ken Raeburn Newsgroups: gmane.emacs.devel Subject: Re: Let's shut down bug-gnu-emacs@gnu.org Date: Mon, 12 Dec 2005 13:49:51 -0500 Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1134422184 20700 80.91.229.2 (12 Dec 2005 21:16:24 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 12 Dec 2005 21:16:24 +0000 (UTC) Cc: "Richard M. Stallman" , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 12 22:16:22 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Eluzp-0001Bc-D8 for ged-emacs-devel@m.gmane.org; Mon, 12 Dec 2005 22:14:09 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Elv0K-0001Vb-RV for ged-emacs-devel@m.gmane.org; Mon, 12 Dec 2005 16:14:40 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Elsme-0002mF-8h for emacs-devel@gnu.org; Mon, 12 Dec 2005 13:52:24 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Elsmc-0002jw-9f for emacs-devel@gnu.org; Mon, 12 Dec 2005 13:52:23 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Elsmb-0002j8-1R for emacs-devel@gnu.org; Mon, 12 Dec 2005 13:52:21 -0500 Original-Received: from [204.127.198.35] (helo=rwcrmhc11.comcast.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1ElsoK-0002z8-Sb; Mon, 12 Dec 2005 13:54:09 -0500 Original-Received: from raeburn.org (c-65-96-168-237.hsd1.ma.comcast.net[65.96.168.237]) by comcast.net (rwcrmhc11) with ESMTP id <2005121218495501300c8qnue>; Mon, 12 Dec 2005 18:49:56 +0000 Original-Received: from [18.101.0.226] (laptop.raeburn.org [18.101.0.226]) by raeburn.org (8.12.11/8.12.11) with ESMTP id jBCInsvJ025624; Mon, 12 Dec 2005 13:49:54 -0500 (EST) In-Reply-To: Original-To: Alan Mackenzie X-Mailer: Apple Mail (2.746.2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:47560 Archived-At: On Dec 12, 2005, at 04:10, Alan Mackenzie wrote: > Morning, Richard! > > On Sun, 11 Dec 2005, Richard M. Stallman wrote: > >> gnu.emacs.bug is supposedly a moderated newsgroup. > >> Where does it say that? This group is not moderated, and never was. > > Hmmm. It's certainly moderated at my ISP's server, and all posts I've > ever seen sport the header: "Moderated" for a mailing list generally means someone is actually monitoring the content and choosing which messages to let through. "Moderated" for a newsgroup, I believe, just means that submissions are sent to an email address for "approval" rather than distributed from the server where the posting is done. This can be used for "moderation" in the normal sense, or just some automated processing/ filtering with no human intervention. I believe the latter is what's going on, thus the confusion. >> Reducing the spam would be useful. One thing we could do to reduce >> the spam is set things up to reject messages which fail to contain >> "emacs" in the subject or body. If these rejections send back an >> auto-reply telling real users what to do, it should not be an >> inconvenience. > > Probably the most effective simple measure would be to block > everything > whose subject line starts with "?$B". Various other techniques are available too, especially if the gnu.org mail system can be tweaked -- greylisting, HELO-dotted-quad checks, delayed-greeting... depends on what risks you're willing to take for poorly-behaved or non-RFC-compliant senders, etc. (I use a combination of the above on my home system, and get very little directly-delivered spam. At work, we don't use them, but some simple tests suggest that the HELO-dotted-quad test would trap almost 40% of my spam.) > The sort of process I envisage would work something like this: > (i) Mail arriving at the list goes through the (presumably already > installed) automatic filter (Spamassassin?). > (ii) Of what's left, anything from a known serious poster passes > through. > (iii) Anything which is a response to an existing article passes > through. > (iv) The rest stays in limbo for up to 24 hours; during that time, a > moderator may accept it or reject it; > (v) After 24 hours (moderator on holiday?) articles will get passed > through to the list. That sounds sensible. Though in my experience, the Mailman message moderation interface is nice for small amounts of work, but kind of clunky for dealing with large quantities of mail. Enough so that I hacked up some elisp to parse the HTML pages, and I do most of my list moderation in emacs/ielm. My hacks are still kind of clunky, but reduce the amount of wrist motion and per-message typing, when most of them are to be treated the same way. Anyone want to hack up a real mailman-interaction mode, with summary listings and automatically-applied per-list filters and other fun stuff? :-) Ken