From: Matti Eiden <snaipperi@gmail.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: Tue, 8 Jun 2010 06:14:08 +0300 [thread overview]
Message-ID: <AANLkTikI63bB_jx3EJsJ15iObHWLZJf_x0d8iw-gDrXP@mail.gmail.com> (raw)
In-Reply-To: <20100604134404.GA28767@artemis.silentflame.com>
Hi Sean,
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..
Let's get one thing straight first, sup doesn't really use specific
status flags/tags or such for mails. Instead, every piece of
information is in the labels. A couple of labels are predefined:
Attachment, Deleted, Draft, Inbox, Killed, Sent, Spam, Starred and
Unread. Technically, a message that is archived is simply lacking the
label "Inbox". Rest of the labels are user-defined.
Standard maildir format already provides following flags by default:
(S)een, (T)rashed, (D)raft. In addition flags that sup doesn't need;
Passed, Replied and Flagged.
Dovecot (an IMAP server) provides user defined flags for maildirs. The
flags are lowercase letters ranging a-z (up to 26 different), and
seems like it works OK with the maildir. (
http://wiki.dovecot.org/MailboxFormat/Maildir ). This could be one
nice option if a limit of some 20 user tags aren't too few.
Example maildir mail flags:
:2,Sacd
S - standard maildir flag: Seen, MUA would label as "Read"
a - custom flag - MUA would label as "Archived"
b - custom flag - MUA would label as "Starred"
d - custom flag - User would label as "Work"
This is of course kinda opposite to sup's current situation where
messages are defined as Unread or Inbox, but anyway..
Personally I don't like the idea of MUA messing up with the email
headers as you suggested. Plus, this would result in a lot of
fragmentation on a hard disk with tens of thousands of emails, if on
initial sync sup would need to write label information in the middle
of every email. And as always when writing, there's a risk of data
loss, which would require additional measures.
This area interests me, however, and I guess I'm gonna make some
experiments how the flagging thing works in action, and if it makes
other mail clients break. (I doubt it does, otherwise Dovecot wouldn't
be using it, huh?).
Regards,
Matti
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-06-08 3:16 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 [this message]
2010-06-09 17:42 ` Sean Whitton
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=AANLkTikI63bB_jx3EJsJ15iObHWLZJf_x0d8iw-gDrXP@mail.gmail.com \
--to=snaipperi@gmail.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