From: daniel@electricrain.com (Dan Sully)
Subject: [sup-talk] Syncing from Exchange IMAP
Date: Wed, 28 Nov 2007 10:09:01 -0800 [thread overview]
Message-ID: <20071128180901.GA22871@electricrain.com> (raw)
In-Reply-To: <1196269754-sup-8420@south>
* William Morgan shaped the electrons to say...
>This suggests that Exchange is crazy and is giving different sizes for
>the same message at different points in time.
I concur that Exchange is crazy.
>But that error is only a sanity check (hence "crazy"). If you comment
>out the line that raises it (lib/sup/imap.rb line 276), do things work
>right? Specifically, when you hit enter in thread-index-mode, do you
>actually see the messages you thought you would?
Yes, things appear to work right. The mismatch only fails on the first 2
messages.
-D
--
<dsully> please describe web 2.0 to me in 2 sentences or less.
<jwb> you make all the content. they keep all the revenue.
next prev parent reply other threads:[~2007-11-28 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 1:25 Dan Sully
2007-11-28 17:11 ` William Morgan
2007-11-28 18:09 ` Dan Sully [this message]
2007-11-28 22:35 ` Brendan O'Connor
2007-12-08 21:46 ` William Morgan
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=20071128180901.GA22871@electricrain.com \
--to=daniel@electricrain.com \
/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