From owner-ietf-mta-filters Thu Feb  1 12:16:46 2007
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 l11JGkS1025733
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 1 Feb 2007 12:16:46 -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 l11JGkM3025732;
	Thu, 1 Feb 2007 12:16:46 -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 rufus.isode.com (rufus.isode.com [62.3.217.251])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l11JGjcv025726
	for <ietf-mta-filters@imc.org>; Thu, 1 Feb 2007 12:16:46 -0700 (MST)
	(envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) 
          by rufus.isode.com (submission channel) via TCP with ESMTPA 
          id <RcI8nABXDi1z@rufus.isode.com>; Thu, 1 Feb 2007 19:16:44 +0000
Message-ID: <45C23C87.6040501@isode.com>
Date: Thu, 01 Feb 2007 19:16:23 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
            Gecko/20050915
X-Accept-Language: en-us, en
To: ietf-mta-filters@imc.org
Subject: Re: Results of the Working Group Last Call on
         draft-ietf-sieve-notify-05.txt
References: <45AFDB20.2030703@isode.com> <45AFE9DE.6040005@isode.com> <45BB8AC8.1000600@isode.com>
In-Reply-To: <45BB8AC8.1000600@isode.com>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>


Hi folks,
Quick summary of comments received so far below:

Alexey Melnikov wrote:

> Alexey Melnikov wrote:
>
>>> Issue #3:
>>>
>>> :subject versa :message. Aaron, Dilyan in favor of adding :subject. 
>>> Michael wants to keep using :message.
>>
> I need to poll people on this, as I don't hear a clear consensus on 
> this. Please pick one of the following:
>
> 1). keep the existing :message (it may or may not map to email 
> Subject:, this is a separate issue at this point)
> 2). rename existing :message to :subject
> 3). I don't care whether we have :message or :subject, but we should 
> have only one of them.
> 4). notify should have both :message and :subject
>
> Let me know your opinion or if I've missed some choice.

My reading of the rough consensus so far is to keep :message (no change 
to the draft).

>>> Issue #4:
>>>
>>> Dilyan suggested to add "expiration" parameter/option to the notify 
>>> action. While I see some utility in this option, I am reluctant to 
>>> extend the document so late in the game, unless there is strong 
>>> support from the WG. I would recommend to add this option in a 
>>> separate document. Opinions?
>>
> I've heard a couple of voices for this feature, but no rough consensus 
> yet.
>
> Hint for people who want this functionality: please provide some text 
> for inclusion into the document. This will improve your chances of 
> winning the argument ;-).

Even though specific text was suggested for inclusion, my reading of the 
rough consensus is that there is no support for adding this feature to 
the base Sieve notify document.

>>> Issue #5:
>>>
>>> Ken (in a private message) has suggested to extend "body" test 
>>> instead of introducing a new "extract_text" test. Opinions?
>>
> In order to make some progress on this issue, here is how the updated 
> body test can look like:

It sounds like people would prefer to extend the body test, rather than 
introducing a new action.
However people are not entirely sure about the new syntax I've suggested.

I think there is agreement to move this part of the document somewhere 
else, like Sieve MIME loops. So the WG should continue discussing the 
best syntax for this test or action, but this open issue is not blocking 
publication of the Sieve notify document.

>   "body" [COMPARATOR] [MATCH-TYPE] [BODY-TRANSFORM] [BODY-EXTRACT]
>                <key-list: string-list>
>
> where BODY-TRANSFORM is defined as (section 4 of 
> draft-ietf-sieve-body-05.txt):
>
>          ":raw"
>        / ":content" <content-types: string-list>
>        / ":text"
>
> I've added BODY-EXTRACT:
>
>    :extract_none /
>    :extract_whole /
>    :extract_first number
>
> :extract_none is the default, i.e. if the variables extension is 
> present, then the match variables ${1}, ${2}, ... are not set as a 
> side effect of successful matching;
> :extract_first will truncate the current body part after <number> 
> bytes and will set the match variables.
> :extract_whole will set the match variable, without performing any 
> truncation.
>
>>> Issue #6:
>>>
>>> Arnt wants to be able to do "send notification over XMPP, if can be 
>>> delivered immediately. Otherwise send it over SMS".
>>> This issue needs further discussion.
>>
> Aaron replied that he likes the idea. Anybody else?
>
> Arnt has suggested that the notify action should take multiple :method 
> parameters. As tagged parameters can't be specified multiple times in 
> the same test (3028bis, section 2.6), this will mean changing the 
> :method parameter to be a string list.
>
> Other alternative are:
> 1). Add a test to check if a notification method (specified as an URI) 
> can deliver the notification immediately.
> IMHO, I like this a bit better than Arnt's proposal, as it is easier 
> to implement and the resulting script is going to be easier to read.

Consensus seems to be to go with option #1.

> 2). Keep the existing syntax. A new "stackable" notification method 
> can be specified that will perform the desired functionality.
>
> Opinions?
> =======
> + A new issues (# 8): the Sieve notify document needs to describe what 
> should happen if a parameter specified in two ways in the same notify 
> call: as a notify action parameter and as an URI parameter to the 
> method parameter, for example:
>
>        notify :method "xmpp:tim@example.com?message;subject=SIEVE" 
> :message "You got mail";
>
> (assume for a moment that the content of the :message gets translated 
> into the subject of the resulting notification)
>
> Options suggested so far:
> 1). URI parameters are always ignored
> 2). URI parameters (if any) override the corresponding notify parameters
> 3). the notify parameters override the corresponding URI parameters
> 4). specify both the notify and the URI parameters is an error.

I don't see any consensus on this issue so far. More discussion/opinions 
needed.

> Opinions?



From owner-ietf-mta-filters Thu Feb  1 13:50:04 2007
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 l11Ko4oa032752
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 1 Feb 2007 13:50:04 -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 l11Ko4N1032751;
	Thu, 1 Feb 2007 13:50:04 -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 ns3.neustar.com (ns3.neustar.com [156.154.24.138])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l11Ko39G032745
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-mta-filters@imc.org>; Thu, 1 Feb 2007 13:50:03 -0700 (MST)
	(envelope-from ietf@ietf.org)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10])
	by ns3.neustar.com (Postfix) with ESMTP id 91DB717642;
	Thu,  1 Feb 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HCisc-00084w-5o; Thu, 01 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: ietf-mta-filters@imc.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-sieve-notify-06.txt 
Message-Id: <E1HCisc-00084w-5o@stiedprstage1.ietf.org>
Date: Thu, 01 Feb 2007 15:50:02 -0500
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>


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

	Title		: Sieve Extension: Notifications
	Author(s)	: A. Melnikov, et al.
	Filename	: draft-ietf-sieve-notify-06.txt
	Pages		: 18
	Date		: 2007-2-1
	
Users go to great lengths to be notified as quickly as possible that
   they have received new mail.  Most of these methods involve polling
   to check for new messages periodically.  A push method handled by the
   final delivery agent gives users quicker notifications and saves
   server resources.  This document does not specify the notification
   method but it is expected that using existing instant messaging
   infrastructure such as XMPP, or SMS messages will be popular.  This
   draft describes an extension to the Sieve mail filtering language
   that allows users to give specific rules for how and when
   notifications should be sent.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-notify-06.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sieve-notify-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sieve-notify-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2007-2-1112040.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sieve-notify-06.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sieve-notify-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2007-2-1112040.I-D@ietf.org>

--OtherAccess--

--NextPart--


From owner-ietf-mta-filters Fri Feb  2 13:50:05 2007
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 l12Ko5dY048602
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 2 Feb 2007 13:50:05 -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 l12Ko52q048601;
	Fri, 2 Feb 2007 13:50:05 -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 ns1.neustar.com (ns1.neustar.com [156.154.16.138])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l12Ko4Nj048595
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-mta-filters@imc.org>; Fri, 2 Feb 2007 13:50:05 -0700 (MST)
	(envelope-from ietf@ietf.org)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10])
	by ns1.neustar.com (Postfix) with ESMTP id A20D826ECD;
	Fri,  2 Feb 2007 20:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HD5MA-0002NU-7M; Fri, 02 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: ietf-mta-filters@imc.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-sieve-3028bis-10.txt 
Message-Id: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org>
Date: Fri, 02 Feb 2007 15:50:02 -0500
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>


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

	Title		: Sieve: An Email Filtering Language
	Author(s)	: T. Showalter, P. Guenther
	Filename	: draft-ietf-sieve-3028bis-10.txt
	Pages		: 44
	Date		: 2007-2-2
	
This document describes a language for filtering email messages at
   time of final delivery.  It is designed to be implementable on either
   a mail client or mail server.  It is meant to be extensible, simple,
   and independent of access protocol, mail architecture, and operating
   system.  It is suitable for running on a mail server where users may
   not be allowed to execute arbitrary programs, such as on black box
   Internet Message Access Protocol (IMAP) servers, as the base language
   has no variables, loops, or ability to shell out to external
   programs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-3028bis-10.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sieve-3028bis-10.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sieve-3028bis-10.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2007-2-2140105.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sieve-3028bis-10.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sieve-3028bis-10.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2007-2-2140105.I-D@ietf.org>

--OtherAccess--

--NextPart--


From owner-ietf-mta-filters Fri Feb  2 13:50:04 2007
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 l12Ko3Qv048593
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 2 Feb 2007 13:50:03 -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 l12Ko37n048592;
	Fri, 2 Feb 2007 13:50:03 -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 ns3.neustar.com (ns3.neustar.com [156.154.24.138])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l12Ko3Iw048583
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-mta-filters@imc.org>; Fri, 2 Feb 2007 13:50:03 -0700 (MST)
	(envelope-from ietf@ietf.org)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10])
	by ns3.neustar.com (Postfix) with ESMTP id 7EB0917677;
	Fri,  2 Feb 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HD5MA-0002NF-3Z; Fri, 02 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: ietf-mta-filters@imc.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-sieve-notify-xmpp-03.txt 
Message-Id: <E1HD5MA-0002NF-3Z@stiedprstage1.ietf.org>
Date: Fri, 02 Feb 2007 15:50:02 -0500
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>


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

	Title		: Sieve Notification Mechanism: xmpp
	Author(s)	: P. Saint-Andre, A. Melnikov
	Filename	: draft-ietf-sieve-notify-xmpp-03.txt
	Pages		: 8
	Date		: 2007-2-2
	
This document describes a profile of the Sieve extension for
   notifications, to allow notifications to be sent over the Extensible
   Messaging and Presence Protocol (XMPP), also known as Jabber.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-notify-xmpp-03.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sieve-notify-xmpp-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sieve-notify-xmpp-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2007-2-2135255.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sieve-notify-xmpp-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sieve-notify-xmpp-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2007-2-2135255.I-D@ietf.org>

--OtherAccess--

--NextPart--


From owner-ietf-mta-filters Sun Feb  4 06:16:57 2007
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 l14DGvH4000983
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sun, 4 Feb 2007 06:16:57 -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 l14DGvtE000982;
	Sun, 4 Feb 2007 06:16:57 -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 kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l14DGtca000976
	for <ietf-mta-filters@imc.org>; Sun, 4 Feb 2007 06:16:56 -0700 (MST)
	(envelope-from arnt@oryx.com)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9])
	by kalyani.oryx.com (Postfix) with ESMTP id 82B734ACB2;
	Sun,  4 Feb 2007 14:16:55 +0100 (CET)
Message-Id: <Eenws6h6ux1twUVVTZyVtw.md5@libertango.oryx.com>
Date: Sun, 4 Feb 2007 14:17:21 +0100
From: Arnt Gulbrandsen <arnt@oryx.com>
To: ietf-mta-filters@imc.org
Subject: Re: Results of the Working Group Last Call on
  draft-ietf-sieve-notify-05.txt
Cc: Alexey Melnikov <alexey.melnikov@isode.com>
References: <45AFDB20.2030703@isode.com> <45AFE9DE.6040005@isode.com>
  <45BB8AC8.1000600@isode.com> <45C23C87.6040501@isode.com>
In-Reply-To: <45C23C87.6040501@isode.com>
Content-Type: text/plain; format=flowed
MIME-Version: 1.0
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>


Alexey Melnikov writes:
> Alexey Melnikov wrote:
>> Alexey Melnikov wrote:
>>>> Issue #6:
>>>>
>>>> Arnt wants to be able to do "send notification over XMPP, if can be 
>>>> delivered immediately. Otherwise send it over SMS".
>>>> This issue needs further discussion.
>>
>> Aaron replied that he likes the idea. Anybody else?
>>
>> Arnt has suggested that the notify action should take multiple 
>> :method parameters. As tagged parameters can't be specified multiple 
>> times in the same test (3028bis, section 2.6), this will mean 
>> changing the :method parameter to be a string list.
>>
>> Other alternative are:
>> 1). Add a test to check if a notification method (specified as an 
>> URI) can deliver the notification immediately.
>> IMHO, I like this a bit better than Arnt's proposal, as it is easier 
>> to implement and the resulting script is going to be easier to read.
>
> Consensus seems to be to go with option #1.

Fine with me. There is a bit of complexity or even a race condition 
("can deliver at the time of the test" vs. "can deliver at the time of 
the notify execution"), but I don't think it's serious. (If we worry 
about that, we'd better worry something much bigger: what happens if 
the notification is dislayed, but not seen because the screensaver 
kicks in 0.02 seconds later, or the user logs out 0.04 seconds later, 
or the mobile device runs out of power and dies 0.01 seconds later.)

Arnt


From owner-ietf-mta-filters Mon Feb  5 09:03:00 2007
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 l15G30Fp060654
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 5 Feb 2007 09:03:00 -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 l15G30s1060653;
	Mon, 5 Feb 2007 09:03:00 -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 rufus.isode.com (rufus.isode.com [62.3.217.251])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l15G2xKh060647
	for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 09:03:00 -0700 (MST)
	(envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) 
          by rufus.isode.com (submission channel) via TCP with ESMTPA 
          id <RcdVMQBXDsf-@rufus.isode.com>; Mon, 5 Feb 2007 16:02:58 +0000
Message-ID: <45C7551B.7000309@isode.com>
Date: Mon, 05 Feb 2007 16:02:35 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
            Gecko/20050915
X-Accept-Language: en-us, en
To: ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before
         sending         it to IESG
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com>
In-Reply-To: <45C753CF.7080906@isode.com>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>


Alexey Melnikov wrote:

> Folks,
> This is your last chance to review that the document is correct and 
> complete. No new issues can be raised at this stage unless they are 
> very serious.

