From morg-bounces@ietf.org  Mon May 12 21:49:52 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1AF363A6859;
	Mon, 12 May 2008 21:49:52 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9600C3A6859
	for <morg@core3.amsl.com>; Mon, 12 May 2008 21:49:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.399
X-Spam-Level: 
X-Spam-Status: No, score=-5.399 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_64=0.6, J_CHICKENPOX_66=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id y4mHlBwtq3NG for <morg@core3.amsl.com>;
	Mon, 12 May 2008 21:49:48 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id 632373A681E
	for <morg@ietf.org>; Mon, 12 May 2008 21:49:48 -0700 (PDT)
Received: from [192.168.10.2] (82-203-162-146.dsl.gohome.fi [82.203.162.146])
	by dovecot.org (Postfix) with ESMTP id 5E60916471E3;
	Tue, 13 May 2008 07:49:12 +0300 (EEST)
From: Timo Sirainen <tss@iki.fi>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Date: Tue, 13 May 2008 07:49:11 +0300
Message-Id: <1210654151.9518.539.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.1 
Cc: morg@ietf.org
Subject: [MORG] SEARCH=INTHREAD
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0548498371=="
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org


--===============0548498371==
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-tDy10xnZU40g0VgpU/23"


--=-tDy10xnZU40g0VgpU/23
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

I'm planning on implementing this pretty soon (I need SEARCH INTHREAD
feature). Two issues though:

1) SEARCH THREADROOT sounds like it should return a list of roots for
all threads (should "For each thread in the message" be "in the mailbox"
instead?). The problem is with threads where the root is a dummy instead
of a message. I guess SEARCH THREADROOT just doesn't return anything
with them? I can't really think of a good alternative for that behavior.

2) THREAD=3DREFS algorithm. It has 4 differences from THREAD=3DREFERENCES:

1. In-Reply-To: header is ignored.
2. Date: header is ignored (and I assume INTERNALDATE is too?)
3. Base subject merging isn't done
4. Server is allowed to return "wrong" THREAD replies because of caching

I think 1 shouldn't be done. Using the same base threading algorithm as
THREAD=3DREFERENCES makes it a lot easier to implement THREAD=3DREFS as wel=
l
as making a better result.

Why 2? With THREAD command it seems useful to sort messages in threads
by their Date: header so they could be read in correct order (but for
root sorting I prefer sorting by newest-INTERNALDATE-in-thread). With
SEARCH INTHREAD command the server is free to ignore Date: header (and
INTERNALDATE) also with THREAD=3DREFERENCES, because it doesn't affect the
result. Although with SEARCH THREADROOT/THREADLEAF the date may affect
the result with THREAD=3DREFERENCES because of subject merging.

3 I agree with and 4 I'm not sure.

I was planning on writing a draft about THREAD=3DREFERENCES2. It basically
sorts thread roots using newest-INTERNALDATE-in-thread and doesn't do
base subject merging. This also means that SEARCH
INTHREAD/THREADROOT/THREADLEAF work correctly without looking up dates.
So I'd think it accomplishes all goals of THREAD=3DREFS except for 4.

If 4 is really wanted, I'm beginning to think maybe the entire algorithm
should be changed to be described simply as "server-dependent
implementation" where the server is free to use whatever algorithm it
thinks is the best (could even be user-configurable). It could renamed
then to THREAD=3DSERVER or something.

--=-tDy10xnZU40g0VgpU/23
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBIKR3HyUhSUUBViskRAn4cAJ415ZtlEyuBZsdhwLgO9G9YWMRADACfeohQ
emizDJ5vp4s6xyQBDj2wY5I=
=F5VT
-----END PGP SIGNATURE-----

--=-tDy10xnZU40g0VgpU/23--


--===============0548498371==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html

--===============0548498371==--



From morg-bounces@ietf.org  Tue May 13 01:10:55 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 825123A6835;
	Tue, 13 May 2008 01:10:55 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 58B7F3A6815
	for <morg@core3.amsl.com>; Tue, 13 May 2008 01:10:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_64=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dtmLfI9a1CuT for <morg@core3.amsl.com>;
	Tue, 13 May 2008 01:10:37 -0700 (PDT)
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by core3.amsl.com (Postfix) with ESMTP id 5B2953A67A5
	for <morg@ietf.org>; Tue, 13 May 2008 01:10:36 -0700 (PDT)
Received: from kalyani.oryx.com (localhost.oryx.com [127.0.0.1])
	by kalyani.oryx.com (Postfix) with ESMTP id DF0D84AC81;
	Tue, 13 May 2008 10:09:14 +0200 (CEST)
Received: from 195.30.37.40 (HELO lochnagar.oryx.com) by kalyani.oryx.com with
	esmtp id 1210666153-37219-2075; Tue, 13 May 2008 10:09:13 +0200
