From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] IMAP folder/label integration and playing better with changed sources?
Date: Mon, 27 Apr 2009 11:18:27 -0700 [thread overview]
Message-ID: <1240856180-sup-6270@entry> (raw)
In-Reply-To: <0c334e4c-0480-4def-b64a-b4996431f5c9@x3g2000yqa.googlegroups.com>
Reformatted excerpts from Saku Ytti's message of 2009-04-22:
> Problem for me is, I want to use also mobile phone email client and
> webmail, so I'm kinda stuck with mutt. Is it likely that this could be
> addressed in future?
One thing I'd like to do with Sup the Service would be to provide an
IMAP server interface to it. Then you could use with standard IMAP
clients. But that's probably a ways off.
> And for the actual subject related matter, could it be possible to
> store labels as folders optionally? This would play along really well
> for those who use gmail, as you would essentially get synchronised
> labeling between sup and webclient.
Sounds like a good idea but a lot of work...
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-04-27 18:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 7:29 Saku Ytti
2009-04-27 18:18 ` William Morgan [this message]
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=1240856180-sup-6270@entry \
--to=wmorgan-sup@masanjin.net \
/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