From: its.jeff.balogh@gmail.com (Jeff Balogh)
Subject: [sup-talk] Gmail IMAP with sup
Date: Tue, 15 Apr 2008 21:46:45 -0400 [thread overview]
Message-ID: <1208309556-sup-3399@archie> (raw)
In-Reply-To: <6038aa2a0804151530uae50bbbxc6b8eed49906fcf8@mail.gmail.com>
Miles Pomeroy wrote:
> Setup:
> I'm a new user of sup trying use it will my gmail account. I set it up
> using imaps://imap.gmail.com:993/INBOX. Sup went through and indexed
> the 2000 some odd emails in my inbox and then present them to me just
> fine, great.
>
> The problem:
> 1. When new mail come in sup downloads it but it is not marked new. At
> least not in anyway that I can distinguish from other messages.
I don't know the cause of that.
> 2. When I look at those messages and then go back to gmail through the
> browser, those messages are not marked as being read.
This is part of the sup philosophy. It treats mail sources as dumb stores, and
doesn't try to change them.
> The question:
> Does anyone else use gmail imap with sup? If so did you set it up
> differently than I? Am I doing something wrong? Is there any tutorial
> for setting up gmail imap specifically for sup?
I used to run sup on gmail imap, using the '[Gmail]/All Mail' folder (which you
need to url encode as '%5BGmail%5D/All%20Mail').
I got tired of the imap slowness though, and switched to using offlineimap, so I
haven't had sup talking to gmail in a while.
-- jeff
next prev parent reply other threads:[~2008-04-16 1:46 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 [this message]
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
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=1208309556-sup-3399@archie \
--to=its.jeff.balogh@gmail.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