Message-Id: <M36GB7SjVS/ecjHThF/mug.md5@lochnagar.oryx.com>
Date: Tue, 13 May 2008 10:09:02 +0200
From: Arnt Gulbrandsen <arnt@oryx.com>
To: Timo Sirainen <tss@iki.fi>
References: <1210654151.9518.539.camel@hurina>
In-Reply-To: <1210654151.9518.539.camel@hurina>
Mime-Version: 1.0
Cc: morg@ietf.org, Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Subject: Re: [MORG] SEARCH=INTHREAD
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

Timo Sirainen writes:
> I'm planning on implementing this pretty soon (I need SEARCH INTHREAD 
> feature). Two issues though:
>
> 1) SEARCH THREADROOT sounds like it should return a list of roots for 
> all threads (should "For each thread in the message" be "in the 
> mailbox" instead?). The problem is with threads where the root is a 
> dummy instead of a message. I guess SEARCH THREADROOT just doesn't 
> return anything with them? I can't really think of a good alternative 
> for that behavior.

THREADROOT was difficult. I haven't implemented it. The root of a thread 
seems to be a fuzzy concept.

> 2) THREAD=REFS algorithm. It has 4 differences from THREAD=REFERENCES:
>
> 1. In-Reply-To: header is ignored.
> 2. Date: header is ignored (and I assume INTERNALDATE is too?)
> 3. Base subject merging isn't done
> 4. Server is allowed to return "wrong" THREAD replies because of caching

No, let's use i-r-t.

I don't use Date, but that's, hm, orthogonal. The code I have doesn't 
make a list of threads, it makes a set of threads, so sorting threads 
by date or anything else is not something I've had to do.

The THREAD command has to sort threads. I don't care how it's done - as 
REFERENCES, as REFERENCES2 or another way. All are fine IMO.

> I think 1 shouldn't be done. Using the same base threading algorithm 
> as THREAD=REFERENCES makes it a lot easier to implement THREAD=REFS 
> as well as making a better result.
>
> Why 2?

It just slipped my mind. I somehow didn't realize that the part I hadn't 
written needed Date.

> With THREAD command it seems useful to sort messages in threads by 
> their Date: header so they could be read in correct order (but for 
> root sorting I prefer sorting by newest-INTERNALDATE-in-thread). With 
> SEARCH INTHREAD command the server is free to ignore Date: header 
> (and INTERNALDATE) also with THREAD=REFERENCES, because it doesn't 
> affect the result. Although with SEARCH THREADROOT/THREADLEAF the 
> date may affect the result with THREAD=REFERENCES because of subject 
> merging.
>
> 3 I agree with and 4 I'm not sure.
>
> I was planning on writing a draft about THREAD=REFERENCES2. It 
> basically sorts thread roots using newest-INTERNALDATE-in-thread and 
> doesn't do base subject merging. This also means that SEARCH 
> INTHREAD/THREADROOT/THREADLEAF work correctly without looking up 
> dates. So I'd think it accomplishes all goals of THREAD=REFS except 
> for 4.

I'd like to have only one of THREAD=REFS and THREAD=REFERENCES2, so if 
we can find a way to make one serve both of our needs, that would make 
me happy.

I don't care very much about 4. I assume my server will be noncompliant 
of 4 is dropped, but that doesn't scare me in this case. (I used to 
think there would be differences in practice, but don't think so any 
more.)

If I understand it correctly, then this would satisfy us both:

1. Use References.
2. Use In-Reply-To exactly as THREAD=REFERENCES does.
3. Don't use Subject.
4. Sort the threads by the thread's most recent internaldate.

Arnt
_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html


From morg-bounces@ietf.org  Tue May 13 01:20:34 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E723E3A6883;
	Tue, 13 May 2008 01:20:34 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9ACF03A6883
	for <morg@core3.amsl.com>; Tue, 13 May 2008 01:20:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8FEs-KXQ22jg for <morg@core3.amsl.com>;
	Tue, 13 May 2008 01:20:31 -0700 (PDT)
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by core3.amsl.com (Postfix) with ESMTP id A17FD3A67A4
	for <morg@ietf.org>; Tue, 13 May 2008 01:20:31 -0700 (PDT)
Received: from kalyani.oryx.com (localhost.oryx.com [127.0.0.1])
	by kalyani.oryx.com (Postfix) with ESMTP id 350454AC7E;
	Tue, 13 May 2008 10:19:36 +0200 (CEST)
Received: from 195.30.37.40 (HELO lochnagar.oryx.com) by kalyani.oryx.com with
	esmtp id 1210666775-37219-2088; Tue, 13 May 2008 10:19:35 +0200
Message-Id: <oIEPsQEdUzK3jJzESbFg+Q.md5@lochnagar.oryx.com>
Date: Tue, 13 May 2008 10:19:24 +0200
From: Arnt Gulbrandsen <arnt@oryx.com>
To: morg@ietf.org
References: <1210654151.9518.539.camel@hurina>
	<M36GB7SjVS/ecjHThF/mug.md5@lochnagar.oryx.com>
In-Reply-To: <M36GB7SjVS/ecjHThF/mug.md5@lochnagar.oryx.com>
Mime-Version: 1.0
Subject: [MORG] THREADROOT and THREADLEAF
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

