From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: w3 under development or not?
Date: Sat, 15 Nov 2003 08:31:26 -0500 [thread overview]
Message-ID: <4nd6bt3gi9.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: uy8uiy3qb.fsf@swbell.net
On Fri, 14 Nov 2003, pete_lee@swbell.net wrote:
>>>>> 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
> Ted> them up. I don't use Windows mail servers but I'm sure
> Ted> similar 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.
You asked for server-side options. Procmail and SA are best
installed on the server if you want to cut down the download times.
> 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.
With any reasonable ISP that provides you a shell account, you can
set up your personal rules in ~/.spamassassin/user_prefs
I use pair.com but there are many others.
> 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.
You can actually do all that and more with spam.el, a package for Gnus
which I maintain. Check out the CVS version of Gnus and look in the
manual (Oort Gnus comes with spam.el also, but many bugs have been
fixed meanwhile). spam.el is sort of a framework, and inside it are
various flexible spam checks you can enable depending on your needs.
I would still do server-side filtering in addition to client-side
filtering, but that's your choice and moving away from swbell is
certainly going to be a hassle for you.
To only get mail headers, use IMAP. There's more to it, I suggest you
read the Gnus manual in the spam.el section, but what you describe is
definitely possible - and you should continue the discussion on the
gnu.emacs.gnus newsgroup if you have any questions.
Ted
next prev parent reply other threads:[~2003-11-15 13:31 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 [this message]
2003-11-17 15:44 ` Alan Mackenzie
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=4nd6bt3gi9.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
/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).