Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Email reader - anything newer/better than gnus
Date: Thu, 18 Jan 2007 10:18:11 -0500	[thread overview]
Message-ID: <g697ivkuzws.fsf@dhcp-65-162.kendall.corp.akamai.com> (raw)
In-Reply-To: <mailman.3230.1169075705.2155.info-gnus-english@gnu.org>

On 17 Jan 2007, kai@emptydomain.de wrote:

> Some day, there will be similar features in Gnus.
>
> (For searching, there is gnus-namazu and also nnir, but they are
> different from the Opera support.  For learning auto-foldering (in
> Gnus speak, splitting), see ifile.  I vaguely remember having seen
> gnus-ifile.el somewhere...)

The gnus-registry does a good job (IMO) of catching references and
message subjects, and moving messages to the folder where those
references and message subjects went before.  It's not learning, but
it follows the user's command.

I think actual "smart" sorting of mail is dangerous.  You could end up
with misclassified mail, which is annoying (very much like
misclassified ham/spam, except it's not a binary choice so it's harder
to make).  Anyhow, spam.el had some support for ifile, but there must
be a better solution.  gnus-ifile.el hasn't been updated in a long
time.

Ted

  parent reply	other threads:[~2007-01-18 15:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-17 11:03 Torben Knudsen
2007-01-17 11:30 ` Gian Uberto Lauri
2007-01-17 12:17 ` Petter Gustad
2007-01-17 12:55 ` Leo
2007-01-17 17:20 ` Felix E. Klee
2007-01-17 23:14 ` Kai Großjohann
2007-01-17 23:27   ` Rendering HTML mail (was: Email reader - anything newer/better than gnus) Reiner Steib
2007-01-19 22:48     ` Rendering HTML mail Kai Großjohann
     [not found] ` <mailman.3230.1169075705.2155.info-gnus-english@gnu.org>
2007-01-18 15:18   ` Ted Zlatanov [this message]
2007-01-19  8:06 ` Email reader - anything newer/better than gnus Torben Knudsen
2007-01-19 10:48   ` Tassilo Horn

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=g697ivkuzws.fsf@dhcp-65-162.kendall.corp.akamai.com \
    --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 NNTP newsgroup(s).