Dave wanted THREADROOT and THREADLEAF, and I agree they make sense. 
However, I'm not sure they carry their load. How about these 
definitions?

THREADROOT matches a message if none of the message's ancestors (as 
listed in References and In-Reply-To) exist in the current mailbox.

THREADLEAF matches a message if no messages in this mailbox list its 
message-id in References or In-Reply-To.

Are there good enough use cases to add these? (They're tricky for me to 
implement.)

Arnt
_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html


From morg-bounces@ietf.org  Tue May 13 01:40:41 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C969628C2D4;
	Tue, 13 May 2008 01:40:41 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 032AA28C2D4
	for <morg@core3.amsl.com>; Tue, 13 May 2008 01:40:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.001
X-Spam-Level: 
X-Spam-Status: No, score=-5.001 tagged_above=-999 required=5
	tests=[AWL=-0.398, BAYES_00=-2.599, J_CHICKENPOX_64=0.6,
	MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rAq2TDOgDH+s for <morg@core3.amsl.com>;
	Tue, 13 May 2008 01:40:39 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id B826328C2D3
	for <morg@ietf.org>; Tue, 13 May 2008 01:40:38 -0700 (PDT)
Received: from [192.168.10.2] (82-203-162-146.dsl.gohome.fi [82.203.162.146])
	by dovecot.org (Postfix) with ESMTP id 97317FA8B07;
	Tue, 13 May 2008 11:39:05 +0300 (EEST)
From: Timo Sirainen <tss@iki.fi>
To: Arnt Gulbrandsen <arnt@oryx.com>
In-Reply-To: <M36GB7SjVS/ecjHThF/mug.md5@lochnagar.oryx.com>
References: <1210654151.9518.539.camel@hurina>
	<M36GB7SjVS/ecjHThF/mug.md5@lochnagar.oryx.com>
Date: Tue, 13 May 2008 11:39:05 +0300
Message-Id: <1210667945.9518.576.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.1 
Cc: morg@ietf.org, Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Subject: Re: [MORG] SEARCH=INTHREAD
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1239608910=="
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org


--===============1239608910==
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-iGeKC8sCQ9wIGuGCp3+W"


--=-iGeKC8sCQ9wIGuGCp3+W
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, 2008-05-13 at 10:09 +0200, Arnt Gulbrandsen wrote:
> Timo Sirainen writes:
> > I'm planning on implementing this pretty soon (I need SEARCH INTHREAD=20
> > feature). Two issues though:
> >
> > 1) SEARCH THREADROOT sounds like it should return a list of roots for=20
> > all threads (should "For each thread in the message" be "in the=20
> > mailbox" instead?). The problem is with threads where the root is a=20
> > dummy instead of a message. I guess SEARCH THREADROOT just doesn't=20
> > return anything with them? I can't really think of a good alternative=20
> > for that behavior.
>=20
> THREADROOT was difficult. I haven't implemented it. The root of a thread=20
> seems to be a fuzzy concept.

Maybe in case of a dummy root return all its children as roots? Probably
more useful than not returning them at all.

I can think of a couple of use cases for THREADROOT, but is THREADLEAF
actually useful for something? But I guess it would be simple enough for
me to implement, so I don't mind that much.

> I'd like to have only one of THREAD=3DREFS and THREAD=3DREFERENCES2, so i=
f=20
> we can find a way to make one serve both of our needs, that would make=20
> me happy.

That would be better, yes. I also don't care if it's called REFS or
REFERENCES2.

> I don't care very much about 4. I assume my server will be noncompliant=20
> of 4 is dropped, but that doesn't scare me in this case. (I used to=20
> think there would be differences in practice, but don't think so any=20
> more.)

I'm mainly concerned that such sentence would be a loop hole for a lazy
server developer. "It's not returning a correct reply because it's
caching some data" is an easy reply for all bug reports. :)

> If I understand it correctly, then this would satisfy us both:
>=20
> 1. Use References.
> 2. Use In-Reply-To exactly as THREAD=3DREFERENCES does.

1. also "exactly as THREAD=3DREFERENCES does".

> 3. Don't use Subject.
> 4. Sort the threads by the thread's most recent internaldate.

Yes. I had thought about writing something like:

THREAD=3DREFERENCES2 changes THREAD=3DREFERENCES algorithm in two ways:

=EF=BB=BF1) Skip the step "(5) Gather together messages under the root that=
 have
the same base subject text".

2) Replace the step (4) sorting with the following algorithm:

Initialize each thread root's sort-date to non-existing. For each
(non-dummy) message get its INTERNALDATE and find its thread root. If
the thread root's sort-date is non-existing or the INTERNALDATE is
higher than sort-date, update sort-date to INTERNALDATE. Finally sort
all the thread roots by their sort-date. Because all threads have at
least one non-dummy message, there should be no non-existing sort-dates
left when sorting.

Doesn't really seem worth having a separate RFC for that, so if you can
change THREAD=3DREFS to do something similar that'd be great. :)

