Reformatted excerpts from Ben Walton's message of 2008-05-20:
> I think you'll find that things get better if you do plain IMAP with
> stunnel instead of relying on the ssl support in ruby/ruby-imap.  I
> had horrible (to the point where I almost had to switch away from
> ruby) problems with a project that relied on the ability to do imaps.
> The imap library may be partially to blame (and the imap spec
> requiring threading doesn't help...), but I found that things got much
> better without ssl being handled by ruby.

Interesting. I didn't know about stunnel. Kevin, if you're seeing this
on a regular basis, you could try that... or switch to offlineimap like
everyone else has for performance reasons.

Sup's IMAP support leaves a lot to be desired and I'm happy to blame
this library. Irritatingly slow, and prone to insane errors like this
one. I don't want to disable it, though, and I sure as heck don't want
to write my own IMAP library. So for the time being we're stuck with it.
-- 
William <[EMAIL PROTECTED]>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

Reply via email to