I actually do have one issue with a recent change in -10 which I 
consider to be serious, because it broke my Sieve implementation (as 
well as CMU's)

 > 8.1.     Lexical Tokens
 >
 >    Sieve scripts are encoded in UTF-8.  The following assumes a valid
 >    UTF-8 encoding; special characters in Sieve scripts are all US-ASCII.
 >
 >    The following are tokens in Sieve:
 >
 >            - identifiers
 >            - tags
 >            - numbers
 >            - quoted strings
 >            - multi-line strings
 >            - other separators
 >
 >    Identifiers, tags, and numbers are case-insensitive, while quoted
 >    strings and multi-line strings are case-sensitive.

I actually have a problem with *numbers* being case-insensitive. Cyrus
Sieve doesn't accept "k", "m" and "g" prefixes in numbers.

So I would like to poll the WG regarding this issue. Do people want to 
make to make number case-insensitive, or should this change be undone?
(In the latter case there is one example in 3028bis-10 which uses 
lowercase 'k' now, which has to change)

Thanks,
Alexey


From owner-ietf-mta-filters Mon Feb  5 08:57:39 2007
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 l15Fvd1i059388
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 5 Feb 2007 08:57:39 -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 l15FvdnZ059387;
	Mon, 5 Feb 2007 08:57:39 -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 rufus.isode.com (rufus.isode.com [62.3.217.251])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l15FvcEn059372
	for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 08:57:39 -0700 (MST)
	(envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) 
          by rufus.isode.com (submission channel) via TCP with ESMTPA 
          id <RcdT8ABXDpTg@rufus.isode.com>; Mon, 5 Feb 2007 15:57:37 +0000
Message-ID: <45C753CF.7080906@isode.com>
Date: Mon, 05 Feb 2007 15:57:03 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
            Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-mta-filters@imc.org
Subject: Last chance to review draft-ietf-sieve-3028bis-10.txt before sending
         it to IESG
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org>
In-Reply-To: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>


Internet-Drafts@ietf.org wrote:

>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.
>
>	Title		: Sieve: An Email Filtering Language
>	Author(s)	: T. Showalter, P. Guenther
>	Filename	: draft-ietf-sieve-3028bis-10.txt
>	Pages		: 44
>	Date		: 2007-2-2
>	
>This document describes a language for filtering email messages at
>   time of final delivery.  It is designed to be implementable on either
>   a mail client or mail server.  It is meant to be extensible, simple,
>   and independent of access protocol, mail architecture, and operating
>   system.  It is suitable for running on a mail server where users may
>   not be allowed to execute arbitrary programs, such as on black box
>   Internet Message Access Protocol (IMAP) servers, as the base language
>   has no variables, loops, or ability to shell out to external
>   programs.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-sieve-3028bis-10.txt
>  
>
Folks,
This is your last chance to review that the document is correct and 
complete. No new issues can be raised at this stage unless they are very 
serious.

Please review the document by the end of February 11th. Cyrus and I are 
planning to send it to IESG soon after February 11th.

Regards,
Alexey and Cyrus.


From owner-ietf-mta-filters Mon Feb  5 09:40:57 2007
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 l15GevHW069694
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 5 Feb 2007 09:40:57 -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 l15GevNg069692;
	Mon, 5 Feb 2007 09:40:57 -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 smtp.aegee.uni-karlsruhe.de (smtp.aegee.uni-karlsruhe.de [129.13.62.220])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l15GesxK069677
	(version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO)
	for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 09:40:56 -0700 (MST)
	(envelope-from Dilyan.Palauzov@aegee.org)
Received: from aegeeserv.aegee.org (aegeeserv.aegee.uni-karlsruhe.de [129.13.131.80])
	by smtp2.rz.uni-karlsruhe.de with esmtp (Exim 4.63 #1)
	id 1HE6th-00041h-4N; Mon, 05 Feb 2007 17:40:53 +0100
Received: from AEGEEserv.aegee.uni-karlsruhe.de (localhost [127.0.0.1])
	by aegeeserv.aegee.org (8.13.8/8.13.6) with ESMTP id l15Geq9S030011
	for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 16:40:52 GMT
Received: (from wwwrun@localhost)
	by AEGEEserv.aegee.uni-karlsruhe.de (8.13.8/8.13.6/Submit) id l15GeqX2030010
	for ietf-mta-filters@imc.org; Mon, 5 Feb 2007 17:40:52 +0100
X-Authentication-Warning: AEGEEserv.aegee.uni-karlsruhe.de: wwwrun set sender to Dilyan.Palauzov@aegee.org using -f
Received: from nan-y403.nan.uni-karlsruhe.de (nan-y403.nan.uni-karlsruhe.de
	[172.20.21.213]) by mail.aegee.org (Horde MIME library) with HTTP; Mon, 05
	Feb 2007 17:40:52 +0100
Message-ID: <20070205174052.dj1w9orq4g08osg8@mail.aegee.org>
Date: Mon, 05 Feb 2007 17:40:52 +0100
From: Dilyan Palauzov <Dilyan.Palauzov@aegee.org>
To: ietf-mta-filters@imc.org
Subject: some thoughts
MIME-Version: 1.0
Content-Type: text/plain;
	charset=UTF-8;
	DelSp="Yes";
	format="flowed"
Content-Disposition: inline
User-Agent: Internet Messaging Program (IMP) H3 (4.1.3)
X-Virus-Scanned: ClamAV 0.88.7/2523/Sun Feb  4 19:16:40 2007 on AEGEEserv.aegee.uni-karlsruhe.de
X-Virus-Status: Clean
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l15GevxJ069687
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>


   Hi folks,

   I was thinking on implementing a sieve-milter, an addon for  
sendmail, that filters mails for users, which do not necessary have  
mailbox on that server. In such cases the filter is applied to the  
whole envelope with its contents (except where the message is  
modified, in which case a new message shall be generated). And on some  
points I continue to think how to implement them.
  - test size
How shall the implementation determine the size of the message: if the  
smtp server supports rfc 1870 (esmtp, size), can the sieve  
implementation use that value (MAIL FROM: nana@aegee.org size=10000 ,  
or shall count by itself the bytes contained?

  - envelopes
If a mail goes to several recepients, but in one envelope, test  
address and test envelope can figure it out, but then the rfc3028  
permits that one user removes the other from the envelope. E.g. if a  
mail goes
To: a@d.e, b@d.e

the a@d.e. might have the follwoing script

if envelope :all is "to" b@d.e discard;

then the mail might not be delivered to b@d.e . Is there any sentence,  
I have overseen, prohibiting that the different users' scripts may not  
interfere?
   Greetings,
     Ð”Ð¸Ð»Ñ�Ð½



From owner-ietf-mta-filters Mon Feb  5 11:01:15 2007
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 l15I1FX0014200
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 5 Feb 2007 11:01:15 -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 l15I1FiA014193;
	Mon, 5 Feb 2007 11:01:15 -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 smtp.andrew.cmu.edu (smtp.andrew.cmu.edu [128.2.10.81])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l15I1DeL014123
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 11:01:14 -0700 (MST)
	(envelope-from murch@andrew.cmu.edu)
Received: from [192.168.137.23] (ntonawnd-cuda1-cable-bundle-68-69-73-26.kntnny.adelphia.net [68.69.73.26])
	(user=murch mech=PLAIN (0 bits))
	by smtp.andrew.cmu.edu (8.13.6/8.13.6) with ESMTP id l15I151j011858
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT)
	for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 13:01:10 -0500
Message-ID: <45C770D8.9070504@andrew.cmu.edu>
Date: Mon, 05 Feb 2007 13:00:56 -0500
From: Ken Murchison <murch@andrew.cmu.edu>
Organization: Carnegie Mellon University
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before
         sending         it to IESG
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com>
In-Reply-To: <45C7551B.7000309@isode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 128.2.10.81
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>


Alexey Melnikov wrote:
> 
> Alexey Melnikov wrote:
> 
>> Folks,
>> This is your last chance to review that the document is correct and 
>> complete. No new issues can be raised at this stage unless they are 
>> very serious.
> 
> I actually do have one issue with a recent change in -10 which I 
> consider to be serious, because it broke my Sieve implementation (as 
> well as CMU's)
> 
>  > 8.1.     Lexical Tokens
>  >
>  >    Sieve scripts are encoded in UTF-8.  The following assumes a valid
>  >    UTF-8 encoding; special characters in Sieve scripts are all US-ASCII.
>  >
>  >    The following are tokens in Sieve:
>  >
>  >            - identifiers
>  >            - tags
>  >            - numbers
>  >            - quoted strings
>  >            - multi-line strings
>  >            - other separators
>  >
>  >    Identifiers, tags, and numbers are case-insensitive, while quoted
>  >    strings and multi-line strings are case-sensitive.
> 
> I actually have a problem with *numbers* being case-insensitive. Cyrus
> Sieve doesn't accept "k", "m" and "g" prefixes in numbers.
> 
> So I would like to poll the WG regarding this issue. Do people want to 
> make to make number case-insensitive, or should this change be undone?
> (In the latter case there is one example in 3028bis-10 which uses 
> lowercase 'k' now, which has to change)

Obviously, digits are case-insensitive, but by stating "number" this 
also includes QUANTIFIER, which only allows uppercase per the ABNF.

I think we should move "numbers" from the case-insensitive list to the 
case-sensitive list in order to maintain backwards compatibility.

-- 
Kenneth Murchison
Project Cyrus Developer/Maintainer
Carnegie Mellon University


From owner-ietf-mta-filters Mon Feb  5 11:06:26 2007
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 l15I6QML020320
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 5 Feb 2007 11:06:26 -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 l15I6Q2B020319;
	Mon, 5 Feb 2007 11:06:26 -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 kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l15I6PZm020309
	for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 11:06:26 -0700 (MST)
	(envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9])
	by kalyani.oryx.com (Postfix) with ESMTP id 092984AC8C;
	Mon,  5 Feb 2007 19:06:25 +0100 (CET)
Message-Id: <66Cb5v2uUGlahT+ZZhXGHg.md5@libertango.oryx.com>
Date: Mon, 5 Feb 2007 19:06:56 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-mta-filters@imc.org
Subject: Re: some thoughts
Cc: Dilyan Palauzov <Dilyan.Palauzov@aegee.org>
References: <20070205174052.dj1w9orq4g08osg8@mail.aegee.org>
In-Reply-To: <20070205174052.dj1w9orq4g08osg8@mail.aegee.org>
Content-Type: text/plain; charset=koi8-r; format=flowed
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l15I6QZm020314
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>


Dilyan Palauzov writes:
>   Hi folks,
>
>   I was thinking on implementing a sieve-milter, an addon for  
>   sendmail, that filters mails for users, which do not necessary have 
>    mailbox on that server. In such cases the filter is applied to the 
>    whole envelope with its contents (except where the message is  
>   modified, in which case a new message shall be generated). And on 
>   some  points I continue to think how to implement them.
>  - test size
> How shall the implementation determine the size of the message: if the 
>  smtp server supports rfc 1870 (esmtp, size), can the sieve  
> implementation use that value (MAIL FROM: nana@aegee.org size=10000 , 
>  or shall count by itself the bytes contained?

I was pondering this (about postfix, not sendmail, in order to do 
protocol-level reject) and thought I'd use SIZE=x until the counted 
size is available, and after that use the counted size.

>  - envelopes
> If a mail goes to several recepients, but in one envelope, test  
> address and test envelope can figure it out, but then the rfc3028  
> permits that one user removes the other from the envelope. E.g. if a  
> mail goes
> To: a@d.e, b@d.e
>
> the a@d.e. might have the follwoing script
>
> if envelope :all is "to" b@d.e discard;
>
> then the mail might not be delivered to b@d.e . Is there any sentence, 
>  I have overseen, prohibiting that the different users' scripts may 
> not  interfere?

I eventually decided that a@d.e should not be able to tell whether the 
envelope contains b@d.e. If b@d.e is a bcc, revealing it in sieve would 
be a privacy leak.

>   Greetings,
>     äÉÌÑÎ

(I can read all of that. I feel proud.)

Arnt


From owner-ietf-mta-filters Mon Feb  5 11:56:38 2007
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 l15Iuc7b094450
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 5 Feb 2007 11:56:38 -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 l15IucbV094449;
	Mon, 5 Feb 2007 11:56:38 -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 rufus.isode.com (rufus.isode.com [62.3.217.251])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l15Iubgr094436
	for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 11:56:37 -0700 (MST)
	(envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) 
          by rufus.isode.com (submission channel) via TCP with ESMTPA 
          id <Rcd94wBXDoaE@rufus.isode.com>; Mon, 5 Feb 2007 18:56:35 +0000
Message-ID: <45C77DCC.7040508@isode.com>
Date: Mon, 05 Feb 2007 18:56:12 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
            Gecko/20050915
X-Accept-Language: en-us, en
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
CC: ietf-mta-filters@imc.org, Dilyan Palauzov <Dilyan.Palauzov@aegee.org>
Subject: Re: some thoughts
References: <20070205174052.dj1w9orq4g08osg8@mail.aegee.org> <66Cb5v2uUGlahT+ZZhXGHg.md5@libertango.oryx.com>
In-Reply-To: <66Cb5v2uUGlahT+ZZhXGHg.md5@libertango.oryx.com>
MIME-version: 1.0
Content-type: text/plain; charset="KOI8-R"; format="flowed"
Content-transfer-encoding: 7bit
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>


Arnt Gulbrandsen wrote:

>>  - envelopes
>> If a mail goes to several recepients, but in one envelope, test  
>> address and test envelope can figure it out, but then the rfc3028  
>> permits that one user removes the other from the envelope. E.g. if a  
>> mail goes
>> To: a@d.e, b@d.e
>>
>> the a@d.e. might have the follwoing script
>>
>> if envelope :all is "to" b@d.e discard;
>>
>> then the mail might not be delivered to b@d.e . Is there any 
>> sentence,  I have overseen, prohibiting that the different users' 
>> scripts may not  interfere?
>
> I eventually decided that a@d.e should not be able to tell whether the 
> envelope contains b@d.e. If b@d.e is a bcc, revealing it in sieve 
> would be a privacy leak.

Indeed. As far as Sieve is concerned, each envelope always contains a 
single recipient.


From owner-ietf-mta-filters Mon Feb  5 11:56:36 2007
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 l15IuZPc094399
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 5 Feb 2007 11:56:36 -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 l15IuZGh094396;
	Mon, 5 Feb 2007 11:56:35 -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 rufus.isode.com (rufus.isode.com [62.3.217.251])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l15IuYJk094367
	for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 11:56:35 -0700 (MST)
	(envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) 
          by rufus.isode.com (submission channel) via TCP with ESMTPA 
          id <Rcd94QBXDkGD@rufus.isode.com>; Mon, 5 Feb 2007 18:56:33 +0000
Message-ID: <45C77DCA.4050707@isode.com>
Date: Mon, 05 Feb 2007 18:56:10 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
            Gecko/20050915
X-Accept-Language: en-us, en
To: Dilyan Palauzov <Dilyan.Palauzov@aegee.org>
CC: ietf-mta-filters@imc.org
Subject: Re: some thoughts
References: <20070205174052.dj1w9orq4g08osg8@mail.aegee.org>
In-Reply-To: <20070205174052.dj1w9orq4g08osg8@mail.aegee.org>
MIME-version: 1.0
Content-type: text/plain; charset="UTF-8"; format="flowed"
Content-transfer-encoding: 7bit
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>


Dilyan Palauzov wrote:

>   Hi folks,
>
>   I was thinking on implementing a sieve-milter, an addon for  
> sendmail, that filters mails for users, which do not necessary have  
> mailbox on that server. In such cases the filter is applied to the  
> whole envelope with its contents (except where the message is  
> modified, in which case a new message shall be generated). And on 
> some  points I continue to think how to implement them.
>  - test size
> How shall the implementation determine the size of the message: if 
> the  smtp server supports rfc 1870 (esmtp, size), can the sieve  
> implementation use that value (MAIL FROM: nana@aegee.org size=10000 ,  
> or shall count by itself the bytes contained?

Hi Dilyan,
SMTP SIZE is an approximation of the size, so ideally you should count 
bytes.


From owner-ietf-mta-filters Mon Feb  5 12:05:05 2007
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 l15J55R7006805
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 5 Feb 2007 12:05:05 -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 l15J54Jd006797;
	Mon, 5 Feb 2007 12:05:05 -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 kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l15J52pM006731
	for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 12:05:04 -0700 (MST)
	(envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9])
	by kalyani.oryx.com (Postfix) with ESMTP id 1D3594AC8C;
	Mon,  5 Feb 2007 20:05:03 +0100 (CET)
Message-Id: <oXaabEEMm76YjD0UKajbMw.md5@libertango.oryx.com>
Date: Mon, 5 Feb 2007 20:05:35 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-mta-filters@imc.org
Subject: Re: some thoughts
Cc: Alexey Melnikov <alexey.melnikov@isode.com>,
        Dilyan Palauzov
  <Dilyan.Palauzov@aegee.org>
References: <20070205174052.dj1w9orq4g08osg8@mail.aegee.org>
  <66Cb5v2uUGlahT+ZZhXGHg.md5@libertango.oryx.com>
  <45C77DCC.7040508@isode.com>
In-Reply-To: <45C77DCC.7040508@isode.com>
Content-Type: text/plain; format=flowed
MIME-Version: 1.0
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>


Alexey Melnikov writes:
> Indeed. As far as Sieve is concerned, each envelope always contains a 
> single recipient.

I would not protest strongly if an implementation were to include 
aliases leading to the recipient.

Arnt


From owner-ietf-mta-filters Tue Feb  6 01:42:41 2007
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 l168gSAi078902
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 6 Feb 2007 01:42:41 -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 l15KY4WG069939;
	Mon, 5 Feb 2007 13:34:04 -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 smtp-out.sendmail.com (smtp-out.sendmail.com [209.246.26.45])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l15KY0We069774
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 13:34:02 -0700 (MST)
	(envelope-from guenther+mtafilters@sendmail.com)
Received: from [10.0.0.51] (71-208-198-236.hlrn.qwest.net [71.208.198.236])
	(authenticated bits=0)
	by foon.sendmail.com (Switch-3.2.5/Switch-3.2.0) with ESMTP id l15KXi8j000331
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 5 Feb 2007 12:33:46 -0800
X-DKIM: Sendmail DKIM Filter v0.5.1 foon.sendmail.com l15KXi8j000331
DKIM-Signature: a=rsa-sha1; c=relaxed/simple; d=sendmail.com; s=tls.dkim;
	t=1170707631; bh=jH+MF8+WOuE4yvEEF3SENIVvA8M=; h=X-DomainKeys:
	 DomainKey-Signature:Date:From:X-X-Sender:To:cc:Subject:In-Reply-To:
	 Message-ID:References:MIME-Version:Content-Type; b=kkVbYHmQcFpj1zSv
	hcAhSe8LoPVmlXvdo6iIz998gx+UCiJ39craoqw7bEB6119KgwmqQZLUMn/VgA99VQv
	i8IK4F/JAciEmSdhSnh4K9hmuCeSujZCAwIDsany4Mk5AOp0nv51EBZacEW6x0frpyq
	FWaBv0MObVNhP+C3tfOEw=
X-DomainKeys: Sendmail DomainKeys Filter v0.4.1 foon.sendmail.com l15KXi8j000331
DomainKey-Signature: a=rsa-sha1; s=tls; d=sendmail.com; c=nofws; q=dns;
	h=date:from:x-x-sender:to:cc:subject:in-reply-to:message-id:
	references:mime-version:content-type;
	b=PdVUn8XGPgB1RKDeQIlS6CZ+TQdQYNjFlM7s5efMzTc5YnRTQydMW89uK0a0ftnUP
	OZqpU8P99R9kHPJAMCLNVGTFb93FH6OuQxVqKq0qQtVd3FI/uROgN1/uo2PSbbNKRa9
	0FUH0gYlMpSs8W/CituZ+TuuOnBqa5stz+uT9j0=
Date: Mon, 5 Feb 2007 13:33:43 -0700
From: Philip Guenther <guenther+mtafilters@sendmail.com>
X-X-Sender: guenther@vanye.mho.net
To: Ken Murchison <murch@andrew.cmu.edu>
cc: ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before  
       sending         it to IESG
In-Reply-To: <45C770D8.9070504@andrew.cmu.edu>
Message-ID: <Pine.BSO.4.64.0702051329280.9988@vanye.mho.net>
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com>
 <45C7551B.7000309@isode.com> <45C770D8.9070504@andrew.cmu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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>


On Mon, 5 Feb 2007, Ken Murchison wrote:
> Alexey Melnikov wrote:
...
>> I actually have a problem with *numbers* being case-insensitive. Cyrus
>> Sieve doesn't accept "k", "m" and "g" prefixes in numbers.
>> 
>> So I would like to poll the WG regarding this issue. Do people want to make 
>> to make number case-insensitive, or should this change be undone?
>> (In the latter case there is one example in 3028bis-10 which uses lowercase 
>> 'k' now, which has to change)
>
> Obviously, digits are case-insensitive, but by stating "number" this also 
> includes QUANTIFIER, which only allows uppercase per the ABNF.

Nope.  RFC 3028 said:

    QUANTIFIER = "K" / "M" / "G"

Literal strings in ABNF are always case-insensitive.

So the question is: was this a bug in the grammar or a bug in those 
implementations?  I know that the Sendmail implementation has treated them 
as case-insensitive from its beginning.


Philip Guenther


From owner-ietf-mta-filters Tue Feb  6 11:03:05 2007
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 l16I35Ui055092
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 6 Feb 2007 11:03:05 -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 l16I350X055091;
	Tue, 6 Feb 2007 11:03:05 -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 kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l16I33hF055084
	for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 11:03:04 -0700 (MST)
	(envelope-from arnt@oryx.com)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9])
	by kalyani.oryx.com (Postfix) with ESMTP id 4AE204AC5B;
	Tue,  6 Feb 2007 19:03:04 +0100 (CET)
Message-Id: <d2Or/zTym5ykDhlHnjOEFQ.md5@libertango.oryx.com>
Date: Tue, 6 Feb 2007 19:03:41 +0100
From: Arnt Gulbrandsen <arnt@oryx.com>
To: ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before
  sending it to IESG
Cc: Alexey Melnikov <alexey.melnikov@isode.com>
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org>
  <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com>
In-Reply-To: <45C7551B.7000309@isode.com>
Content-Type: text/plain; format=flowed
MIME-Version: 1.0
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>


Alexey Melnikov writes:
> I actually do have one issue with a recent change in -10 which I 
> consider to be serious, because it broke my Sieve implementation (as 
> well as CMU's)

Why did this break your implementation? It did not cause any previously 
valid scripts to become invalid. All it did was clarify an existing 
rule.

> I actually have a problem with *numbers* being case-insensitive. Cyrus 
> Sieve doesn't accept "k", "m" and "g" prefixes in numbers.
>
> So I would like to poll the WG regarding this issue. Do people want to 
> make to make number case-insensitive, or should this change be 
> undone?

Making numbers case-sensitive could invalidate extant valid scripts. 
That needs strong justification IMO.

Arnt


From owner-ietf-mta-filters Tue Feb  6 11:19:08 2007
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 l16IJ7Q3056507
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 6 Feb 2007 11:19:08 -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 l16IJ7or056506;
	Tue, 6 Feb 2007 11:19:07 -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 rufus.isode.com (rufus.isode.com [62.3.217.251])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l16IJ7SU056500
	for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 11:19:07 -0700 (MST)
	(envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) 
          by rufus.isode.com (submission channel) via TCP with ESMTPA 
          id <RcjGmABXDpJW@rufus.isode.com>; Tue, 6 Feb 2007 18:19:04 +0000
Message-ID: <45C8C681.5080900@isode.com>
Date: Tue, 06 Feb 2007 18:18:41 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
            Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Arnt Gulbrandsen <arnt@oryx.com>
CC: ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before
         sending it to IESG
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org>  <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com> <d2Or/zTym5ykDhlHnjOEFQ.md5@libertango.oryx.com>
In-Reply-To: <d2Or/zTym5ykDhlHnjOEFQ.md5@libertango.oryx.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>


Arnt Gulbrandsen wrote:

> Alexey Melnikov writes:
>
>> I actually do have one issue with a recent change in -10 which I 
>> consider to be serious, because it broke my Sieve implementation (as 
>> well as CMU's)
>
> Why did this break your implementation? It did not cause any 
> previously valid scripts to become invalid. All it did was clarify an 
> existing rule.

If somebody puts "100k" in a Sieve script, Sieve lexer is going to 
reject such script.

>> I actually have a problem with *numbers* being case-insensitive. 
>> Cyrus Sieve doesn't accept "k", "m" and "g" prefixes in numbers.
>>
>> So I would like to poll the WG regarding this issue. Do people want 
>> to make to make number case-insensitive, or should this change be 
>> undone?
>
> Making numbers case-sensitive could invalidate extant valid scripts. 
> That needs strong justification IMO.

Let's assess the damage first. If it turns out that the majority of 
implementations implement case-insensitive suffixes, then I will have to 
fix my implementation ;-).


From owner-ietf-mta-filters Tue Feb  6 11:18:04 2007
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 l16II4F5056420
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 6 Feb 2007 11:18:04 -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 l16II4Qr056419;
	Tue, 6 Feb 2007 11:18:04 -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 rufus.isode.com (rufus.isode.com [62.3.217.251])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l16II2td056411
	for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 11:18:03 -0700 (MST)
	(envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) 
          by rufus.isode.com (submission channel) via TCP with ESMTPA 
          id <RcjGWABXDqxQ@rufus.isode.com>; Tue, 6 Feb 2007 18:18:01 +0000
Message-ID: <45C8C641.5090801@isode.com>
Date: Tue, 06 Feb 2007 18:17:37 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
            Gecko/20050915
X-Accept-Language: en-us, en
To: Philip Guenther <guenther+mtafilters@sendmail.com>
CC: Ken Murchison <murch@andrew.cmu.edu>, ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before
         sending         it to IESG
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com> <45C770D8.9070504@andrew.cmu.edu> <Pine.BSO.4.64.0702051329280.9988@vanye.mho.net>
In-Reply-To: <Pine.BSO.4.64.0702051329280.9988@vanye.mho.net>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>


Philip Guenther wrote:

> On Mon, 5 Feb 2007, Ken Murchison wrote:
>
>> Alexey Melnikov wrote:
>
> ...
>
>>> I actually have a problem with *numbers* being case-insensitive. Cyrus
>>> Sieve doesn't accept "k", "m" and "g" prefixes in numbers.
>>>
>>> So I would like to poll the WG regarding this issue. Do people want 
>>> to make to make number case-insensitive, or should this change be 
>>> undone?
>>> (In the latter case there is one example in 3028bis-10 which uses 
>>> lowercase 'k' now, which has to change)
>>
>> Obviously, digits are case-insensitive, but by stating "number" this 
>> also includes QUANTIFIER, which only allows uppercase per the ABNF.
>
> Nope.  RFC 3028 said:
>
>    QUANTIFIER = "K" / "M" / "G"
>
> Literal strings in ABNF are always case-insensitive.

Ok, you are right. But many people got beaten by this ABNF "feature".

> So the question is: was this a bug in the grammar or a bug in those 
> implementations?

Indeed.

> I know that the Sendmail implementation has treated them as 
> case-insensitive from its beginning.



From owner-ietf-mta-filters Tue Feb  6 11:42:20 2007
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 l16IgKm4058112
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 6 Feb 2007 11:42:20 -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 l16IgKA9058111;
	Tue, 6 Feb 2007 11:42:20 -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 smtp.andrew.cmu.edu (smtp.andrew.cmu.edu [128.2.10.81])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l16IgIKw058100
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 11:42:19 -0700 (MST)
	(envelope-from murch@andrew.cmu.edu)
Received: from [192.168.137.23] (ntonawnd-cuda1-cable-bundle-68-69-73-26.kntnny.adelphia.net [68.69.73.26])
	(user=murch mech=PLAIN (0 bits))
	by smtp.andrew.cmu.edu (8.13.6/8.13.6) with ESMTP id l16IgAsP032350
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Tue, 6 Feb 2007 13:42:11 -0500
Message-ID: <45C8CBEE.8030102@andrew.cmu.edu>
Date: Tue, 06 Feb 2007 13:41:50 -0500
From: Ken Murchison <murch@andrew.cmu.edu>
Organization: Carnegie Mellon University
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
CC: Philip Guenther <guenther+mtafilters@sendmail.com>,
        ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before
         sending         it to IESG
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com> <45C770D8.9070504@andrew.cmu.edu> <Pine.BSO.4.64.0702051329280.9988@vanye.mho.net> <45C8C641.5090801@isode.com>
In-Reply-To: <45C8C641.5090801@isode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 128.2.10.81
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>


Alexey Melnikov wrote:
> Philip Guenther wrote:
> 
>> On Mon, 5 Feb 2007, Ken Murchison wrote:
>>
>>> Alexey Melnikov wrote:
>>
>> ...
>>
>>>> I actually have a problem with *numbers* being case-insensitive. Cyrus
>>>> Sieve doesn't accept "k", "m" and "g" prefixes in numbers.
>>>>
>>>> So I would like to poll the WG regarding this issue. Do people want 
>>>> to make to make number case-insensitive, or should this change be 
>>>> undone?
>>>> (In the latter case there is one example in 3028bis-10 which uses 
>>>> lowercase 'k' now, which has to change)
>>>
>>> Obviously, digits are case-insensitive, but by stating "number" this 
>>> also includes QUANTIFIER, which only allows uppercase per the ABNF.
>>
>> Nope.  RFC 3028 said:
>>
>>    QUANTIFIER = "K" / "M" / "G"
>>
>> Literal strings in ABNF are always case-insensitive.
> 
> Ok, you are right. But many people got beaten by this ABNF "feature".

Including CMU (before my time).  Its about a 10 sec fix for me, so I'll 
do whatever the consensus dictates.

-- 
Kenneth Murchison
Project Cyrus Developer/Maintainer
Carnegie Mellon University


From owner-ietf-mta-filters Tue Feb  6 11:39:32 2007
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 l16IdWjl057885
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 6 Feb 2007 11:39:32 -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 l16IdVgx057884;
	Tue, 6 Feb 2007 11:39:31 -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 kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l16IdUc8057873
	for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 11:39:31 -0700 (MST)
	(envelope-from arnt@oryx.com)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9])
	by kalyani.oryx.com (Postfix) with ESMTP id CDA6C4AC5B;
	Tue,  6 Feb 2007 19:39:30 +0100 (CET)
Message-Id: <iQX+wKZNMRoWQX58zgxdpQ.md5@libertango.oryx.com>
Date: Tue, 6 Feb 2007 19:40:07 +0100
From: Arnt Gulbrandsen <arnt@oryx.com>
To: ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before
  sending it to IESG
Cc: Alexey Melnikov <alexey.melnikov@isode.com>
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org>
  <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com>
  <d2Or/zTym5ykDhlHnjOEFQ.md5@libertango.oryx.com>
  <45C8C681.5080900@isode.com>
In-Reply-To: <45C8C681.5080900@isode.com>
Content-Type: text/plain; format=flowed
MIME-Version: 1.0
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>


Alexey Melnikov writes:
> Arnt Gulbrandsen wrote:
>
>> Alexey Melnikov writes:
>>
>>> I actually do have one issue with a recent change in -10 which I 
>>> consider to be serious, because it broke my Sieve implementation 
>>> (as well as CMU's)
>>
>> Why did this break your implementation? It did not cause any 
>> previously valid scripts to become invalid. All it did was clarify 
>> an existing rule.
>
> If somebody puts "100k" in a Sieve script, Sieve lexer is going to 
> reject such script.

Yes. But that's not lasting damage - the user has to change kmg to KMG 
and upload the script again.

Compare that with the alternative: Scripts which have passed 
managesieve's putscript checking become syntactically invalid when the 
server is upgraded.

>>> I actually have a problem with *numbers* being case-insensitive. 
>>> Cyrus Sieve doesn't accept "k", "m" and "g" prefixes in numbers.
>>>
>>> So I would like to poll the WG regarding this issue. Do people want 
>>> to make to make number case-insensitive, or should this change be 
>>> undone?
>>
>> Making numbers case-sensitive could invalidate extant valid scripts. 
>> That needs strong justification IMO.
>
> Let's assess the damage first. If it turns out that the majority of 
> implementations implement case-insensitive suffixes, then I will have 
> to fix my implementation ;-).

I wrote my code case-insensitively, but it's unreleased as yet.

Arnt


From owner-ietf-mta-filters Tue Feb  6 12:04:56 2007
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 l16J4t8j059824
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 6 Feb 2007 12:04:55 -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 l16J4t6u059823;
	Tue, 6 Feb 2007 12:04:55 -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 mauve.mrochek.com (netblock-68-183-106-173.brandx.net [68.183.106.173] (may be forged))
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l16J4r1W059817
	for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 12:04:53 -0700 (MST)
	(envelope-from ned.freed@mrochek.com)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com
 (PMDF V6.1-1 #35243) id <01MCT5QTUKHC001ACT@mauve.mrochek.com> for
 ietf-mta-filters@imc.org; Tue, 6 Feb 2007 11:04:49 -0800 (PST)
DKIM-Signature: a=rsa-sha1; c=nowsp; d=mrochek.com; s=mauve; t=1170788688;
 h=Date: 	 From:Subject:MIME-version:Content-type; b=s5UyP1knrCLh8wK0lbvrx/3ia
	lkZ6zcEO8B/ckbWSi+Fcm3HV+CsYvIo0/So9ZGrqqtfRNzN6lb6niOKVp9BBw==
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243)
 id <01MCSCUL997K00004S@mauve.mrochek.com>; Tue,
 06 Feb 2007 11:04:44 -0800 (PST)
Cc: ietf-mta-filters@imc.org, Alexey Melnikov <alexey.melnikov@isode.com>
Message-id: <01MCT5QRXR5600004S@mauve.mrochek.com>
Date: Tue, 06 Feb 2007 10:58:54 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before
 sending it to IESG
In-reply-to: "Your message dated Tue, 06 Feb 2007 19:40:07 +0100"
 <iQX+wKZNMRoWQX58zgxdpQ.md5@libertango.oryx.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; format=flowed
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org>
 <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com>
 <d2Or/zTym5ykDhlHnjOEFQ.md5@libertango.oryx.com> <45C8C681.5080900@isode.com>
 <iQX+wKZNMRoWQX58zgxdpQ.md5@libertango.oryx.com>
To: Arnt Gulbrandsen <arnt@oryx.com>
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>



> Alexey Melnikov writes:
> > Arnt Gulbrandsen wrote:
> >
> >> Alexey Melnikov writes:
> >>
> >>> I actually do have one issue with a recent change in -10 which I
> >>> consider to be serious, because it broke my Sieve implementation
> >>> (as well as CMU's)
> >>
> >> Why did this break your implementation? It did not cause any
> >> previously valid scripts to become invalid. All it did was clarify
> >> an existing rule.
> >
> > If somebody puts "100k" in a Sieve script, Sieve lexer is going to
> > reject such script.

> Yes. But that's not lasting damage - the user has to change kmg to KMG
> and upload the script again.

> Compare that with the alternative: Scripts which have passed
> managesieve's putscript checking become syntactically invalid when the
> server is upgraded.

> >>> I actually have a problem with *numbers* being case-insensitive.
> >>> Cyrus Sieve doesn't accept "k", "m" and "g" prefixes in numbers.
> >>>
> >>> So I would like to poll the WG regarding this issue. Do people want
> >>> to make to make number case-insensitive, or should this change be
> >>> undone?
> >>
> >> Making numbers case-sensitive could invalidate extant valid scripts.
> >> That needs strong justification IMO.
> >
> > Let's assess the damage first. If it turns out that the majority of
> > implementations implement case-insensitive suffixes, then I will have
> > to fix my implementation ;-).

> I wrote my code case-insensitively, but it's unreleased as yet.

FWIW, our implementation also handles either case. The only "problem" we've ever
had with this feature is users who enter values like 100000G and then get upset
when it says "integer too large" or something similar. (Yes, we frequently get
absurd complaints like this.)

I believe our script generator puts these out in upper case and I know I've
seen hand-constructed scripts have them in lower case. So scripts are probably
gonna break if we make this case-sensitive.

				Ned


From owner-ietf-mta-filters Tue Feb  6 12:11:02 2007
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 l16JB2kP060178
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 6 Feb 2007 12:11:02 -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 l16JB2Kq060177;
	Tue, 6 Feb 2007 12:11:02 -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.serendipity.cx (serendipity.palo-alto.ca.us [66.92.2.87])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l16JAxvA060148
	for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 12:11:01 -0700 (MST)
	(envelope-from aaron@serendipity.cx)
Received: from serendipity.palo-alto.ca.us (localhost [127.0.0.1])
	by mail.serendipity.cx (Postfix) with SMTP id BCEB66024E31;
	Tue,  6 Feb 2007 11:10:08 -0800 (PST)
Date: Tue, 6 Feb 2007 19:10:08 -0000
To: "Ken Murchison" <murch@andrew.cmu.edu>
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before         sending         it to IESG
From: "Aaron Stone" <aaron@serendipity.cx>
X-Mailer: TWIG 2.8.2
Message-ID: <twig.1170789008.70289@serendipity.palo-alto.ca.us>
In-Reply-To: <45C8CBEE.8030102@andrew.cmu.edu>
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com> <45C770D8.9070504@andrew.cmu.edu> <Pine.BSO.4.64.0702051329280.9988@vanye.mho.net> <45C8C641.5090801@isode.com>, <45C8C641.5090801@isode.com>
Cc: <ietf-mta-filters@imc.org>
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>


On Tue, Feb 6, 2007, Ken Murchison <murch@andrew.cmu.edu> said:

>>>> Obviously, digits are case-insensitive, but by stating "number" this 
>>>> also includes QUANTIFIER, which only allows uppercase per the ABNF.
>>>
>>> Nope.  RFC 3028 said:
>>>
>>>    QUANTIFIER = "K" / "M" / "G"
>>>
>>> Literal strings in ABNF are always case-insensitive.
>> 
>> Ok, you are right. But many people got beaten by this ABNF "feature".
> 
> Including CMU (before my time).  Its about a 10 sec fix for me, so I'll 
> do whatever the consensus dictates.

I've inherited that same line in my lexer (with the same effort required
to change it ;-). I don't feel strongly either way as to whether we should
relax the spec to be case insensitive.

Aaron


From owner-ietf-mta-filters Tue Feb  6 12:40:37 2007
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 l16Jeb0k062778
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 6 Feb 2007 12:40:37 -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 l16JebPt062777;
	Tue, 6 Feb 2007 12:40:37 -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.serendipity.cx (serendipity.palo-alto.ca.us [66.92.2.87])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l16JeaoY062771
	for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 12:40:36 -0700 (MST)
	(envelope-from aaron@serendipity.cx)
Received: from serendipity.palo-alto.ca.us (localhost [127.0.0.1])
	by mail.serendipity.cx (Postfix) with SMTP id A42E56024E31;
	Tue,  6 Feb 2007 11:39:50 -0800 (PST)
Date: Tue, 6 Feb 2007 19:39:50 -0000
To: "Ned Freed" <ned.freed@mrochek.com>
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before sending it to IESG
From: "Aaron Stone" <aaron@serendipity.cx>
X-Mailer: TWIG 2.8.2
Message-ID: <twig.1170790790.9342@serendipity.palo-alto.ca.us>
In-Reply-To: <01MCT5QRXR5600004S@mauve.mrochek.com>
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com> <d2Or/zTym5ykDhlHnjOEFQ.md5@libertango.oryx.com> <45C8C681.5080900@isode.com> <iQX+wKZNMRoWQX58zgxdpQ.md5@libertango.oryx.com>, 
Cc: <ietf-mta-filters@imc.org>, "Alexey Melnikov" <alexey.melnikov@isode.com>,
        "Arnt Gulbrandsen" <arnt@oryx.com>
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>


On Tue, Feb 6, 2007, Ned Freed <ned.freed@mrochek.com> said:

>> Alexey Melnikov writes:
>> > Arnt Gulbrandsen wrote:
>> >> Alexey Melnikov writes:
[snip]
>> >>> I actually have a problem with *numbers* being case-insensitive.
>> >>> Cyrus Sieve doesn't accept "k", "m" and "g" prefixes in numbers.
>> >>>
>> >>> So I would like to poll the WG regarding this issue. Do people want
>> >>> to make to make number case-insensitive, or should this change be
>> >>> undone?
>> >>
>> >> Making numbers case-sensitive could invalidate extant valid scripts.
>> >> That needs strong justification IMO.
>> >
>> > Let's assess the damage first. If it turns out that the majority of
>> > implementations implement case-insensitive suffixes, then I will have
>> > to fix my implementation ;-).
> 
>> I wrote my code case-insensitively, but it's unreleased as yet.
[snip]
> I believe our script generator puts these out in upper case and I know
> I've seen hand-constructed scripts have them in lower case. So scripts
> are probably gonna break if we make this case-sensitive.

Sounds like one of those cases where the spec should be strict but the
implementations should be relaxed.

Aaron


From owner-ietf-mta-filters Tue Feb  6 13:33:17 2007
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 l16KXHfU066125
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 6 Feb 2007 13:33:17 -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 l16KXHe6066124;
	Tue, 6 Feb 2007 13:33:17 -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 mulberrymail.com (static-71-240-120-213.pitt.east.verizon.net [71.240.120.213])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l16KXFui066104
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 13:33:16 -0700 (MST)
	(envelope-from cyrus@daboo.name)
Received: from [17.101.32.44] ([17.101.32.44])
	(authenticated bits=0)
	by mulberrymail.com (8.13.6/8.13.6) with ESMTP id l16KX7o4031488
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 6 Feb 2007 15:33:09 -0500
Date: Tue, 06 Feb 2007 15:33:02 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Philip Guenther <guenther+mtafilters@sendmail.com>,
        Ken Murchison <murch@andrew.cmu.edu>
cc: ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before   
      sending         it to IESG
Message-ID: <EB285C61567E499E69874B94@caldav.apple.com>
In-Reply-To: <Pine.BSO.4.64.0702051329280.9988@vanye.mho.net>
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org>
 <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com>
 <45C770D8.9070504@andrew.cmu.edu>
 <Pine.BSO.4.64.0702051329280.9988@vanye.mho.net>
X-Mailer: Mulberry/4.1.0a1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Status: No, score=0.7 required=5.0 tests=SUBJ_HAS_SPACES 
	autolearn=disabled version=3.1.1
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on 
	piper.mulberrymail.com
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>


Hi Philip,

--On February 5, 2007 1:33:43 PM -0700 Philip Guenther 
<guenther+mtafilters@sendmail.com> wrote:

>> Obviously, digits are case-insensitive, but by stating "number" this
>> also  includes QUANTIFIER, which only allows uppercase per the ABNF.
>
> Nope.  RFC 3028 said:
>
>     QUANTIFIER = "K" / "M" / "G"
>
> Literal strings in ABNF are always case-insensitive.
>
> So the question is: was this a bug in the grammar or a bug in those
> implementations?

Based on responses from others, I think we have to leave this as-is. 
Implementations treating those quantifiers as case-sensitive will need to 
be fixed.

-- 
Cyrus Daboo


From owner-ietf-mta-filters Tue Feb  6 15:53:50 2007
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 l16MroPa074834
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 6 Feb 2007 15:53:50 -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 l16Mro4C074832;
	Tue, 6 Feb 2007 15:53:50 -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 shell.mv.net (osmium.mv.net [199.125.85.152])
	by balder-227.proper.com (8.13.5/8.13.5) with SMTP id l16MrmAB074824
	for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 15:53:49 -0700 (MST)
	(envelope-from mem@mv.mv.com)
