also sprach Carl Worth [2010.01.15.1124 +1300]:
> > You might have marked a message 'read' on one machine and if the two
> > get out of sync on another machine, you might have the same message
> > unread there.
>
> That's a different issue though. With two databases there's clearly the
>
also sprach Carl Worth [2010.01.14.1432 +1300]:
> Yes. This approach requires some external means of synchronizing the
> tags from one system to another.
>
> I don't understand what it would mean to have the mailstore and the
> database out of synch here. This approach doesn't have the tags in
On Thu, 14 Jan 2010 21:04:21 +1300, martin f krafft
wrote:
> You might have marked a message 'read' on one machine and if the two
> get out of sync on another machine, you might have the same message
> unread there.
That's a different issue though. With two databases there's clearly the
On Thu, 14 Jan 2010 21:04:21 +1300, martin f krafft madd...@madduck.net wrote:
You might have marked a message 'read' on one machine and if the two
get out of sync on another machine, you might have the same message
unread there.
That's a different issue though. With two databases there's
also sprach Carl Worth cwo...@cworth.org [2010.01.15.1124 +1300]:
You might have marked a message 'read' on one machine and if the two
get out of sync on another machine, you might have the same message
unread there.
That's a different issue though. With two databases there's clearly the
also sprach Scott Morrison [2010.01.13.1752 +1300]:
> The problem with anything that is not universally supported is
> that for a package that is to appeal to a wide userbase, most
> don't know and don't care about the particulars of this IMAP
> server vs that IMAP server. all they know it that
On Wed, 13 Jan 2010 00:39:14 -0500, Scott Morrison wrote:
> > Maybe a better approach would be content addressing (see below).
>
> Content hashing -- good Idea (& not something that has hit me before)
> -- better than Message-Id as I believe there are still some MUA /MTAs
> that allow messages
On Tue, 12 Jan 2010 11:19:09 +1300, martin f krafft
wrote:
> 1. External database, which has the downside of not being
>synchronisable with standard IMAP, like the rest of your mail
>(assuming you use IMAP). Also, it's possible for mailstore and
>database to get out of sync.
Yes.
also sprach Scott Morrison [2010.01.12.1711 +1300]:
> 1. synchronization of tag data with emails -- if they are in
> a subfolder then it presents the issue of maintaining this
> subfolder when managing emails (moving, deleting, duplicating etc)
> and any .tag folder unaware clients are likely
On 2010-01-12, at 8:24 PM, martin f krafft wrote:
> also sprach Scott Morrison [2010.01.12.1711 +1300]:
>> 1. synchronization of tag data with emails -- if they are in
>> a subfolder then it presents the issue of maintaining this
>> subfolder when managing emails (moving, deleting, duplicating
On Wed, 13 Jan 2010 00:39:14 -0500, Scott Morrison sm...@indev.ca wrote:
Maybe a better approach would be content addressing (see below).
Content hashing -- good Idea ( not something that has hit me before)
-- better than Message-Id as I believe there are still some MUA /MTAs
that allow
also sprach Scott Robinson [2010.01.12.1644 +1300]:
> I wrote a script to store and sync my tags.
>
> * One filename per message-ID.
> * Line-feed seperated tags in each file.
>
> Then the whole structure is controlled via git.
> Conflict-resolution and sync comes for free.
How do you
On Tue, Jan 12, 2010 at 11:19:09AM +1300, martin f krafft wrote:
> I think [tag leakage] it makes in-headers unusable. After all, I don't
> ever want anyone else to know that I tag e-mails from my boss as
> "from-idiots",
You can cryptographically hash tags so that third-parties can't read
the
Folks, over in #notmuch, we just floated an idea that I'd like to
get out to you. We've been debating storing tags for messages.
Therefore I am cross-posting. Please forgive me.
So far, there are two approaches:
1. External database, which has the downside of not being
synchronisable with
Thought you would be interested in my experiences and thoughts from actually
doing this kind of stuff.
With my software MailTags (www.indev.ca/MailTags.html) and I have looked at all
these options and decided to go with storing tags in headers (in json
formatted data for the X-MailTags
I wrote a script to store and sync my tags.
* One filename per message-ID.
* Line-feed seperated tags in each file.
Then the whole structure is controlled via git. Conflict-resolution and sync
comes for free.
It isn't clear what use-case the earlier e-mail is aiming to satisfy. This is
how
16 matches
Mail list logo
