Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Benjamin Slade <slade@jnanam.net>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: info-gnus-english@gnu.org
Subject: Re: new gnus setup with Dovecot
Date: Mon, 14 Dec 2015 23:48:02 -0700	[thread overview]
Message-ID: <874mfk8axp.fsf@jnanam.net> (raw)
In-Reply-To: <87lh8wee21.fsf@ericabrahamsen.net>

> I wrote this last year, and it's more focused on searching, but the
> basic setup should be plenty viable for you. See if this helps!
>
> https://ericabrahamsen.net/tech/2014/oct/gnus-dovecot-lucene.html

Thanks for this. It looks very close to what I need to set up. Multiple
accounts etc. I was originally thinking to try to piggyback the Gnus
setup on the offlineimap setup I already have for mu4e (so that I could
continue to use both), but looking at the details of the setup, it seems
like it would be better to do a separate setup with mbsync and a
separate maildir for gnus.

Does this setup synchronise well across machines?  I have 3 different
machines that need to synchronise.  For the older offlineimap setup of
http://roland.entierement.nu/blog/2010/09/08/gnus-dovecot-offlineimap-search-a-howto.html
, I note that he customises offlineimap.py to synchronise some Gnus
flags (expire). Can something equivalent be done with mbsync, or this is
no longer necessary?

Is the Lucien search solution working out well for you? One thing I do
really like about mu4e is the speed and flexibility of search.



  reply	other threads:[~2015-12-15  6:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14 20:36 Benjamin Slade
2015-12-14 20:55 ` Rasmus
2015-12-15  0:44 ` Eric Abrahamsen
2015-12-15  6:48   ` Benjamin Slade [this message]
2015-12-15 14:19     ` Eric Abrahamsen
2015-12-16 15:59 ` Julien Cubizolles

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=874mfk8axp.fsf@jnanam.net \
    --to=slade@jnanam.net \
    --cc=eric@ericabrahamsen.net \
    --cc=info-gnus-english@gnu.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).