From: Alan Mackenzie<none@example.invalid>
Subject: Re: w3 under development or not?
Date: Mon, 17 Nov 2003 15:44:40 +0000 [thread overview]
Message-ID: <8dqapb.e6.ln@acm.acm> (raw)
In-Reply-To: uy8uiy3qb.fsf@swbell.net
Peter Lee <pete_lee@swbell.net> 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").
next prev parent reply other threads:[~2003-11-17 15:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.124.1068506807.2005.help-gnu-emacs@gnu.org>
2003-11-11 17:16 ` w3 under development or not? Björn Lindström
2003-11-11 22:50 ` Stefan Monnier
[not found] ` <bosoof$hru$1@news1.wdf.sap-ag.de>
2003-11-12 10:21 ` A. L. Meyers
2003-11-12 13:59 ` Stefan Monnier
2003-11-13 15:10 ` Friedrich Dominicus
2003-11-14 8:12 ` Shane
2003-11-14 9:19 ` Poppong mail (Re: w3 under development or not?) Gian Uberto Lauri
2003-11-14 10:23 ` OT spamfilter A. L. Meyers
2003-11-14 18:22 ` Harry Putnam
2003-11-14 20:07 ` A. L. Meyers
2003-11-14 19:01 ` Tim McNamara
2003-11-14 15:30 ` w3 under development or not? Peter Lee
2003-11-14 16:09 ` Ted Zlatanov
2003-11-14 17:40 ` Peter Lee
2003-11-14 18:43 ` Ted Zlatanov
2003-11-14 22:39 ` Peter Lee
2003-11-15 4:34 ` Juri Linkov
2003-11-15 13:31 ` Ted Zlatanov
2003-11-17 15:44 ` Alan Mackenzie [this message]
2003-11-14 18:21 ` Harry Putnam
2003-11-14 16:01 ` Gnus attachment downloading blocks other Emacs interaction (was: w3 under development or not?) Ted Zlatanov
2003-11-12 21:07 w3 under development or not? Joe Corneli
-- strict thread matches above, loose matches on Subject: below --
2003-11-10 21:59 Joe Corneli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8dqapb.e6.ln@acm.acm \
--to=none@example.invalid \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).