--=-iGeKC8sCQ9wIGuGCp3+W
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBIKVOpyUhSUUBViskRAlH6AJ0SC/qJAj4av41Hm/Q0nBYC2O8arQCgpi6K
5nD7uf6A0flT9FJoXAXJFqo=
=5eKj
-----END PGP SIGNATURE-----

--=-iGeKC8sCQ9wIGuGCp3+W--


--===============1239608910==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html

--===============1239608910==--



From morg-bounces@ietf.org  Tue May 13 01:47:06 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 86EFF3A6859;
	Tue, 13 May 2008 01:47:06 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 39F8C3A6859
	for <morg@core3.amsl.com>; Tue, 13 May 2008 01:47:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.8
X-Spam-Level: 
X-Spam-Status: No, score=-5.8 tagged_above=-999 required=5 tests=[AWL=0.799,
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PU2LfCkKCPvR for <morg@core3.amsl.com>;
	Tue, 13 May 2008 01:47:04 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id 5CEE93A67A5
	for <morg@ietf.org>; Tue, 13 May 2008 01:47:04 -0700 (PDT)
Received: from [192.168.10.2] (82-203-162-146.dsl.gohome.fi [82.203.162.146])
	by dovecot.org (Postfix) with ESMTP id 1DDD0FA8B35;
	Tue, 13 May 2008 11:45:48 +0300 (EEST)
From: Timo Sirainen <tss@iki.fi>
To: Arnt Gulbrandsen <arnt@oryx.com>
In-Reply-To: <oIEPsQEdUzK3jJzESbFg+Q.md5@lochnagar.oryx.com>
References: <1210654151.9518.539.camel@hurina>
	<M36GB7SjVS/ecjHThF/mug.md5@lochnagar.oryx.com>
	<oIEPsQEdUzK3jJzESbFg+Q.md5@lochnagar.oryx.com>
Date: Tue, 13 May 2008 11:45:47 +0300
Message-Id: <1210668347.9518.582.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.1 
Cc: morg@ietf.org
Subject: Re: [MORG] THREADROOT and THREADLEAF
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1237313883=="
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org


--===============1237313883==
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-1gb1ZWZZz44YqDy/Q2fW"


--=-1gb1ZWZZz44YqDy/Q2fW
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2008-05-13 at 10:19 +0200, Arnt Gulbrandsen wrote:
> Dave wanted THREADROOT and THREADLEAF, and I agree they make sense.=20
> However, I'm not sure they carry their load. How about these=20
> definitions?
>=20
> THREADROOT matches a message if none of the message's ancestors (as=20
> listed in References and In-Reply-To) exist in the current mailbox.
>=20
> THREADLEAF matches a message if no messages in this mailbox list its=20
> message-id in References or In-Reply-To.

I just realized that these don't specify the threading algorithm. I
don't think they're very useful with these kind of static definitions,
since THREAD command may give a completely different kind of a thread
tree.


--=-1gb1ZWZZz44YqDy/Q2fW
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBIKVU7yUhSUUBViskRAlArAJ9DJ9F6UCqFtf1pSxO2gWe8120vkQCggwKS
sxn/9n3w1Y0u7/Zy4CSgLfI=
=i9Gw
-----END PGP SIGNATURE-----

--=-1gb1ZWZZz44YqDy/Q2fW--


--===============1237313883==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html

--===============1237313883==--



From morg-bounces@ietf.org  Tue May 13 02:51:15 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 914643A6BFE;
	Tue, 13 May 2008 02:51:15 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 41F9B3A6859
	for <morg@core3.amsl.com>; Tue, 13 May 2008 02:51:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id E+Nk53l1ci4d for <morg@core3.amsl.com>;
	Tue, 13 May 2008 02:51:11 -0700 (PDT)
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by core3.amsl.com (Postfix) with ESMTP id 8F4EF3A6BFE
	for <morg@ietf.org>; Tue, 13 May 2008 02:51:10 -0700 (PDT)
Received: from kalyani.oryx.com (localhost.oryx.com [127.0.0.1])
	by kalyani.oryx.com (Postfix) with ESMTP id 1B9A54AC7E;
	Tue, 13 May 2008 11:50:13 +0200 (CEST)
Received: from 195.30.37.40 (HELO lochnagar.oryx.com) by kalyani.oryx.com with
	esmtp id 1210672212-37219-2135; Tue, 13 May 2008 11:50:12 +0200
Message-Id: <4B8yShJwEqCSYWhJt1E+Ng.md5@lochnagar.oryx.com>
Date: Tue, 13 May 2008 11:50:01 +0200
From: Arnt Gulbrandsen <arnt@oryx.com>
To: Timo Sirainen <tss@iki.fi>
References: <1210654151.9518.539.camel@hurina>
	<M36GB7SjVS/ecjHThF/mug.md5@lochnagar.oryx.com>
	<oIEPsQEdUzK3jJzESbFg+Q.md5@lochnagar.oryx.com>
	<1210668347.9518.582.camel@hurina>