Received: (qmail 40563 invoked by uid 101); 6 Feb 2007 17:53:45 -0500
From: "Mark E. Mallett" <mem@mv.mv.com>
Date: Tue, 6 Feb 2007 17:53:45 -0500
To: ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before sending         it to IESG
Message-ID: <20070206225345.GA37772@osmium.mv.net>
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com> <45C770D8.9070504@andrew.cmu.edu> <Pine.BSO.4.64.0702051329280.9988@vanye.mho.net> <45C8C641.5090801@isode.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <45C8C641.5090801@isode.com>
User-Agent: Mutt/1.4.2.1i
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>


On Tue, Feb 06, 2007 at 06:17:37PM +0000, Alexey Melnikov wrote:
> 
> Philip Guenther wrote:
> >
> >   QUANTIFIER = "K" / "M" / "G"
> >
> >Literal strings in ABNF are always case-insensitive.
> 
> Ok, you are right. But many people got beaten by this ABNF "feature".

My implementation treats them as case insensitive, mainly because I
wanted it that way and didn't think it would hurt anything to be
friendlier to humans typing numbers.  

So I'm happy with the change :)

mm


From owner-ietf-mta-filters Tue Feb  6 17:26:26 2007
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 l170QQhi080230
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 6 Feb 2007 17:26:26 -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 l170QQ24080229;
	Tue, 6 Feb 2007 17:26:26 -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 foon.sendmail.com (smtp-out.sendmail.com [209.246.26.45])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l170QNGr080223
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 17:26:26 -0700 (MST)
	(envelope-from guenther+mtafilters@sendmail.com)
Received: from [192.168.0.4] (71-212-236-65.hlrn.qwest.net [71.212.236.65])
	(authenticated bits=0)
	by foon.sendmail.com (Switch-3.2.5/Switch-3.2.0) with ESMTP id l170QG95012109
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 16:26:21 -0800
X-DKIM: Sendmail DKIM Filter v0.5.1 foon.sendmail.com l170QG95012109
DKIM-Signature: a=rsa-sha1; c=relaxed/simple; d=sendmail.com; s=tls.dkim;
	t=1170807982; bh=y38g7d0CYXqkId2G4/Uw0BiNo1A=; h=X-DomainKeys:
	 DomainKey-Signature:Date:From:X-X-Sender:To:Subject:Message-ID:
	 MIME-Version:Content-Type; b=s+22gFdyFqHZ34nPS605SQ5nvM/sGdcCBHyhDF
	ugF/kpWD5zTa4PkL8Rm/CazAKhJEN+d+/+NR8KDq4IvBNnsHBo5jNPlvoVf2/AL4Isy
	wNHsydlv2JkfAX7sCmvBIZRr9JTzojsjxY49drT4TmSC4e26uiBZQ/lREW6wN00Bf4=
X-DomainKeys: Sendmail DomainKeys Filter v0.4.1 foon.sendmail.com l170QG95012109
DomainKey-Signature: a=rsa-sha1; s=tls; d=sendmail.com; c=nofws; q=dns;
	h=date:from:x-x-sender:to:subject:message-id:mime-version:content-type;
	b=LaXlOhRE9FCxXCyqMim0QOYJPwolW+XRWZ868gE4Z+kvl0zN6KdQyoMQiY3SMkPId
	IGlc75YE0PbiTV3JpqHZcEHniyoWtgsu5yNYIv/A4usl6H8CNP5+8VfBmzNd2EJk4gx
	hJimBZyQTk7g06cITRseuJ4bk5hE/WJk7w2dHgU=
Date: Tue, 6 Feb 2007 17:26:16 -0700
From: Philip Guenther <guenther+mtafilters@sendmail.com>
X-X-Sender: guenther@vanye.mho.net
To: ietf-mta-filters@imc.org
Subject: 3028bis, section 4.2, paragraph 2
Message-ID: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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>



There's been some lingering dislike of the description of the redirect 
action, particularly how it describes the change of envelope recipient. 
3028bis-10 removed this sentence
 	The "redirect" modifies the envelope recipient.

as it was observed that it implied that the result of the 'envelope' test 
would be affected.  With that gone, only the second paragraph actually 
described how the address in the action was to become an envelope 
recipient, but it's description is fairly indirect.  So, I propose 
replacing most of that paragraph, so that instead of reading thusly:

    The redirect command performs an MTA-style "forward"--that is, what
    you get from a .forward file using sendmail under UNIX.  The address
    on the [SMTP] envelope is replaced with the one on the redirect
    command and the message is sent back out.  (This is not an MUA-style
    forward, which creates a new message with a different sender and
    message ID, wrapping the old message in a new one.)

it would instead say:

    The message is send back out with the address from the redirect
    command as an envelope recipient.  Implementations MAY combine
    separate redirects for a given message into a single submission with
    multiple envelope recipients.  (This is not an MUA-style forward,
    which creates a new message with a different sender and message ID,
    wrapping the old message in a new one.)

And yes, the elimination of the mention of .forward files in intentional, 
as that irked some.


Are there any objections to the above change?


Philip Guenther


From owner-ietf-mta-filters Wed Feb  7 01:42:49 2007
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 l178gnCd010495
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 7 Feb 2007 01:42:49 -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 l178gnWT010494;
	Wed, 7 Feb 2007 01:42:49 -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 kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l178glBD010486
	for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 01:42:49 -0700 (MST)
	(envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9])
	by kalyani.oryx.com (Postfix) with ESMTP id DB8694AC77;
	Wed,  7 Feb 2007 09:42:47 +0100 (CET)
Message-Id: <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com>
Date: Wed, 7 Feb 2007 09:43:27 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
Cc: Philip Guenther <guenther+mtafilters@sendmail.com>
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>
In-Reply-To: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>
Content-Type: text/plain; format=flowed
MIME-Version: 1.0
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>


Philip Guenther writes:
> it would instead say:
>
>    The message is send back out with the address from the redirect
>    command as an envelope recipient.  Implementations MAY combine
>    separate redirects for a given message into a single submission with
>    multiple envelope recipients.  (This is not an MUA-style forward,
>    which creates a new message with a different sender and message ID,
>    wrapping the old message in a new one.)
>
> And yes, the elimination of the mention of .forward files in 
> intentional, as that irked some.
>
> Are there any objections to the above change?

No, but maybe I want to add a requirement to prepend a new 'Received' 
field so that a human tracing problems can tell what happened to the 
message. Not 100% sure. In some (many?) cases there are enough Received 
fields anyway.

Arnt


From owner-ietf-mta-filters Wed Feb  7 03:10:25 2007
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 l17AAPc8016722
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 7 Feb 2007 03:10:25 -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 l17AAPPn016721;
	Wed, 7 Feb 2007 03:10:25 -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 kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l17AAOTo016713
	for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 03:10:25 -0700 (MST)
	(envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9])
	by kalyani.oryx.com (Postfix) with ESMTP id B671F4AC77;
	Wed,  7 Feb 2007 11:10:24 +0100 (CET)
Message-Id: <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com>
Date: Wed, 7 Feb 2007 11:11:05 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
Cc: Philip Guenther <guenther+mtafilters@sendmail.com>
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>
  <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com>
In-Reply-To: <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com>
Content-Type: text/plain; format=flowed
MIME-Version: 1.0
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>


Arnt Gulbrandsen writes:
> Philip Guenther writes:
>> it would instead say:
>>
>>    The message is send back out with the address from the redirect
>>    command as an envelope recipient.  Implementations MAY combine
>>    separate redirects for a given message into a single submission with
>>    multiple envelope recipients.  (This is not an MUA-style forward,
>>    which creates a new message with a different sender and message ID,
>>    wrapping the old message in a new one.)
>>
>> And yes, the elimination of the mention of .forward files in 
>> intentional, as that irked some.
>>
>> Are there any objections to the above change?
>
> No, but maybe I want to add a requirement to prepend a new 'Received' 
> field so that a human tracing problems can tell what happened to the 
> message. Not 100% sure. In some (many?) cases there are enough 
> Received fields anyway.

Perhaps: SHOULD ensure that there is sufficient information in the chain 
of 'Received' fields that a human observer can see what happened?

Arnt


From owner-ietf-mta-filters Wed Feb  7 04:52:44 2007
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 l17BqipK025072
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 7 Feb 2007 04:52:44 -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 l17Bqi9c025071;
	Wed, 7 Feb 2007 04:52:44 -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 rufus.isode.com (rufus.isode.com [62.3.217.251])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l17BqdlA025060
	for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 04:52:43 -0700 (MST)
	(envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) 
          by rufus.isode.com (submission channel) via TCP with ESMTPA 
          id <Rcm9hQBXDl7b@rufus.isode.com>; Wed, 7 Feb 2007 11:52:37 +0000
Message-ID: <45C9BD6C.6060505@isode.com>
Date: Wed, 07 Feb 2007 11:52:12 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
            Gecko/20050915
X-Accept-Language: en-us, en
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
CC: ietf-mta-filters@imc.org,
        Philip Guenther <guenther+mtafilters@sendmail.com>
Subject: Re: 3028bis, section 4.2, paragraph 2
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>  <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com> <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com>
In-Reply-To: <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>


Arnt Gulbrandsen wrote:

> Arnt Gulbrandsen writes:
>
>> Philip Guenther writes:
>>
>>> it would instead say:
>>>
>>>    The message is send back out with the address from the redirect
>>>    command as an envelope recipient.  Implementations MAY combine
>>>    separate redirects for a given message into a single submission with
>>>    multiple envelope recipients.  (This is not an MUA-style forward,
>>>    which creates a new message with a different sender and message ID,
>>>    wrapping the old message in a new one.)
>>>
>>> And yes, the elimination of the mention of .forward files in 
>>> intentional, as that irked some.
>>>
>>> Are there any objections to the above change?
>>
>> No, but maybe I want to add a requirement to prepend a new 'Received' 
>> field so that a human tracing problems can tell what happened to the 
>> message. Not 100% sure. In some (many?) cases there are enough 
>> Received fields anyway.
>
> Perhaps: SHOULD ensure that there is sufficient information in the 
> chain of 'Received' fields that a human observer can see what happened?

Arnt,
I think this is already covered by existing paragraph in -10 (which 
Philip didn't plan to change):

   The "redirect" action is used to send the message to another user at
   a supplied address, as a mail forwarding feature does.  The
   "redirect" action makes no changes to the message body or existing
   headers, but it may add new headers.  In particular, existing
   Received headers MUST be preserved and the count of Received headers
   in the outgoing message MUST be larger than the same count on the
   message as received by the implementation.  (An implementation that
   adds a Received header before processing the message does not need to
   add another when redirecting.)


From owner-ietf-mta-filters Wed Feb  7 05:07:00 2007
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 l17C6xqt026443
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 7 Feb 2007 05:06:59 -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 l17C6xHY026442;
	Wed, 7 Feb 2007 05:06:59 -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 kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l17C6wk3026436
	for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 05:06:59 -0700 (MST)
	(envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9])
	by kalyani.oryx.com (Postfix) with ESMTP id E57074AC77;
	Wed,  7 Feb 2007 13:06:58 +0100 (CET)
Message-Id: <93rxMqbGUTx6BM1YSwq1fw.md5@libertango.oryx.com>
Date: Wed, 7 Feb 2007 13:07:39 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
Cc: Alexey Melnikov <alexey.melnikov@isode.com>,
        Philip Guenther
  <guenther+mtafilters@sendmail.com>
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>
  <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com>
  <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com>
  <45C9BD6C.6060505@isode.com>
In-Reply-To: <45C9BD6C.6060505@isode.com>
Content-Type: text/plain; format=flowed
MIME-Version: 1.0
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>


Alexey Melnikov writes:
> I think this is already covered by existing paragraph in -10 (which 
> Philip didn't plan to change):
>
>   The "redirect" action is used to send the message to another user at
>   a supplied address, as a mail forwarding feature does.  The
>   "redirect" action makes no changes to the message body or existing
>   headers, but it may add new headers.  In particular, existing
>   Received headers MUST be preserved and the count of Received headers
>   in the outgoing message MUST be larger than the same count on the
>   message as received by the implementation.  (An implementation that
>   adds a Received header before processing the message does not need to
>   add another when redirecting.)

Fine. A 'for' clause is desirable, but I suppose it always is.

Arnt


From owner-ietf-mta-filters Wed Feb  7 06:38:55 2007
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 l17DctCq033854
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 7 Feb 2007 06:38:55 -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 l17DctMp033853;
	Wed, 7 Feb 2007 06:38:55 -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 foon.sendmail.com (smtp-out.sendmail.com [209.246.26.45])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l17Dcss7033847
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 06:38:54 -0700 (MST)
	(envelope-from guenther+mtafilters@sendmail.com)
Received: from [10.201.0.212] (adsl-64-58-1-252.mho.net [64.58.1.252] (may be forged))
	(authenticated bits=0)
	by foon.sendmail.com (Switch-3.2.5/Switch-3.2.0) with ESMTP id l17DcYkj019343
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 7 Feb 2007 05:38:36 -0800
X-DKIM: Sendmail DKIM Filter v0.5.1 foon.sendmail.com l17DcYkj019343
DKIM-Signature: a=rsa-sha1; c=relaxed/simple; d=sendmail.com; s=tls.dkim;
	t=1170855519; bh=EqEA+0Mcp9aiVc3J5jSj3fmlJgA=; h=X-DomainKeys:
	 DomainKey-Signature:Date:From:X-X-Sender:To:cc:Subject:In-Reply-To:
	 Message-ID:References:MIME-Version:Content-Type; b=LO2cewyFDROPXhfN
	P6b7pAMHdeUAKeUKaPXJtI5k3FBMV11NOVBVPiuvixU5AhJ008wED8vSHSZ3/pnegU4
	x7D8BpXDhGw/pq05LpEz4TT6bKcjlP7qJgJUYt4wMtZN5rreAo3aBusUmj8Q3Yf1tJJ
	bOhh0WlOoVHqAhaQ11o0c=
X-DomainKeys: Sendmail DomainKeys Filter v0.4.1 foon.sendmail.com l17DcYkj019343
DomainKey-Signature: a=rsa-sha1; s=tls; d=sendmail.com; c=nofws; q=dns;
	h=date:from:x-x-sender:to:cc:subject:in-reply-to:message-id:
	references:mime-version:content-type;
	b=unKI+WZfjRQ+vDOOD9o125/pcEUEwdkZhAn3fEjKX4uYW+PQWw3kXdmVCInNjepq3
	cNNCA3ank4SVCYqyPFYUJ1HpddiwuephKYlruYW1XEUN3fTuu0MQfZYucMVJ8ZXxhQg
	vN7Y9KGcduibr1on/pwV3bhYKZuKUbatjZ8v8Lc=
Date: Wed, 7 Feb 2007 06:38:33 -0700
From: Philip Guenther <guenther+mtafilters@sendmail.com>
X-X-Sender: guenther@vanye.mho.net
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
cc: ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
In-Reply-To: <93rxMqbGUTx6BM1YSwq1fw.md5@libertango.oryx.com>
Message-ID: <Pine.BSO.4.64.0702070626170.8473@vanye.mho.net>
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net> 
 <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com>  <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com>
  <45C9BD6C.6060505@isode.com> <93rxMqbGUTx6BM1YSwq1fw.md5@libertango.oryx.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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>


On Wed, 7 Feb 2007, Arnt Gulbrandsen wrote:
...
> Fine. A 'for' clause is desirable, but I suppose it always is.

IMHO, if the discussion in RFC 2821 of 'for' clauses and when they should 
or should not be included (c.f. sections 4.4, 7.2, and 7.5) is 
insufficient, then it should be fixed there and not in 3028bis.


Philip Guenther


From owner-ietf-mta-filters Wed Feb  7 06:51:01 2007
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 l17Dp1w3034715
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 7 Feb 2007 06:51:01 -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 l17Dp11D034714;
	Wed, 7 Feb 2007 06:51:01 -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 rufus.isode.com (rufus.isode.com [62.3.217.251])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l17Dp0l7034708
	for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 06:51:00 -0700 (MST)
	(envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) 
          by rufus.isode.com (submission channel) via TCP with ESMTPA 
          id <RcnZQgBXDr1K@rufus.isode.com>; Wed, 7 Feb 2007 13:50:59 +0000
Message-ID: <45C9D92A.7070702@isode.com>
Date: Wed, 07 Feb 2007 13:50:34 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
            Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Philip Guenther <guenther+mtafilters@sendmail.com>
CC: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>  <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com>  <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com>  <45C9BD6C.6060505@isode.com> <93rxMqbGUTx6BM1YSwq1fw.md5@libertango.oryx.com> <Pine.BSO.4.64.0702070626170.8473@vanye.mho.net>
In-Reply-To: <Pine.BSO.4.64.0702070626170.8473@vanye.mho.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>


Philip Guenther wrote:

> On Wed, 7 Feb 2007, Arnt Gulbrandsen wrote:
> ...
>
>> Fine. A 'for' clause is desirable, but I suppose it always is.
>
> IMHO, if the discussion in RFC 2821 of 'for' clauses and when they 
> should or should not be included (c.f. sections 4.4, 7.2, and 7.5) is 
> insufficient, then it should be fixed there and not in 3028bis.

Agreed. IMHO, this is not 3028bis business.


From owner-ietf-mta-filters Wed Feb  7 06:54:49 2007
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 l17DsngE034949
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 7 Feb 2007 06:54:49 -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 l17DsnBs034948;
	Wed, 7 Feb 2007 06:54:49 -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 rufus.isode.com (rufus.isode.com [62.3.217.251])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l17Dsm9H034941
	for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 06:54:49 -0700 (MST)
	(envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) 
          by rufus.isode.com (submission channel) via TCP with ESMTPA 
          id <RcnaHQBXDqhl@rufus.isode.com>; Wed, 7 Feb 2007 13:54:37 +0000
Message-ID: <45C9DA05.3070300@isode.com>
Date: Wed, 07 Feb 2007 13:54:13 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
            Gecko/20050915
X-Accept-Language: en-us, en
To: Philip Guenther <guenther+mtafilters@sendmail.com>
CC: ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>
In-Reply-To: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>


Philip Guenther wrote:

>
>
> There's been some lingering dislike of the description of the redirect 
> action, particularly how it describes the change of envelope 
> recipient. 3028bis-10 removed this sentence
>     The "redirect" modifies the envelope recipient.
>
> as it was observed that it implied that the result of the 'envelope' 
> test would be affected.  With that gone, only the second paragraph 
> actually described how the address in the action was to become an 
> envelope recipient, but it's description is fairly indirect.  So, I 
> propose replacing most of that paragraph, so that instead of reading 
> thusly:
>
>    The redirect command performs an MTA-style "forward"--that is, what
>    you get from a .forward file using sendmail under UNIX.  The address
>    on the [SMTP] envelope is replaced with the one on the redirect
>    command and the message is sent back out.  (This is not an MUA-style
>    forward, which creates a new message with a different sender and
>    message ID, wrapping the old message in a new one.)
>
> it would instead say:
>
>    The message is send back out with the address from the redirect
>    command as an envelope recipient.  Implementations MAY combine
>    separate redirects for a given message into a single submission with
>    multiple envelope recipients.  (This is not an MUA-style forward,
>    which creates a new message with a different sender and message ID,
>    wrapping the old message in a new one.)

Speaking as an individual: No objections from me.

> And yes, the elimination of the mention of .forward files in 
> intentional, as that irked some.
>
>
> Are there any objections to the above change?



From owner-ietf-mta-filters Wed Feb  7 09:13:46 2007
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 l17GDkel046819
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 7 Feb 2007 09:13:46 -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 l17GDk7J046818;
	Wed, 7 Feb 2007 09:13:46 -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 kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l17GDi7n046811
	for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 09:13:45 -0700 (MST)
	(envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9])
	by kalyani.oryx.com (Postfix) with ESMTP id 46A4A4AC6C;
	Wed,  7 Feb 2007 17:13:45 +0100 (CET)
Message-Id: <DJEirQFqnxmv59CfDss2Bw.md5@libertango.oryx.com>
Date: Wed, 7 Feb 2007 17:14:26 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
Cc: Philip Guenther <guenther+mtafilters@sendmail.com>
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>
  <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com>
  <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com>
  <45C9BD6C.6060505@isode.com>
  <93rxMqbGUTx6BM1YSwq1fw.md5@libertango.oryx.com>
  <Pine.BSO.4.64.0702070626170.8473@vanye.mho.net>
In-Reply-To: <Pine.BSO.4.64.0702070626170.8473@vanye.mho.net>
Content-Type: text/plain; format=flowed
MIME-Version: 1.0
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>


Philip Guenther writes:
> On Wed, 7 Feb 2007, Arnt Gulbrandsen wrote:
> ...
>> Fine. A 'for' clause is desirable, but I suppose it always is.
>
> IMHO, if the discussion in RFC 2821 of 'for' clauses and when they 
> should or should not be included (c.f. sections 4.4, 7.2, and 7.5) is 
> insufficient, then it should be fixed there and not in 3028bis.

I could argue that one either way... so let's just use the text you 
proposed earlier today.

Arnt


From owner-ietf-mta-filters Wed Feb  7 13:43:12 2007
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 l17KhCfQ066529
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 7 Feb 2007 13:43:12 -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 l17KhCWx066528;
	Wed, 7 Feb 2007 13:43:12 -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 shell.mv.net (osmium.mv.net [199.125.85.152])
	by balder-227.proper.com (8.13.5/8.13.5) with SMTP id l17KhAad066521
	for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 13:43:11 -0700 (MST)
	(envelope-from mem@mv.mv.com)
Received: (qmail 30811 invoked by uid 101); 7 Feb 2007 15:43:08 -0500
From: "Mark E. Mallett" <mem@mv.mv.com>
Date: Wed, 7 Feb 2007 15:43:08 -0500
To: Philip Guenther <guenther+mtafilters@sendmail.com>
Cc: ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
Message-ID: <20070207204308.GA26384@osmium.mv.net>
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>
User-Agent: Mutt/1.4.2.1i
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>


On Tue, Feb 06, 2007 at 05:26:16PM -0700, Philip Guenther wrote:


> it would instead say:
> 
>    The message is send back out with the address from the redirect
>    command as an envelope recipient.  Implementations MAY combine
>    separate redirects for a given message into a single submission with
>    multiple envelope recipients.  (This is not an MUA-style forward,
>    which creates a new message with a different sender and message ID,
>    wrapping the old message in a new one.)
> 
> And yes, the elimination of the mention of .forward files in intentional, 
> as that irked some.

(yay!)


> Are there any objections to the above change?

Only that you should replace "send" with "sent" ("The message is sent...").
Otherwise fine.

mm


From owner-ietf-mta-filters Wed Feb  7 14:48:42 2007
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 l17LmgoZ070929
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 7 Feb 2007 14:48:42 -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 l17LmgxI070928;
	Wed, 7 Feb 2007 14:48:42 -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 shell.mv.net (osmium.mv.net [199.125.85.152])
	by balder-227.proper.com (8.13.5/8.13.5) with SMTP id l17LmeZp070920
	for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 14:48:41 -0700 (MST)
	(envelope-from mem@mv.mv.com)
Received: (qmail 55771 invoked by uid 101); 7 Feb 2007 16:48:40 -0500
From: "Mark E. Mallett" <mem@mv.mv.com>
Date: Wed, 7 Feb 2007 16:48:40 -0500
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, ietf-mta-filters@imc.org,
        Philip Guenther <guenther+mtafilters@sendmail.com>
Subject: Re: 3028bis, section 4.2, paragraph 2
Message-ID: <20070207214840.GB26384@osmium.mv.net>
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net> <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com> <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com> <45C9BD6C.6060505@isode.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <45C9BD6C.6060505@isode.com>
User-Agent: Mutt/1.4.2.1i
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>


On Wed, Feb 07, 2007 at 11:52:12AM +0000, Alexey Melnikov wrote:
> 
> Arnt Gulbrandsen wrote:
> >
> >Perhaps: SHOULD ensure that there is sufficient information in the 
> >chain of 'Received' fields that a human observer can see what happened?
> 
> Arnt,
> I think this is already covered by existing paragraph in -10 (which 
> Philip didn't plan to change):
> 
>   The "redirect" action is used to send the message to another user at
>   a supplied address, as a mail forwarding feature does.  The
>   "redirect" action makes no changes to the message body or existing
>   headers, but it may add new headers.  In particular, existing
>   Received headers MUST be preserved and the count of Received headers
>   in the outgoing message MUST be larger than the same count on the
>   message as received by the implementation.  (An implementation that
>   adds a Received header before processing the message does not need to
>   add another when redirecting.)

That's interesting, I didn't notice that change.  That does mandate the
addition of a Received by (or as of) the time a redirect is done.  It
also implies that adding a Received line is at least discussed elsewhere
in the document, which it isn't (other than a casual mention in loop
control).  Maybe that's picky, but if the addition of a Received line is
alluded to, perhaps it should be discussed.  For example, there could
be a recommendation that an implementation "adds a Received header before
processing the message" -- but then is this considered part of the
original message?  e.g. as applied to the 'editheader' mandate that

    if an error terminates processing of the script, the original
    message header MUST be used when doing the implicit keep required by
    [SIEVE] section 2.10.6.

where I think it could be argued that such an added "Received" line
would be valuable to preserve.  (as would, I think, other annotating
information, but I've said that before: I think that that editheader
prohibition is too broad since it reaches beyond changes made by
editheader, but I seem to be the only one who thinks that.)

The new language that "Received headers MUST be preserved" also implies
that the removal of any Received headers via an extension (e.g.
'editheader') must be ignored for the redirect.  Is that the intent?  I
dunno whether I think that's good -- I probably do, but it certainly
means more special-case work for me :)

mm  (yes, I kind of got off on a tangent)


From owner-ietf-mta-filters Wed Feb  7 21:21:56 2007
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 l184LtET092950
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 7 Feb 2007 21:21:56 -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 l184Lt3F092949;
	Wed, 7 Feb 2007 21:21:55 -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 e-nvb.com (e-nvb.com [69.27.17.200] (may be forged))
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l184LsnK092943
	for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 21:21:55 -0700 (MST)
	(envelope-from guenther+mtafilters@sendmail.com)
Received: from [10.0.67.61] (unknown [71.39.21.73])
	by e-nvb.com (Postfix) with ESMTP id C34F5183810;
	Thu,  8 Feb 2007 04:20:16 -0700 (MST)
Date: Wed, 7 Feb 2007 21:21:49 -0700
From: Philip Guenther <guenther+mtafilters@sendmail.com>
X-X-Sender: guenther@vanye.mho.net
To: "Mark E. Mallett" <mem@mv.mv.com>
cc: ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
In-Reply-To: <20070207214840.GB26384@osmium.mv.net>
Message-ID: <Pine.BSO.4.64.0702071947160.14328@vanye.mho.net>
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>
 <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com> <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com>
 <45C9BD6C.6060505@isode.com> <20070207214840.GB26384@osmium.mv.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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>



Mark Mallett wrote, in regards to this text in 3028bis-10, section 4.2:
    <...>  In particular, existing
    Received headers MUST be preserved and the count of Received headers
    in the outgoing message MUST be larger than the same count on the
    message as received by the implementation.  (An implementation that
    adds a Received header before processing the message does not need to
    add another when redirecting.)

...
> That's interesting, I didn't notice that change.  That does mandate the
> addition of a Received by (or as of) the time a redirect is done.  It
> also implies that adding a Received line is at least discussed elsewhere
> in the document, which it isn't (other than a casual mention in loop
> control).  Maybe that's picky, but if the addition of a Received line is
> alluded to, perhaps it should be discussed.  For example, there could
> be a recommendation that an implementation "adds a Received header before
> processing the message" -- but then is this considered part of the
> original message?

I don't get what's unclear about this.  If the addition was made "before 
processing the message", then by definition the message being processed 
has the added header field.

Oh, and the phrase "original message" is used exactly once in 3028bis-10, 
where it says that the envelope sender of a redirected messaage "MAY be 
copied from the original message".  I'll change that to say "MAY be copied 
from the message being processed" to kill that phrase completely from 
3028bis.

I'd like to stress that the *critical* thing in that paragraph is the bit 
about "count of 'received's MUST be higher", as that's what provides a way 
to break loops.  If the parenthetical comment about implementations that 
do things a particular way raises more issues than it clarifies, then the 
correct action at this point is to *remove* the comment.


> e.g. as applied to the 'editheader' mandate that
>    if an error terminates processing of the script, the original
>    message header MUST be used when doing the implicit keep required by
>    [SIEVE] section 2.10.6.
> where I think it could be argued that such an added "Received" line
> would be valuable to preserve.

In the context of 'editheader', I think it's clear that "the original 
message" just means "the message as it was before any addheader or 
deleteheader actions were processed".  If you disagree about that being 
clear, well, suggest text for editheader...but that doesn't affect this 
discussion of 3028bis.


