From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] IMAP questions (n00b) :)
Date: Thu, 07 May 2009 06:12:31 -0700 [thread overview]
Message-ID: <1241701676-sup-657@entry> (raw)
In-Reply-To: <24cc29320905070338u1e23c6d3sa78c20dd0da60b19@mail.gmail.com>
Reformatted excerpts from Filip Stokkeland's message of 2009-05-07:
> Hi! I just discovered and started testing Sup. And it looks great!
Thanks!
> I tried browsing through some of the mailing list archives, and I
> found postings saying Sup does not sync back to IMAP(S). So I take it
> then, that when I mark mail as read or as spam, nothing happens on the
> IMAP server, but only in the local Sup index?
That's correct. I'm not opposed to pushing those flags back to the IMAP
server in principle, at least in batch mode (there's a tool that does
that now for mbox, and I'm working on Maildir), but writing that code
pretty low on my personal priority queue at the moment.
> And another thing. I have my main work email today sorted on the
> server, using Sieve, so I get new email sorted into 40 different IMAP
> folders. In Sup, can I get it to automatically fetch from all
> subscribed IMAP folders?
There's not a good automatic way of doing this. If you can generate the
list of folders, then you can run sup-add on each one.
> Or maybe I should rather fetch all this email into my own local server
> using fetchmail or something and then either put it all in one big
> inbox or multiple mboxes locally and then add this as source?
Current best practice for IMAP is to sync it locally with a program like
offlineimap. That also speeds things up, e.g. when you open a thread
with 100 messages, Sup wants to download them all at once, and IMAP is
much slower than Maildir for that.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-05-07 13:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 10:38 Filip Stokkeland
2009-05-07 13:12 ` 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=1241701676-sup-657@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