From: Matthieu Rakotojaona <matthieu.rakotojaona@gmail.com>
To: Steven Hum <sdothum@gmail.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] any testimonials from users who transitioned from mutt?
Date: Fri, 21 Sep 2012 01:58:34 +0200 [thread overview]
Message-ID: <CAMiZLn3pLumCw2Zmm6i+5hV8y_FtgjDBtDjJH57qhVoRONWT5g@mail.gmail.com> (raw)
In-Reply-To: <1348177473-sup-7941@monad>
On Fri, Sep 21, 2012 at 12:25 AM, Steven Hum <sdothum@gmail.com> wrote:
> Even then, I am not sure if heliotrope will address the maildir
> back sync issue (there is an imaptrope fork which may address this). If
> it doesn't, it may not provide me with any benefit towards my offline
> mail usage.
I guess you're talking about https://github.com/rakoo/imaptrope. This
was actually the only reason why I didn't use heliotrope/turnsole (and
sup before it) full-time : I didn't want to do some gymnastics back
and forth for my mail, like everyone here. That's why I started
imaptrope. Unfortunately, I arrived to a point where using http
doesn't give me sufficient speed for the task. So I set out to
integrate it directly in heliotrope.
The result of my work is at
https://github.com/rakoo/heliotrope/tree/imap. You can now run an imap
server along the http one with the following command :
ruby -Ilib bin/heliotrope-server -d /path/to/data --with-imap
and connect to it on localhost:10142. As I explain in the README, the
goal is not to do a fully functional IMAP server, but just enough bits
to work with OfflineIMAP. This software does a great job, and will be
a very helpful tool for a smooth transition. This will be better than
reimplementing some 2-way-syncing-magic once again.
For the moment, heliotrope -> maildir works with a standard
offlineimap installation. Yay ! Don't do it on big mailboxes though,
because it will be horribly long (and by big I mean 100 messages. Yes,
that's not big, I'm working on it)
It is saddening to see that many people are interested in this great
project yet seems to be dying. I was thinking this may be due to
William abandoning sup in favor of heliotrope, and everyone still
following the former ? Anyway, I'll be happily hacking on heliotrope,
so everyone who is willing to continue is warmly invited to test
things out !
--
Matthieu RAKOTOJAONA
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2012-09-20 23:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 21:15 Naveen Nathan
2012-09-19 21:47 ` Alfredo Palhares
2012-09-19 21:56 ` Allan Wind
2012-09-20 0:12 ` Jim Cheetham
2012-09-20 6:43 ` Ico
2012-09-20 22:25 ` Steven Hum
2012-09-20 23:58 ` Matthieu Rakotojaona [this message]
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=CAMiZLn3pLumCw2Zmm6i+5hV8y_FtgjDBtDjJH57qhVoRONWT5g@mail.gmail.com \
--to=matthieu.rakotojaona@gmail.com \
--cc=sdothum@gmail.com \
--cc=sup-talk@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