Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Matthieu Rakotojaona <matthieu.rakotojaona@gmail.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] heliotrope-syncback
Date: Wed, 9 Nov 2011 04:22:51 +0100	[thread overview]
Message-ID: <CAMiZLn3dsR_sRfpZV9MLKhJpVhfgsSpd6t3DwHDeg5uydY39Ow@mail.gmail.com> (raw)
In-Reply-To: <1320692090-sup-9935@stapelberg.de>

Okay, forget about buggy syncback, now comes the IMAP interface ! I've
begun to hack ximapd[0], a ruby IMAP server, to work with heliotrope.
Unfortunately it is not supported anymore.

So far, I can connect with it (but with no security), list "mailboxes"
(just like GMail, they are just labels) select one and search for
something, all using imap4rev1 specs and, of course, heliotrope as a
backend. The most interesting parts like FETCHing and STORing are
still a few lines of code away. Of course, the goal is to use
something like offlineimap, Because It Works, to sync both mail stores
in a reliable fashion.

Considering the implementation, I've considered only UIDs, which are
heliotrope's message_ids. Both can and must only go up as messages
come and go, so it's cool.

So if you want to test it, go to https://github.com/rakoo/ximapd-heliotrope.
This leads me to the question : what is the license of Heliotrope ?
Ximapd seems to be something BSD-like, but Heliotrope has none.

Cya !

[0] https://github.com/shugo/ximapd
-- 
Matthieu RAKOTOJAONA
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


  reply	other threads:[~2011-11-09  3:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 23:55 Matthieu Rakotojaona
2011-11-07  6:57 ` William Morgan
2011-11-07 18:56   ` Michael Stapelberg
2011-11-09  3:22     ` Matthieu Rakotojaona [this message]
2011-11-09 23:18       ` William Morgan
2011-11-11  1:25         ` [sup-talk] " Matthieu Rakotojaona
2011-11-17  1:33           ` Matthieu Rakotojaona

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=CAMiZLn3dsR_sRfpZV9MLKhJpVhfgsSpd6t3DwHDeg5uydY39Ow@mail.gmail.com \
    --to=matthieu.rakotojaona@gmail.com \
    --cc=sup-devel@rubyforge.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