In-Reply-To: <1210668347.9518.582.camel@hurina>
Mime-Version: 1.0
Cc: morg@ietf.org
Subject: Re: [MORG] THREADROOT and THREADLEAF
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

Timo Sirainen writes:
> I just realized that these don't specify the threading algorithm. I 
> don't think they're very useful with these kind of static 
> definitions, since THREAD command may give a completely different 
> kind of a thread tree.

Indeed. But how do you specify THREADLEAF in orderedsubject?

Arnt
_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html


From morg-bounces@ietf.org  Tue May 13 03:28:57 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2079828C260;
	Tue, 13 May 2008 03:28:57 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 604BE28C260
	for <morg@core3.amsl.com>; Tue, 13 May 2008 03:28:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.066
X-Spam-Level: 
X-Spam-Status: No, score=-6.066 tagged_above=-999 required=5 tests=[AWL=0.533, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vExjkJxuIqup for <morg@core3.amsl.com>;
	Tue, 13 May 2008 03:28:53 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id 86F433A67A5
	for <morg@ietf.org>; Tue, 13 May 2008 03:28:53 -0700 (PDT)
Received: from [192.168.10.200] (82-203-162-146.dsl.gohome.fi [82.203.162.146])
	by dovecot.org (Postfix) with ESMTP id 0AC3F16471E3;
	Tue, 13 May 2008 13:27:18 +0300 (EEST)
Message-Id: <B74CD463-6F4B-44C2-AF4C-CAFE87E36BB1@iki.fi>
From: Timo Sirainen <tss@iki.fi>
To: Arnt Gulbrandsen <arnt@oryx.com>
In-Reply-To: <4B8yShJwEqCSYWhJt1E+Ng.md5@lochnagar.oryx.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 13 May 2008 13:27:13 +0300
References: <1210654151.9518.539.camel@hurina>
	<M36GB7SjVS/ecjHThF/mug.md5@lochnagar.oryx.com>
	<oIEPsQEdUzK3jJzESbFg+Q.md5@lochnagar.oryx.com>
	<1210668347.9518.582.camel@hurina>
	<4B8yShJwEqCSYWhJt1E+Ng.md5@lochnagar.oryx.com>
X-Pgp-Agent: GPGMail d51 (Leopard)
X-Mailer: Apple Mail (2.919.2)
Cc: morg@ietf.org
Subject: Re: [MORG] THREADROOT and THREADLEAF
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0453993274=="
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0453993274==
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-29-438999499"
Content-Transfer-Encoding: 7bit

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--Apple-Mail-29-438999499
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit

On May 13, 2008, at 12:50 PM, Arnt Gulbrandsen wrote:

> Timo Sirainen writes:
>> I just realized that these don't specify the threading algorithm. I  
>> don't think they're very useful with these kind of static  
>> definitions, since THREAD command may give a completely different  
>> kind of a thread tree.
>
> Indeed. But how do you specify THREADLEAF in orderedsubject?


Each thread has one root and the rest are leaves :) But I was more  
thinking about REFERENCES vs. REFERENCES2.


--Apple-Mail-29-438999499
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkgpbQEACgkQyUhSUUBVisk0xwCgm7mAZKz0526FA+/5bLV8pi3c
MagAoKSpc/eXYLljaYhz8Tv1Zh4/uzhC
=sBfu
-----END PGP SIGNATURE-----

--Apple-Mail-29-438999499--

--===============0453993274==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html

--===============0453993274==--


From morg-bounces@ietf.org  Tue May 13 03:46:13 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 805323A6B75;
	Tue, 13 May 2008 03:46:13 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E4C143A6B75
	for <morg@core3.amsl.com>; Tue, 13 May 2008 03:46:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level: 
X-Spam-Status: No, score=-2.199 tagged_above=-999 required=5
	tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_64=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9TSalubnZU5o for <morg@core3.amsl.com>;
	Tue, 13 May 2008 03:46:11 -0700 (PDT)
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by core3.amsl.com (Postfix) with ESMTP id BFC853A67A1
	for <morg@ietf.org>; Tue, 13 May 2008 03:46:10 -0700 (PDT)
Received: from kalyani.oryx.com (localhost.oryx.com [127.0.0.1])
	by kalyani.oryx.com (Postfix) with ESMTP id 740A04AC87;
	Tue, 13 May 2008 12:45:02 +0200 (CEST)
Received: from 195.30.37.40 (HELO lochnagar.oryx.com) by kalyani.oryx.com with
	esmtp id 1210675502-37219-2162; Tue, 13 May 2008 12:45:02 +0200
Message-Id: <LlUhDnH6JIquIZhjaQW39w.md5@lochnagar.oryx.com>
Date: Tue, 13 May 2008 12:44:50 +0200
From: Arnt Gulbrandsen <arnt@oryx.com>
To: Timo Sirainen <tss@iki.fi>
References: <1210654151.9518.539.camel@hurina>
	<M36GB7SjVS/ecjHThF/mug.md5@lochnagar.oryx.com>
	<1210667945.9518.576.camel@hurina>
