From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Google and IMAP
Date: Thu, 01 Nov 2007 20:02:44 -0700 [thread overview]
Message-ID: <1193971010-sup-3497@south> (raw)
In-Reply-To: <1193677196-sup-2982@londonbackup>
Excerpts from Tim Vaughan's message of Mon Oct 29 10:17:57 -0700 2007:
> * 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.
This is correct. I don't ever plan to write IMAP saving code, but I
would accept a patch to this effect.
> * Sometimes I load a largeish thread and find that a thread has a red
> line with "message not downloaded" in it.
If you mean a "message not received" line in Sup, that signifies that
some message had a References: header that mentioned some message id
that never occurred. So it could be symptomatic of someone replying to
an off-list message, or it could be a corrupted References: header, or
it could be a message that you just didn't receive for whatever reason.
(Or that isn't stored in Gmail.)
> * Feature request: saved searches!
Acknowledged. On the todo.
> * 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)?
If you add an account to config.yaml with that email address, it should
start replying from it as well. Unfortunately this is still a manual
process at this point.
> * 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.
Sadly, yes...
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2007-11-02 3:02 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
2007-11-02 3:02 ` William Morgan [this message]
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=1193971010-sup-3497@south \
--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