> The new language that "Received headers MUST be preserved" also implies
> that the removal of any Received headers via an extension (e.g.
> 'editheader') must be ignored for the redirect.  Is that the intent?  I
> dunno whether I think that's good -- I probably do, but it certainly
> means more special-case work for me :)

An excellent question, but again, one that should be raised against 
editheader and not 3028bis.

(I'm not sure either what the Right Thing is.  I'll note that editheader 
could override 3028bis, just as body overrides variables.  The key 
procedural requirement, I think, would be the inclusion of "Updates: 
3028bis" on the title page of editheader.)


I hope I'm not coming across as trying to dodge the issues here.  I just 
feel we need to "keep our eyes on the prize": getting 3028bis published. 
It's what, 2 years late, by the original schedule?  Issues that 3028bis 
raises in other documents should be left to those other documents, even if 
they've been last called.  If it's a general mail agent issue and not 
specific to sieve, then perhaps it belongs in 2821bis or 2822bis ...or in 
a completely new I-D.


Philip Guenther


From owner-ietf-mta-filters Thu Feb  8 04:04:52 2007
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 l18B4pBe019358
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 8 Feb 2007 04:04: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 l18B4p0R019357;
	Thu, 8 Feb 2007 04:04:51 -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 rufus.isode.com (rufus.isode.com [62.3.217.251])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l18B4oCk019345
	for <ietf-mta-filters@imc.org>; Thu, 8 Feb 2007 04:04:50 -0700 (MST)
	(envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) 
          by rufus.isode.com (submission channel) via TCP with ESMTPA 
          id <RcsDzwBXDqp0@rufus.isode.com>; Thu, 8 Feb 2007 11:04:48 +0000
Message-ID: <45CB03B6.3030500@isode.com>
Date: Thu, 08 Feb 2007 11:04:22 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
            Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before
         sending         it to IESG
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com>
In-Reply-To: <45C753CF.7080906@isode.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>


Alexey Melnikov wrote:

> Internet-Drafts@ietf.org wrote:
>
>> http://www.ietf.org/internet-drafts/draft-ietf-sieve-3028bis-10.txt
>
> Folks,
> This is your last chance to review that the document is correct and 
> complete. No new issues can be raised at this stage unless they are 
> very serious.

Clarification: no editorial changes will be accepted at this stage 
without any concrete text. Thanks.

> Please review the document by the end of February 11th. Cyrus and I 
> are planning to send it to IESG soon after February 11th.

> Regards,
> Alexey and Cyrus.



From owner-ietf-mta-filters Thu Feb  8 04:18:32 2007
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 l18BIWiG020812
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 8 Feb 2007 04:18:32 -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 l18BIWk5020811;
	Thu, 8 Feb 2007 04:18:32 -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 rufus.isode.com (rufus.isode.com [62.3.217.251])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l18BITEI020803
	for <ietf-mta-filters@imc.org>; Thu, 8 Feb 2007 04:18:30 -0700 (MST)
	(envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) 
          by rufus.isode.com (submission channel) via TCP with ESMTPA 
          id <RcsHAQBXDnHO@rufus.isode.com>; Thu, 8 Feb 2007 11:18:26 +0000
Message-ID: <45CB06E7.40104@isode.com>
Date: Thu, 08 Feb 2007 11:17:59 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
            Gecko/20050915
X-Accept-Language: en-us, en
To: Philip Guenther <guenther+mtafilters@sendmail.com>
CC: "Mark E. Mallett" <mem@mv.mv.com>, ietf-mta-filters@imc.org
Subject: Interaction between redirect and editheader
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net> <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com> <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com> <45C9BD6C.6060505@isode.com> <20070207214840.GB26384@osmium.mv.net> <Pine.BSO.4.64.0702071947160.14328@vanye.mho.net>
In-Reply-To: <Pine.BSO.4.64.0702071947160.14328@vanye.mho.net>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>


Philip Guenther wrote:

>> e.g. as applied to the 'editheader' mandate that
>>    if an error terminates processing of the script, the original
>>    message header MUST be used when doing the implicit keep required by
>>    [SIEVE] section 2.10.6.
>> where I think it could be argued that such an added "Received" line
>> would be valuable to preserve.
>
> In the context of 'editheader', I think it's clear that "the original 
> message" just means "the message as it was before any addheader or 
> deleteheader actions were processed".  If you disagree about that 
> being clear, well, suggest text for editheader...

I would just remind people that WGLC for editheader has ended as well. 
Cyrus and I are planning to request its publication next week.

So at this point we need specific text.

> but that doesn't affect this discussion of 3028bis.
>
>> The new language that "Received headers MUST be preserved" also implies
>> that the removal of any Received headers via an extension (e.g.
>> 'editheader') must be ignored for the redirect.  Is that the intent?
>
I don't think this was the intent.

>>  I dunno whether I think that's good -- I probably do, but it certainly
>> means more special-case work for me :)
>
> An excellent question, but again, one that should be raised against 
> editheader and not 3028bis.
>
> (I'm not sure either what the Right Thing is.  I'll note that 
> editheader could override 3028bis, just as body overrides variables.

Indeed. It is somewhat difficult to put normative requirements on future 
document (or in this case on a document that gets published later).

> The key procedural requirement, I think, would be the inclusion of 
> "Updates: 3028bis" on the title page of editheader.

Yes, go for it! :-)

> )



From owner-ietf-mta-filters Thu Feb  8 04:21:40 2007
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 l18BLekB021093
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 8 Feb 2007 04:21:40 -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 l18BLea3021092;
	Thu, 8 Feb 2007 04:21:40 -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 rufus.isode.com (rufus.isode.com [62.3.217.251])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l18BLZwY021085
	for <ietf-mta-filters@imc.org>; Thu, 8 Feb 2007 04:21:38 -0700 (MST)
	(envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) 
          by rufus.isode.com (submission channel) via TCP with ESMTPA 
          id <RcsHuwBXDrDj@rufus.isode.com>; Thu, 8 Feb 2007 11:21:31 +0000
Message-ID: <45CB07A2.9000302@isode.com>
Date: Thu, 08 Feb 2007 11:21:06 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
            Gecko/20050915
X-Accept-Language: en-us, en
To: ietf-mta-filters@imc.org
Subject: Let's get 3028bis published
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net> <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com> <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com> <45C9BD6C.6060505@isode.com> <20070207214840.GB26384@osmium.mv.net> <Pine.BSO.4.64.0702071947160.14328@vanye.mho.net>
In-Reply-To: <Pine.BSO.4.64.0702071947160.14328@vanye.mho.net>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>


Philip Guenther wrote:

> I hope I'm not coming across as trying to dodge the issues here.  I 
> just feel we need to "keep our eyes on the prize": getting 3028bis 
> published.

Yes, we are way beyond our originally intended publication date.

> It's what, 2 years late, by the original schedule?  Issues that 
> 3028bis raises in other documents should be left to those other 
> documents, even if they've been last called.  If it's a general mail 
> agent issue and not specific to sieve, then perhaps it belongs in 
> 2821bis or 2822bis ...or in a completely new I-D.

Agreed.


From owner-ietf-mta-filters Thu Feb  8 16:11:52 2007
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 l18NBqR2081623
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 8 Feb 2007 16:11: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 l18NBqER081620;
	Thu, 8 Feb 2007 16:11: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 shell.mv.net (osmium.mv.net [199.125.85.152])
	by balder-227.proper.com (8.13.5/8.13.5) with SMTP id l18NBmbQ081610
	for <ietf-mta-filters@imc.org>; Thu, 8 Feb 2007 16:11:50 -0700 (MST)
	(envelope-from mem@mv.mv.com)
Received: (qmail 58873 invoked by uid 101); 8 Feb 2007 18:11:47 -0500
From: "Mark E. Mallett" <mem@mv.mv.com>
Date: Thu, 8 Feb 2007 18:11:47 -0500
To: Philip Guenther <guenther+mtafilters@sendmail.com>
Cc: "Mark E. Mallett" <mem@mv.mv.com>, ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
Message-ID: <20070208231147.GA49702@osmium.mv.net>
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net> <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com> <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com> <45C9BD6C.6060505@isode.com> <20070207214840.GB26384@osmium.mv.net> <Pine.BSO.4.64.0702071947160.14328@vanye.mho.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.BSO.4.64.0702071947160.14328@vanye.mho.net>
User-Agent: Mutt/1.4.2.1i
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>


On Wed, Feb 07, 2007 at 09:21:49PM -0700, Philip Guenther wrote:
> 
> Mark Mallett wrote, in regards to this text in 3028bis-10, section 4.2:

 ...


> I'd like to stress that the *critical* thing in that paragraph is the bit 
> about "count of 'received's MUST be higher", as that's what provides a way 
> to break loops.

Ah... I didn't get that connection at all.  OK, there is the text later
in that section:

   Implementations SHOULD take measures to implement loop control,
   possibly including adding headers to the message or counting Received
   headers.

So it sounds like you are saying that the new text about how the count
of Received headers MUST be larger is connected to that.  That since
some implementations may choose to count Received lines to avoid loops,
all implementations must have a higher Received line count when doing
redirect.  I don't see that as a valid prescription, I think that the
"take measures to implement loop control" is enough (especially since I
don't really think that Received-line counting is all that great a
technique).

I don't mean to be anal (other than it coming naturally, perhaps),
but I just don't see that as a valid justification for the MUST.
(Even though I am in favor of implementations adding a Received line.)

  ...

> I hope I'm not coming across as trying to dodge the issues here.

And again I hope I'm not being a pain.  However the text I commented on
is new as of -10, so it seems [more] reasonable to comment on it.  It
may be that everyone decides it's a non-issue... so be it.

At any rate I feel conflicted:  I like the idea of recommending that
implementations add a Received line, but not in the "redirect" section.
Evidently it's too late for that.  I not wild about the new MUST in the
redirect section, especially now having learned that its only reason for
being there is for loop control.  (I could probably even imagine good
reasons for removing some Received lines prior to redirect-- but I
dunno.)

My 2c...

-mm-


From owner-ietf-mta-filters Thu Feb  8 17:44:25 2007
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 l190iPaw087712
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 8 Feb 2007 17:44:25 -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 l190iPQu087711;
	Thu, 8 Feb 2007 17:44:25 -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 smtp110.plus.mail.mud.yahoo.com (smtp110.plus.mail.mud.yahoo.com [68.142.206.243])
	by balder-227.proper.com (8.13.5/8.13.5) with SMTP id l190iNd3087705
	for <ietf-mta-filters@imc.org>; Thu, 8 Feb 2007 17:44:24 -0700 (MST)
	(envelope-from tjs@psaux.com)
Received: (qmail 39384 invoked from network); 9 Feb 2007 00:44:15 -0000
Received: from unknown (HELO ?172.21.103.31?) (ts4z@216.145.49.15 with plain)
  by smtp110.plus.mail.mud.yahoo.com with SMTP; 9 Feb 2007 00:44:14 -0000
X-YMail-OSG: H1e2RWsVM1l_uYeidhv6GP5UwTQ9Up5m4Fw2_CsxmT85ZYGB5qjeo0kikSbaHYFu4GCUes6jSjEt65.8187Rasp2zaSSs4BMMH0yNbKhQk_kKHLdyY_XQ4YDltA94iCBS.li3pjJZzYVJShVRLqLmA1UbrzRhCUxNYzxA8h0Qx2FNc2o_E4QCxP7OMLl
Message-ID: <45CBC3DD.3010805@psaux.com>
Date: Thu, 08 Feb 2007 16:44:13 -0800
From: Tim Showalter <tjs@psaux.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: "Mark E. Mallett" <mem@mv.mv.com>
CC: Philip Guenther <guenther+mtafilters@sendmail.com>,
        ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net> <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com> <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com> <45C9BD6C.6060505@isode.com> <20070207214840.GB26384@osmium.mv.net> <Pine.BSO.4.64.0702071947160.14328@vanye.mho.net> <20070208231147.GA49702@osmium.mv.net>
In-Reply-To: <20070208231147.GA49702@osmium.mv.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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>


Mark E. Mallett wrote:
> So it sounds like you are saying that the new text about how the count
> of Received headers MUST be larger is connected to that.  That since
> some implementations may choose to count Received lines to avoid loops,
> all implementations must have a higher Received line count when doing
> redirect.

If two (or more) implementations are configured to loop, just one adds 
Received headers and uses them for loop control, that's enough to stop 
the loop.

I can't imagine why anyone wouldn't add Received anyway, just based on 
advice in 2821 (and common sense).

Tim


From owner-ietf-mta-filters Thu Feb  8 22:04:55 2007
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 l1954t7C002501
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 8 Feb 2007 22:04:55 -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 l1954tKl002500;
	Thu, 8 Feb 2007 22:04:55 -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 foon.sendmail.com (smtp-out.sendmail.com [209.246.26.45])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l1954sO7002493
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-mta-filters@imc.org>; Thu, 8 Feb 2007 22:04:54 -0700 (MST)
	(envelope-from guenther+mtafilters@sendmail.com)
Received: from [10.201.0.240] (adsl-64-58-1-252.mho.net [64.58.1.252] (may be forged))
	(authenticated bits=0)
	by foon.sendmail.com (Switch-3.2.5/Switch-3.2.0) with ESMTP id l1954hBw008413
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 8 Feb 2007 21:04:46 -0800
X-DKIM: Sendmail DKIM Filter v0.5.1 foon.sendmail.com l1954hBw008413
DKIM-Signature: a=rsa-sha1; c=relaxed/simple; d=sendmail.com; s=tls.dkim;
	t=1170997488; bh=+ce7K4J8CBOh58zrI8huTF6hPUc=; h=X-DomainKeys:
	 DomainKey-Signature:Date:From:X-X-Sender:To:cc:Subject:In-Reply-To:
	 Message-ID:References:MIME-Version:Content-Type; b=AIpDNdyPjY3t5zWV
	jizaI3JkS+eH1s6VkJtDjJ3iUB34qEdNgN9V5noft8bU1c3KB4+KMl6GVCJ0fIR+O3P
	hwdT40pRyw+uO5hm7uZlX8hUQwlGUBoiZhoRb/Eyuko1WkXtvv1+n840+4Ao+fzx+8w
	7AUPqwkzoFRc0NvXDOd2g=
X-DomainKeys: Sendmail DomainKeys Filter v0.4.1 foon.sendmail.com l1954hBw008413
DomainKey-Signature: a=rsa-sha1; s=tls; d=sendmail.com; c=nofws; q=dns;
	h=date:from:x-x-sender:to:cc:subject:in-reply-to:message-id:
	references:mime-version:content-type;
	b=l25bTeYxc8hyOAYM2lMswBrQJQAmuEyOVFy5IqDxPrpr2Ys0FJZL5fzbfjZvY10Iq
	C6SXOwNGuCSNGYuGCJax6nSThPIRqtnap7TkVOZsJ+5uOhrLQb9OlFIikvkHBUInEqa
	HUvayi5e8UkPc9h4yaTaqETalQ8ZvSIe8ZlYxNU=
Date: Thu, 8 Feb 2007 22:04:40 -0700
From: Philip Guenther <guenther+mtafilters@sendmail.com>
X-X-Sender: guenther@vanye.mho.net
To: Tim Showalter <tjs@psaux.com>
cc: "Mark E. Mallett" <mem@mv.mv.com>, ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
In-Reply-To: <45CBC3DD.3010805@psaux.com>
Message-ID: <Pine.BSO.4.64.0702082146060.1973@vanye.mho.net>
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>
 <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com> <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com>
 <45C9BD6C.6060505@isode.com> <20070207214840.GB26384@osmium.mv.net>
 <Pine.BSO.4.64.0702071947160.14328@vanye.mho.net> <20070208231147.GA49702@osmium.mv.net>
 <45CBC3DD.3010805@psaux.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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>


On Thu, 8 Feb 2007, Tim Showalter wrote:
> Mark E. Mallett wrote:
>> So it sounds like you are saying that the new text about how the count
>> of Received headers MUST be larger is connected to that.  That since
>> some implementations may choose to count Received lines to avoid loops,
>> all implementations must have a higher Received line count when doing
>> redirect.

Yes.  That seemed to be the list concensus, based on the thread with 
subject "Comments on draft-ietf-sieve-3028bis-09 from Eric Rescorla" at 
the beginning of November.  I didn't see any one arguing against mandating 
the addition of Received header fields by 'redirect' back then, so I took 
it to be agreed.


> If two (or more) implementations are configured to loop, just one adds 
> Received headers and uses them for loop control, that's enough to stop the 
> loop.

Yes, but if just one implementation (in the "code base" sense) does _not_ 
add Received header fields and it is installed at multiple site, then it 
can sustain a loop.  Heck, an implementation with no loop control can be a 
mailbomb generator if it supports multiple redirects for a single message: 
it would just a sieve script that redirects to its own address as well as 
the victim address.


> I can't imagine why anyone wouldn't add Received anyway, just based on 
> advice in 2821 (and common sense).

Common sense is as common as a sense of humor, apparently.  (References to 
solving the Halting Problem were removed from 3028bis after multiple 
reviewers expressed their dislike for the text.)


Philip Guenther


From owner-ietf-mta-filters Mon Feb 12 04:20:30 2007
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 l1CBKUDo015441
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 12 Feb 2007 04:20:30 -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 l1CBKUhh015440;
	Mon, 12 Feb 2007 04:20:30 -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 rufus.isode.com (rufus.isode.com [62.3.217.251])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l1CBKQmn015434
	for <ietf-mta-filters@imc.org>; Mon, 12 Feb 2007 04:20:27 -0700 (MST)
	(envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) 
          by rufus.isode.com (submission channel) via TCP with ESMTPA 
          id <RdBNcQBXDl4R@rufus.isode.com>; Mon, 12 Feb 2007 11:20:19 +0000
Message-ID: <45CE71B2.9050008@isode.com>
Date: Sun, 11 Feb 2007 01:30:26 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
            Gecko/20050915
X-Accept-Language: en-us, en
To: Dilyan Palauzov <Dilyan.Palauzov@aegee.org>
CC: ietf-mta-filters@imc.org
Subject: Re: the notify issues
References: <20070127220648.ufdeeeu4socwwgss@mail.aegee.org>
In-Reply-To: <20070127220648.ufdeeeu4socwwgss@mail.aegee.org>
MIME-version: 1.0
Content-type: text/plain; charset="UTF-8"; format="flowed"
Content-transfer-encoding: 7bit
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>


Dilyan Palauzov wrote:

>> Issue #6
>> "send notification over XMPP, if can be delivered immediately.  
>> Otherwise send it over SMS"
>
 [...]

>   2). Keep the existing syntax. A new "stackable" notification method
>   can be specified that will perform the desired functionality.
>
> I do not get what means "stackable notification".

I meant a new notification mechanism which tries to deliver notification 
using different mechanisms.
E.g. something [horrible] like:
 <stack:mech1=xmpp:me@example.org:...;mech2=sms:...>



From owner-ietf-mta-filters Mon Feb 12 04:20:32 2007
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 l1CBKWqS015450
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 12 Feb 2007 04:20:32 -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 l1CBKWu5015449;
	Mon, 12 Feb 2007 04:20:32 -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 rufus.isode.com (rufus.isode.com [62.3.217.251])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l1CBKVYY015443
	for <ietf-mta-filters@imc.org>; Mon, 12 Feb 2007 04:20:31 -0700 (MST)
	(envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) 
          by rufus.isode.com (submission channel) via TCP with ESMTPA 
          id <RdBNewBXDnwW@rufus.isode.com>; Mon, 12 Feb 2007 11:20:28 +0000
Message-ID: <45CF9E11.4080407@isode.com>
Date: Sun, 11 Feb 2007 22:52:01 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
            Gecko/20050915
X-Accept-Language: en-us, en
To: Dilyan Palauzov <Dilyan.Palauzov@aegee.org>
CC: ietf-mta-filters@imc.org
Subject: Re: the notify issues
References: <20070127220648.ufdeeeu4socwwgss@mail.aegee.org>
In-Reply-To: <20070127220648.ufdeeeu4socwwgss@mail.aegee.org>
MIME-version: 1.0
Content-type: text/plain; charset="UTF-8"; format="flowed"
Content-transfer-encoding: 7bit
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>


Dilyan Palauzov wrote:

>> Issue #6
>> "send notification over XMPP, if can be delivered immediately.  
>> Otherwise send it over SMS"
>
> I am in favour of:
>
>   1). Add a test to check if a notification method (specified
>   as an URI) can deliver the notification immediately.

I've done this part.

>   1)  Add a test to check if a notification method (specified
>   as an URI) HAS delieverED the notification immediately.
>
> Expanations: for sending an SMS, or mail it cannot be said if the  
> message can be delivered immediately, as it depends on many things,  
> and even if a notification can be delivered during the test, this 
> does  not mean that it is delivered delivered immediately at a later 
> point,  when the notification is send. On the other side, if an SMS of 
> mail is  send, an acknowledgement can be requested, that the 
> notification is  read/delivered. Naturally, this will mean that the 
> interpreter has to  stop for certain time, like 10s, and wait for the 
> acknowledgement.

I don't particularly like this part of your suggestion. In particular 
because many implementations don't send a notification when a notify 
action is called, they defer sending the notification till after the 
script evaluation is complete and can do this asynchronously.

What you suggest will also block message delivery, which might be 
inacceptable for some deployments.



From owner-ietf-mta-filters Mon Feb 12 04:41:12 2007
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 l1CBfCsM017934
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 12 Feb 2007 04:41:12 -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 l1CBfCix017933;
	Mon, 12 Feb 2007 04:41:12 -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 kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l1CBfBXf017921
	for <ietf-mta-filters@imc.org>; Mon, 12 Feb 2007 04:41:12 -0700 (MST)
	(envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9])
	by kalyani.oryx.com (Postfix) with ESMTP id C2DA24AC7B;
	Mon, 12 Feb 2007 12:41:11 +0100 (CET)
Message-Id: <G8wtYd+grNHX3HjfTihV7A.md5@libertango.oryx.com>
Date: Mon, 12 Feb 2007 12:42:17 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-mta-filters@imc.org
Subject: Re: the notify issues
Cc: Alexey Melnikov <alexey.melnikov@isode.com>,
        Dilyan Palauzov
  <Dilyan.Palauzov@aegee.org>
References: <20070127220648.ufdeeeu4socwwgss@mail.aegee.org>
  <45CF9E11.4080407@isode.com>
In-Reply-To: <45CF9E11.4080407@isode.com>
Content-Type: text/plain; format=flowed
MIME-Version: 1.0
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>


Alexey Melnikov writes:
> I don't particularly like this part of your suggestion. In particular 
> because many implementations don't send a notification when a notify 
> action is called, they defer sending the notification till after the 
> script evaluation is complete and can do this asynchronously.

Makes sense.

But please add some text that long delays are best avoided, particularly 
for scripts that use the new 'can deliver immediately' test. 0.1 
seconds is not a problem, but the ability to deliver immediately could 
easily change in 10 seconds.

Arnt


From owner-ietf-mta-filters Wed Feb 14 13:50:05 2007
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 l1EKo5do084047
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 14 Feb 2007 13:50:05 -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 l1EKo5mF084045;
	Wed, 14 Feb 2007 13:50:05 -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 ns1.neustar.com (ns1.neustar.com [156.154.16.138])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l1EKo271084023
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-mta-filters@imc.org>; Wed, 14 Feb 2007 13:50:05 -0700 (MST)
	(envelope-from ietf@ietf.org)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10])
	by ns1.neustar.com (Postfix) with ESMTP id 01A8026F0B;
	Wed, 14 Feb 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HHR4j-0004JL-S0; Wed, 14 Feb 2007 15:50:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: ietf-mta-filters@imc.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-sieve-3028bis-11.txt 
Message-Id: <E1HHR4j-0004JL-S0@stiedprstage1.ietf.org>
Date: Wed, 14 Feb 2007 15:50:01 -0500
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>


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

	Title		: Sieve: An Email Filtering Language
	Author(s)	: T. Showalter, P. Guenther
	Filename	: draft-ietf-sieve-3028bis-11.txt
	Pages		: 44
	Date		: 2007-2-14
	
This document describes a language for filtering email messages at
   time of final delivery.  It is designed to be implementable on either
   a mail client or mail server.  It is meant to be extensible, simple,
   and independent of access protocol, mail architecture, and operating
   system.  It is suitable for running on a mail server where users may
   not be allowed to execute arbitrary programs, such as on black box
   Internet Message Access Protocol (IMAP) servers, as the base language
   has no variables, loops, or ability to shell out to external
   programs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-3028bis-11.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sieve-3028bis-11.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sieve-3028bis-11.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2007-2-14121956.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sieve-3028bis-11.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sieve-3028bis-11.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2007-2-14121956.I-D@ietf.org>

--OtherAccess--

--NextPart--


From owner-ietf-mta-filters Thu Feb 15 16:50:03 2007
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 l1FNo3GA098794
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 15 Feb 2007 16:50:03 -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 l1FNo392098793;
	Thu, 15 Feb 2007 16:50:03 -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 ns4.neustar.com (ns4.neustar.com [156.154.24.139])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l1FNo2Ah098787
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-mta-filters@imc.org>; Thu, 15 Feb 2007 16:50:03 -0700 (MST)
	(envelope-from ietf@ietf.org)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10])
	by ns4.neustar.com (Postfix) with ESMTP id 41F632AD74;
	Thu, 15 Feb 2007 23:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HHqMU-0003gr-0f; Thu, 15 Feb 2007 18:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: ietf-mta-filters@imc.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-sieve-3028bis-12.txt 
Message-Id: <E1HHqMU-0003gr-0f@stiedprstage1.ietf.org>
Date: Thu, 15 Feb 2007 18:50:02 -0500
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>


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

	Title		: Sieve: An Email Filtering Language
	Author(s)	: T. Showalter, P. Guenther
	Filename	: draft-ietf-sieve-3028bis-12.txt
	Pages		: 44
	Date		: 2007-2-15
	
This document describes a language for filtering email messages at
   time of final delivery.  It is designed to be implementable on either
   a mail client or mail server.  It is meant to be extensible, simple,
   and independent of access protocol, mail architecture, and operating
   system.  It is suitable for running on a mail server where users may
   not be allowed to execute arbitrary programs, such as on black box
   Internet Message Access Protocol (IMAP) servers, as the base language
   has no variables, loops, or ability to shell out to external
   programs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-3028bis-12.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sieve-3028bis-12.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sieve-3028bis-12.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2007-2-15152316.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sieve-3028bis-12.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sieve-3028bis-12.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2007-2-15152316.I-D@ietf.org>

--OtherAccess--

--NextPart--


From owner-ietf-mta-filters Wed Feb 21 08:50:08 2007
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 l1LFo88h046445
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 21 Feb 2007 08:50:08 -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 l1LFo8cf046442;
	Wed, 21 Feb 2007 08:50:08 -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 ns1.neustar.com (ns1.neustar.com [156.154.16.138])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l1LFo6XE046427
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-mta-filters@imc.org>; Wed, 21 Feb 2007 08:50:07 -0700 (MST)
	(envelope-from ietf@ietf.org)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10])
	by ns1.neustar.com (Postfix) with ESMTP id 629F026ED1;
	Wed, 21 Feb 2007 15:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HJtjG-0008T7-6Q; Wed, 21 Feb 2007 10:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: ietf-mta-filters@imc.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-sieve-notify-07.txt 
Message-Id: <E1HJtjG-0008T7-6Q@stiedprstage1.ietf.org>
Date: Wed, 21 Feb 2007 10:50:02 -0500
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>


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

	Title		: Sieve Extension: Notifications
	Author(s)	: A. Melnikov, et al.
	Filename	: draft-ietf-sieve-notify-07.txt
	Pages		: 18
	Date		: 2007-2-21
	
Users go to great lengths to be notified as quickly as possible that
   they have received new mail.  Most of these methods involve polling
   to check for new messages periodically.  A push method handled by the
   final delivery agent gives users quicker notifications and saves
   server resources.  This document does not specify the notification
   method but it is expected that using existing instant messaging
   infrastructure such as XMPP, or SMS messages will be popular.  This
   draft describes an extension to the Sieve mail filtering language
   that allows users to give specific rules for how and when
   notifications should be sent.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-notify-07.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sieve-notify-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sieve-notify-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2007-2-21084907.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sieve-notify-07.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sieve-notify-07.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2007-2-21084907.I-D@ietf.org>

--OtherAccess--

--NextPart--


From owner-ietf-mta-filters Wed Feb 21 09:27:17 2007
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 l1LGRHX0049498
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 21 Feb 2007 09:27:17 -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 l1LGRHOk049497;
	Wed, 21 Feb 2007 09:27:17 -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 rufus.isode.com (rufus.isode.com [62.3.217.251])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l1LGRElj049490
	for <ietf-mta-filters@imc.org>; Wed, 21 Feb 2007 09:27:17 -0700 (MST)
	(envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) 
          by rufus.isode.com (submission channel) via TCP with ESMTPA 
          id <Rdxy4QAgG4NY@rufus.isode.com>; Wed, 21 Feb 2007 16:27:13 +0000