In-Reply-To: <1210667945.9518.576.camel@hurina>
Mime-Version: 1.0
Cc: morg@ietf.org
Subject: Re: [MORG] SEARCH=INTHREAD
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

Timo Sirainen writes:
> On Tue, 2008-05-13 at 10:09 +0200, Arnt Gulbrandsen wrote:
>> I'd like to have only one of THREAD=REFS and THREAD=REFERENCES2, so 
>> if we can find a way to make one serve both of our needs, that would 
>> make me happy.
>
> That would be better, yes. I also don't care if it's called REFS or 
> REFERENCES2.

Btw. I care at least a little. I don't like the name THREAD=REFS and 
actively dislike the name THREAD=REFERENCES2. T=R2 reminds me of the 
Windows API, which has many such names. For example, CreateWindow() 
takes maybe a dozen arguments, but they forgot one, so they added 
CreateWindowEx() with n+1. IMNSHO a function with a dozen arguments has 
a problem, but it's not that it lacks a thirteenth.

I know it's irrational and not at all related to IMAP, but I hope you 
forgive me for hating anything that reminds me of that %@#!$@#$!#$#!$.

Arnt
_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html


From morg-bounces@ietf.org  Tue May 13 03:50:58 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C78053A6BE5;
	Tue, 13 May 2008 03:50:58 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 470CB3A6BF3
	for <morg@core3.amsl.com>; Tue, 13 May 2008 03:50:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.2
X-Spam-Level: 
X-Spam-Status: No, score=-6.2 tagged_above=-999 required=5 tests=[AWL=0.400,
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id k0kqomSc0mjO for <morg@core3.amsl.com>;
	Tue, 13 May 2008 03:50:56 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id 714833A67A1
	for <morg@ietf.org>; Tue, 13 May 2008 03:50:56 -0700 (PDT)
Received: from [192.168.10.200] (82-203-162-146.dsl.gohome.fi [82.203.162.146])
	by dovecot.org (Postfix) with ESMTP id 6E084FA895A;
	Tue, 13 May 2008 13:49:00 +0300 (EEST)
Message-Id: <66300821-2E31-40E8-A607-E74FB5DB8102@iki.fi>
From: Timo Sirainen <tss@iki.fi>
To: Arnt Gulbrandsen <arnt@oryx.com>
In-Reply-To: <Y6HHn2n080KFJZpFEzcyGw.md5@lochnagar.oryx.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 13 May 2008 13:48:59 +0300
References: <1210654151.9518.539.camel@hurina>
	<M36GB7SjVS/ecjHThF/mug.md5@lochnagar.oryx.com>
	<oIEPsQEdUzK3jJzESbFg+Q.md5@lochnagar.oryx.com>
	<1210668347.9518.582.camel@hurina>
	<4B8yShJwEqCSYWhJt1E+Ng.md5@lochnagar.oryx.com>
	<B74CD463-6F4B-44C2-AF4C-CAFE87E36BB1@iki.fi>
	<Y6HHn2n080KFJZpFEzcyGw.md5@lochnagar.oryx.com>
X-Pgp-Agent: GPGMail d51 (Leopard)
X-Mailer: Apple Mail (2.919.2)
Cc: morg@ietf.org
Subject: Re: [MORG] THREADROOT and THREADLEAF
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0344092685=="
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0344092685==
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-30-440305625"
Content-Transfer-Encoding: 7bit

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--Apple-Mail-30-440305625
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit

On May 13, 2008, at 1:32 PM, Arnt Gulbrandsen wrote:

> Timo Sirainen writes:
>> Each thread has one root and the rest are leaves :)
>
> I thought it would be more likely that the thread has one root and  
> one leaf, and the rest are intermediate nodes.

Oh, could be. I've never implemented orderedsubject so I don't  
remember if it was (1 2 3) or (1 (2)(3)). Anyway I don't think it  
should be a special case. It's already defined what the reply thread  
tree looks like, so THREADLEAF lists the leaves from the returned tree.


--Apple-Mail-30-440305625
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkgpchsACgkQyUhSUUBVislzdACghPtn7rdL55yHwRxA+t5eBI0M
8eAAnjBn7pyvIl111/SL85QrjBoCMDCl
=2MgQ
-----END PGP SIGNATURE-----

--Apple-Mail-30-440305625--

--===============0344092685==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html

--===============0344092685==--


From morg-bounces@ietf.org  Tue May 13 09:41:55 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DA6D23A68D5;
	Tue, 13 May 2008 09:41:55 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A09B73A68D5
	for <morg@core3.amsl.com>; Tue, 13 May 2008 09:41:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LhiGVU5-VOZB for <morg@core3.amsl.com>;
	Tue, 13 May 2008 09:41:53 -0700 (PDT)
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by core3.amsl.com (Postfix) with ESMTP id 9AB003A67D4
	for <morg@ietf.org>; Tue, 13 May 2008 09:41:52 -0700 (PDT)
