IETF Logo Mail Archive

Updated Sieve notification draft

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 26 September 2005 14:26 UTC

Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j8QEQpve045101; Mon, 26 Sep 2005 07:26:51 -0700 (PDT) (envelope-from owner-ietf-mta-filters@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j8QEQpjX045100; Mon, 26 Sep 2005 07:26:51 -0700 (PDT)
X-Authentication-Warning: above.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 above.proper.com (8.12.11/8.12.9) with ESMTP id j8QEQoVq045094 for <ietf-mta-filters@imc.org>; Mon, 26 Sep 2005 07:26:50 -0700 (PDT) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.2.143] (shiny.isode.com [62.3.217.250]) by rufus.isode.com via TCP (internal) with ESMTPA; Mon, 26 Sep 2005 15:26:47 +0100
Message-ID: <43380526.4070001@isode.com>
Date: Mon, 26 Sep 2005 15:26:46 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: MTA filtering mailing list <ietf-mta-filters@imc.org>
Subject: Updated Sieve notification draft
Content-Type: multipart/mixed; boundary="------------080601090609070100030801"
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 took a stab at updating draft-martin-sieve-notify-01.txt, which should 
be published soon as draft-ietf-sieve-notify-00.txt. The document is 
attached.

The two major changes are:
1). updated the document to reference Sieve variables. Some notification 
variables line "$text$" can't be mapped directly, but I will send a 
separate message on this.
2). changed the document to use notification URIs, e.g. "sms:+123456789"

I remember there was a discussion few months ago about defining a 
separate SMS notification mechanism. I just want to let people know that 
the update I've made doesn't prevent any other documents in this area. 
Just treat it as an input for discussion.

Alexey

v2.23.0 | Report a Bug | By Email