Message-ID: <45DC72C2.4080507@isode.com>
Date: Wed, 21 Feb 2007 16:26:42 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
            Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-mta-filters@imc.org
Subject: Request for agenda items for the Sieve WG meeting in Prague
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>


Please send your requests directly to me or just reply to this message.

Also, I would like to ask people to let me know who is planning to come 
to the Sieve WG meeting in Prague. (Ignore this, if you've already told me).

Thanks,
Alexey, Sieve WG co-chair


From owner-ietf-mta-filters Mon Feb 26 04:41:41 2007
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 l1QBffQE055103
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 26 Feb 2007 04:41:41 -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 l1QBff0M055102;
	Mon, 26 Feb 2007 04:41:41 -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 rufus.isode.com (rufus.isode.com [62.3.217.251])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l1QBfdpK055094
	for <ietf-mta-filters@imc.org>; Mon, 26 Feb 2007 04:41:40 -0700 (MST)
	(envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) 
          by rufus.isode.com (submission channel) via TCP with ESMTPA 
          id <ReLHcgB5I2BO@rufus.isode.com>; Mon, 26 Feb 2007 11:41:38 +0000
Message-ID: <45E22AC4.5020104@isode.com>
Date: Mon, 26 Feb 2007 00:33:08 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
            Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-mta-filters@imc.org
Subject: Re: I-D ACTION:draft-ietf-sieve-notify-07.txt
References: <E1HJtjG-0008T7-6Q@stiedprstage1.ietf.org>
In-Reply-To: <E1HJtjG-0008T7-6Q@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>


Internet-Drafts@ietf.org wrote:

>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.
>
>	Title		: Sieve Extension: Notifications
>	Author(s)	: A. Melnikov, et al.
>	Filename	: draft-ietf-sieve-notify-07.txt
>	Pages		: 18
>	Date		: 2007-2-21
>	
>Users go to great lengths to be notified as quickly as possible that
>   they have received new mail.  Most of these methods involve polling
>   to check for new messages periodically.  A push method handled by the
>   final delivery agent gives users quicker notifications and saves
>   server resources.  This document does not specify the notification
>   method but it is expected that using existing instant messaging
>   infrastructure such as XMPP, or SMS messages will be popular.  This
>   draft describes an extension to the Sieve mail filtering language
>   that allows users to give specific rules for how and when
>   notifications should be sent.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-sieve-notify-07.txt
>  
>
Barry and I recently submitted -07. We believe this version addresses 
all issues brought up during WGLC.

I would like to issue an additional 1 week WGLC on this version of the 
document.

In particular, I would like to bring people's attention to the following 
3 changes:

1). New notify_method_capability test.

2). One major editorial change is the removal of extract_text test, as 
per WG discussion. The replacement test or action is more likely to move 
to the MIME loops document, but this decision is not final.

3). Regarding describing interaction of the notify action parameters 
with URI parameters in the method parameter: Looking through comments 
received during WGLC, I found no single agreeable solution. Pretty much 
everybody wanted different behavior. So sieve-notify was updated to list 
available choices, but not prescribe any specific behavior, which is 
left up to specifications describing notification methods. Once the new 
Sieve notify is deployed and we get some implementation experience with 
different notification methods, some consensus might emerge. At which 
point sieve-notify-bis can prescribe a specific behavior.



From owner-ietf-mta-filters Mon Feb 26 13:50:04 2007
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 l1QKo40Z099690
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 26 Feb 2007 13:50:04 -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 l1QKo41P099689;
	Mon, 26 Feb 2007 13:50:04 -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 ns1.neustar.com (ns1.neustar.com [156.154.16.138])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l1QKo3Dl099682
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-mta-filters@imc.org>; Mon, 26 Feb 2007 13:50:04 -0700 (MST)
	(envelope-from ietf@ietf.org)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10])
	by ns1.neustar.com (Postfix) with ESMTP id 5257026EDD;
	Mon, 26 Feb 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HLmnK-0004xw-5F; Mon, 26 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: ietf-mta-filters@imc.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-sieve-body-06.txt 
Message-Id: <E1HLmnK-0004xw-5F@stiedprstage1.ietf.org>
Date: Mon, 26 Feb 2007 15:50:02 -0500
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>


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

	Title		: Sieve Email Filtering: Body Extension
	Author(s)	: P. Guenther, J. Degener
	Filename	: draft-ietf-sieve-body-06.txt
	Pages		: 12
	Date		: 2007-2-26
	
This document defines a new command for the "Sieve" email
   filtering language that tests for the occurrence of one or more
   strings in the body of an email message.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-body-06.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sieve-body-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sieve-body-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2007-2-26105009.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sieve-body-06.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sieve-body-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2007-2-26105009.I-D@ietf.org>

--OtherAccess--

--NextPart--



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 l1QKo40Z099690 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 26 Feb 2007 13:50:04 -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 l1QKo41P099689; Mon, 26 Feb 2007 13:50:04 -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 ns1.neustar.com (ns1.neustar.com [156.154.16.138]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l1QKo3Dl099682 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-mta-filters@imc.org>; Mon, 26 Feb 2007 13:50:04 -0700 (MST) (envelope-from ietf@ietf.org)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 5257026EDD; Mon, 26 Feb 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HLmnK-0004xw-5F; Mon, 26 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: ietf-mta-filters@imc.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-sieve-body-06.txt 
Message-Id: <E1HLmnK-0004xw-5F@stiedprstage1.ietf.org>
Date: Mon, 26 Feb 2007 15:50:02 -0500
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

	Title		: Sieve Email Filtering: Body Extension
	Author(s)	: P. Guenther, J. Degener
	Filename	: draft-ietf-sieve-body-06.txt
	Pages		: 12
	Date		: 2007-2-26
	
This document defines a new command for the "Sieve" email
   filtering language that tests for the occurrence of one or more
   strings in the body of an email message.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-body-06.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sieve-body-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sieve-body-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2007-2-26105009.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sieve-body-06.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sieve-body-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2007-2-26105009.I-D@ietf.org>

--OtherAccess--

--NextPart--



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 l1QBffQE055103 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 26 Feb 2007 04:41:41 -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 l1QBff0M055102; Mon, 26 Feb 2007 04:41:41 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l1QBfdpK055094 for <ietf-mta-filters@imc.org>; Mon, 26 Feb 2007 04:41:40 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <ReLHcgB5I2BO@rufus.isode.com>; Mon, 26 Feb 2007 11:41:38 +0000
Message-ID: <45E22AC4.5020104@isode.com>
Date: Mon, 26 Feb 2007 00:33:08 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-mta-filters@imc.org
Subject: Re: I-D ACTION:draft-ietf-sieve-notify-07.txt
References: <E1HJtjG-0008T7-6Q@stiedprstage1.ietf.org>
In-Reply-To: <E1HJtjG-0008T7-6Q@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Internet-Drafts@ietf.org wrote:

>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.
>
>	Title		: Sieve Extension: Notifications
>	Author(s)	: A. Melnikov, et al.
>	Filename	: draft-ietf-sieve-notify-07.txt
>	Pages		: 18
>	Date		: 2007-2-21
>	
>Users go to great lengths to be notified as quickly as possible that
>   they have received new mail.  Most of these methods involve polling
>   to check for new messages periodically.  A push method handled by the
>   final delivery agent gives users quicker notifications and saves
>   server resources.  This document does not specify the notification
>   method but it is expected that using existing instant messaging
>   infrastructure such as XMPP, or SMS messages will be popular.  This
>   draft describes an extension to the Sieve mail filtering language
>   that allows users to give specific rules for how and when
>   notifications should be sent.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-sieve-notify-07.txt
>  
>
Barry and I recently submitted -07. We believe this version addresses 
all issues brought up during WGLC.

I would like to issue an additional 1 week WGLC on this version of the 
document.

In particular, I would like to bring people's attention to the following 
3 changes:

1). New notify_method_capability test.

2). One major editorial change is the removal of extract_text test, as 
per WG discussion. The replacement test or action is more likely to move 
to the MIME loops document, but this decision is not final.

3). Regarding describing interaction of the notify action parameters 
with URI parameters in the method parameter: Looking through comments 
received during WGLC, I found no single agreeable solution. Pretty much 
everybody wanted different behavior. So sieve-notify was updated to list 
available choices, but not prescribe any specific behavior, which is 
left up to specifications describing notification methods. Once the new 
Sieve notify is deployed and we get some implementation experience with 
different notification methods, some consensus might emerge. At which 
point sieve-notify-bis can prescribe a specific behavior.




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 l1LGRHX0049498 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Feb 2007 09:27:17 -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 l1LGRHOk049497; Wed, 21 Feb 2007 09:27:17 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l1LGRElj049490 for <ietf-mta-filters@imc.org>; Wed, 21 Feb 2007 09:27:17 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <Rdxy4QAgG4NY@rufus.isode.com>; Wed, 21 Feb 2007 16:27:13 +0000
Message-ID: <45DC72C2.4080507@isode.com>
Date: Wed, 21 Feb 2007 16:26:42 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-mta-filters@imc.org
Subject: Request for agenda items for the Sieve WG meeting in Prague
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Please send your requests directly to me or just reply to this message.

Also, I would like to ask people to let me know who is planning to come 
to the Sieve WG meeting in Prague. (Ignore this, if you've already told me).

Thanks,
Alexey, Sieve WG co-chair



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 l1LFo88h046445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Feb 2007 08:50:08 -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 l1LFo8cf046442; Wed, 21 Feb 2007 08:50:08 -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 ns1.neustar.com (ns1.neustar.com [156.154.16.138]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l1LFo6XE046427 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-mta-filters@imc.org>; Wed, 21 Feb 2007 08:50:07 -0700 (MST) (envelope-from ietf@ietf.org)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 629F026ED1; Wed, 21 Feb 2007 15:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HJtjG-0008T7-6Q; Wed, 21 Feb 2007 10:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: ietf-mta-filters@imc.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-sieve-notify-07.txt 
Message-Id: <E1HJtjG-0008T7-6Q@stiedprstage1.ietf.org>
Date: Wed, 21 Feb 2007 10:50:02 -0500
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

	Title		: Sieve Extension: Notifications
	Author(s)	: A. Melnikov, et al.
	Filename	: draft-ietf-sieve-notify-07.txt
	Pages		: 18
	Date		: 2007-2-21
	
Users go to great lengths to be notified as quickly as possible that
   they have received new mail.  Most of these methods involve polling
   to check for new messages periodically.  A push method handled by the
   final delivery agent gives users quicker notifications and saves
   server resources.  This document does not specify the notification
   method but it is expected that using existing instant messaging
   infrastructure such as XMPP, or SMS messages will be popular.  This
   draft describes an extension to the Sieve mail filtering language
   that allows users to give specific rules for how and when
   notifications should be sent.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-notify-07.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sieve-notify-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sieve-notify-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2007-2-21084907.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sieve-notify-07.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sieve-notify-07.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2007-2-21084907.I-D@ietf.org>

--OtherAccess--

--NextPart--



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 l1FNo3GA098794 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Feb 2007 16:50:03 -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 l1FNo392098793; Thu, 15 Feb 2007 16:50:03 -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 ns4.neustar.com (ns4.neustar.com [156.154.24.139]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l1FNo2Ah098787 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-mta-filters@imc.org>; Thu, 15 Feb 2007 16:50:03 -0700 (MST) (envelope-from ietf@ietf.org)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 41F632AD74; Thu, 15 Feb 2007 23:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HHqMU-0003gr-0f; Thu, 15 Feb 2007 18:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: ietf-mta-filters@imc.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-sieve-3028bis-12.txt 
Message-Id: <E1HHqMU-0003gr-0f@stiedprstage1.ietf.org>
Date: Thu, 15 Feb 2007 18:50:02 -0500
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

	Title		: Sieve: An Email Filtering Language
	Author(s)	: T. Showalter, P. Guenther
	Filename	: draft-ietf-sieve-3028bis-12.txt
	Pages		: 44
	Date		: 2007-2-15
	
This document describes a language for filtering email messages at
   time of final delivery.  It is designed to be implementable on either
   a mail client or mail server.  It is meant to be extensible, simple,
   and independent of access protocol, mail architecture, and operating
   system.  It is suitable for running on a mail server where users may
   not be allowed to execute arbitrary programs, such as on black box
   Internet Message Access Protocol (IMAP) servers, as the base language
   has no variables, loops, or ability to shell out to external
   programs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-3028bis-12.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sieve-3028bis-12.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sieve-3028bis-12.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2007-2-15152316.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sieve-3028bis-12.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sieve-3028bis-12.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2007-2-15152316.I-D@ietf.org>

--OtherAccess--

--NextPart--



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 l1EKo5do084047 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Feb 2007 13:50:05 -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 l1EKo5mF084045; Wed, 14 Feb 2007 13:50:05 -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 ns1.neustar.com (ns1.neustar.com [156.154.16.138]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l1EKo271084023 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-mta-filters@imc.org>; Wed, 14 Feb 2007 13:50:05 -0700 (MST) (envelope-from ietf@ietf.org)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 01A8026F0B; Wed, 14 Feb 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HHR4j-0004JL-S0; Wed, 14 Feb 2007 15:50:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: ietf-mta-filters@imc.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-sieve-3028bis-11.txt 
Message-Id: <E1HHR4j-0004JL-S0@stiedprstage1.ietf.org>
Date: Wed, 14 Feb 2007 15:50:01 -0500
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

	Title		: Sieve: An Email Filtering Language
	Author(s)	: T. Showalter, P. Guenther
	Filename	: draft-ietf-sieve-3028bis-11.txt
	Pages		: 44
	Date		: 2007-2-14
	
This document describes a language for filtering email messages at
   time of final delivery.  It is designed to be implementable on either
   a mail client or mail server.  It is meant to be extensible, simple,
   and independent of access protocol, mail architecture, and operating
   system.  It is suitable for running on a mail server where users may
   not be allowed to execute arbitrary programs, such as on black box
   Internet Message Access Protocol (IMAP) servers, as the base language
   has no variables, loops, or ability to shell out to external
   programs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-3028bis-11.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sieve-3028bis-11.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sieve-3028bis-11.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2007-2-14121956.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sieve-3028bis-11.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sieve-3028bis-11.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2007-2-14121956.I-D@ietf.org>

--OtherAccess--

--NextPart--



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 l1CBfCsM017934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Feb 2007 04:41:12 -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 l1CBfCix017933; Mon, 12 Feb 2007 04:41:12 -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 kalyani.oryx.com (kalyani.oryx.com [195.30.37.30]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l1CBfBXf017921 for <ietf-mta-filters@imc.org>; Mon, 12 Feb 2007 04:41:12 -0700 (MST) (envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id C2DA24AC7B; Mon, 12 Feb 2007 12:41:11 +0100 (CET)
Message-Id: <G8wtYd+grNHX3HjfTihV7A.md5@libertango.oryx.com>
Date: Mon, 12 Feb 2007 12:42:17 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-mta-filters@imc.org
Subject: Re: the notify issues
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Dilyan Palauzov <Dilyan.Palauzov@aegee.org>
References: <20070127220648.ufdeeeu4socwwgss@mail.aegee.org> <45CF9E11.4080407@isode.com>
In-Reply-To: <45CF9E11.4080407@isode.com>
Content-Type: text/plain; format=flowed
MIME-Version: 1.0
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>

Alexey Melnikov writes:
> I don't particularly like this part of your suggestion. In particular 
> because many implementations don't send a notification when a notify 
> action is called, they defer sending the notification till after the 
> script evaluation is complete and can do this asynchronously.

Makes sense.

But please add some text that long delays are best avoided, particularly 
for scripts that use the new 'can deliver immediately' test. 0.1 
seconds is not a problem, but the ability to deliver immediately could 
easily change in 10 seconds.

Arnt



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 l1CBKWqS015450 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Feb 2007 04:20:32 -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 l1CBKWu5015449; Mon, 12 Feb 2007 04:20:32 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l1CBKVYY015443 for <ietf-mta-filters@imc.org>; Mon, 12 Feb 2007 04:20:31 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <RdBNewBXDnwW@rufus.isode.com>; Mon, 12 Feb 2007 11:20:28 +0000
Message-ID: <45CF9E11.4080407@isode.com>
Date: Sun, 11 Feb 2007 22:52:01 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Dilyan Palauzov <Dilyan.Palauzov@aegee.org>
CC: ietf-mta-filters@imc.org
Subject: Re: the notify issues
References: <20070127220648.ufdeeeu4socwwgss@mail.aegee.org>
In-Reply-To: <20070127220648.ufdeeeu4socwwgss@mail.aegee.org>
MIME-version: 1.0
Content-type: text/plain; charset="UTF-8"; format="flowed"
Content-transfer-encoding: 7bit
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>

Dilyan Palauzov wrote:

>> Issue #6
>> "send notification over XMPP, if can be delivered immediately.  
>> Otherwise send it over SMS"
>
> I am in favour of:
>
>   1). Add a test to check if a notification method (specified
>   as an URI) can deliver the notification immediately.

I've done this part.

>   1)  Add a test to check if a notification method (specified
>   as an URI) HAS delieverED the notification immediately.
>
> Expanations: for sending an SMS, or mail it cannot be said if the  
> message can be delivered immediately, as it depends on many things,  
> and even if a notification can be delivered during the test, this 
> does  not mean that it is delivered delivered immediately at a later 
> point,  when the notification is send. On the other side, if an SMS of 
> mail is  send, an acknowledgement can be requested, that the 
> notification is  read/delivered. Naturally, this will mean that the 
> interpreter has to  stop for certain time, like 10s, and wait for the 
> acknowledgement.

I don't particularly like this part of your suggestion. In particular 
because many implementations don't send a notification when a notify 
action is called, they defer sending the notification till after the 
script evaluation is complete and can do this asynchronously.

What you suggest will also block message delivery, which might be 
inacceptable for some deployments.




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 l1CBKUDo015441 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Feb 2007 04:20:30 -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 l1CBKUhh015440; Mon, 12 Feb 2007 04:20:30 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l1CBKQmn015434 for <ietf-mta-filters@imc.org>; Mon, 12 Feb 2007 04:20:27 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <RdBNcQBXDl4R@rufus.isode.com>; Mon, 12 Feb 2007 11:20:19 +0000
Message-ID: <45CE71B2.9050008@isode.com>
Date: Sun, 11 Feb 2007 01:30:26 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Dilyan Palauzov <Dilyan.Palauzov@aegee.org>
CC: ietf-mta-filters@imc.org
Subject: Re: the notify issues
References: <20070127220648.ufdeeeu4socwwgss@mail.aegee.org>
In-Reply-To: <20070127220648.ufdeeeu4socwwgss@mail.aegee.org>
MIME-version: 1.0
Content-type: text/plain; charset="UTF-8"; format="flowed"
Content-transfer-encoding: 7bit
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>

Dilyan Palauzov wrote:

>> Issue #6
>> "send notification over XMPP, if can be delivered immediately.  
>> Otherwise send it over SMS"
>
 [...]

>   2). Keep the existing syntax. A new "stackable" notification method
>   can be specified that will perform the desired functionality.
>
> I do not get what means "stackable notification".

I meant a new notification mechanism which tries to deliver notification 
using different mechanisms.
E.g. something [horrible] like:
 <stack:mech1=xmpp:me@example.org:...;mech2=sms:...>




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 l1954t7C002501 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Feb 2007 22:04:55 -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 l1954tKl002500; Thu, 8 Feb 2007 22:04:55 -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 foon.sendmail.com (smtp-out.sendmail.com [209.246.26.45]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l1954sO7002493 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-mta-filters@imc.org>; Thu, 8 Feb 2007 22:04:54 -0700 (MST) (envelope-from guenther+mtafilters@sendmail.com)
Received: from [10.201.0.240] (adsl-64-58-1-252.mho.net [64.58.1.252] (may be forged)) (authenticated bits=0) by foon.sendmail.com (Switch-3.2.5/Switch-3.2.0) with ESMTP id l1954hBw008413 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Feb 2007 21:04:46 -0800
X-DKIM: Sendmail DKIM Filter v0.5.1 foon.sendmail.com l1954hBw008413
DKIM-Signature: a=rsa-sha1; c=relaxed/simple; d=sendmail.com; s=tls.dkim; t=1170997488; bh=+ce7K4J8CBOh58zrI8huTF6hPUc=; h=X-DomainKeys: DomainKey-Signature:Date:From:X-X-Sender:To:cc:Subject:In-Reply-To: Message-ID:References:MIME-Version:Content-Type; b=AIpDNdyPjY3t5zWV jizaI3JkS+eH1s6VkJtDjJ3iUB34qEdNgN9V5noft8bU1c3KB4+KMl6GVCJ0fIR+O3P hwdT40pRyw+uO5hm7uZlX8hUQwlGUBoiZhoRb/Eyuko1WkXtvv1+n840+4Ao+fzx+8w 7AUPqwkzoFRc0NvXDOd2g=
X-DomainKeys: Sendmail DomainKeys Filter v0.4.1 foon.sendmail.com l1954hBw008413
DomainKey-Signature: a=rsa-sha1; s=tls; d=sendmail.com; c=nofws; q=dns; h=date:from:x-x-sender:to:cc:subject:in-reply-to:message-id: references:mime-version:content-type; b=l25bTeYxc8hyOAYM2lMswBrQJQAmuEyOVFy5IqDxPrpr2Ys0FJZL5fzbfjZvY10Iq C6SXOwNGuCSNGYuGCJax6nSThPIRqtnap7TkVOZsJ+5uOhrLQb9OlFIikvkHBUInEqa HUvayi5e8UkPc9h4yaTaqETalQ8ZvSIe8ZlYxNU=
Date: Thu, 8 Feb 2007 22:04:40 -0700
From: Philip Guenther <guenther+mtafilters@sendmail.com>
X-X-Sender: guenther@vanye.mho.net
To: Tim Showalter <tjs@psaux.com>
cc: "Mark E. Mallett" <mem@mv.mv.com>, ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
In-Reply-To: <45CBC3DD.3010805@psaux.com>
Message-ID: <Pine.BSO.4.64.0702082146060.1973@vanye.mho.net>
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net> <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com> <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com> <45C9BD6C.6060505@isode.com> <20070207214840.GB26384@osmium.mv.net> <Pine.BSO.4.64.0702071947160.14328@vanye.mho.net> <20070208231147.GA49702@osmium.mv.net> <45CBC3DD.3010805@psaux.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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>

On Thu, 8 Feb 2007, Tim Showalter wrote:
> Mark E. Mallett wrote:
>> So it sounds like you are saying that the new text about how the count
>> of Received headers MUST be larger is connected to that.  That since
>> some implementations may choose to count Received lines to avoid loops,
>> all implementations must have a higher Received line count when doing
>> redirect.

Yes.  That seemed to be the list concensus, based on the thread with 
subject "Comments on draft-ietf-sieve-3028bis-09 from Eric Rescorla" at 
the beginning of November.  I didn't see any one arguing against mandating 
the addition of Received header fields by 'redirect' back then, so I took 
it to be agreed.


> If two (or more) implementations are configured to loop, just one adds 
> Received headers and uses them for loop control, that's enough to stop the 
> loop.

Yes, but if just one implementation (in the "code base" sense) does _not_ 
add Received header fields and it is installed at multiple site, then it 
can sustain a loop.  Heck, an implementation with no loop control can be a 
mailbomb generator if it supports multiple redirects for a single message: 
it would just a sieve script that redirects to its own address as well as 
the victim address.


> I can't imagine why anyone wouldn't add Received anyway, just based on 
> advice in 2821 (and common sense).

Common sense is as common as a sense of humor, apparently.  (References to 
solving the Halting Problem were removed from 3028bis after multiple 
reviewers expressed their dislike for the text.)


Philip Guenther



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 l190iPaw087712 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Feb 2007 17:44:25 -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 l190iPQu087711; Thu, 8 Feb 2007 17:44:25 -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 smtp110.plus.mail.mud.yahoo.com (smtp110.plus.mail.mud.yahoo.com [68.142.206.243]) by balder-227.proper.com (8.13.5/8.13.5) with SMTP id l190iNd3087705 for <ietf-mta-filters@imc.org>; Thu, 8 Feb 2007 17:44:24 -0700 (MST) (envelope-from tjs@psaux.com)
Received: (qmail 39384 invoked from network); 9 Feb 2007 00:44:15 -0000
Received: from unknown (HELO ?172.21.103.31?) (ts4z@216.145.49.15 with plain) by smtp110.plus.mail.mud.yahoo.com with SMTP; 9 Feb 2007 00:44:14 -0000
X-YMail-OSG: H1e2RWsVM1l_uYeidhv6GP5UwTQ9Up5m4Fw2_CsxmT85ZYGB5qjeo0kikSbaHYFu4GCUes6jSjEt65.8187Rasp2zaSSs4BMMH0yNbKhQk_kKHLdyY_XQ4YDltA94iCBS.li3pjJZzYVJShVRLqLmA1UbrzRhCUxNYzxA8h0Qx2FNc2o_E4QCxP7OMLl
Message-ID: <45CBC3DD.3010805@psaux.com>
Date: Thu, 08 Feb 2007 16:44:13 -0800
From: Tim Showalter <tjs@psaux.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: "Mark E. Mallett" <mem@mv.mv.com>
CC: Philip Guenther <guenther+mtafilters@sendmail.com>, ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net> <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com> <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com> <45C9BD6C.6060505@isode.com> <20070207214840.GB26384@osmium.mv.net> <Pine.BSO.4.64.0702071947160.14328@vanye.mho.net> <20070208231147.GA49702@osmium.mv.net>
In-Reply-To: <20070208231147.GA49702@osmium.mv.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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>

Mark E. Mallett wrote:
> So it sounds like you are saying that the new text about how the count
> of Received headers MUST be larger is connected to that.  That since
> some implementations may choose to count Received lines to avoid loops,
> all implementations must have a higher Received line count when doing
> redirect.

If two (or more) implementations are configured to loop, just one adds 
Received headers and uses them for loop control, that's enough to stop 
the loop.

I can't imagine why anyone wouldn't add Received anyway, just based on 
advice in 2821 (and common sense).

Tim



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 l18NBqR2081623 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Feb 2007 16:11: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 l18NBqER081620; Thu, 8 Feb 2007 16:11: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 shell.mv.net (osmium.mv.net [199.125.85.152]) by balder-227.proper.com (8.13.5/8.13.5) with SMTP id l18NBmbQ081610 for <ietf-mta-filters@imc.org>; Thu, 8 Feb 2007 16:11:50 -0700 (MST) (envelope-from mem@mv.mv.com)
Received: (qmail 58873 invoked by uid 101); 8 Feb 2007 18:11:47 -0500
From: "Mark E. Mallett" <mem@mv.mv.com>
Date: Thu, 8 Feb 2007 18:11:47 -0500
To: Philip Guenther <guenther+mtafilters@sendmail.com>
Cc: "Mark E. Mallett" <mem@mv.mv.com>, ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
Message-ID: <20070208231147.GA49702@osmium.mv.net>
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net> <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com> <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com> <45C9BD6C.6060505@isode.com> <20070207214840.GB26384@osmium.mv.net> <Pine.BSO.4.64.0702071947160.14328@vanye.mho.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.BSO.4.64.0702071947160.14328@vanye.mho.net>
User-Agent: Mutt/1.4.2.1i
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>

On Wed, Feb 07, 2007 at 09:21:49PM -0700, Philip Guenther wrote:
> 
> Mark Mallett wrote, in regards to this text in 3028bis-10, section 4.2:

 ...


> I'd like to stress that the *critical* thing in that paragraph is the bit 
> about "count of 'received's MUST be higher", as that's what provides a way 
> to break loops.

Ah... I didn't get that connection at all.  OK, there is the text later
in that section:

   Implementations SHOULD take measures to implement loop control,
   possibly including adding headers to the message or counting Received
   headers.

So it sounds like you are saying that the new text about how the count
of Received headers MUST be larger is connected to that.  That since
some implementations may choose to count Received lines to avoid loops,
all implementations must have a higher Received line count when doing
redirect.  I don't see that as a valid prescription, I think that the
"take measures to implement loop control" is enough (especially since I
don't really think that Received-line counting is all that great a
technique).

I don't mean to be anal (other than it coming naturally, perhaps),
but I just don't see that as a valid justification for the MUST.
(Even though I am in favor of implementations adding a Received line.)

  ...

> I hope I'm not coming across as trying to dodge the issues here.

And again I hope I'm not being a pain.  However the text I commented on
is new as of -10, so it seems [more] reasonable to comment on it.  It
may be that everyone decides it's a non-issue... so be it.

At any rate I feel conflicted:  I like the idea of recommending that
implementations add a Received line, but not in the "redirect" section.
Evidently it's too late for that.  I not wild about the new MUST in the
redirect section, especially now having learned that its only reason for
being there is for loop control.  (I could probably even imagine good
reasons for removing some Received lines prior to redirect-- but I
dunno.)

My 2c...

-mm-



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 l18BLekB021093 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Feb 2007 04:21:40 -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 l18BLea3021092; Thu, 8 Feb 2007 04:21:40 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l18BLZwY021085 for <ietf-mta-filters@imc.org>; Thu, 8 Feb 2007 04:21:38 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <RcsHuwBXDrDj@rufus.isode.com>; Thu, 8 Feb 2007 11:21:31 +0000
Message-ID: <45CB07A2.9000302@isode.com>
Date: Thu, 08 Feb 2007 11:21:06 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: ietf-mta-filters@imc.org
Subject: Let's get 3028bis published
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net> <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com> <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com> <45C9BD6C.6060505@isode.com> <20070207214840.GB26384@osmium.mv.net> <Pine.BSO.4.64.0702071947160.14328@vanye.mho.net>
In-Reply-To: <Pine.BSO.4.64.0702071947160.14328@vanye.mho.net>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>

Philip Guenther wrote:

> I hope I'm not coming across as trying to dodge the issues here.  I 
> just feel we need to "keep our eyes on the prize": getting 3028bis 
> published.

Yes, we are way beyond our originally intended publication date.

> It's what, 2 years late, by the original schedule?  Issues that 
> 3028bis raises in other documents should be left to those other 
> documents, even if they've been last called.  If it's a general mail 
> agent issue and not specific to sieve, then perhaps it belongs in 
> 2821bis or 2822bis ...or in a completely new I-D.

Agreed.



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 l18BIWiG020812 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Feb 2007 04:18:32 -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 l18BIWk5020811; Thu, 8 Feb 2007 04:18:32 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l18BITEI020803 for <ietf-mta-filters@imc.org>; Thu, 8 Feb 2007 04:18:30 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <RcsHAQBXDnHO@rufus.isode.com>; Thu, 8 Feb 2007 11:18:26 +0000
Message-ID: <45CB06E7.40104@isode.com>
Date: Thu, 08 Feb 2007 11:17:59 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Philip Guenther <guenther+mtafilters@sendmail.com>
CC: "Mark E. Mallett" <mem@mv.mv.com>, ietf-mta-filters@imc.org
Subject: Interaction between redirect and editheader
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net> <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com> <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com> <45C9BD6C.6060505@isode.com> <20070207214840.GB26384@osmium.mv.net> <Pine.BSO.4.64.0702071947160.14328@vanye.mho.net>
In-Reply-To: <Pine.BSO.4.64.0702071947160.14328@vanye.mho.net>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>

Philip Guenther wrote:

>> e.g. as applied to the 'editheader' mandate that
>>    if an error terminates processing of the script, the original
>>    message header MUST be used when doing the implicit keep required by
>>    [SIEVE] section 2.10.6.
>> where I think it could be argued that such an added "Received" line
>> would be valuable to preserve.
>
> In the context of 'editheader', I think it's clear that "the original 
> message" just means "the message as it was before any addheader or 
> deleteheader actions were processed".  If you disagree about that 
> being clear, well, suggest text for editheader...

I would just remind people that WGLC for editheader has ended as well. 
Cyrus and I are planning to request its publication next week.

So at this point we need specific text.

> but that doesn't affect this discussion of 3028bis.
>
>> The new language that "Received headers MUST be preserved" also implies
>> that the removal of any Received headers via an extension (e.g.
>> 'editheader') must be ignored for the redirect.  Is that the intent?
>
I don't think this was the intent.

>>  I dunno whether I think that's good -- I probably do, but it certainly
>> means more special-case work for me :)
>
> An excellent question, but again, one that should be raised against 
> editheader and not 3028bis.
>
> (I'm not sure either what the Right Thing is.  I'll note that 
> editheader could override 3028bis, just as body overrides variables.

Indeed. It is somewhat difficult to put normative requirements on future 
document (or in this case on a document that gets published later).

> The key procedural requirement, I think, would be the inclusion of 
> "Updates: 3028bis" on the title page of editheader.

Yes, go for it! :-)

> )




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 l18B4pBe019358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Feb 2007 04:04: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 l18B4p0R019357; Thu, 8 Feb 2007 04:04:51 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l18B4oCk019345 for <ietf-mta-filters@imc.org>; Thu, 8 Feb 2007 04:04:50 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <RcsDzwBXDqp0@rufus.isode.com>; Thu, 8 Feb 2007 11:04:48 +0000
Message-ID: <45CB03B6.3030500@isode.com>
Date: Thu, 08 Feb 2007 11:04:22 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before sending         it to IESG
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com>
In-Reply-To: <45C753CF.7080906@isode.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Alexey Melnikov wrote:

> Internet-Drafts@ietf.org wrote:
>
>> http://www.ietf.org/internet-drafts/draft-ietf-sieve-3028bis-10.txt
>
> Folks,
> This is your last chance to review that the document is correct and 
> complete. No new issues can be raised at this stage unless they are 
> very serious.

Clarification: no editorial changes will be accepted at this stage 
without any concrete text. Thanks.

> Please review the document by the end of February 11th. Cyrus and I 
> are planning to send it to IESG soon after February 11th.

> Regards,
> Alexey and Cyrus.




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 l184LtET092950 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Feb 2007 21:21:56 -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 l184Lt3F092949; Wed, 7 Feb 2007 21:21:55 -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 e-nvb.com (e-nvb.com [69.27.17.200] (may be forged)) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l184LsnK092943 for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 21:21:55 -0700 (MST) (envelope-from guenther+mtafilters@sendmail.com)
Received: from [10.0.67.61] (unknown [71.39.21.73]) by e-nvb.com (Postfix) with ESMTP id C34F5183810; Thu,  8 Feb 2007 04:20:16 -0700 (MST)
Date: Wed, 7 Feb 2007 21:21:49 -0700
From: Philip Guenther <guenther+mtafilters@sendmail.com>
X-X-Sender: guenther@vanye.mho.net
To: "Mark E. Mallett" <mem@mv.mv.com>
cc: ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
In-Reply-To: <20070207214840.GB26384@osmium.mv.net>
Message-ID: <Pine.BSO.4.64.0702071947160.14328@vanye.mho.net>
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net> <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com> <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com> <45C9BD6C.6060505@isode.com> <20070207214840.GB26384@osmium.mv.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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>

Mark Mallett wrote, in regards to this text in 3028bis-10, section 4.2:
    <...>  In particular, existing
    Received headers MUST be preserved and the count of Received headers
    in the outgoing message MUST be larger than the same count on the
    message as received by the implementation.  (An implementation that
    adds a Received header before processing the message does not need to
    add another when redirecting.)

...
> That's interesting, I didn't notice that change.  That does mandate the
> addition of a Received by (or as of) the time a redirect is done.  It
> also implies that adding a Received line is at least discussed elsewhere
> in the document, which it isn't (other than a casual mention in loop
> control).  Maybe that's picky, but if the addition of a Received line is
> alluded to, perhaps it should be discussed.  For example, there could
> be a recommendation that an implementation "adds a Received header before
> processing the message" -- but then is this considered part of the
> original message?

I don't get what's unclear about this.  If the addition was made "before 
processing the message", then by definition the message being processed 
has the added header field.

Oh, and the phrase "original message" is used exactly once in 3028bis-10, 
where it says that the envelope sender of a redirected messaage "MAY be 
copied from the original message".  I'll change that to say "MAY be copied 
from the message being processed" to kill that phrase completely from 
3028bis.

I'd like to stress that the *critical* thing in that paragraph is the bit 
about "count of 'received's MUST be higher", as that's what provides a way 
to break loops.  If the parenthetical comment about implementations that 
do things a particular way raises more issues than it clarifies, then the 
correct action at this point is to *remove* the comment.


> e.g. as applied to the 'editheader' mandate that
>    if an error terminates processing of the script, the original
>    message header MUST be used when doing the implicit keep required by
>    [SIEVE] section 2.10.6.
> where I think it could be argued that such an added "Received" line
> would be valuable to preserve.

In the context of 'editheader', I think it's clear that "the original 
message" just means "the message as it was before any addheader or 
deleteheader actions were processed".  If you disagree about that being 
clear, well, suggest text for editheader...but that doesn't affect this 
discussion of 3028bis.


> The new language that "Received headers MUST be preserved" also implies
> that the removal of any Received headers via an extension (e.g.
> 'editheader') must be ignored for the redirect.  Is that the intent?  I
> dunno whether I think that's good -- I probably do, but it certainly
> means more special-case work for me :)

