Return-Path: <owner-ietf-mta-filters@mail.imc.org>
X-Original-To: ietfarch-sieve-archive-Aet6aiqu@core3.amsl.com
Delivered-To: ietfarch-sieve-archive-Aet6aiqu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by core3.amsl.com (Postfix) with ESMTP id BDD173A6809
 for <ietfarch-sieve-archive-Aet6aiqu@core3.amsl.com>;
 Sun, 11 Jan 2009 18:20:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.534
X-Spam-Level: 
X-Spam-Status: No, score=-2.534 tagged_above=-999 required=5 tests=[AWL=0.065, 
 BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
 by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 9s3eJeJRJEIr
 for <ietfarch-sieve-archive-Aet6aiqu@core3.amsl.com>;
 Sun, 11 Jan 2009 18:20:50 -0800 (PST)
Received: from balder-227.proper.com
 (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2])
 by core3.amsl.com (Postfix) with ESMTP id 9D27D3A677D
 for <sieve-archive-Aet6aiqu@ietf.org>; Sun, 11 Jan 2009 18:20:49 -0800 (PST)
Received: from balder-227.proper.com (localhost [127.0.0.1])
 by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n0C2EuU9077182
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
 Sun, 11 Jan 2009 19:14:56 -0700 (MST)
 (envelope-from owner-ietf-mta-filters@mail.imc.org)
Received: (from majordom@localhost)
 by balder-227.proper.com (8.14.2/8.13.5/Submit) id n0C2Euwj077181;
 Sun, 11 Jan 2009 19:14:56 -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 (mauve.mrochek.com [66.59.230.40])
 by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n0C2EjZ9077171
 for <ietf-mta-filters@imc.org>; Sun, 11 Jan 2009 19:14:55 -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 <01N46G8BPSM800V35K@mauve.mrochek.com> for
 ietf-mta-filters@imc.org; Sun, 11 Jan 2009 18:14:43 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243)
 id <01N46FUPZOSW00007A@mauve.mrochek.com>; Sun,
 11 Jan 2009 18:14:40 -0800 (PST)
Date: Sun, 11 Jan 2009 18:05:01 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
Subject: Re: draft-freed-sieve-in-xml status?
In-reply-to: "Your message dated Sun, 11 Jan 2009 22:01:34 +0000"
 <f470f68e0901111401w7a8f9bccv9a19b6ec46e83253@mail.gmail.com>
To: Robert Burrell Donkin <robertburrelldonkin@gmail.com>
Cc: Ned Freed <ned.freed@mrochek.com>, ietf-mta-filters@imc.org
Message-id: <01N46G8A8H6K00007A@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
Content-transfer-encoding: 7BIT
References: <f470f68e0812041225x318bfdccg1bf9201b53ce8c2e@mail.gmail.com>
 <01N32VHWP1EK00SE3A@mauve.mrochek.com>
 <f470f68e0812141304i228b5a03s890e0f101b76b07e@mail.gmail.com>
 <01N335CY3MAQ00SE3A@mauve.mrochek.com>
 <f470f68e0812150500r5d1916f4obbd941434295fe07@mail.gmail.com>
 <01N3MQQCAYL000007A@mauve.mrochek.com>
 <f470f68e0901061657g3aa2d63dwcdbee2ae91b3bbda@mail.gmail.com>
 <01N41Q9BQSU800007A@mauve.mrochek.com>
 <f470f68e0901101020i7f12bce7j8d22748b596285a9@mail.gmail.com>
 <01N465T9JTGS00007A@mauve.mrochek.com>
 <f470f68e0901111401w7a8f9bccv9a19b6ec46e83253@mail.gmail.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 Sun, Jan 11, 2009 at 6:21 PM, Ned Freed <ned.freed@mrochek.com> wrote:

> <snip>

> >> > But really, this entire discussion has gone very far afield. Like it or not,
> >> > Sieve is intended to be a language used to process email messages at or around
> >> > the time of final delivery.
> >> > The fact that it can be adapted for other uses may
> >> > be interesting to you but simply is not relevant in the context of the work
> >> > this group is chartered to do.
> >
> >> is this http://www.ietf.org/html.charters/sieve-charter.html the charter?
> >
> > Yes

> could anyone kindly point me to the sections which indicate that only
> mail servers of a particular class of architecture are in scope?

I've already done so in previous messages. It's the very first thing RFC 5228,
the Sieve base specification, says:

   This document describes a language for filtering email messages at
   time of final delivery.

Final delivery is a formal term used in many IETF email standards. It refers to
the point at which the message exists the SMTP transport infrastructure and
enters the message store.

As its charter makes clear, the current Sieve group is chartered to work on a
very specific set of Sieve extensions. There is nothing in there about
revisiting the scope of applicability of Sieve.

				Ned