From: William Morgan <wmorgan-sup@masanjin.net>
To: Steffan Davies <steff@steff.name>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] exception on first IMAPS load in 0.8.1-1
Date: Mon, 25 Jan 2010 15:25:02 -0500 [thread overview]
Message-ID: <1264451054-sup-7120@masanjin.net> (raw)
In-Reply-To: <20100123151414.GB2294@steff.name>
Reformatted excerpts from Steffan Davies's message of 2010-01-23:
> Got this while sup was inhaling my 60+k-item mailbox. Xubuntu Karmic,
> loading from Dovecot across an idle gigabit ethernet.
Can you try with 0.10.1 please? Also note that the Ruby IMAP library is
not great, and tends to break with big things like this. The preferred
solution is to turn IMAP into a maildir with something like offlineimap.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-01-25 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 15:14 Steffan Davies
2010-01-25 20:25 ` William Morgan [this message]
2010-01-25 20:30 ` Ben Walton
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=1264451054-sup-7120@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=steff@steff.name \
--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