Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: Ding Mailing List <ding@gnus.org>
Subject: Re: Indexing Gnus (and other...) mails
Date: Thu, 09 Apr 2009 08:02:11 -0500	[thread overview]
Message-ID: <86ws9uugj0.fsf@lifelogs.com> (raw)
In-Reply-To: <86ab6rypnt.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 08 Apr 2009 13:19:02 -0500")

The following message is a courtesy copy of an article
that has been posted to gnu.emacs.gnus as well.

On Wed, 08 Apr 2009 13:19:02 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote: 

TZ> Gnus (imap.el AFAICT, so the support is missing all the way down) does
TZ> not support the IMAP SEARCH command, except by UID.  It probably should
TZ> allow SEARCH by TEXT, FROM, TO, SUBJECT, and probably all the other
TZ> standard search keys in RFC 3501 (section 6.4.4) [1].

Well, I mistyped "grep -i seach *.el" and assumed there was no IMAP
SEARCH support.  Sorry about the confusion--I was wrong.

nnir is the backend that implements search at the highest level in Gnus.
nnmairix is independent of it, but could probably be converted to a nnir
backend.  There are some TODO items with nnir as Tassilo pointed out,
with duplicate searches being a pretty big one.

Finally, nnir doesn't support incremental results AFAICT, which are
important for people with 30 GB of mail.  It would be nice if it did.
In general Gnus backends do very little incrementally, and that causes
problems with entering large groups and elsewhere, not just searching.

TZ> I don't know how IMAP servers implement SEARCH.  Is the speed decent?
TZ> If not, that should be an issue for the server maintainers (or they can
TZ> allow search plugins, so things like mairix can be integrated).  It
TZ> seems to me that IMAP SEARCH is a good way to provide universal
TZ> searching in Gnus for IMAP backends.

If anyone has experience integrating mairix with Courier or Dovecot,
please let me know.

Ted



  parent reply	other threads:[~2009-04-09 13:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87y6ubo5th.fsf@an-dro.enstb.org>
     [not found] ` <87ab6rbi5p.fsf@thinkpad.tsdh.de>
     [not found]   ` <mailman.4911.1239209214.31690.info-gnus-english@gnu.org>
2009-04-08 18:19     ` Ted Zlatanov
2009-04-08 18:28       ` Tassilo Horn
2009-04-09  7:15         ` Tassilo Horn
2009-04-09 12:22           ` Tassilo Horn
2009-04-09 18:34           ` Tassilo Horn
2009-04-09 13:02       ` Ted Zlatanov [this message]
     [not found]       ` <86ws9uugj0.fsf__11476.5163431459$1239285119$gmane$org@lifelogs.com>
2009-04-09 14:40         ` David Engster

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=86ws9uugj0.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    /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).