Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] IMAP server restart causes Sup exception
Date: Sat, 24 May 2008 19:45:14 -0700	[thread overview]
Message-ID: <1211683173-sup-855@south> (raw)
In-Reply-To: <f96e0240805200923r6eb46c9fwc53dcc99c63489d5@mail.gmail.com>

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 <wmorgan-sup at masanjin.net>


      reply	other threads:[~2008-05-25  2:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14  1:23 Kevin Riggle
2008-05-19 23:16 ` William Morgan
2008-05-20 15:03   ` Marcus Williams
2008-05-20 16:05     ` William Morgan
2008-05-20 16:23       ` Ben Walton
2008-05-25  2:45         ` William Morgan [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=1211683173-sup-855@south \
    --to=wmorgan-sup@masanjin.net \
    /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