Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Nicolas Pouillard <nicolas.pouillard@gmail.com>
To: hollunder <hollunder@lavabit.com>, sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Switching to Exchange
Date: Sun, 21 Feb 2010 09:40:20 -0800 (PST)	[thread overview]
Message-ID: <4b817004.0f67f10a.39f6.7d86@mx.google.com> (raw)
In-Reply-To: <1266614806-sup-9832@eris>

On Fri, 19 Feb 2010 22:28:59 +0100, hollunder <hollunder@lavabit.com> wrote:
> Excerpts from Steve Goldman's message of 2010-02-19 21:57:02 +0100:
> > Excerpts from Steve Goldman's message of Thu Feb 18 17:56:53 -0500 2010:
> > > 
> > > Hey guys,
> > > 
> > > Thanks for the wild ride, but I need to switch to something more
> > > reliable.  Not sure if there are incompatibilities with my version of
> > > ruby or whatnot, but I'm getting ridiculous CPU usage and random seg
> > > faults.  It's too much stress for me.  And after a crash when I
> > > restart, I have a random collection of seventy or so messages in my
> > > inbox, even though it was zero when I crashed.
> > > 
> > > This combined with not being able to convert to xapian without a seg
> > > fault...
> > > 
> > > Maybe I'll be back some day.
> > > 
> > > Good luck.
> > 
> > In case anyone was worried, I'm back.  I took matters into my own
> > hand.
> > 
> > Essentially, I was dealing with a slow IMAP server.  Since sup doesn't
> > cache IMAP messages locally, this gave me huge headaches when trying
> > to sync with the server during busy times.
> > 
> > The remedy was to download all the messages off the server into a
> > local mbox file and to use fetchmail/procmail to poll for new IMAP
> > messages and append them to the mbox file.
> > 
> > As a result, I was able to successfully use sup-sync to build a xapian
> > index and everything is lightning fast.  Life is good... for now.
> > 
> > Thanks.
> > -- 
> > 
> > Steve Goldman
> > sgoldman@tower-research.com
> > 
> > T: 212.219.6014
> > F: 212.219.6007
> > 
> > Tower Research Capital, LLC
> > 377 Broadway, 11th Fl.
> > New York, NY 10013
> 
> I think most of us just use offlineimap.

I don't use offlineimap, I've tried it but it was not reliable enough for my amount of
messages. I stick to mpop and mboxes.

-- 
Nicolas Pouillard
http://nicolaspouillard.fr
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2010-02-21 17:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 22:56 Steve Goldman
2010-02-19 20:57 ` Steve Goldman
2010-02-19 21:28   ` hollunder
2010-02-21 17:40     ` Nicolas Pouillard [this message]
2010-02-20 17:38   ` Ben Gamari
2010-02-20 21:10     ` Mark Alexander

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=4b817004.0f67f10a.39f6.7d86@mx.google.com \
    --to=nicolas.pouillard@gmail.com \
    --cc=hollunder@lavabit.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