IETF Logo Mail Archive

Re: [Notifications] Re: I-D ACTION:draft-ietf-sieve-notify-02.txt

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 08 February 2006 18:43 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6uHW-0003ti-Oi; Wed, 08 Feb 2006 13:43:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6uHT-0003pW-Vb for notifications@megatron.ietf.org; Wed, 08 Feb 2006 13:43:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20480 for <notifications@ietf.org>; Wed, 8 Feb 2006 13:41:26 -0500 (EST)
Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6uU6-00004t-9t for notifications@ietf.org; Wed, 08 Feb 2006 13:56:12 -0500
Received: from [172.16.1.198] (shiny.isode.com [62.3.217.250]) by rufus.isode.com via TCP (submission) with ESMTPA; Wed, 8 Feb 2006 18:42:38 +0000
Message-ID: <43EA3B9D.2030202@isode.com>
Date: Wed, 08 Feb 2006 18:42: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.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alexandros Vellis <avel@noc.uoa.gr>
Subject: Re: [Notifications] Re: I-D ACTION:draft-ietf-sieve-notify-02.txt
References: <E1F6DJB-0001Ck-JY@newodin.ietf.org> <20060207110513.GA10924@nostromo.freenet-ag.de> <1139317905.5030.19.camel@localhost.localdomain>
In-Reply-To: <1139317905.5030.19.camel@localhost.localdomain>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit
Cc: ietf-mta-filters@imc.org, notifications@ietf.org
X-BeenThere: notifications@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Message Notifications interest group discussion list <notifications.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/notifications>, <mailto:notifications-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/notifications>
List-Post: <mailto:notifications@ietf.org>
List-Help: <mailto:notifications-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/notifications>, <mailto:notifications-request@ietf.org?subject=subscribe>
Sender: notifications-bounces@ietf.org
Errors-To: notifications-bounces@ietf.org

Alexandros Vellis wrote:

>On Tue, 2006-02-07 at 12:05 +0100, Michael Haardt wrote:  
>
>>I suggest that allowed modifications MUST or at least SHOULD be
>>documented.
>>
>>   Usage:  valid_notif_method <notification-uris: string-list>
>>
>>Of course that is real easy to implement, but it is also real ugly.
>>There is nothing I know of else in Sieve that checks certain options
>>of actions for validity.  I still suggest a generic extension for
>>exception handling.
>>    
>>
>
>I don't know about generic exception handling, but wouldn't it make more
>sense, in this particular case, that the available notifications are
>present in the capabilities of the Sieve server?
>
>So, just as IMAP4 Capability responds with a set such as AUTH=DIGEST-MD5
>AUTH=ANONYMOUS or THREAD=ORDEREDSUBJECT THREAD=REFERENCES, a Sieve
>server could respond with "notify notifymethod=mailto
>notifymethod=xmpp", or something similar.
>
If you are talking about ManageSieve protocol 
(draft-martin-managesieve), then draft-ietf-sieve-notify-02.txt already 
has text describing relevant capability.


_______________________________________________
Notifications mailing list
Notifications@ietf.org
https://www1.ietf.org/mailman/listinfo/notifications

v2.8.7 | Report a Bug | By Email