Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: tim@timvaughan.co.uk (Tim Vaughan)
Subject: [sup-talk] Google and IMAP
Date: Mon, 29 Oct 2007 17:17:57 +0000	[thread overview]
Message-ID: <1193677196-sup-2982@londonbackup> (raw)
In-Reply-To: <20071024084757.GO5471@horacrux>

Excerpts from Kevin Mark's message of Wed Oct 24 09:47:57 +0100 2007:
> Thanks for the heads up, I just created a gmail account and added imap
> support. Mutt to only a few minutes to get it to read imap. Now on to
> sup...

I'd be interested to know how you get on.  A couple of things I've noticed
after using sup for a day or two:

* Gmail seems to store messages sent with its SMTP server so when a
  brand-new email is sent it appears in the inbox.  This is a bit annoying
  but I don't think that you can make sup store its sent emails in an IMAP
  folder.

* Sometimes I load a largeish thread and find that a thread has a red line
  with "message not downloaded" in it.

* Feature request: saved searches!

* Is there a way to make sup reply from the address an email was sent to
  (like Gmail does when it handles more than one account)?

* Sup is great but having to rebuild the index every time I use Gmail's web
  interface to send an email hurts :(.  Although I realise that's just the
  Way Things Are.

I'm really hoping I can start using sup full time though rather than Gmail's
web interface because it's so much more fun!
-- 
Tim Vaughan
07725749263


  reply	other threads:[~2007-10-29 17:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24  7:51 Tim Vaughan
2007-10-24  8:47 ` Kevin Mark
2007-10-29 17:17   ` Tim Vaughan [this message]
2007-11-02  3:02     ` William Morgan
2007-10-27  1:49 ` William Morgan
2007-10-27 16:28   ` Tim Vaughan
2007-10-27 16:56     ` 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=1193677196-sup-2982@londonbackup \
    --to=tim@timvaughan.co.uk \
    /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