From: marc.hartstein@alum.vassar.edu (Marc Hartstein)
Subject: [sup-talk] Gmail IMAP with sup
Date: Wed, 16 Apr 2008 13:15:09 -0400 [thread overview]
Message-ID: <1208366079-sup-486@cabinet> (raw)
In-Reply-To: <1208358880-sup-751@south>
Excerpts from William Morgan's message of Wed Apr 16 11:16:57 -0400 2008:
>
> There's no tutorial, at least not yet. What Jeff said is best practice
> at this point---most everyone has switched to offlineimap as an
> intermediate layer because Gmail (and possibly the Ruby IMAP libraries)
> isn't fast enough for loading large threads.
Just curious, why do people prefer offlineimap to fetchmail (using
either IMAP or POP protocols)? Given that sup doesn't write back to the
store, so you're not getting the IMAP advantage of sending read status
back to the server...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20080416/742bc4f5/attachment.bin
next prev parent reply other threads:[~2008-04-16 17:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 22:30 Miles Pomeroy
2008-04-16 1:46 ` Jeff Balogh
2008-04-28 16:25 ` Miles Pomeroy
2008-04-29 17:45 ` William Morgan
2008-04-16 15:16 ` William Morgan
2008-04-16 15:30 ` Kendall Grant Clark
2008-04-16 17:15 ` Marc Hartstein [this message]
2008-04-16 19:02 ` Chris Warrington
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=1208366079-sup-486@cabinet \
--to=marc.hartstein@alum.vassar.edu \
/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