From: Sean Whitton <sean@silentflame.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Storing message tags and other Sup info as headers in Maildir
Date: Wed, 9 Jun 2010 18:42:08 +0100 [thread overview]
Message-ID: <20100609174207.GA22445@artemis.silentflame.com> (raw)
In-Reply-To: <AANLkTikI63bB_jx3EJsJ15iObHWLZJf_x0d8iw-gDrXP@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1100 bytes --]
Hi Matti,
Thanks for the informative reply. IMAP user-defined flags sound like an
excellent way to go about this, but of course, not everyone uses dovecot
(dunno why!). Let me know how you get on.
On Tue, Jun 08, 2010 at 06:14:08AM +0300, Matti Eiden wrote:
> I was expecting somebody else to reply in this but since I'm not
> seeing anyone doing so, I'll give it a shot. I only recently
> discovered sup, and I'm not a Ruby programmer, however I got quite a
> bunch of experience with Python (now the rest of the mailing list can
> proceed flaming me). The following post is purely speculative.
>
> Shortly put, I don't expect to see any change on this matter, at least
> in the near future. There is and has been a tool, sup-sync-back which
> should reflect the changes back to mbox/maildir but the way it works
> is far from ideal, I guess. Anyway..
I keep hearing about sup-sync-back but I'm not sure really what it does.
Where can I find information about it?
S
--
Sean Whitton / <sean@silentflame.com>
OpenPGP KeyID: 0x3B6D411B
http://seanwhitton.com/
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2010-06-09 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 13:44 Sean Whitton
2010-06-08 3:14 ` Matti Eiden
2010-06-09 17:42 ` Sean Whitton [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=20100609174207.GA22445@artemis.silentflame.com \
--to=sean@silentflame.com \
--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