Re: [sieve] Notify: notify_method_capability capability case sensitivity?
Hannah Schroeter <hannah@schlund.de> Tue, 17 November 2009 14:33 UTC
Return-Path: <hannah@schlund.de>
X-Original-To: sieve@core3.amsl.com
Delivered-To: sieve@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 96AF43A6AAD for <sieve@core3.amsl.com>; Tue, 17 Nov 2009 06:33:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.649
X-Spam-Level:
X-Spam-Status: No, score=-3.649 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
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 yITTecpnwaoV for <sieve@core3.amsl.com>; Tue, 17 Nov 2009 06:33:28 -0800 (PST)
Received: from mxintern.schlund.de (mxintern.schlund.de [212.227.126.205]) by core3.amsl.com (Postfix) with ESMTP id CB3D63A696E for <sieve@ietf.org>; Tue, 17 Nov 2009 06:33:27 -0800 (PST)
Received: from [172.19.16.7] (helo=home.kundenserver.de) by mxintern.schlund.de with esmtp (envelope-from <hannah@schlund.de>) id 1NAP7V-0000is-1b for sieve@ietf.org; Tue, 17 Nov 2009 15:33:25 +0100
Received: from hannah by home.kundenserver.de with local (Exim 3.36 #1) id 1NAP7U-0003e0-00 for sieve@ietf.org; Tue, 17 Nov 2009 15:33:24 +0100
Date: Tue, 17 Nov 2009 15:33:24 +0100
From: Hannah Schroeter <hannah@schlund.de>
To: sieve@ietf.org
Message-ID: <20091117143324.GA30774@schlund.de>
Mail-Followup-To: sieve@ietf.org
References: <20091110153345.GA16516@schlund.de> <4B008003.4060402@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4B008003.4060402@isode.com>
Organization: Schlund + Partner AG
X-Virus-Scanned: Symantec AntiVirus Scan Engine
X-UI-Msg-Verification: 45bc65e9cb25049763d27b9f029291fa
Subject: Re: [sieve] Notify: notify_method_capability capability case sensitivity?
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIEVE Working Group <sieve.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sieve>, <mailto:sieve-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sieve>
List-Post: <mailto:sieve@ietf.org>
List-Help: <mailto:sieve-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sieve>, <mailto:sieve-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Nov 2009 14:33:28 -0000
Hi! On Mon, Nov 16, 2009 at 07:26:11AM +0900, Alexey Melnikov wrote: >Hannah Schroeter wrote: >Hi Hannah, >Sorry for the slow response. It's ok. >>Is the notification-capability parameter of notify_method_capability >>(RFC 5435) case sensitive or not? >>The RFC doesn't say yes or no in any place. >I think you've missed it. RFC 5435 says in section 5: > The notification-capability parameter is case insensitive. Yes, I missed that indeed. Thank you. >Regards, >Alexey Kind regards, Hannah.
- [sieve] Notify: notify_method_capability capabili… Hannah Schroeter
- Re: [sieve] Notify: notify_method_capability capa… Alexey Melnikov
- Re: [sieve] Notify: notify_method_capability capa… Hannah Schroeter