Gnus development mailing list
 help / color / mirror / Atom feed
From: Rainer@krugs.de (Rainer M. Krug)
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: isync plus dovecot?
Date: Thu, 16 May 2013 09:47:31 +0200	[thread overview]
Message-ID: <87wqqzcqng.fsf@krugs.de> (raw)
In-Reply-To: <874ne3xwpu.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 16 May 2013 14:30:53 +0800")

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> I'm finally trying to ditch nnml for mail reading, and move to imap.
> Offlineimap plus dovecot seems to be a popular solution (I am offline a
> lot), but I also saw a lot of complaints about offlineimap, and the
> suggestion of isync/mbsync as a replacement.

I am using offlineimap, and I also saw many complains (and had a few
problems myself and looked at isync briefly), but it is now running solidly, after I reduced the
number of emails in a folder (or tag, as I am syncing from  gmail to
localhost, also dovecot).

One reason which kept me at offlineimap is that it seems to be more
widely used then isync.

So I can only say it works for me.

Cheers,

Rainer


>
> Has anyone done that? I realize this isn't quite a gnus question, but
> I'm having a bit of trouble wrapping my head around this, and google
> isn't helping any.
>
> Specifically, you tell offlineimap to deliver to dovecot with a line
> like:
>
> preauthtunnel = /usr/lib/dovecot/imap -o mail_location=maildir:$HOME/Maildir
>
> I can't find the equivalent command for mbsync. I don't know if it's
> possible, and worse I don't really understand what's going on well
> enough to really figure it out logically.
>
> Is it enough just to have mbsync dump to a Maildir directly, and then
> tell gnus to access that maildir via dovecot?
>
> Any pointers very welcome!
>
> Eric
>
>
>
<#secure method=pgpmime mode=sign>

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :       +33 - (0)9 53 10 27 44
Cell:       +33 - (0)6 85 62 59 98
Fax :       +33 - (0)9 58 10 27 44

Fax (D):    +49 - (0)3 21 21 25 22 44

email:      Rainer@krugs.de

Skype:      RMkrug



  reply	other threads:[~2013-05-16  7:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16  6:30 Eric Abrahamsen
2013-05-16  7:47 ` Rainer M. Krug [this message]
2013-05-16 11:28   ` Eric Abrahamsen
2013-05-17  9:06     ` Rainer M. Krug
2013-06-16 18:52   ` Dave Abrahams
2013-05-16 13:07 ` Dan Christensen
2013-05-17  4:02   ` Eric Abrahamsen
2013-05-17  7:50     ` Eric S Fraga
2013-05-17  8:35     ` Dan Christensen
2013-05-17  9:13     ` Rainer M. Krug
2013-05-17  9:17   ` Rainer M. Krug
2013-05-17 20:52     ` Dan Christensen
2013-05-18  1:48       ` Eric Abrahamsen
2013-05-18 21:06         ` Erik Colson
2013-05-16 16:02 ` Eric S Fraga
2013-05-20 17:30 ` Drew Raines
2013-05-21  1:35   ` Eric Abrahamsen
2013-05-22 18:24     ` Drew Raines
2013-05-24  4:36       ` Eric Abrahamsen
2013-06-16 18:49 ` Dave Abrahams
2013-06-17  7:18   ` Eric Abrahamsen
2013-06-18  3:56     ` Dave Abrahams
2013-06-24 14:06   ` Eric Abrahamsen
2013-06-24 16:39     ` 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=87wqqzcqng.fsf@krugs.de \
    --to=rainer@krugs.de \
    --cc=ding@gnus.org \
    --cc=eric@ericabrahamsen.net \
    /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).