An excellent question, but again, one that should be raised against 
editheader and not 3028bis.

(I'm not sure either what the Right Thing is.  I'll note that editheader 
could override 3028bis, just as body overrides variables.  The key 
procedural requirement, I think, would be the inclusion of "Updates: 
3028bis" on the title page of editheader.)


I hope I'm not coming across as trying to dodge the issues here.  I just 
feel we need to "keep our eyes on the prize": getting 3028bis published. 
It's what, 2 years late, by the original schedule?  Issues that 3028bis 
raises in other documents should be left to those other documents, even if 
they've been last called.  If it's a general mail agent issue and not 
specific to sieve, then perhaps it belongs in 2821bis or 2822bis ...or in 
a completely new I-D.


Philip Guenther



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 l17LmgoZ070929 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Feb 2007 14:48:42 -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 l17LmgxI070928; Wed, 7 Feb 2007 14:48:42 -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 shell.mv.net (osmium.mv.net [199.125.85.152]) by balder-227.proper.com (8.13.5/8.13.5) with SMTP id l17LmeZp070920 for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 14:48:41 -0700 (MST) (envelope-from mem@mv.mv.com)
Received: (qmail 55771 invoked by uid 101); 7 Feb 2007 16:48:40 -0500
From: "Mark E. Mallett" <mem@mv.mv.com>
Date: Wed, 7 Feb 2007 16:48:40 -0500
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, ietf-mta-filters@imc.org, Philip Guenther <guenther+mtafilters@sendmail.com>
Subject: Re: 3028bis, section 4.2, paragraph 2
Message-ID: <20070207214840.GB26384@osmium.mv.net>
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net> <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com> <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com> <45C9BD6C.6060505@isode.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <45C9BD6C.6060505@isode.com>
User-Agent: Mutt/1.4.2.1i
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>

On Wed, Feb 07, 2007 at 11:52:12AM +0000, Alexey Melnikov wrote:
> 
> Arnt Gulbrandsen wrote:
> >
> >Perhaps: SHOULD ensure that there is sufficient information in the 
> >chain of 'Received' fields that a human observer can see what happened?
> 
> Arnt,
> I think this is already covered by existing paragraph in -10 (which 
> Philip didn't plan to change):
> 
>   The "redirect" action is used to send the message to another user at
>   a supplied address, as a mail forwarding feature does.  The
>   "redirect" action makes no changes to the message body or existing
>   headers, but it may add new headers.  In particular, existing
>   Received headers MUST be preserved and the count of Received headers
>   in the outgoing message MUST be larger than the same count on the
>   message as received by the implementation.  (An implementation that
>   adds a Received header before processing the message does not need to
>   add another when redirecting.)

That's interesting, I didn't notice that change.  That does mandate the
addition of a Received by (or as of) the time a redirect is done.  It
also implies that adding a Received line is at least discussed elsewhere
in the document, which it isn't (other than a casual mention in loop
control).  Maybe that's picky, but if the addition of a Received line is
alluded to, perhaps it should be discussed.  For example, there could
be a recommendation that an implementation "adds a Received header before
processing the message" -- but then is this considered part of the
original message?  e.g. as applied to the 'editheader' mandate that

    if an error terminates processing of the script, the original
    message header MUST be used when doing the implicit keep required by
    [SIEVE] section 2.10.6.

where I think it could be argued that such an added "Received" line
would be valuable to preserve.  (as would, I think, other annotating
information, but I've said that before: I think that that editheader
prohibition is too broad since it reaches beyond changes made by
editheader, but I seem to be the only one who thinks that.)

The new language that "Received headers MUST be preserved" also implies
that the removal of any Received headers via an extension (e.g.
'editheader') must be ignored for the redirect.  Is that the intent?  I
dunno whether I think that's good -- I probably do, but it certainly
means more special-case work for me :)

mm  (yes, I kind of got off on a tangent)



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 l17KhCfQ066529 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Feb 2007 13:43:12 -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 l17KhCWx066528; Wed, 7 Feb 2007 13:43:12 -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 shell.mv.net (osmium.mv.net [199.125.85.152]) by balder-227.proper.com (8.13.5/8.13.5) with SMTP id l17KhAad066521 for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 13:43:11 -0700 (MST) (envelope-from mem@mv.mv.com)
Received: (qmail 30811 invoked by uid 101); 7 Feb 2007 15:43:08 -0500
From: "Mark E. Mallett" <mem@mv.mv.com>
Date: Wed, 7 Feb 2007 15:43:08 -0500
To: Philip Guenther <guenther+mtafilters@sendmail.com>
Cc: ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
Message-ID: <20070207204308.GA26384@osmium.mv.net>
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>
User-Agent: Mutt/1.4.2.1i
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>

On Tue, Feb 06, 2007 at 05:26:16PM -0700, Philip Guenther wrote:


> it would instead say:
> 
>    The message is send back out with the address from the redirect
>    command as an envelope recipient.  Implementations MAY combine
>    separate redirects for a given message into a single submission with
>    multiple envelope recipients.  (This is not an MUA-style forward,
>    which creates a new message with a different sender and message ID,
>    wrapping the old message in a new one.)
> 
> And yes, the elimination of the mention of .forward files in intentional, 
> as that irked some.

(yay!)


> Are there any objections to the above change?

Only that you should replace "send" with "sent" ("The message is sent...").
Otherwise fine.

