From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: blog post on gnus, dovecot, and lucene
Date: Wed, 08 Oct 2014 00:30:31 +0800 [thread overview]
Message-ID: <87iojvzvtk.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <878uks9ooo.fsf@zoro.exoscale.ch>
Vincent Bernat <bernat@luffy.cx> writes:
> ❦ 7 octobre 2014 13:43 +0800, Eric Abrahamsen <eric@ericabrahamsen.net> :
>
>> I mentioned a bit ago that I had shifted my gnus/dovecot setup, and
>> would blog about it. I finally did that:
>>
>> http://ericabrahamsen.net/tech/2014/oct/gnus-dovecot-lucene.html
>>
>> The gist of it is how to move to an always-running dovecot daemon, fed
>> by isync, and incorporating lucene searches into that.
>
> Note that you don't have to run dovecot as a server. You can run it as a
> process. In mbsyncrc:
>
> Tunnel "/usr/lib/dovecot/imap -o mail_location=maildir:~/.mbsync/mails/XXXXX"
>
> In Gnus:
>
> #+BEGIN_SRC elisp
> (nnimap-stream shell)
> (nnimap-shell-program "/usr/lib/dovecot/imap -o mail_location=maildir:~/.mbsync/mails/XXXXX")
> #+END_SRC
Yes, hence the section titled "The Problem" in that blog post :) Perhaps
I could have made that clearer!
So far as I can tell, if you're calling dovecot as a process, you can't
integrate lucene text indexing -- that only works when running dovecot
as a daemon.
In fact that was the whole impetus for the shift, and the blog post:
going from dovecot-the-process to dovecot-the-daemon, because of the
need for search indexing.
E
next prev parent reply other threads:[~2014-10-07 16:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 5:43 Eric Abrahamsen
2014-10-07 5:51 ` Igor Sosa Mayor
2014-10-07 11:14 ` Feng Shu
2014-10-07 11:59 ` Rasmus
2014-10-07 10:09 ` Vincent Bernat
2014-10-07 16:30 ` Eric Abrahamsen [this message]
2014-10-08 5:12 ` Vincent Bernat
2014-10-08 14:15 ` Eric Abrahamsen
2014-10-09 5:30 ` Vincent Bernat
2014-10-09 8:23 ` Eric Abrahamsen
2014-10-09 8:30 ` Rainer M Krug
[not found] ` <m2oatos5yt.fsf@krugs.de>
2014-10-07 16:47 ` Eric Abrahamsen
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=87iojvzvtk.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).