From: pomeroymiles@gmail.com (Miles Pomeroy)
Subject: [sup-talk] Gmail IMAP with sup
Date: Mon, 28 Apr 2008 09:25:57 -0700 [thread overview]
Message-ID: <C1A07365-2CDE-4C1A-9416-9B4C125610D4@gmail.com> (raw)
In-Reply-To: <1208309556-sup-3399@archie>
>> 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.
If this is part of sup philosophy then I'm assuming that it's not
going to change. Can someone explain to me why this is a good thing? I
use multiple computers and would like to use multiple clients to check
my email, but this philosophy seems to only allow for one computer,
one client.
next prev parent reply other threads:[~2008-04-28 16:25 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 [this message]
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=C1A07365-2CDE-4C1A-9416-9B4C125610D4@gmail.com \
--to=pomeroymiles@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