Received: from kalyani.oryx.com (localhost.oryx.com [127.0.0.1])
	by kalyani.oryx.com (Postfix) with ESMTP id D7C1B4AC7E;
	Tue, 13 May 2008 12:32:42 +0200 (CEST)
Received: from 195.30.37.40 (HELO lochnagar.oryx.com) by kalyani.oryx.com with
	esmtp id 1210674762-37219-2161; Tue, 13 May 2008 12:32:42 +0200
Message-Id: <Y6HHn2n080KFJZpFEzcyGw.md5@lochnagar.oryx.com>
Date: Tue, 13 May 2008 12:32:31 +0200
From: Arnt Gulbrandsen <arnt@oryx.com>
To: Timo Sirainen <tss@iki.fi>
References: <1210654151.9518.539.camel@hurina>
	<M36GB7SjVS/ecjHThF/mug.md5@lochnagar.oryx.com>
	<oIEPsQEdUzK3jJzESbFg+Q.md5@lochnagar.oryx.com>
	<1210668347.9518.582.camel@hurina>
	<4B8yShJwEqCSYWhJt1E+Ng.md5@lochnagar.oryx.com>
	<B74CD463-6F4B-44C2-AF4C-CAFE87E36BB1@iki.fi>
In-Reply-To: <B74CD463-6F4B-44C2-AF4C-CAFE87E36BB1@iki.fi>
Mime-Version: 1.0
Cc: morg@ietf.org
Subject: Re: [MORG] THREADROOT and THREADLEAF
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

Timo Sirainen writes:
> Each thread has one root and the rest are leaves :)

I thought it would be more likely that the thread has one root and one 
leaf, and the rest are intermediate nodes.

> But I was more   thinking about REFERENCES vs. REFERENCES2.

Yes, the useful stuff is simple, it's specifying the thing so rest isn't 
damaging that's difficult.

Arnt
_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html


From morg-bounces@ietf.org  Tue May 13 09:42:19 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0EA493A6C54;
	Tue, 13 May 2008 09:42:19 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5093F3A6C4D
	for <morg@core3.amsl.com>; Tue, 13 May 2008 09:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.179
