Gnus development mailing list
 help / color / mirror / Atom feed
From: Rainer@krugs.de (Rainer M. Krug)
To: ding@gnus.org
Subject: Re: isync plus dovecot?
Date: Fri, 17 May 2013 11:13:37 +0200	[thread overview]
Message-ID: <87wqqy9dfi.fsf@krugs.de> (raw)
In-Reply-To: <874ne2uudj.fsf@ericabrahamsen.net>

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Dan Christensen <jdc@uwo.ca> writes:
>
>> 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've used offlineimap for a couple of years, and I find it works well.
>> I've posted on the offlineimap list a way to get it to sync some of
>> the Gnus specific flags, like gnus-expire.  If you can't find the
>> message, let me know and I'll dig it up.
>>
>>> 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.
>>
>> Nothing in my .offlineimaprc mentions dovecot, and I don't use a
>> preauthtunnel.  I just tell offlineimap to connect to an IMAP server
>> at 127.0.0.1 and to another IMAP server at a certain host name.
>>
>>> Is it enough just to have mbsync dump to a Maildir directly, and then
>>> tell gnus to access that maildir via dovecot?
>>
>> That might work too, but I decided to let dovecot be in charge of the
>> Maildir directory, and make both Gnus and offlineimap interact with that
>> directory via the IMAP protocol.  My method of syncing the non-standard
>> flags relies on this.
>>
>> I'm also curious to hear about alternatives to offlineimap, so I hope
>> some people reply with their experience.
>
> Ugh, clearly I just don't know enough about how this all actually works
> to make an informed decision. I don't even really get what letting
> dovecot "be in charge of the Maildir directory" really means. And if the
> other Eric is able to use the native Gnus agent and it works fine
> offline, why is everyone jumping through all these hoops?

preauthtunnel simply means (from my ignorant understanding of dovecot et
al) that you don't have to supply a password to connect to the local
imap server, but that you (the user) use dovecot (imap) directly to
access you maildir. It is *still* via docecot and even Erics setup
should work with the usage of the preauth tunnel instead of localhost. 

Direct Maildir access is a different story.

Rainer

>
> Maybe I'll just spend some time with google until I actually understand
> what's happening...
>
> Thanks,
> Eric
>
> PS I'm also using gmail. Actually I have four addresses, all of them
> google, three of them google apps domains. Yeesh
>
>
>




  parent reply	other threads:[~2013-05-17  9:13 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
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 [this message]
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=87wqqy9dfi.fsf@krugs.de \
    --to=rainer@krugs.de \
    --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).