mm



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 l17GDkel046819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Feb 2007 09:13:46 -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 l17GDk7J046818; Wed, 7 Feb 2007 09:13:46 -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 kalyani.oryx.com (kalyani.oryx.com [195.30.37.30]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l17GDi7n046811 for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 09:13:45 -0700 (MST) (envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id 46A4A4AC6C; Wed,  7 Feb 2007 17:13:45 +0100 (CET)
Message-Id: <DJEirQFqnxmv59CfDss2Bw.md5@libertango.oryx.com>
Date: Wed, 7 Feb 2007 17:14:26 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
Cc: Philip Guenther <guenther+mtafilters@sendmail.com>
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net> <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com> <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com> <45C9BD6C.6060505@isode.com> <93rxMqbGUTx6BM1YSwq1fw.md5@libertango.oryx.com> <Pine.BSO.4.64.0702070626170.8473@vanye.mho.net>
In-Reply-To: <Pine.BSO.4.64.0702070626170.8473@vanye.mho.net>
Content-Type: text/plain; format=flowed
MIME-Version: 1.0
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>

Philip Guenther writes:
> On Wed, 7 Feb 2007, Arnt Gulbrandsen wrote:
> ...
>> Fine. A 'for' clause is desirable, but I suppose it always is.
>
> IMHO, if the discussion in RFC 2821 of 'for' clauses and when they 
> should or should not be included (c.f. sections 4.4, 7.2, and 7.5) is 
> insufficient, then it should be fixed there and not in 3028bis.

I could argue that one either way... so let's just use the text you 
proposed earlier today.

Arnt



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 l17DsngE034949 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Feb 2007 06:54:49 -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 l17DsnBs034948; Wed, 7 Feb 2007 06:54:49 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l17Dsm9H034941 for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 06:54:49 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <RcnaHQBXDqhl@rufus.isode.com>; Wed, 7 Feb 2007 13:54:37 +0000
Message-ID: <45C9DA05.3070300@isode.com>
Date: Wed, 07 Feb 2007 13:54:13 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Philip Guenther <guenther+mtafilters@sendmail.com>
CC: ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>
In-Reply-To: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>

Philip Guenther wrote:

>
>
> There's been some lingering dislike of the description of the redirect 
> action, particularly how it describes the change of envelope 
> recipient. 3028bis-10 removed this sentence
>     The "redirect" modifies the envelope recipient.
>
> as it was observed that it implied that the result of the 'envelope' 
> test would be affected.  With that gone, only the second paragraph 
> actually described how the address in the action was to become an 
> envelope recipient, but it's description is fairly indirect.  So, I 
> propose replacing most of that paragraph, so that instead of reading 
> thusly:
>
>    The redirect command performs an MTA-style "forward"--that is, what
>    you get from a .forward file using sendmail under UNIX.  The address
>    on the [SMTP] envelope is replaced with the one on the redirect
>    command and the message is sent back out.  (This is not an MUA-style
>    forward, which creates a new message with a different sender and
>    message ID, wrapping the old message in a new one.)
>
> it would instead say:
>
>    The message is send back out with the address from the redirect
>    command as an envelope recipient.  Implementations MAY combine
>    separate redirects for a given message into a single submission with
>    multiple envelope recipients.  (This is not an MUA-style forward,
>    which creates a new message with a different sender and message ID,
>    wrapping the old message in a new one.)

Speaking as an individual: No objections from me.

> And yes, the elimination of the mention of .forward files in 
> intentional, as that irked some.
>
>
> Are there any objections to the above change?




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 l17Dp1w3034715 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Feb 2007 06:51:01 -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 l17Dp11D034714; Wed, 7 Feb 2007 06:51:01 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l17Dp0l7034708 for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 06:51:00 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <RcnZQgBXDr1K@rufus.isode.com>; Wed, 7 Feb 2007 13:50:59 +0000
Message-ID: <45C9D92A.7070702@isode.com>
Date: Wed, 07 Feb 2007 13:50:34 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Philip Guenther <guenther+mtafilters@sendmail.com>
CC: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>  <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com>  <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com>  <45C9BD6C.6060505@isode.com> <93rxMqbGUTx6BM1YSwq1fw.md5@libertango.oryx.com> <Pine.BSO.4.64.0702070626170.8473@vanye.mho.net>
In-Reply-To: <Pine.BSO.4.64.0702070626170.8473@vanye.mho.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Philip Guenther wrote:

> On Wed, 7 Feb 2007, Arnt Gulbrandsen wrote:
> ...
>
>> Fine. A 'for' clause is desirable, but I suppose it always is.
>
> IMHO, if the discussion in RFC 2821 of 'for' clauses and when they 
> should or should not be included (c.f. sections 4.4, 7.2, and 7.5) is 
> insufficient, then it should be fixed there and not in 3028bis.

Agreed. IMHO, this is not 3028bis business.



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 l17DctCq033854 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Feb 2007 06:38:55 -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 l17DctMp033853; Wed, 7 Feb 2007 06:38:55 -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 foon.sendmail.com (smtp-out.sendmail.com [209.246.26.45]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l17Dcss7033847 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 06:38:54 -0700 (MST) (envelope-from guenther+mtafilters@sendmail.com)
Received: from [10.201.0.212] (adsl-64-58-1-252.mho.net [64.58.1.252] (may be forged)) (authenticated bits=0) by foon.sendmail.com (Switch-3.2.5/Switch-3.2.0) with ESMTP id l17DcYkj019343 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Feb 2007 05:38:36 -0800
X-DKIM: Sendmail DKIM Filter v0.5.1 foon.sendmail.com l17DcYkj019343
DKIM-Signature: a=rsa-sha1; c=relaxed/simple; d=sendmail.com; s=tls.dkim; t=1170855519; bh=EqEA+0Mcp9aiVc3J5jSj3fmlJgA=; h=X-DomainKeys: DomainKey-Signature:Date:From:X-X-Sender:To:cc:Subject:In-Reply-To: Message-ID:References:MIME-Version:Content-Type; b=LO2cewyFDROPXhfN P6b7pAMHdeUAKeUKaPXJtI5k3FBMV11NOVBVPiuvixU5AhJ008wED8vSHSZ3/pnegU4 x7D8BpXDhGw/pq05LpEz4TT6bKcjlP7qJgJUYt4wMtZN5rreAo3aBusUmj8Q3Yf1tJJ bOhh0WlOoVHqAhaQ11o0c=
X-DomainKeys: Sendmail DomainKeys Filter v0.4.1 foon.sendmail.com l17DcYkj019343
DomainKey-Signature: a=rsa-sha1; s=tls; d=sendmail.com; c=nofws; q=dns; h=date:from:x-x-sender:to:cc:subject:in-reply-to:message-id: references:mime-version:content-type; b=unKI+WZfjRQ+vDOOD9o125/pcEUEwdkZhAn3fEjKX4uYW+PQWw3kXdmVCInNjepq3 cNNCA3ank4SVCYqyPFYUJ1HpddiwuephKYlruYW1XEUN3fTuu0MQfZYucMVJ8ZXxhQg vN7Y9KGcduibr1on/pwV3bhYKZuKUbatjZ8v8Lc=
Date: Wed, 7 Feb 2007 06:38:33 -0700
From: Philip Guenther <guenther+mtafilters@sendmail.com>
X-X-Sender: guenther@vanye.mho.net
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
cc: ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
In-Reply-To: <93rxMqbGUTx6BM1YSwq1fw.md5@libertango.oryx.com>
Message-ID: <Pine.BSO.4.64.0702070626170.8473@vanye.mho.net>
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>  <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com>  <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com> <45C9BD6C.6060505@isode.com> <93rxMqbGUTx6BM1YSwq1fw.md5@libertango.oryx.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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>

On Wed, 7 Feb 2007, Arnt Gulbrandsen wrote:
...
> Fine. A 'for' clause is desirable, but I suppose it always is.

IMHO, if the discussion in RFC 2821 of 'for' clauses and when they should 
or should not be included (c.f. sections 4.4, 7.2, and 7.5) is 
insufficient, then it should be fixed there and not in 3028bis.


Philip Guenther



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 l17C6xqt026443 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Feb 2007 05:06:59 -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 l17C6xHY026442; Wed, 7 Feb 2007 05:06:59 -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 kalyani.oryx.com (kalyani.oryx.com [195.30.37.30]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l17C6wk3026436 for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 05:06:59 -0700 (MST) (envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id E57074AC77; Wed,  7 Feb 2007 13:06:58 +0100 (CET)
Message-Id: <93rxMqbGUTx6BM1YSwq1fw.md5@libertango.oryx.com>
Date: Wed, 7 Feb 2007 13:07:39 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Philip Guenther <guenther+mtafilters@sendmail.com>
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net> <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com> <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com> <45C9BD6C.6060505@isode.com>
In-Reply-To: <45C9BD6C.6060505@isode.com>
Content-Type: text/plain; format=flowed
MIME-Version: 1.0
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>

Alexey Melnikov writes:
> I think this is already covered by existing paragraph in -10 (which 
> Philip didn't plan to change):
>
>   The "redirect" action is used to send the message to another user at
>   a supplied address, as a mail forwarding feature does.  The
>   "redirect" action makes no changes to the message body or existing
>   headers, but it may add new headers.  In particular, existing
>   Received headers MUST be preserved and the count of Received headers
>   in the outgoing message MUST be larger than the same count on the
>   message as received by the implementation.  (An implementation that
>   adds a Received header before processing the message does not need to
>   add another when redirecting.)

Fine. A 'for' clause is desirable, but I suppose it always is.

Arnt



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 l17BqipK025072 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Feb 2007 04:52:44 -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 l17Bqi9c025071; Wed, 7 Feb 2007 04:52:44 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l17BqdlA025060 for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 04:52:43 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <Rcm9hQBXDl7b@rufus.isode.com>; Wed, 7 Feb 2007 11:52:37 +0000
Message-ID: <45C9BD6C.6060505@isode.com>
Date: Wed, 07 Feb 2007 11:52:12 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
CC: ietf-mta-filters@imc.org, Philip Guenther <guenther+mtafilters@sendmail.com>
Subject: Re: 3028bis, section 4.2, paragraph 2
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>  <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com> <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com>
In-Reply-To: <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>

Arnt Gulbrandsen wrote:

> Arnt Gulbrandsen writes:
>
>> Philip Guenther writes:
>>
>>> it would instead say:
>>>
>>>    The message is send back out with the address from the redirect
>>>    command as an envelope recipient.  Implementations MAY combine
>>>    separate redirects for a given message into a single submission with
>>>    multiple envelope recipients.  (This is not an MUA-style forward,
>>>    which creates a new message with a different sender and message ID,
>>>    wrapping the old message in a new one.)
>>>
>>> And yes, the elimination of the mention of .forward files in 
>>> intentional, as that irked some.
>>>
>>> Are there any objections to the above change?
>>
>> No, but maybe I want to add a requirement to prepend a new 'Received' 
>> field so that a human tracing problems can tell what happened to the 
>> message. Not 100% sure. In some (many?) cases there are enough 
>> Received fields anyway.
>
> Perhaps: SHOULD ensure that there is sufficient information in the 
> chain of 'Received' fields that a human observer can see what happened?

Arnt,
I think this is already covered by existing paragraph in -10 (which 
Philip didn't plan to change):

   The "redirect" action is used to send the message to another user at
   a supplied address, as a mail forwarding feature does.  The
   "redirect" action makes no changes to the message body or existing
   headers, but it may add new headers.  In particular, existing
   Received headers MUST be preserved and the count of Received headers
   in the outgoing message MUST be larger than the same count on the
   message as received by the implementation.  (An implementation that
   adds a Received header before processing the message does not need to
   add another when redirecting.)



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 l17AAPc8016722 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Feb 2007 03:10:25 -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 l17AAPPn016721; Wed, 7 Feb 2007 03:10:25 -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 kalyani.oryx.com (kalyani.oryx.com [195.30.37.30]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l17AAOTo016713 for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 03:10:25 -0700 (MST) (envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id B671F4AC77; Wed,  7 Feb 2007 11:10:24 +0100 (CET)
Message-Id: <vinvoLkx5ajmjJBTyVKBFg.md5@libertango.oryx.com>
Date: Wed, 7 Feb 2007 11:11:05 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
Cc: Philip Guenther <guenther+mtafilters@sendmail.com>
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net> <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com>
In-Reply-To: <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com>
Content-Type: text/plain; format=flowed
MIME-Version: 1.0
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>

Arnt Gulbrandsen writes:
> Philip Guenther writes:
>> it would instead say:
>>
>>    The message is send back out with the address from the redirect
>>    command as an envelope recipient.  Implementations MAY combine
>>    separate redirects for a given message into a single submission with
>>    multiple envelope recipients.  (This is not an MUA-style forward,
>>    which creates a new message with a different sender and message ID,
>>    wrapping the old message in a new one.)
>>
>> And yes, the elimination of the mention of .forward files in 
>> intentional, as that irked some.
>>
>> Are there any objections to the above change?
>
> No, but maybe I want to add a requirement to prepend a new 'Received' 
> field so that a human tracing problems can tell what happened to the 
> message. Not 100% sure. In some (many?) cases there are enough 
> Received fields anyway.

Perhaps: SHOULD ensure that there is sufficient information in the chain 
of 'Received' fields that a human observer can see what happened?

Arnt



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 l178gnCd010495 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Feb 2007 01:42:49 -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 l178gnWT010494; Wed, 7 Feb 2007 01:42:49 -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 kalyani.oryx.com (kalyani.oryx.com [195.30.37.30]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l178glBD010486 for <ietf-mta-filters@imc.org>; Wed, 7 Feb 2007 01:42:49 -0700 (MST) (envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id DB8694AC77; Wed,  7 Feb 2007 09:42:47 +0100 (CET)
Message-Id: <KeX9wp55qjOCP2lD80yM3A.md5@libertango.oryx.com>
Date: Wed, 7 Feb 2007 09:43:27 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-mta-filters@imc.org
Subject: Re: 3028bis, section 4.2, paragraph 2
Cc: Philip Guenther <guenther+mtafilters@sendmail.com>
References: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>
In-Reply-To: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>
Content-Type: text/plain; format=flowed
MIME-Version: 1.0
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>

Philip Guenther writes:
> it would instead say:
>
>    The message is send back out with the address from the redirect
>    command as an envelope recipient.  Implementations MAY combine
>    separate redirects for a given message into a single submission with
>    multiple envelope recipients.  (This is not an MUA-style forward,
>    which creates a new message with a different sender and message ID,
>    wrapping the old message in a new one.)
>
> And yes, the elimination of the mention of .forward files in 
> intentional, as that irked some.
>
> Are there any objections to the above change?

No, but maybe I want to add a requirement to prepend a new 'Received' 
field so that a human tracing problems can tell what happened to the 
message. Not 100% sure. In some (many?) cases there are enough Received 
fields anyway.

Arnt



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 l170QQhi080230 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Feb 2007 17:26:26 -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 l170QQ24080229; Tue, 6 Feb 2007 17:26:26 -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 foon.sendmail.com (smtp-out.sendmail.com [209.246.26.45]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l170QNGr080223 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 17:26:26 -0700 (MST) (envelope-from guenther+mtafilters@sendmail.com)
Received: from [192.168.0.4] (71-212-236-65.hlrn.qwest.net [71.212.236.65]) (authenticated bits=0) by foon.sendmail.com (Switch-3.2.5/Switch-3.2.0) with ESMTP id l170QG95012109 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 16:26:21 -0800
X-DKIM: Sendmail DKIM Filter v0.5.1 foon.sendmail.com l170QG95012109
DKIM-Signature: a=rsa-sha1; c=relaxed/simple; d=sendmail.com; s=tls.dkim; t=1170807982; bh=y38g7d0CYXqkId2G4/Uw0BiNo1A=; h=X-DomainKeys: DomainKey-Signature:Date:From:X-X-Sender:To:Subject:Message-ID: MIME-Version:Content-Type; b=s+22gFdyFqHZ34nPS605SQ5nvM/sGdcCBHyhDF ugF/kpWD5zTa4PkL8Rm/CazAKhJEN+d+/+NR8KDq4IvBNnsHBo5jNPlvoVf2/AL4Isy wNHsydlv2JkfAX7sCmvBIZRr9JTzojsjxY49drT4TmSC4e26uiBZQ/lREW6wN00Bf4=
X-DomainKeys: Sendmail DomainKeys Filter v0.4.1 foon.sendmail.com l170QG95012109
DomainKey-Signature: a=rsa-sha1; s=tls; d=sendmail.com; c=nofws; q=dns; h=date:from:x-x-sender:to:subject:message-id:mime-version:content-type; b=LaXlOhRE9FCxXCyqMim0QOYJPwolW+XRWZ868gE4Z+kvl0zN6KdQyoMQiY3SMkPId IGlc75YE0PbiTV3JpqHZcEHniyoWtgsu5yNYIv/A4usl6H8CNP5+8VfBmzNd2EJk4gx hJimBZyQTk7g06cITRseuJ4bk5hE/WJk7w2dHgU=
Date: Tue, 6 Feb 2007 17:26:16 -0700
From: Philip Guenther <guenther+mtafilters@sendmail.com>
X-X-Sender: guenther@vanye.mho.net
To: ietf-mta-filters@imc.org
Subject: 3028bis, section 4.2, paragraph 2
Message-ID: <Pine.BSO.4.64.0702061716310.25985@vanye.mho.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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>

There's been some lingering dislike of the description of the redirect 
action, particularly how it describes the change of envelope recipient. 
3028bis-10 removed this sentence
 	The "redirect" modifies the envelope recipient.

as it was observed that it implied that the result of the 'envelope' test 
would be affected.  With that gone, only the second paragraph actually 
described how the address in the action was to become an envelope 
recipient, but it's description is fairly indirect.  So, I propose 
replacing most of that paragraph, so that instead of reading thusly:

    The redirect command performs an MTA-style "forward"--that is, what
    you get from a .forward file using sendmail under UNIX.  The address
    on the [SMTP] envelope is replaced with the one on the redirect
    command and the message is sent back out.  (This is not an MUA-style
    forward, which creates a new message with a different sender and
    message ID, wrapping the old message in a new one.)

it would instead say:

    The message is send back out with the address from the redirect
    command as an envelope recipient.  Implementations MAY combine
    separate redirects for a given message into a single submission with
    multiple envelope recipients.  (This is not an MUA-style forward,
    which creates a new message with a different sender and message ID,
    wrapping the old message in a new one.)

And yes, the elimination of the mention of .forward files in intentional, 
as that irked some.


Are there any objections to the above change?


Philip Guenther



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 l16MroPa074834 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Feb 2007 15:53:50 -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 l16Mro4C074832; Tue, 6 Feb 2007 15:53:50 -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 shell.mv.net (osmium.mv.net [199.125.85.152]) by balder-227.proper.com (8.13.5/8.13.5) with SMTP id l16MrmAB074824 for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 15:53:49 -0700 (MST) (envelope-from mem@mv.mv.com)
Received: (qmail 40563 invoked by uid 101); 6 Feb 2007 17:53:45 -0500
From: "Mark E. Mallett" <mem@mv.mv.com>
Date: Tue, 6 Feb 2007 17:53:45 -0500
To: ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before sending         it to IESG
Message-ID: <20070206225345.GA37772@osmium.mv.net>
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com> <45C770D8.9070504@andrew.cmu.edu> <Pine.BSO.4.64.0702051329280.9988@vanye.mho.net> <45C8C641.5090801@isode.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <45C8C641.5090801@isode.com>
User-Agent: Mutt/1.4.2.1i
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>

On Tue, Feb 06, 2007 at 06:17:37PM +0000, Alexey Melnikov wrote:
> 
> Philip Guenther wrote:
> >
> >   QUANTIFIER = "K" / "M" / "G"
> >
> >Literal strings in ABNF are always case-insensitive.
> 
> Ok, you are right. But many people got beaten by this ABNF "feature".

My implementation treats them as case insensitive, mainly because I
wanted it that way and didn't think it would hurt anything to be
friendlier to humans typing numbers.  

So I'm happy with the change :)

mm



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 l16KXHfU066125 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Feb 2007 13:33:17 -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 l16KXHe6066124; Tue, 6 Feb 2007 13:33:17 -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 mulberrymail.com (static-71-240-120-213.pitt.east.verizon.net [71.240.120.213]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l16KXFui066104 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 13:33:16 -0700 (MST) (envelope-from cyrus@daboo.name)
Received: from [17.101.32.44] ([17.101.32.44]) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id l16KX7o4031488 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Feb 2007 15:33:09 -0500
Date: Tue, 06 Feb 2007 15:33:02 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Philip Guenther <guenther+mtafilters@sendmail.com>, Ken Murchison <murch@andrew.cmu.edu>
cc: ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before    sending         it to IESG
Message-ID: <EB285C61567E499E69874B94@caldav.apple.com>
In-Reply-To: <Pine.BSO.4.64.0702051329280.9988@vanye.mho.net>
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com> <45C770D8.9070504@andrew.cmu.edu> <Pine.BSO.4.64.0702051329280.9988@vanye.mho.net>
X-Mailer: Mulberry/4.1.0a1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Status: No, score=0.7 required=5.0 tests=SUBJ_HAS_SPACES  autolearn=disabled version=3.1.1
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on  piper.mulberrymail.com
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>

Hi Philip,

--On February 5, 2007 1:33:43 PM -0700 Philip Guenther 
<guenther+mtafilters@sendmail.com> wrote:

>> Obviously, digits are case-insensitive, but by stating "number" this
>> also  includes QUANTIFIER, which only allows uppercase per the ABNF.
>
> Nope.  RFC 3028 said:
>
>     QUANTIFIER = "K" / "M" / "G"
>
> Literal strings in ABNF are always case-insensitive.
>
> So the question is: was this a bug in the grammar or a bug in those
> implementations?

Based on responses from others, I think we have to leave this as-is. 
Implementations treating those quantifiers as case-sensitive will need to 
be fixed.

-- 
Cyrus Daboo



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 l16Jeb0k062778 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Feb 2007 12:40:37 -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 l16JebPt062777; Tue, 6 Feb 2007 12:40:37 -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.serendipity.cx (serendipity.palo-alto.ca.us [66.92.2.87]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l16JeaoY062771 for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 12:40:36 -0700 (MST) (envelope-from aaron@serendipity.cx)
Received: from serendipity.palo-alto.ca.us (localhost [127.0.0.1]) by mail.serendipity.cx (Postfix) with SMTP id A42E56024E31; Tue,  6 Feb 2007 11:39:50 -0800 (PST)
Date: Tue, 6 Feb 2007 19:39:50 -0000
To: "Ned Freed" <ned.freed@mrochek.com>
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before sending it to IESG
From: "Aaron Stone" <aaron@serendipity.cx>
X-Mailer: TWIG 2.8.2
Message-ID: <twig.1170790790.9342@serendipity.palo-alto.ca.us>
In-Reply-To: <01MCT5QRXR5600004S@mauve.mrochek.com>
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com> <d2Or/zTym5ykDhlHnjOEFQ.md5@libertango.oryx.com> <45C8C681.5080900@isode.com> <iQX+wKZNMRoWQX58zgxdpQ.md5@libertango.oryx.com>, 
Cc: <ietf-mta-filters@imc.org>, "Alexey Melnikov" <alexey.melnikov@isode.com>, "Arnt Gulbrandsen" <arnt@oryx.com>
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>

On Tue, Feb 6, 2007, Ned Freed <ned.freed@mrochek.com> said:

>> Alexey Melnikov writes:
>> > Arnt Gulbrandsen wrote:
>> >> Alexey Melnikov writes:
[snip]
>> >>> I actually have a problem with *numbers* being case-insensitive.
>> >>> Cyrus Sieve doesn't accept "k", "m" and "g" prefixes in numbers.
>> >>>
>> >>> So I would like to poll the WG regarding this issue. Do people want
>> >>> to make to make number case-insensitive, or should this change be
>> >>> undone?
>> >>
>> >> Making numbers case-sensitive could invalidate extant valid scripts.
>> >> That needs strong justification IMO.
>> >
>> > Let's assess the damage first. If it turns out that the majority of
>> > implementations implement case-insensitive suffixes, then I will have
>> > to fix my implementation ;-).
> 
>> I wrote my code case-insensitively, but it's unreleased as yet.
[snip]
> I believe our script generator puts these out in upper case and I know
> I've seen hand-constructed scripts have them in lower case. So scripts
> are probably gonna break if we make this case-sensitive.

Sounds like one of those cases where the spec should be strict but the
implementations should be relaxed.

Aaron



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 l16JB2kP060178 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Feb 2007 12:11:02 -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 l16JB2Kq060177; Tue, 6 Feb 2007 12:11:02 -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.serendipity.cx (serendipity.palo-alto.ca.us [66.92.2.87]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l16JAxvA060148 for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 12:11:01 -0700 (MST) (envelope-from aaron@serendipity.cx)
Received: from serendipity.palo-alto.ca.us (localhost [127.0.0.1]) by mail.serendipity.cx (Postfix) with SMTP id BCEB66024E31; Tue,  6 Feb 2007 11:10:08 -0800 (PST)
Date: Tue, 6 Feb 2007 19:10:08 -0000
To: "Ken Murchison" <murch@andrew.cmu.edu>
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before         sending         it to IESG
From: "Aaron Stone" <aaron@serendipity.cx>
X-Mailer: TWIG 2.8.2
Message-ID: <twig.1170789008.70289@serendipity.palo-alto.ca.us>
In-Reply-To: <45C8CBEE.8030102@andrew.cmu.edu>
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com> <45C770D8.9070504@andrew.cmu.edu> <Pine.BSO.4.64.0702051329280.9988@vanye.mho.net> <45C8C641.5090801@isode.com>, <45C8C641.5090801@isode.com>
Cc: <ietf-mta-filters@imc.org>
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>

On Tue, Feb 6, 2007, Ken Murchison <murch@andrew.cmu.edu> said:

>>>> Obviously, digits are case-insensitive, but by stating "number" this 
>>>> also includes QUANTIFIER, which only allows uppercase per the ABNF.
>>>
>>> Nope.  RFC 3028 said:
>>>
>>>    QUANTIFIER = "K" / "M" / "G"
>>>
>>> Literal strings in ABNF are always case-insensitive.
>> 
>> Ok, you are right. But many people got beaten by this ABNF "feature".
> 
> Including CMU (before my time).  Its about a 10 sec fix for me, so I'll 
> do whatever the consensus dictates.

I've inherited that same line in my lexer (with the same effort required
to change it ;-). I don't feel strongly either way as to whether we should
relax the spec to be case insensitive.

Aaron



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 l16J4t8j059824 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Feb 2007 12:04:55 -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 l16J4t6u059823; Tue, 6 Feb 2007 12:04:55 -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 mauve.mrochek.com (netblock-68-183-106-173.brandx.net [68.183.106.173] (may be forged)) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l16J4r1W059817 for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 12:04:53 -0700 (MST) (envelope-from ned.freed@mrochek.com)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01MCT5QTUKHC001ACT@mauve.mrochek.com> for ietf-mta-filters@imc.org; Tue, 6 Feb 2007 11:04:49 -0800 (PST)
DKIM-Signature: a=rsa-sha1; c=nowsp; d=mrochek.com; s=mauve; t=1170788688; h=Date: 	 From:Subject:MIME-version:Content-type; b=s5UyP1knrCLh8wK0lbvrx/3ia lkZ6zcEO8B/ckbWSi+Fcm3HV+CsYvIo0/So9ZGrqqtfRNzN6lb6niOKVp9BBw==
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01MCSCUL997K00004S@mauve.mrochek.com>; Tue, 06 Feb 2007 11:04:44 -0800 (PST)
Cc: ietf-mta-filters@imc.org, Alexey Melnikov <alexey.melnikov@isode.com>
Message-id: <01MCT5QRXR5600004S@mauve.mrochek.com>
Date: Tue, 06 Feb 2007 10:58:54 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before sending it to IESG
In-reply-to: "Your message dated Tue, 06 Feb 2007 19:40:07 +0100" <iQX+wKZNMRoWQX58zgxdpQ.md5@libertango.oryx.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; format=flowed
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com> <d2Or/zTym5ykDhlHnjOEFQ.md5@libertango.oryx.com> <45C8C681.5080900@isode.com> <iQX+wKZNMRoWQX58zgxdpQ.md5@libertango.oryx.com>
To: Arnt Gulbrandsen <arnt@oryx.com>
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>

> Alexey Melnikov writes:
> > Arnt Gulbrandsen wrote:
> >
> >> Alexey Melnikov writes:
> >>
> >>> I actually do have one issue with a recent change in -10 which I
> >>> consider to be serious, because it broke my Sieve implementation
> >>> (as well as CMU's)
> >>
> >> Why did this break your implementation? It did not cause any
> >> previously valid scripts to become invalid. All it did was clarify
> >> an existing rule.
> >
> > If somebody puts "100k" in a Sieve script, Sieve lexer is going to
> > reject such script.

> Yes. But that's not lasting damage - the user has to change kmg to KMG
> and upload the script again.

> Compare that with the alternative: Scripts which have passed
> managesieve's putscript checking become syntactically invalid when the
> server is upgraded.

> >>> I actually have a problem with *numbers* being case-insensitive.
> >>> Cyrus Sieve doesn't accept "k", "m" and "g" prefixes in numbers.
> >>>
> >>> So I would like to poll the WG regarding this issue. Do people want
> >>> to make to make number case-insensitive, or should this change be
> >>> undone?
> >>
> >> Making numbers case-sensitive could invalidate extant valid scripts.
> >> That needs strong justification IMO.
> >
> > Let's assess the damage first. If it turns out that the majority of
> > implementations implement case-insensitive suffixes, then I will have
> > to fix my implementation ;-).

> I wrote my code case-insensitively, but it's unreleased as yet.

FWIW, our implementation also handles either case. The only "problem" we've ever
had with this feature is users who enter values like 100000G and then get upset
when it says "integer too large" or something similar. (Yes, we frequently get
absurd complaints like this.)

I believe our script generator puts these out in upper case and I know I've
seen hand-constructed scripts have them in lower case. So scripts are probably
gonna break if we make this case-sensitive.

				Ned



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 l16IgKm4058112 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Feb 2007 11:42:20 -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 l16IgKA9058111; Tue, 6 Feb 2007 11:42:20 -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 smtp.andrew.cmu.edu (smtp.andrew.cmu.edu [128.2.10.81]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l16IgIKw058100 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 11:42:19 -0700 (MST) (envelope-from murch@andrew.cmu.edu)
Received: from [192.168.137.23] (ntonawnd-cuda1-cable-bundle-68-69-73-26.kntnny.adelphia.net [68.69.73.26]) (user=murch mech=PLAIN (0 bits)) by smtp.andrew.cmu.edu (8.13.6/8.13.6) with ESMTP id l16IgAsP032350 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 6 Feb 2007 13:42:11 -0500
Message-ID: <45C8CBEE.8030102@andrew.cmu.edu>
Date: Tue, 06 Feb 2007 13:41:50 -0500
From: Ken Murchison <murch@andrew.cmu.edu>
Organization: Carnegie Mellon University
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
CC: Philip Guenther <guenther+mtafilters@sendmail.com>, ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before sending         it to IESG
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com> <45C770D8.9070504@andrew.cmu.edu> <Pine.BSO.4.64.0702051329280.9988@vanye.mho.net> <45C8C641.5090801@isode.com>
In-Reply-To: <45C8C641.5090801@isode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 128.2.10.81
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>

Alexey Melnikov wrote:
> Philip Guenther wrote:
> 
>> On Mon, 5 Feb 2007, Ken Murchison wrote:
>>
>>> Alexey Melnikov wrote:
>>
>> ...
>>
>>>> I actually have a problem with *numbers* being case-insensitive. Cyrus
>>>> Sieve doesn't accept "k", "m" and "g" prefixes in numbers.
>>>>
>>>> So I would like to poll the WG regarding this issue. Do people want 
>>>> to make to make number case-insensitive, or should this change be 
>>>> undone?
>>>> (In the latter case there is one example in 3028bis-10 which uses 
>>>> lowercase 'k' now, which has to change)
>>>
>>> Obviously, digits are case-insensitive, but by stating "number" this 
>>> also includes QUANTIFIER, which only allows uppercase per the ABNF.
>>
>> Nope.  RFC 3028 said:
>>
>>    QUANTIFIER = "K" / "M" / "G"
>>
>> Literal strings in ABNF are always case-insensitive.
> 
> Ok, you are right. But many people got beaten by this ABNF "feature".

Including CMU (before my time).  Its about a 10 sec fix for me, so I'll 
do whatever the consensus dictates.

-- 
Kenneth Murchison
Project Cyrus Developer/Maintainer
Carnegie Mellon University



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 l16IdWjl057885 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Feb 2007 11:39:32 -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 l16IdVgx057884; Tue, 6 Feb 2007 11:39:31 -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 kalyani.oryx.com (kalyani.oryx.com [195.30.37.30]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l16IdUc8057873 for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 11:39:31 -0700 (MST) (envelope-from arnt@oryx.com)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id CDA6C4AC5B; Tue,  6 Feb 2007 19:39:30 +0100 (CET)
Message-Id: <iQX+wKZNMRoWQX58zgxdpQ.md5@libertango.oryx.com>
Date: Tue, 6 Feb 2007 19:40:07 +0100
From: Arnt Gulbrandsen <arnt@oryx.com>
To: ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before sending it to IESG
Cc: Alexey Melnikov <alexey.melnikov@isode.com>
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com> <d2Or/zTym5ykDhlHnjOEFQ.md5@libertango.oryx.com> <45C8C681.5080900@isode.com>
In-Reply-To: <45C8C681.5080900@isode.com>
Content-Type: text/plain; format=flowed
MIME-Version: 1.0
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>

Alexey Melnikov writes:
> Arnt Gulbrandsen wrote:
>
>> Alexey Melnikov writes:
>>
>>> I actually do have one issue with a recent change in -10 which I 
>>> consider to be serious, because it broke my Sieve implementation 
>>> (as well as CMU's)
>>
>> Why did this break your implementation? It did not cause any 
>> previously valid scripts to become invalid. All it did was clarify 
>> an existing rule.
>
> If somebody puts "100k" in a Sieve script, Sieve lexer is going to 
> reject such script.

Yes. But that's not lasting damage - the user has to change kmg to KMG 
and upload the script again.

Compare that with the alternative: Scripts which have passed 
managesieve's putscript checking become syntactically invalid when the 
server is upgraded.

>>> I actually have a problem with *numbers* being case-insensitive. 
>>> Cyrus Sieve doesn't accept "k", "m" and "g" prefixes in numbers.
>>>
>>> So I would like to poll the WG regarding this issue. Do people want 
>>> to make to make number case-insensitive, or should this change be 
>>> undone?
>>
>> Making numbers case-sensitive could invalidate extant valid scripts. 
>> That needs strong justification IMO.
>
> Let's assess the damage first. If it turns out that the majority of 
> implementations implement case-insensitive suffixes, then I will have 
> to fix my implementation ;-).

I wrote my code case-insensitively, but it's unreleased as yet.

Arnt



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 l16IJ7Q3056507 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Feb 2007 11:19:08 -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 l16IJ7or056506; Tue, 6 Feb 2007 11:19:07 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l16IJ7SU056500 for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 11:19:07 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <RcjGmABXDpJW@rufus.isode.com>; Tue, 6 Feb 2007 18:19:04 +0000
Message-ID: <45C8C681.5080900@isode.com>
Date: Tue, 06 Feb 2007 18:18:41 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Arnt Gulbrandsen <arnt@oryx.com>
CC: ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before sending it to IESG
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org>  <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com> <d2Or/zTym5ykDhlHnjOEFQ.md5@libertango.oryx.com>
In-Reply-To: <d2Or/zTym5ykDhlHnjOEFQ.md5@libertango.oryx.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Arnt Gulbrandsen wrote:

> Alexey Melnikov writes:
>
>> I actually do have one issue with a recent change in -10 which I 
>> consider to be serious, because it broke my Sieve implementation (as 
>> well as CMU's)
>
> Why did this break your implementation? It did not cause any 
> previously valid scripts to become invalid. All it did was clarify an 
> existing rule.

If somebody puts "100k" in a Sieve script, Sieve lexer is going to 
reject such script.

>> I actually have a problem with *numbers* being case-insensitive. 
>> Cyrus Sieve doesn't accept "k", "m" and "g" prefixes in numbers.
>>
>> So I would like to poll the WG regarding this issue. Do people want 
>> to make to make number case-insensitive, or should this change be 
>> undone?
>
> Making numbers case-sensitive could invalidate extant valid scripts. 
> That needs strong justification IMO.

Let's assess the damage first. If it turns out that the majority of 
implementations implement case-insensitive suffixes, then I will have to 
fix my implementation ;-).



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 l16II4F5056420 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Feb 2007 11:18:04 -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 l16II4Qr056419; Tue, 6 Feb 2007 11:18:04 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l16II2td056411 for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 11:18:03 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <RcjGWABXDqxQ@rufus.isode.com>; Tue, 6 Feb 2007 18:18:01 +0000
Message-ID: <45C8C641.5090801@isode.com>
Date: Tue, 06 Feb 2007 18:17:37 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Philip Guenther <guenther+mtafilters@sendmail.com>
CC: Ken Murchison <murch@andrew.cmu.edu>, ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before sending         it to IESG
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com> <45C770D8.9070504@andrew.cmu.edu> <Pine.BSO.4.64.0702051329280.9988@vanye.mho.net>
In-Reply-To: <Pine.BSO.4.64.0702051329280.9988@vanye.mho.net>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>

Philip Guenther wrote:

> On Mon, 5 Feb 2007, Ken Murchison wrote:
>
>> Alexey Melnikov wrote:
>
> ...
>
>>> I actually have a problem with *numbers* being case-insensitive. Cyrus
>>> Sieve doesn't accept "k", "m" and "g" prefixes in numbers.
>>>
>>> So I would like to poll the WG regarding this issue. Do people want 
>>> to make to make number case-insensitive, or should this change be 
>>> undone?
>>> (In the latter case there is one example in 3028bis-10 which uses 
>>> lowercase 'k' now, which has to change)
>>
>> Obviously, digits are case-insensitive, but by stating "number" this 
>> also includes QUANTIFIER, which only allows uppercase per the ABNF.
>
> Nope.  RFC 3028 said:
>
>    QUANTIFIER = "K" / "M" / "G"
>
> Literal strings in ABNF are always case-insensitive.

Ok, you are right. But many people got beaten by this ABNF "feature".

> So the question is: was this a bug in the grammar or a bug in those 
> implementations?

Indeed.

> I know that the Sendmail implementation has treated them as 
> case-insensitive from its beginning.




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 l16I35Ui055092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Feb 2007 11:03:05 -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 l16I350X055091; Tue, 6 Feb 2007 11:03:05 -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 kalyani.oryx.com (kalyani.oryx.com [195.30.37.30]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l16I33hF055084 for <ietf-mta-filters@imc.org>; Tue, 6 Feb 2007 11:03:04 -0700 (MST) (envelope-from arnt@oryx.com)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id 4AE204AC5B; Tue,  6 Feb 2007 19:03:04 +0100 (CET)
Message-Id: <d2Or/zTym5ykDhlHnjOEFQ.md5@libertango.oryx.com>
Date: Tue, 6 Feb 2007 19:03:41 +0100
From: Arnt Gulbrandsen <arnt@oryx.com>
To: ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before sending it to IESG
Cc: Alexey Melnikov <alexey.melnikov@isode.com>
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com>
In-Reply-To: <45C7551B.7000309@isode.com>
Content-Type: text/plain; format=flowed
MIME-Version: 1.0
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>

Alexey Melnikov writes:
> I actually do have one issue with a recent change in -10 which I 
> consider to be serious, because it broke my Sieve implementation (as 
> well as CMU's)

Why did this break your implementation? It did not cause any previously 
valid scripts to become invalid. All it did was clarify an existing 
rule.

> I actually have a problem with *numbers* being case-insensitive. Cyrus 
> Sieve doesn't accept "k", "m" and "g" prefixes in numbers.
>
> So I would like to poll the WG regarding this issue. Do people want to 
> make to make number case-insensitive, or should this change be 
> undone?

Making numbers case-sensitive could invalidate extant valid scripts. 
That needs strong justification IMO.

Arnt



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 l168gSAi078902 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Feb 2007 01:42:41 -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 l15KY4WG069939; Mon, 5 Feb 2007 13:34:04 -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 smtp-out.sendmail.com (smtp-out.sendmail.com [209.246.26.45]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l15KY0We069774 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 13:34:02 -0700 (MST) (envelope-from guenther+mtafilters@sendmail.com)
Received: from [10.0.0.51] (71-208-198-236.hlrn.qwest.net [71.208.198.236]) (authenticated bits=0) by foon.sendmail.com (Switch-3.2.5/Switch-3.2.0) with ESMTP id l15KXi8j000331 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Feb 2007 12:33:46 -0800
X-DKIM: Sendmail DKIM Filter v0.5.1 foon.sendmail.com l15KXi8j000331
DKIM-Signature: a=rsa-sha1; c=relaxed/simple; d=sendmail.com; s=tls.dkim; t=1170707631; bh=jH+MF8+WOuE4yvEEF3SENIVvA8M=; h=X-DomainKeys: DomainKey-Signature:Date:From:X-X-Sender:To:cc:Subject:In-Reply-To: Message-ID:References:MIME-Version:Content-Type; b=kkVbYHmQcFpj1zSv hcAhSe8LoPVmlXvdo6iIz998gx+UCiJ39craoqw7bEB6119KgwmqQZLUMn/VgA99VQv i8IK4F/JAciEmSdhSnh4K9hmuCeSujZCAwIDsany4Mk5AOp0nv51EBZacEW6x0frpyq FWaBv0MObVNhP+C3tfOEw=
X-DomainKeys: Sendmail DomainKeys Filter v0.4.1 foon.sendmail.com l15KXi8j000331
DomainKey-Signature: a=rsa-sha1; s=tls; d=sendmail.com; c=nofws; q=dns; h=date:from:x-x-sender:to:cc:subject:in-reply-to:message-id: references:mime-version:content-type; b=PdVUn8XGPgB1RKDeQIlS6CZ+TQdQYNjFlM7s5efMzTc5YnRTQydMW89uK0a0ftnUP OZqpU8P99R9kHPJAMCLNVGTFb93FH6OuQxVqKq0qQtVd3FI/uROgN1/uo2PSbbNKRa9 0FUH0gYlMpSs8W/CituZ+TuuOnBqa5stz+uT9j0=
Date: Mon, 5 Feb 2007 13:33:43 -0700
From: Philip Guenther <guenther+mtafilters@sendmail.com>
X-X-Sender: guenther@vanye.mho.net
To: Ken Murchison <murch@andrew.cmu.edu>
cc: ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before   sending         it to IESG
In-Reply-To: <45C770D8.9070504@andrew.cmu.edu>
Message-ID: <Pine.BSO.4.64.0702051329280.9988@vanye.mho.net>
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com> <45C770D8.9070504@andrew.cmu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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>

On Mon, 5 Feb 2007, Ken Murchison wrote:
> Alexey Melnikov wrote:
...
>> I actually have a problem with *numbers* being case-insensitive. Cyrus
>> Sieve doesn't accept "k", "m" and "g" prefixes in numbers.
>> 
>> So I would like to poll the WG regarding this issue. Do people want to make 
>> to make number case-insensitive, or should this change be undone?
>> (In the latter case there is one example in 3028bis-10 which uses lowercase 
>> 'k' now, which has to change)
>
> Obviously, digits are case-insensitive, but by stating "number" this also 
> includes QUANTIFIER, which only allows uppercase per the ABNF.

Nope.  RFC 3028 said:

    QUANTIFIER = "K" / "M" / "G"

Literal strings in ABNF are always case-insensitive.

So the question is: was this a bug in the grammar or a bug in those 
implementations?  I know that the Sendmail implementation has treated them 
as case-insensitive from its beginning.


Philip Guenther



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 l15J55R7006805 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Feb 2007 12:05:05 -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 l15J54Jd006797; Mon, 5 Feb 2007 12:05:05 -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 kalyani.oryx.com (kalyani.oryx.com [195.30.37.30]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l15J52pM006731 for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 12:05:04 -0700 (MST) (envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id 1D3594AC8C; Mon,  5 Feb 2007 20:05:03 +0100 (CET)
Message-Id: <oXaabEEMm76YjD0UKajbMw.md5@libertango.oryx.com>
Date: Mon, 5 Feb 2007 20:05:35 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-mta-filters@imc.org
Subject: Re: some thoughts
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Dilyan Palauzov <Dilyan.Palauzov@aegee.org>
References: <20070205174052.dj1w9orq4g08osg8@mail.aegee.org> <66Cb5v2uUGlahT+ZZhXGHg.md5@libertango.oryx.com> <45C77DCC.7040508@isode.com>
In-Reply-To: <45C77DCC.7040508@isode.com>
Content-Type: text/plain; format=flowed
MIME-Version: 1.0
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>

Alexey Melnikov writes:
> Indeed. As far as Sieve is concerned, each envelope always contains a 
> single recipient.

I would not protest strongly if an implementation were to include 
aliases leading to the recipient.

Arnt



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 l15Iuc7b094450 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Feb 2007 11:56:38 -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 l15IucbV094449; Mon, 5 Feb 2007 11:56:38 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l15Iubgr094436 for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 11:56:37 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <Rcd94wBXDoaE@rufus.isode.com>; Mon, 5 Feb 2007 18:56:35 +0000
Message-ID: <45C77DCC.7040508@isode.com>
Date: Mon, 05 Feb 2007 18:56:12 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
CC: ietf-mta-filters@imc.org, Dilyan Palauzov <Dilyan.Palauzov@aegee.org>
Subject: Re: some thoughts
References: <20070205174052.dj1w9orq4g08osg8@mail.aegee.org> <66Cb5v2uUGlahT+ZZhXGHg.md5@libertango.oryx.com>
In-Reply-To: <66Cb5v2uUGlahT+ZZhXGHg.md5@libertango.oryx.com>
MIME-version: 1.0
Content-type: text/plain; charset="KOI8-R"; format="flowed"
Content-transfer-encoding: 7bit
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>

Arnt Gulbrandsen wrote:

>>  - envelopes
>> If a mail goes to several recepients, but in one envelope, test  
>> address and test envelope can figure it out, but then the rfc3028  
>> permits that one user removes the other from the envelope. E.g. if a  
>> mail goes
>> To: a@d.e, b@d.e
>>
>> the a@d.e. might have the follwoing script
>>
>> if envelope :all is "to" b@d.e discard;
>>
>> then the mail might not be delivered to b@d.e . Is there any 
>> sentence,  I have overseen, prohibiting that the different users' 
>> scripts may not  interfere?
>
> I eventually decided that a@d.e should not be able to tell whether the 
> envelope contains b@d.e. If b@d.e is a bcc, revealing it in sieve 
> would be a privacy leak.

Indeed. As far as Sieve is concerned, each envelope always contains a 
single recipient.



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 l15IuZPc094399 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Feb 2007 11:56:36 -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 l15IuZGh094396; Mon, 5 Feb 2007 11:56:35 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l15IuYJk094367 for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 11:56:35 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <Rcd94QBXDkGD@rufus.isode.com>; Mon, 5 Feb 2007 18:56:33 +0000
Message-ID: <45C77DCA.4050707@isode.com>
Date: Mon, 05 Feb 2007 18:56:10 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Dilyan Palauzov <Dilyan.Palauzov@aegee.org>
CC: ietf-mta-filters@imc.org
Subject: Re: some thoughts
References: <20070205174052.dj1w9orq4g08osg8@mail.aegee.org>
In-Reply-To: <20070205174052.dj1w9orq4g08osg8@mail.aegee.org>
MIME-version: 1.0
Content-type: text/plain; charset="UTF-8"; format="flowed"
Content-transfer-encoding: 7bit
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>

Dilyan Palauzov wrote:

>   Hi folks,
>
>   I was thinking on implementing a sieve-milter, an addon for  
> sendmail, that filters mails for users, which do not necessary have  
> mailbox on that server. In such cases the filter is applied to the  
> whole envelope with its contents (except where the message is  
> modified, in which case a new message shall be generated). And on 
> some  points I continue to think how to implement them.
>  - test size
> How shall the implementation determine the size of the message: if 
> the  smtp server supports rfc 1870 (esmtp, size), can the sieve  
> implementation use that value (MAIL FROM: nana@aegee.org size=10000 ,  
> or shall count by itself the bytes contained?

Hi Dilyan,
SMTP SIZE is an approximation of the size, so ideally you should count 
bytes.



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 l15I6QML020320 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Feb 2007 11:06:26 -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 l15I6Q2B020319; Mon, 5 Feb 2007 11:06:26 -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 kalyani.oryx.com (kalyani.oryx.com [195.30.37.30]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l15I6PZm020309 for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 11:06:26 -0700 (MST) (envelope-from arnt@gulbrandsen.priv.no)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id 092984AC8C; Mon,  5 Feb 2007 19:06:25 +0100 (CET)
Message-Id: <66Cb5v2uUGlahT+ZZhXGHg.md5@libertango.oryx.com>
Date: Mon, 5 Feb 2007 19:06:56 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-mta-filters@imc.org
Subject: Re: some thoughts
Cc: Dilyan Palauzov <Dilyan.Palauzov@aegee.org>
References: <20070205174052.dj1w9orq4g08osg8@mail.aegee.org>
In-Reply-To: <20070205174052.dj1w9orq4g08osg8@mail.aegee.org>
Content-Type: text/plain; charset=koi8-r; format=flowed
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l15I6QZm020314
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>

Dilyan Palauzov writes:
>   Hi folks,
>
>   I was thinking on implementing a sieve-milter, an addon for  
>   sendmail, that filters mails for users, which do not necessary have 
>    mailbox on that server. In such cases the filter is applied to the 
>    whole envelope with its contents (except where the message is  
>   modified, in which case a new message shall be generated). And on 
>   some  points I continue to think how to implement them.
>  - test size
> How shall the implementation determine the size of the message: if the 
>  smtp server supports rfc 1870 (esmtp, size), can the sieve  
> implementation use that value (MAIL FROM: nana@aegee.org size=10000 , 
>  or shall count by itself the bytes contained?

I was pondering this (about postfix, not sendmail, in order to do 
protocol-level reject) and thought I'd use SIZE=x until the counted 
size is available, and after that use the counted size.

>  - envelopes
> If a mail goes to several recepients, but in one envelope, test  
> address and test envelope can figure it out, but then the rfc3028  
> permits that one user removes the other from the envelope. E.g. if a  
> mail goes
> To: a@d.e, b@d.e
>
> the a@d.e. might have the follwoing script
>
> if envelope :all is "to" b@d.e discard;
>
> then the mail might not be delivered to b@d.e . Is there any sentence, 
>  I have overseen, prohibiting that the different users' scripts may 
> not  interfere?

I eventually decided that a@d.e should not be able to tell whether the 
envelope contains b@d.e. If b@d.e is a bcc, revealing it in sieve would 
be a privacy leak.

>   Greetings,
>     äÉÌÑÎ

(I can read all of that. I feel proud.)

Arnt



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 l15I1FX0014200 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Feb 2007 11:01:15 -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 l15I1FiA014193; Mon, 5 Feb 2007 11:01:15 -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 smtp.andrew.cmu.edu (smtp.andrew.cmu.edu [128.2.10.81]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l15I1DeL014123 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 11:01:14 -0700 (MST) (envelope-from murch@andrew.cmu.edu)
Received: from [192.168.137.23] (ntonawnd-cuda1-cable-bundle-68-69-73-26.kntnny.adelphia.net [68.69.73.26]) (user=murch mech=PLAIN (0 bits)) by smtp.andrew.cmu.edu (8.13.6/8.13.6) with ESMTP id l15I151j011858 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 13:01:10 -0500
Message-ID: <45C770D8.9070504@andrew.cmu.edu>
Date: Mon, 05 Feb 2007 13:00:56 -0500
From: Ken Murchison <murch@andrew.cmu.edu>
Organization: Carnegie Mellon University
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before sending         it to IESG
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com> <45C7551B.7000309@isode.com>
In-Reply-To: <45C7551B.7000309@isode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 128.2.10.81
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>

Alexey Melnikov wrote:
> 
> Alexey Melnikov wrote:
> 
>> Folks,
>> This is your last chance to review that the document is correct and 
>> complete. No new issues can be raised at this stage unless they are 
>> very serious.
> 
> I actually do have one issue with a recent change in -10 which I 
> consider to be serious, because it broke my Sieve implementation (as 
> well as CMU's)
> 
>  > 8.1.     Lexical Tokens
>  >
>  >    Sieve scripts are encoded in UTF-8.  The following assumes a valid
>  >    UTF-8 encoding; special characters in Sieve scripts are all US-ASCII.
>  >
>  >    The following are tokens in Sieve:
>  >
>  >            - identifiers
>  >            - tags
>  >            - numbers
>  >            - quoted strings
>  >            - multi-line strings
>  >            - other separators
>  >
>  >    Identifiers, tags, and numbers are case-insensitive, while quoted
>  >    strings and multi-line strings are case-sensitive.
> 
> I actually have a problem with *numbers* being case-insensitive. Cyrus
> Sieve doesn't accept "k", "m" and "g" prefixes in numbers.
> 
> So I would like to poll the WG regarding this issue. Do people want to 
> make to make number case-insensitive, or should this change be undone?
> (In the latter case there is one example in 3028bis-10 which uses 
> lowercase 'k' now, which has to change)

Obviously, digits are case-insensitive, but by stating "number" this 
also includes QUANTIFIER, which only allows uppercase per the ABNF.

I think we should move "numbers" from the case-insensitive list to the 
case-sensitive list in order to maintain backwards compatibility.

-- 
Kenneth Murchison
Project Cyrus Developer/Maintainer
Carnegie Mellon University



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 l15GevHW069694 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Feb 2007 09:40:57 -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 l15GevNg069692; Mon, 5 Feb 2007 09:40:57 -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 smtp.aegee.uni-karlsruhe.de (smtp.aegee.uni-karlsruhe.de [129.13.62.220]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l15GesxK069677 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 09:40:56 -0700 (MST) (envelope-from Dilyan.Palauzov@aegee.org)
Received: from aegeeserv.aegee.org (aegeeserv.aegee.uni-karlsruhe.de [129.13.131.80]) by smtp2.rz.uni-karlsruhe.de with esmtp (Exim 4.63 #1) id 1HE6th-00041h-4N; Mon, 05 Feb 2007 17:40:53 +0100
Received: from AEGEEserv.aegee.uni-karlsruhe.de (localhost [127.0.0.1]) by aegeeserv.aegee.org (8.13.8/8.13.6) with ESMTP id l15Geq9S030011 for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 16:40:52 GMT
Received: (from wwwrun@localhost) by AEGEEserv.aegee.uni-karlsruhe.de (8.13.8/8.13.6/Submit) id l15GeqX2030010 for ietf-mta-filters@imc.org; Mon, 5 Feb 2007 17:40:52 +0100
X-Authentication-Warning: AEGEEserv.aegee.uni-karlsruhe.de: wwwrun set sender to Dilyan.Palauzov@aegee.org using -f
Received: from nan-y403.nan.uni-karlsruhe.de (nan-y403.nan.uni-karlsruhe.de [172.20.21.213]) by mail.aegee.org (Horde MIME library) with HTTP; Mon, 05 Feb 2007 17:40:52 +0100
Message-ID: <20070205174052.dj1w9orq4g08osg8@mail.aegee.org>
Date: Mon, 05 Feb 2007 17:40:52 +0100
From: Dilyan Palauzov <Dilyan.Palauzov@aegee.org>
To: ietf-mta-filters@imc.org
Subject: some thoughts
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed"
Content-Disposition: inline
User-Agent: Internet Messaging Program (IMP) H3 (4.1.3)
X-Virus-Scanned: ClamAV 0.88.7/2523/Sun Feb  4 19:16:40 2007 on AEGEEserv.aegee.uni-karlsruhe.de
X-Virus-Status: Clean
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l15GevxJ069687
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>

   Hi folks,

   I was thinking on implementing a sieve-milter, an addon for  
sendmail, that filters mails for users, which do not necessary have  
mailbox on that server. In such cases the filter is applied to the  
whole envelope with its contents (except where the message is  
modified, in which case a new message shall be generated). And on some  
points I continue to think how to implement them.
  - test size
How shall the implementation determine the size of the message: if the  
smtp server supports rfc 1870 (esmtp, size), can the sieve  
implementation use that value (MAIL FROM: nana@aegee.org size=10000 ,  
or shall count by itself the bytes contained?

  - envelopes
If a mail goes to several recepients, but in one envelope, test  
address and test envelope can figure it out, but then the rfc3028  
permits that one user removes the other from the envelope. E.g. if a  
mail goes
To: a@d.e, b@d.e

the a@d.e. might have the follwoing script

if envelope :all is "to" b@d.e discard;

then the mail might not be delivered to b@d.e . Is there any sentence,  
I have overseen, prohibiting that the different users' scripts may not  
interfere?
   Greetings,
     Ð”Ð¸Ð»Ñ�Ð½




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 l15G30Fp060654 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Feb 2007 09:03:00 -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 l15G30s1060653; Mon, 5 Feb 2007 09:03:00 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l15G2xKh060647 for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 09:03:00 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <RcdVMQBXDsf-@rufus.isode.com>; Mon, 5 Feb 2007 16:02:58 +0000
Message-ID: <45C7551B.7000309@isode.com>
Date: Mon, 05 Feb 2007 16:02:35 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: ietf-mta-filters@imc.org
Subject: Re: Last chance to review draft-ietf-sieve-3028bis-10.txt before sending         it to IESG
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org> <45C753CF.7080906@isode.com>
In-Reply-To: <45C753CF.7080906@isode.com>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>

Alexey Melnikov wrote:

> Folks,
> This is your last chance to review that the document is correct and 
> complete. No new issues can be raised at this stage unless they are 
> very serious.

I actually do have one issue with a recent change in -10 which I 
consider to be serious, because it broke my Sieve implementation (as 
well as CMU's)

 > 8.1.     Lexical Tokens
 >
 >    Sieve scripts are encoded in UTF-8.  The following assumes a valid
 >    UTF-8 encoding; special characters in Sieve scripts are all US-ASCII.
 >
 >    The following are tokens in Sieve:
 >
 >            - identifiers
 >            - tags
 >            - numbers
 >            - quoted strings
 >            - multi-line strings
 >            - other separators
 >
 >    Identifiers, tags, and numbers are case-insensitive, while quoted
 >    strings and multi-line strings are case-sensitive.

I actually have a problem with *numbers* being case-insensitive. Cyrus
Sieve doesn't accept "k", "m" and "g" prefixes in numbers.

So I would like to poll the WG regarding this issue. Do people want to 
make to make number case-insensitive, or should this change be undone?
(In the latter case there is one example in 3028bis-10 which uses 
lowercase 'k' now, which has to change)

Thanks,
Alexey



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 l15Fvd1i059388 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Feb 2007 08:57:39 -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 l15FvdnZ059387; Mon, 5 Feb 2007 08:57:39 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l15FvcEn059372 for <ietf-mta-filters@imc.org>; Mon, 5 Feb 2007 08:57:39 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <RcdT8ABXDpTg@rufus.isode.com>; Mon, 5 Feb 2007 15:57:37 +0000
Message-ID: <45C753CF.7080906@isode.com>
Date: Mon, 05 Feb 2007 15:57:03 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-mta-filters@imc.org
Subject: Last chance to review draft-ietf-sieve-3028bis-10.txt before sending it to IESG
References: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org>
In-Reply-To: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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>

Internet-Drafts@ietf.org wrote:

>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.
>
>	Title		: Sieve: An Email Filtering Language
>	Author(s)	: T. Showalter, P. Guenther
>	Filename	: draft-ietf-sieve-3028bis-10.txt
>	Pages		: 44
>	Date		: 2007-2-2
>	
>This document describes a language for filtering email messages at
>   time of final delivery.  It is designed to be implementable on either
>   a mail client or mail server.  It is meant to be extensible, simple,
>   and independent of access protocol, mail architecture, and operating
>   system.  It is suitable for running on a mail server where users may
>   not be allowed to execute arbitrary programs, such as on black box
>   Internet Message Access Protocol (IMAP) servers, as the base language
>   has no variables, loops, or ability to shell out to external
>   programs.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-sieve-3028bis-10.txt
>  
>
Folks,
This is your last chance to review that the document is correct and 
complete. No new issues can be raised at this stage unless they are very 
serious.

Please review the document by the end of February 11th. Cyrus and I are 
planning to send it to IESG soon after February 11th.

Regards,
Alexey and Cyrus.



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 l14DGvH4000983 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 4 Feb 2007 06:16:57 -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 l14DGvtE000982; Sun, 4 Feb 2007 06:16:57 -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 kalyani.oryx.com (kalyani.oryx.com [195.30.37.30]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l14DGtca000976 for <ietf-mta-filters@imc.org>; Sun, 4 Feb 2007 06:16:56 -0700 (MST) (envelope-from arnt@oryx.com)
Received: from libertango.oryx.com (libertango.oryx.com [195.30.37.9]) by kalyani.oryx.com (Postfix) with ESMTP id 82B734ACB2; Sun,  4 Feb 2007 14:16:55 +0100 (CET)
Message-Id: <Eenws6h6ux1twUVVTZyVtw.md5@libertango.oryx.com>
Date: Sun, 4 Feb 2007 14:17:21 +0100
From: Arnt Gulbrandsen <arnt@oryx.com>
To: ietf-mta-filters@imc.org
Subject: Re: Results of the Working Group Last Call on draft-ietf-sieve-notify-05.txt
Cc: Alexey Melnikov <alexey.melnikov@isode.com>
References: <45AFDB20.2030703@isode.com> <45AFE9DE.6040005@isode.com> <45BB8AC8.1000600@isode.com> <45C23C87.6040501@isode.com>
In-Reply-To: <45C23C87.6040501@isode.com>
Content-Type: text/plain; format=flowed
MIME-Version: 1.0
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>

Alexey Melnikov writes:
> Alexey Melnikov wrote:
>> Alexey Melnikov wrote:
>>>> Issue #6:
>>>>
>>>> Arnt wants to be able to do "send notification over XMPP, if can be 
>>>> delivered immediately. Otherwise send it over SMS".
>>>> This issue needs further discussion.
>>
>> Aaron replied that he likes the idea. Anybody else?
>>
>> Arnt has suggested that the notify action should take multiple 
>> :method parameters. As tagged parameters can't be specified multiple 
>> times in the same test (3028bis, section 2.6), this will mean 
>> changing the :method parameter to be a string list.
>>
>> Other alternative are:
>> 1). Add a test to check if a notification method (specified as an 
>> URI) can deliver the notification immediately.
>> IMHO, I like this a bit better than Arnt's proposal, as it is easier 
>> to implement and the resulting script is going to be easier to read.
>
> Consensus seems to be to go with option #1.

Fine with me. There is a bit of complexity or even a race condition 
("can deliver at the time of the test" vs. "can deliver at the time of 
the notify execution"), but I don't think it's serious. (If we worry 
about that, we'd better worry something much bigger: what happens if 
the notification is dislayed, but not seen because the screensaver 
kicks in 0.02 seconds later, or the user logs out 0.04 seconds later, 
or the mobile device runs out of power and dies 0.01 seconds later.)

Arnt



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 l12Ko5dY048602 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Feb 2007 13:50:05 -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 l12Ko52q048601; Fri, 2 Feb 2007 13:50:05 -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 ns1.neustar.com (ns1.neustar.com [156.154.16.138]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l12Ko4Nj048595 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-mta-filters@imc.org>; Fri, 2 Feb 2007 13:50:05 -0700 (MST) (envelope-from ietf@ietf.org)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id A20D826ECD; Fri,  2 Feb 2007 20:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HD5MA-0002NU-7M; Fri, 02 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: ietf-mta-filters@imc.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-sieve-3028bis-10.txt 
Message-Id: <E1HD5MA-0002NU-7M@stiedprstage1.ietf.org>
Date: Fri, 02 Feb 2007 15:50:02 -0500
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

	Title		: Sieve: An Email Filtering Language
	Author(s)	: T. Showalter, P. Guenther
	Filename	: draft-ietf-sieve-3028bis-10.txt
	Pages		: 44
	Date		: 2007-2-2
	
This document describes a language for filtering email messages at
   time of final delivery.  It is designed to be implementable on either
   a mail client or mail server.  It is meant to be extensible, simple,
   and independent of access protocol, mail architecture, and operating
   system.  It is suitable for running on a mail server where users may
   not be allowed to execute arbitrary programs, such as on black box
   Internet Message Access Protocol (IMAP) servers, as the base language
   has no variables, loops, or ability to shell out to external
   programs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-3028bis-10.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sieve-3028bis-10.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sieve-3028bis-10.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2007-2-2140105.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sieve-3028bis-10.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sieve-3028bis-10.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2007-2-2140105.I-D@ietf.org>

--OtherAccess--

--NextPart--



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 l12Ko3Qv048593 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Feb 2007 13:50:03 -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 l12Ko37n048592; Fri, 2 Feb 2007 13:50:03 -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 ns3.neustar.com (ns3.neustar.com [156.154.24.138]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l12Ko3Iw048583 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-mta-filters@imc.org>; Fri, 2 Feb 2007 13:50:03 -0700 (MST) (envelope-from ietf@ietf.org)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 7EB0917677; Fri,  2 Feb 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HD5MA-0002NF-3Z; Fri, 02 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: ietf-mta-filters@imc.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-sieve-notify-xmpp-03.txt 
Message-Id: <E1HD5MA-0002NF-3Z@stiedprstage1.ietf.org>
Date: Fri, 02 Feb 2007 15:50:02 -0500
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

	Title		: Sieve Notification Mechanism: xmpp
	Author(s)	: P. Saint-Andre, A. Melnikov
	Filename	: draft-ietf-sieve-notify-xmpp-03.txt
	Pages		: 8
	Date		: 2007-2-2
	
This document describes a profile of the Sieve extension for
   notifications, to allow notifications to be sent over the Extensible
   Messaging and Presence Protocol (XMPP), also known as Jabber.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-notify-xmpp-03.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sieve-notify-xmpp-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sieve-notify-xmpp-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2007-2-2135255.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sieve-notify-xmpp-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sieve-notify-xmpp-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2007-2-2135255.I-D@ietf.org>

--OtherAccess--

--NextPart--



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 l11Ko4oa032752 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Feb 2007 13:50:04 -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 l11Ko4N1032751; Thu, 1 Feb 2007 13:50:04 -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 ns3.neustar.com (ns3.neustar.com [156.154.24.138]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l11Ko39G032745 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-mta-filters@imc.org>; Thu, 1 Feb 2007 13:50:03 -0700 (MST) (envelope-from ietf@ietf.org)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 91DB717642; Thu,  1 Feb 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HCisc-00084w-5o; Thu, 01 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: ietf-mta-filters@imc.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-sieve-notify-06.txt 
Message-Id: <E1HCisc-00084w-5o@stiedprstage1.ietf.org>
Date: Thu, 01 Feb 2007 15:50:02 -0500
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

	Title		: Sieve Extension: Notifications
	Author(s)	: A. Melnikov, et al.
	Filename	: draft-ietf-sieve-notify-06.txt
	Pages		: 18
	Date		: 2007-2-1
	
Users go to great lengths to be notified as quickly as possible that
   they have received new mail.  Most of these methods involve polling
   to check for new messages periodically.  A push method handled by the
   final delivery agent gives users quicker notifications and saves
   server resources.  This document does not specify the notification
   method but it is expected that using existing instant messaging
   infrastructure such as XMPP, or SMS messages will be popular.  This
   draft describes an extension to the Sieve mail filtering language
   that allows users to give specific rules for how and when
   notifications should be sent.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-notify-06.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sieve-notify-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sieve-notify-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2007-2-1112040.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sieve-notify-06.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sieve-notify-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2007-2-1112040.I-D@ietf.org>

--OtherAccess--

--NextPart--



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 l11JGkS1025733 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Feb 2007 12:16:46 -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 l11JGkM3025732; Thu, 1 Feb 2007 12:16:46 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l11JGjcv025726 for <ietf-mta-filters@imc.org>; Thu, 1 Feb 2007 12:16:46 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <RcI8nABXDi1z@rufus.isode.com>; Thu, 1 Feb 2007 19:16:44 +0000
Message-ID: <45C23C87.6040501@isode.com>
Date: Thu, 01 Feb 2007 19:16:23 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: ietf-mta-filters@imc.org
Subject: Re: Results of the Working Group Last Call on draft-ietf-sieve-notify-05.txt
References: <45AFDB20.2030703@isode.com> <45AFE9DE.6040005@isode.com> <45BB8AC8.1000600@isode.com>
In-Reply-To: <45BB8AC8.1000600@isode.com>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
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>

Hi folks,
Quick summary of comments received so far below:

Alexey Melnikov wrote:

> Alexey Melnikov wrote:
>
>>> Issue #3:
>>>
>>> :subject versa :message. Aaron, Dilyan in favor of adding :subject. 
>>> Michael wants to keep using :message.
>>
> I need to poll people on this, as I don't hear a clear consensus on 
> this. Please pick one of the following:
>
> 1). keep the existing :message (it may or may not map to email 
> Subject:, this is a separate issue at this point)
> 2). rename existing :message to :subject
> 3). I don't care whether we have :message or :subject, but we should 
> have only one of them.
> 4). notify should have both :message and :subject
>
> Let me know your opinion or if I've missed some choice.

My reading of the rough consensus so far is to keep :message (no change 
to the draft).

>>> Issue #4:
>>>
>>> Dilyan suggested to add "expiration" parameter/option to the notify 
>>> action. While I see some utility in this option, I am reluctant to 
>>> extend the document so late in the game, unless there is strong 
>>> support from the WG. I would recommend to add this option in a 
>>> separate document. Opinions?
>>
> I've heard a couple of voices for this feature, but no rough consensus 
> yet.
>
> Hint for people who want this functionality: please provide some text 
> for inclusion into the document. This will improve your chances of 
> winning the argument ;-).

Even though specific text was suggested for inclusion, my reading of the 
rough consensus is that there is no support for adding this feature to 
the base Sieve notify document.

>>> Issue #5:
>>>
>>> Ken (in a private message) has suggested to extend "body" test 
>>> instead of introducing a new "extract_text" test. Opinions?
>>
> In order to make some progress on this issue, here is how the updated 
> body test can look like:

It sounds like people would prefer to extend the body test, rather than 
introducing a new action.
However people are not entirely sure about the new syntax I've suggested.

I think there is agreement to move this part of the document somewhere 
else, like Sieve MIME loops. So the WG should continue discussing the 
best syntax for this test or action, but this open issue is not blocking 
publication of the Sieve notify document.

>   "body" [COMPARATOR] [MATCH-TYPE] [BODY-TRANSFORM] [BODY-EXTRACT]
>                <key-list: string-list>
>
> where BODY-TRANSFORM is defined as (section 4 of 
> draft-ietf-sieve-body-05.txt):
>
>          ":raw"
>        / ":content" <content-types: string-list>
>        / ":text"
>
> I've added BODY-EXTRACT:
>
>    :extract_none /
>    :extract_whole /
>    :extract_first number
>
> :extract_none is the default, i.e. if the variables extension is 
> present, then the match variables ${1}, ${2}, ... are not set as a 
> side effect of successful matching;
> :extract_first will truncate the current body part after <number> 
> bytes and will set the match variables.
> :extract_whole will set the match variable, without performing any 
> truncation.
>
>>> Issue #6:
>>>
>>> Arnt wants to be able to do "send notification over XMPP, if can be 
>>> delivered immediately. Otherwise send it over SMS".
>>> This issue needs further discussion.
>>
> Aaron replied that he likes the idea. Anybody else?
>
> Arnt has suggested that the notify action should take multiple :method 
> parameters. As tagged parameters can't be specified multiple times in 
> the same test (3028bis, section 2.6), this will mean changing the 
> :method parameter to be a string list.
>
> Other alternative are:
> 1). Add a test to check if a notification method (specified as an URI) 
> can deliver the notification immediately.
> IMHO, I like this a bit better than Arnt's proposal, as it is easier 
> to implement and the resulting script is going to be easier to read.

Consensus seems to be to go with option #1.

> 2). Keep the existing syntax. A new "stackable" notification method 
> can be specified that will perform the desired functionality.
>
> Opinions?
> =======
> + A new issues (# 8): the Sieve notify document needs to describe what 
> should happen if a parameter specified in two ways in the same notify 
> call: as a notify action parameter and as an URI parameter to the 
> method parameter, for example:
>
>        notify :method "xmpp:tim@example.com?message;subject=SIEVE" 
> :message "You got mail";
>
> (assume for a moment that the content of the :message gets translated 
> into the subject of the resulting notification)
>
> Options suggested so far:
> 1). URI parameters are always ignored
> 2). URI parameters (if any) override the corresponding notify parameters
> 3). the notify parameters override the corresponding URI parameters
> 4). specify both the notify and the URI parameters is an error.

I don't see any consensus on this issue so far. More discussion/opinions 
needed.

> Opinions?



