From: lists+sup@protozoic.com (Tim Gray)
Subject: [sup-talk] problems with Maildir and IMAP offline
Date: Tue, 14 Jul 2009 11:45:07 -0400 [thread overview]
Message-ID: <20090714154507.GD393@d228.scdc1.swarthmore.edu> (raw)
In-Reply-To: <1247584404-sup-7126@Longbow>
On Tue 14, Jul'09 at 11:14 AM -0400, Andrei Thorp wrote:
> People perhaps don't want this. It's slower, and a lot of folks probably
> do no syncing back since all they use is sup anyway.
I would hope in this day in age we can change a database entry and move a
file at the same time without too much of a performance hit. I would think
it only gets unbearable when you don't update as you go and you have to do a
large batch of messages. But you are right, maybe people don't want that.
Personally, and this is a side note, if I was involved in the project, I'd
push for canning the built in IMAP capabilities all together. Just run
offlineimap or one of the other IMAP syncing utilities. Add to that beefing
up the Maildir handling. Just worry about better and more transparent
sync-back-to-Maildir capabilities and let offlineimap worry about the server
side of the equation.
> Understood. Makes sense in your use case. I don't really understand why
> you'd want to use pine/mutt when you've already got sup though ;)
As you can tell, I'm not quite sold on sup yet. I've switched mail clients
enough over the past few years that switching in and of itself is a giant
pain. I've settled on Maildir as my 'client' for now. I can serve it via
IMAP if I need, I can read it with a couple mail clients, and I can easily
convert it to mbox however I want to with some simple Python code.
If I switch to sup full time, I would be comforted by the fact that if I
choose to change in 2 years, all of my mail is marked read, deleted mail is
actually deleted, and even though I was using sup labels for my
organization, things are still organized in some fashion by appropriate
folders on the file system. The last part could be achievable by some
combination of offlineimap + gmail/sieve filtering and fetchmail/getmail +
procmail. It'd still be nice to be able to move physical messages around in
sup though. Maybe I'm just nuts though.
next prev parent reply other threads:[~2009-07-14 15:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 21:20 Luis Cañas Díaz
2009-07-14 13:24 ` Andrei Thorp
[not found] ` <20090714134544.GD90157@d228.scdc1.swarthmore.edu>
2009-07-14 14:02 ` Andrei Thorp
2009-07-14 15:00 ` Tim Gray
2009-07-14 15:07 ` Ben Walton
2009-07-14 15:28 ` Tim Gray
2009-07-14 15:39 ` Andrei Thorp
2009-07-14 15:59 ` Tim Gray
2009-07-14 15:14 ` Andrei Thorp
2009-07-14 15:45 ` Tim Gray [this message]
2009-07-14 16:21 ` Israel Herraiz
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=20090714154507.GD393@d228.scdc1.swarthmore.edu \
--to=lists+sup@protozoic.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