From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.help Subject: Re: w3 under development or not? Date: Mon, 17 Nov 2003 15:44:40 +0000 Organization: muc.de e.V. -- private internet access Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: <8dqapb.e6.ln@acm.acm> References: <878ymm6d18.fsf@lucien.dreaming> <87brrf2wsu.fsf@yahoo.co.uk> <4nr80b2apy.fsf@lockgroove.bwh.harvard.edu> <4nekwa3i5b.fsf@lockgroove.bwh.harvard.edu> NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1069088549 25624 80.91.224.253 (17 Nov 2003 17:02:29 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 17 Nov 2003 17:02:29 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Nov 17 18:02:26 2003 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1ALmle-0006Mt-00 for ; Mon, 17 Nov 2003 18:02:26 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1ALngE-0005Ql-0c for geh-help-gnu-emacs@m.gmane.org; Mon, 17 Nov 2003 13:00:54 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!irazu.switch.ch!switch.ch!news.belwue.de!news.tesion.net!news.space.net!news.muc.de!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 47 Original-NNTP-Posting-Host: acm.muc.de Original-X-Trace: marvin.muc.de 1069087326 11095 193.149.49.134 (17 Nov 2003 16:42:06 GMT) Original-X-Complaints-To: news-admin@muc.de Original-NNTP-Posting-Date: 17 Nov 2003 16:42:06 GMT User-Agent: tin/1.4.5-20010409 ("One More Nightmare") (UNIX) (Linux/2.0.35 (i686)) Original-Xref: shelby.stanford.edu gnu.emacs.help:118377 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.help:14318 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:14318 Peter Lee wrote on Fri, 14 Nov 2003 22:39:24 GMT: >>>>> Ted Zlatanov writes: > Ted> There are many, many such tools. For Unix mail servers the > Ted> options are plentiful and a simple web search will turn them > Ted> up. I don't use Windows mail servers but I'm sure similar > Ted> tools exist for them. > After a brief look at Procmail and SpamAssassin, I don't see how they > solve the problem. Installing either locally still results in the mail > being pulled down my small pipe from swbell. The only benefit I see to > them is if your mail client either: a) doesn't have spam support b) > retrieves mail in a synchronous fashion My ISP uses SpamAssassin. I can rlogin to my ISP's mailserver and run a mail client there (pine, as it happens). I can use this to mark and delete spam _before_ I download it through my modem. [ .... ] > I suppose I could lobby for swbell to install SpamAssassin. But then > I'm dependent on someone else setting up rules that could potentially > cost me a valid email now and again. They'd never do it anyway. Why not ask them? Are they happy having their modem lines needlessly tied up whilst you download 20 or 80 "Microsoft last security patch"es? Have you got a remote login facility at swbell? > What would be cool is if (in Gnus) you could download mail headers > only first... run through spam processor... then only download valid > mail, and reprocess again including body. The spam would still show > up in spam group, possibly annotated to show that only the headers > have been retrieved on some (hopefully most). If you moved it to a > ham group it would then fetch the mail, otherwise it would be expired > and on expiry be deleted from the server the next time you asked for > mail. This is effectively what I do with an rlogin. > It would be slower, but not as slow as downloading 20-80 of those > patches. -- Alan Mackenzie (Munich, Germany) Email: aacm@muuc.dee; to decode, wherever there is a repeated letter (like "aa"), remove half of them (leaving, say, "a").