From: "Edward Z. Yang" <ezyang@MIT.EDU>
To: Damien Leone <damien.leone@fensalir.fr>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Adding backward synchronization for Maildir sources
Date: Sun, 18 Jul 2010 18:50:39 -0400 [thread overview]
Message-ID: <1279493200-sup-3095@ezyang> (raw)
In-Reply-To: <1278693172-sup-6247@mailer>
Here are some suggestions...
Excerpts from Damien Leone's message of Fri Jul 09 12:44:01 -0400 2010:
> - I wrote a "sup-sync-back-maildir" script that will synchronize all
> messages from your sources at once. This should be executed the first
> time BEFORE any polling, otherwise your IMAP server will be synched to
> your Sup index and if you did not used another client to mark your
> emails as read etc. (like me) and to update your IMAP server then you
> will lose all what you did in Sup (labels, etc.);
I would recommend having some sort of flag like 'sync-back'd' programatically
generated by sup-sync-back-maildir so that Sup will refuse to start if
you turned on sync-backs without running this command.
> - However you will probably lose all your remote 'replied' and
> 'forwarded' flags after your first backward synchronization to Maildir
> since Sup dropped these labels when it added your messages to xapian.
It seems to me that merging the Maildir flags and the Sup flags would
let you preserve this, but for heavy Sup users this isn't a big deal.
> - Moving a message from a Maildir source to another is not (yet?)
> supported.
I think this will be a pretty killer feature to have, because it means
we can then assign "primary" tags and use those to have sync-backs move
messages between Maildir folders (on the same account, I imagine), which
would translate into a folder-sorted webmail view, which is about the
best you can do without first-class label support in Maildir. I know of
at least one friend who this would be a deal-maker.
Cheers,
Edward
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-07-18 23:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 16:44 Damien Leone
2010-07-09 16:56 ` Edward Z. Yang
2010-07-09 17:14 ` Damien Leone
2010-07-09 19:46 ` Edward Z. Yang
2010-07-17 12:55 ` Damien Leone
2010-07-17 17:05 ` Ben Walton
2010-07-17 17:26 ` Damien Leone
2010-07-18 11:19 ` Tero Tilus
2010-07-18 22:46 ` Edward Z. Yang
2010-07-20 9:39 ` Damien Leone
2010-07-21 0:44 ` Edward Z. Yang
2010-07-21 8:52 ` Damien Leone
2010-07-21 8:54 ` Damien Leone
2010-07-18 22:50 ` Edward Z. Yang [this message]
2010-07-20 9:45 ` Damien Leone
2010-07-18 22:57 ` Edward Z. Yang
2010-07-24 21:30 ` Rich Lane
2010-07-25 22:25 ` Edward Z. Yang
2011-03-13 16:41 ` Damien Leone
2011-10-27 12:34 ` Justin Mazzi
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=1279493200-sup-3095@ezyang \
--to=ezyang@mit.edu \
--cc=damien.leone@fensalir.fr \
--cc=sup-devel@rubyforge.org \
/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