From: yanghatespam@gmail.com (Yang Zhang)
Subject: [sup-talk] Beginner questions
Date: Sun, 04 May 2008 20:47:50 -0400 [thread overview]
Message-ID: <481E5936.7040600@gmail.com> (raw)
Hi, I'm interested in getting started with sup. For now, I just ran
sup-config to use Gmail IMAP. Things seem to have gone smoothly, though
I have a few questions:
(1) sup did end up taking many, many hours to download my entire inbox
of messages. I'd rather it lazily download these messages. Is there
some way to achieve this?
(2) At some point, I was prompted:
Enter any labels to be automatically added to all messages from this
source, separated by spaces (or 'none') (enter for "inbox"): none
When dealing with IMAP servers, does sup store its labels as IMAP
keywords (i.e., are they stored on the server)? (A bunch of IMAP
servers support IMAP keywords. Gmail's labels manifest themselves as
folders, however, and not IMAP keywords. [1])
(3) How does sup group messages into the same thread? Does it rely on
References: header fields, subject-matching,
body-substring-matching/overlap, or something else?
(4) yanghatespam at gmail.com is the account I use for mailing lists. I
use many lists, so I needed a way to cope with the large message volume.
Most of the time, I am only interested in the threads in which I have
been a participant (e.g., I'm interested in replies to my posts). I
have Gmail filters that use simple heuristics like "If my name is in the
email, leave it marked as unread; otherwise mark it read." This, of
course, leads to many false positives/negatives (Gmail's filterts are
only so expressive).
If sup's thread-grouping is decent, then it would be neat/more accurate
to extend sup somehow to instead use these groupings for the filtering.
I.e., if an incoming message is grouped with a thread in which I was a
participant, then leave it marked unread; otherwise, mark it read.
Any thoughts on whether such an extension is possible, and if so, where
to start with it? Is sup at all extensible at the current time? Is a
feature such as this already in the works?
(5) I remember reading one archived list post on how others were using
the "[Gmail]/All Mail" folder as their. Should I have used that instead
of "Inbox"?
If I were using a more conventional IMAP server, in which messages don't
appear in multiple folders, does sup expect me to add all the folders,
so that it can display complete threads (e.g. merging Sent and Inbox)?
So is the difference with Gmail, then, that "[Gmail]/All Mail" is the
one and only folder to use?
In general, does sup play nicely with Gmail? Any experiences to be
shared? The only other quirk I'm aware of is that to truly delete a
message requires moving it to the Gmail/Trash folder (otherwise only a
label is removed).
Thanks in advance for any answers!
(6) Scrolling through the buffer that is immediately presented to me
when starting sup, I only see about 3 pages of threads. Is this
correct? How do I get to the rest?
(7) Does sup support Unicode? The inbox display seems to be a bit
screwy for me (extraneous floating characters, things changing when
highlighted, etc.), though it could also be my terminal (I'm using
putty, but I just verified that I'm running it in UTF-8 mode).
[1]
http://weblog.timaltman.com/archive/2008/02/24/gmails-buggy-imap-implementation
--
Yang Zhang
http://www.mit.edu/~y_z/
next reply other threads:[~2008-05-05 0:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 0:47 Yang Zhang [this message]
2008-05-05 1:02 ` Daniel Wagner
2008-05-05 2:08 ` Yang Zhang
2008-05-05 18:09 ` Marc Hartstein
2008-05-05 18:29 ` Yang Zhang
2008-05-19 23:38 ` William Morgan
2008-05-06 2:15 ` Christopher Warrington
2008-05-05 2:48 kendall at clarkparsia.com
2008-05-19 23:44 ` William Morgan
2008-08-03 23:17 Thorsten Kramer
2008-08-04 1:41 ` William Morgan
2008-08-05 21:52 ` Thorsten Kramer
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=481E5936.7040600@gmail.com \
--to=yanghatespam@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