Re: Comments about draft-martin-managesieve-00.txt

Randall Gellens <randy@Qualcomm.Com> Tue, 15 February 2000 00:54 UTC

Received: by ns.secondary.com (8.9.3/8.9.3) id QAA26319 for ietf-mta-filters-bks; Mon, 14 Feb 2000 16:54:14 -0800 (PST)
Received: from fezik.qualcomm.com (fezik.qualcomm.com [129.46.2.74]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id QAA26315 for <ietf-mta-filters@imc.org>; Mon, 14 Feb 2000 16:54:13 -0800 (PST)
Received: from randy-nt.qualcomm.com (randy-nt.qualcomm.com [129.46.218.199]) by fezik.qualcomm.com (8.8.5/1.4/8.7.2/1.15) with ESMTP id QAA09635; Mon, 14 Feb 2000 16:57:34 -0800 (PST)
Message-Id: <4.3.0.20000214164856.00beec30@randy-nt4.qualcomm.com>
X-Sender: randy@randy-nt4.qualcomm.com@randy-nt4.qualcomm.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Mon, 14 Feb 2000 16:53:01 -0800
To: Barry Leiba <leiba@watson.ibm.com>, ietf-mta-filters@imc.org
From: Randall Gellens <randy@Qualcomm.Com>
Subject: Re: Comments about draft-martin-managesieve-00.txt
In-Reply-To: <38A02038.927871BB@watson.ibm.com>
References: <389BD7B1.58CC11F7@messagingdirect.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: owner-ietf-mta-filters@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>

At 08:55 AM 2/8/00 -0500, Barry Leiba wrote:
>I have to say that this whole thing seems a little excessive, considering
>the statement that this is an interim solution anyway:

I agree.  I don't think it's a good idea to go the yet-another-protocol 
route unless it moves us closer to where we want to be.

My proposal all along has been to use ACAP or a subset.  We have prototype 
implementations of an ACAP profile for Sieve (along with a Sieve engine) 
running on NT and Unix, and a prototype Windows GUI that manages scripts.

By using an ACAP profile, both client and server support becomes pretty 
easy, and the client can talk to a full ACAP server just as well as a mini, 
Sieve-only one.  So we get rapid deployment and move closer to a real 
solution (full ACAP servers).