Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: isync plus dovecot?
Date: Sat, 18 May 2013 09:48:43 +0800	[thread overview]
Message-ID: <878v3dnjlw.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <874ne1e3c3.fsf@uwo.ca>

Dan Christensen <jdc@uwo.ca> writes:

> Rainer@krugs.de (Rainer M. Krug) writes:
>
>> Dan Christensen <jdc@uwo.ca> writes:
>>
>>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>>
>>> 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.
>>
>> Yes please - I would be interested as well. Could you provide some
>> keywords to search for?
>
> Here's one place I described it:
>
>   http://lists.gnu.org/archive/html/info-gnus-english/2011-10/msg00052.html
>
> For convenience, I've copied the body of that message below.  I'm using
> offlineimap 6.3.5-rc3.
>
> Dan
>
> offlineimap doesn't sync custom flags by default.  The hack I use just
> monkeypatches the flagmap.  Put the following in .offlineimap.py:
>
> import offlineimap.imaputil as IU
> if not hasattr(IU, 'monkeypatchdone'):
>     IU.flagmap += [('gnus-expire','E'),
>                    ('gnus-dormant', 'Q'),
>                    ('gnus-save', 'V'),
>                    ('gnus-forward', 'W')]
>     IU.monkeypatchdone = True
>
> To activate this, you put
>
> pythonfile = ~/.offlineimap.py
>
> in your .offlineimaprc

This looks a bit like the instructions I started off following online:

http://roland.entierement.nu/blog/2010/09/08/gnus-dovecot-offlineimap-search-a-howto.html

I only realized after I failing to get it to work several times that
there's an update at the bottom of the blog post for versions of dovecot
over 2.0.




  reply	other threads:[~2013-05-18  1:48 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
2013-05-17  9:17   ` Rainer M. Krug
2013-05-17 20:52     ` Dan Christensen
2013-05-18  1:48       ` Eric Abrahamsen [this message]
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=878v3dnjlw.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).