X-Spam-Level: 
X-Spam-Status: No, score=-2.179 tagged_above=-999 required=5
	tests=[AWL=-0.180, BAYES_00=-2.599, J_CHICKENPOX_64=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id mNwNnBoKnQph for <morg@core3.amsl.com>;
	Tue, 13 May 2008 09:42:16 -0700 (PDT)
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by core3.amsl.com (Postfix) with ESMTP id 5493A3A67D4
	for <morg@ietf.org>; Tue, 13 May 2008 09:42:16 -0700 (PDT)
Received: from kalyani.oryx.com (localhost.oryx.com [127.0.0.1])
	by kalyani.oryx.com (Postfix) with ESMTP id AC5184AC7D;
	Tue, 13 May 2008 12:30:58 +0200 (CEST)
Received: from 195.30.37.40 (HELO lochnagar.oryx.com) by kalyani.oryx.com with
	esmtp id 1210674658-37219-2160; Tue, 13 May 2008 12:30:58 +0200
Message-Id: <U0BmkDP1qzNSVH/D+yWTow.md5@lochnagar.oryx.com>
Date: Tue, 13 May 2008 12:30:47 +0200
From: Arnt Gulbrandsen <arnt@oryx.com>
To: Timo Sirainen <tss@iki.fi>
References: <1210654151.9518.539.camel@hurina>
	<M36GB7SjVS/ecjHThF/mug.md5@lochnagar.oryx.com>
	<1210667945.9518.576.camel@hurina>
In-Reply-To: <1210667945.9518.576.camel@hurina>
Mime-Version: 1.0
Cc: morg@ietf.org
Subject: Re: [MORG] SEARCH=INTHREAD
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

Timo Sirainen writes:
> Maybe in case of a dummy root return all its children as roots? 
> Probably more useful than not returning them at all.

Depends on the use.

> I can think of a couple of use cases for THREADROOT, but is THREADLEAF 
> actually useful for something? But I guess it would be simple enough 
> for me to implement, so I don't mind that much.

Dave?

THREADLEAF is basically "messages to which noone has replied", which 
seems interesting, but not necessarily worth standardising.

> Doesn't really seem worth having a separate RFC for that, so if you 
> can change THREAD=REFS to do something similar that'd be great. :)

Will do.

Arnt
_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html


From morg-bounces@ietf.org  Wed May 14 19:00:13 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ED9473A6943;
	Wed, 14 May 2008 19:00:12 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BAB543A682C
	for <morg@core3.amsl.com>; Wed, 14 May 2008 19:00:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.979
X-Spam-Level: 
X-Spam-Status: No, score=-5.979 tagged_above=-999 required=5 tests=[AWL=0.020, 
	BAYES_00=-2.599, J_CHICKENPOX_64=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4NEWrYbPMfvA for <morg@core3.amsl.com>;
	Wed, 14 May 2008 19:00:09 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id A2F913A692A
	for <morg@ietf.org>; Wed, 14 May 2008 19:00:09 -0700 (PDT)
Received: from [192.168.10.200] (82-203-162-146.dsl.gohome.fi [82.203.162.146])
	by dovecot.org (Postfix) with ESMTP id 1AD5916471EF;
	Thu, 15 May 2008 04:59:37 +0300 (EEST)
Message-Id: <C3FA8A64-102C-46F2-A1B4-D4EB3C60DD9F@iki.fi>
From: Timo Sirainen <tss@iki.fi>
To: Arnt Gulbrandsen <arnt@oryx.com>
In-Reply-To: <LlUhDnH6JIquIZhjaQW39w.md5@lochnagar.oryx.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Thu, 15 May 2008 04:59:31 +0300
References: <1210654151.9518.539.camel@hurina>
	<M36GB7SjVS/ecjHThF/mug.md5@lochnagar.oryx.com>
	<1210667945.9518.576.camel@hurina>
	<LlUhDnH6JIquIZhjaQW39w.md5@lochnagar.oryx.com>
X-Pgp-Agent: GPGMail d51 (Leopard)
X-Mailer: Apple Mail (2.919.2)
Cc: morg@ietf.org
Subject: Re: [MORG] SEARCH=INTHREAD
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1495534730=="
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1495534730==
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-34-581338131"
Content-Transfer-Encoding: 7bit

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--Apple-Mail-34-581338131
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit

On May 13, 2008, at 1:44 PM, Arnt Gulbrandsen wrote:

> Timo Sirainen writes:
>> On Tue, 2008-05-13 at 10:09 +0200, Arnt Gulbrandsen wrote:
>>> I'd like to have only one of THREAD=REFS and THREAD=REFERENCES2,  
>>> so if we can find a way to make one serve both of our needs, that  
>>> would make me happy.
>>
>> That would be better, yes. I also don't care if it's called REFS or  
>> REFERENCES2.
>
> Btw. I care at least a little. I don't like the name THREAD=REFS and  
> actively dislike the name THREAD=REFERENCES2.

THREAD=REFSONLY maybe?

BTW. Why don't I see your messages in morg list even though it's Ccd?


--Apple-Mail-34-581338131
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkgrmQQACgkQyUhSUUBVislrCACePkdUOtn4TJKrri+01zQWd/0b
tAQAniRzrGHCvrkuoaSa9IaWMxo7SqdO
=f6rV
-----END PGP SIGNATURE-----

--Apple-Mail-34-581338131--

--===============1495534730==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html

--===============1495534730==--


From morg-bounces@ietf.org  Wed May 14 19:11:13 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 21DDE3A69FD;
	Wed, 14 May 2008 19:11:09 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3E6C53A684D
	for <morg@core3.amsl.com>; Wed, 14 May 2008 19:09:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.283
X-Spam-Level: 
X-Spam-Status: No, score=-6.283 tagged_above=-999 required=5 tests=[AWL=0.316, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id immqF6gkFBOc for <morg@core3.amsl.com>;
	Wed, 14 May 2008 19:09:14 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id 081843A682C
	for <morg@ietf.org>; Wed, 14 May 2008 19:09:10 -0700 (PDT)
Received: from [192.168.10.2] (82-203-162-146.dsl.gohome.fi [82.203.162.146])
	by dovecot.org (Postfix) with ESMTP id 38C5C16471EF
	for <morg@ietf.org>; Thu, 15 May 2008 05:08:39 +0300 (EEST)
From: Timo Sirainen <tss@iki.fi>
To: morg@ietf.org
In-Reply-To: <C3FA8A64-102C-46F2-A1B4-D4EB3C60DD9F@iki.fi>
References: <1210654151.9518.539.camel@hurina>
	<M36GB7SjVS/ecjHThF/mug.md5@lochnagar.oryx.com>
	<1210667945.9518.576.camel@hurina>
	<LlUhDnH6JIquIZhjaQW39w.md5@lochnagar.oryx.com>
	<C3FA8A64-102C-46F2-A1B4-D4EB3C60DD9F@iki.fi>
Date: Thu, 15 May 2008 05:08:38 +0300
Message-Id: <1210817318.9518.595.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.1 
Subject: Re: [MORG] SEARCH=INTHREAD
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1758196032=="
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org


--===============1758196032==
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-9SE3RlwVo1HgCTlieC1i"


--=-9SE3RlwVo1HgCTlieC1i
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Thu, 2008-05-15 at 04:59 +0300, Timo Sirainen wrote:
> BTW. Why don't I see your messages in morg list even though it's Ccd?

Oh, duplicate suppression is enabled by default. I hate that feature.


--=-9SE3RlwVo1HgCTlieC1i
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBIK5smyUhSUUBViskRApEQAJ0dX1nnG8twAA1UGa/5VL2iaP2PVwCfYa79
WDbDO0fYXMtTW0/r4DgqoOs=
=+1Pm
-----END PGP SIGNATURE-----

--=-9SE3RlwVo1HgCTlieC1i--


--===============1758196032==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html

--===============1758196032==--



