Received: from balder-227.proper.com (localhost [127.0.0.1])
 by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3LBLqsG092810;
 Fri, 21 Apr 2006 04:21:52 -0700 (MST)
 (envelope-from owner-ietf-mta-filters@mail.imc.org)
Received: (from majordom@localhost)
 by balder-227.proper.com (8.13.5/8.13.5/Submit) id k3LBLq3W092809;
 Fri, 21 Apr 2006 04:21:52 -0700 (MST)
 (envelope-from owner-ietf-mta-filters@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to
 owner-ietf-mta-filters@mail.imc.org using -f
Received: from mail.rockliffe.com (mail.rockliffe.com [147.208.128.10])
 by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3LBLqbh092800
 for <ietf-mta-filters@imc.org>; Fri, 21 Apr 2006 04:21:52 -0700 (MST)
 (envelope-from Nigel.Swinson@rockliffe.com)
X-Spam-Score: 1
Received: from nigelhome (unverified [10.42.40.204]) by mail.rockliffe.com
 (Rockliffe SMTPRA 7.0.3) with ESMTP id <B0003263640@mail.rockliffe.com> for
 <ietf-mta-filters@imc.org>; Fri, 21 Apr 2006 04:21:42 -0700
Message-ID: <003401c66535$cf86ae20$6401a8c0@nigelhome>
From: "Nigel Swinson" <Nigel.Swinson@rockliffe.com>
To: <ietf-mta-filters@imc.org>
Subject: Default match types and for_every_part
Date: Fri, 21 Apr 2006 12:21:59 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="----=_NextPart_000_0031_01C6653E.300E0240"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1807
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
Sender: owner-ietf-mta-filters@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-mta-filters/mail-archive/>
List-ID: <ietf-mta-filters.imc.org>
List-Unsubscribe: <mailto:ietf-mta-filters-request@imc.org?body=unsubscribe>


This is a multi-part message in MIME format.

------=_NextPart_000_0031_01C6653E.300E0240
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

http://www.ietf.org/internet-drafts/draft-ietf-sieve-3028bis-06.txt

In 2.7.1, buried in a long paragraph, it says "Commands default to using =
":is" matching if no match type argument is supplied".  In 5.7 when =
discussing the header test it explicitly says that the default match =
type for the header test is "is", but in 5.1, and 5.4 when discussing =
envelope and address tests there is no mention.  I found this to be =
inconsistent and initially assumed that the default match type for =
address/envelope was unspecified. =20

I suggest we remove the reference to the default match type from section =
5.7, and split the "long" paragraph in 2.7.1 at the "Note" that =
discusses interactions with comparators.

While you are at it, you might want to correct the "supoprt" typo.

http://www.ietf.org/internet-drafts/draft-ietf-sieve-body-03.txt

I think it makes no sense for the default match type to be :is for the =
body test, could it be :contains, and could say so in section 3?  Or do =
people think it is easier for the default match type to always be :is?

http://www.ietf.org/internet-drafts/draft-ietf-sieve-mime-loop-00.txt

I think it should be foreverypart, not for_every_part.  We already have =
addheader, deleteheader, fileinto.  We don't have add_header, =
delete_header, file_into.

Nigel
------=_NextPart_000_0031_01C6653E.300E0240
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1252"><BASE=20
href=3Dfile://E:\Nigel\>
<STYLE>DIV {
	FONT-SIZE: 10pt; FONT-FAMILY: vernada, sans-serif
}
P {
	FONT-SIZE: 10pt; FONT-FAMILY: vernada, sans-serif
}
 {
	FONT-SIZE: 10pt; FONT-FAMILY: vernada, sans-serif
}
LI {
	FONT-SIZE: 10pt; FONT-FAMILY: vernada, sans-serif
}
H1 {
	COLOR: #a11100
}
H2 {
	COLOR: #336600
}
H3 {
	COLOR: #003366
}
TH {
	COLOR: #003366
}
.note {
	MARGIN-LEFT: 20px; COLOR: #000000; MARGIN-RIGHT: 20px; =
BACKGROUND-COLOR: #cccccc
}
STRONG {
	COLOR: #a11100
}
</STYLE>

<META content=3D"MSHTML 6.00.2800.1543" name=3DGENERATOR></HEAD>
<BODY bgColor=3D#ffffff>
<DIV><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-sieve-3028bis-06.t=
xt">http://www.ietf.org/internet-drafts/draft-ietf-sieve-3028bis-06.txt</=
A></DIV>
<DIV>&nbsp;</DIV>
<DIV>In 2.7.1, buried in a long paragraph,&nbsp;it says "Commands =
default to=20
using ":is" matching if no match type argument is supplied".&nbsp; In =
5.7 when=20
discussing the header test it explicitly says that the default match =
type for=20
the header test is "is", but in 5.1, and 5.4 when discussing envelope =
and=20
address tests there is no mention.&nbsp; I found this to be inconsistent =
and=20
initially assumed that the default match type for address/envelope was=20
unspecified.&nbsp; </DIV>
<DIV>&nbsp;</DIV>
<DIV>I suggest we remove the reference to the default match type from =
section=20
5.7, and split the "long" paragraph in 2.7.1 at the "Note" that =
discusses=20
interactions with comparators.</DIV>
<DIV>&nbsp;</DIV>
<DIV>While you are at it, you might want to correct the "supoprt" =
typo.</DIV>
<DIV>&nbsp;</DIV>
<DIV><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-sieve-body-03.txt"=
>http://www.ietf.org/internet-drafts/draft-ietf-sieve-body-03.txt</A></DI=
V>
<DIV>&nbsp;</DIV>
<DIV>I think it makes no sense for the default match type to be :is for =
the body=20
test, could it be :contains, and&nbsp;could say so in section 3?&nbsp; =
Or do=20
people think it is easier for the default match type to always be =
:is?</DIV>
<DIV>&nbsp;</DIV>
<DIV><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-sieve-mime-loop-00=
.txt">http://www.ietf.org/internet-drafts/draft-ietf-sieve-mime-loop-00.t=
xt</A></DIV>
<DIV>&nbsp;</DIV>
<DIV>I think it should be foreverypart, not for_every_part.&nbsp; We =
already=20
have addheader, deleteheader, fileinto.&nbsp; We don't have add_header,=20
delete_header, file_into.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Nigel</DIV></BODY></HTML>

------=_NextPart_000_0031_01C6653E.300E0240--

