From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: isync plus dovecot?
Date: Fri, 17 May 2013 09:35:12 +0100 [thread overview]
Message-ID: <87txm2dmwv.fsf@uwo.ca> (raw)
In-Reply-To: <874ne2uudj.fsf@ericabrahamsen.net>
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>> 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.
>
> 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.
Offlineimap has two modes of operation. The original way it worked
was to connect to a remote IMAP server using the IMAP protocol and
to write directly to a Maildir in the local filesystem. In this
mode of operation, you don't need a local IMAP server like dovecot,
it's just a Maildir <--> remote IMAP sync.
An alternate way is for offlineimap to synchronize between two IMAP
servers located anywhere on the internet. Offlineimap uses the IMAP
protocol to do this, and has no knowledge of how the servers store
the messages on disk. I use this way.
> 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?
It seems to me that there are very frequent complaints about the agent /
IMAP interaction on this mailing list, and I believe that Lars doesn't
use the agent (at least not for IMAP), so I don't trust that set-up.
Dan
next prev parent reply other threads:[~2013-05-17 8:35 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 [this message]
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=87txm2dmwv.fsf@uwo.ca \
--to=jdc@uwo.ca \
--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).