IETF Logo Mail Archive

Re: [sieve] Working Group Last Call: draft-ietf-sieve... autoreply, notify-presence, vacation-seconds

Barry Leiba <barryleiba@computer.org> Fri, 15 October 2010 13:12 UTC

Return-Path: <barryleiba.mailing.lists@gmail.com>
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 D34D63A6C9D for <sieve@core3.amsl.com>; Fri, 15 Oct 2010 06:12:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.177
X-Spam-Level:
X-Spam-Status: No, score=-102.177 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, USER_IN_WHITELIST=-100]
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 peSLWU3SIGm2 for <sieve@core3.amsl.com>; Fri, 15 Oct 2010 06:12:47 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id AB6C13A6CA2 for <sieve@ietf.org>; Fri, 15 Oct 2010 06:12:34 -0700 (PDT)
Received: by gwaa12 with SMTP id a12so369811gwa.31 for <sieve@ietf.org>; Fri, 15 Oct 2010 06:13:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=q0mfkdS0wleFkBGdRD0tCY5ZVJtvdlswyknUAk8gzIU=; b=mWim6zdJOz3kWwVFc5hMsArdS5ooLk3wsKKQfpVurlNu8M+P55BIyE6YIbgzOy0pgg 2D+Qk3kOcqyr9Vh+MWgAERhc0qc9KDcBhITzWcta1x8WU3TgzItiHA/0UGxd07kjnakN +jxKmuhNhWkB769Ggk906ui1sutHPJupyHHmo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=g/QDM0eZ1vaDGBT+S/bzTS9lfK0IV7lA0hFs6+HzzFqO5KlhEg+JCLF3+g5iSwp2FL eweHB8mYlNDyZHfvgCREBdm+/GYfa5mEiz2c99mASQfkpQvX1vumC+lpjhUFumJE3eg9 EUCBjuOUQtkFCVfEnY0Tn04XZASJrVT9XrIg4=
MIME-Version: 1.0
Received: by 10.42.171.10 with SMTP id h10mr455801icz.430.1287148430100; Fri, 15 Oct 2010 06:13:50 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.42.6.65 with HTTP; Fri, 15 Oct 2010 06:13:49 -0700 (PDT)
In-Reply-To: <4CB77F60.6000006@att.com>
References: <AANLkTik994DjP7T7tj-VzJQ4J1nAgtq4hTdj5ZFQ-h=u@mail.gmail.com> <4CB4F39A.8040806@att.com> <01NSZ2PTFXCI000CVY@mauve.mrochek.com> <AANLkTi=4K21-vdL3B2jQ95QvF2JjZPKLqBS93HRU8R3X@mail.gmail.com> <4CB66F01.9040504@att.com> <AANLkTi=QHwchFBEJcAgqQ=+6yQBAnE-5LYonpOmEhvEH@mail.gmail.com> <4CB77F60.6000006@att.com>
Date: Fri, 15 Oct 2010 09:13:49 -0400
X-Google-Sender-Auth: myYNpb0z0ErgjTSFPlY80g2lcDo
Message-ID: <AANLkTikfbjyLUvp+nTy_MvXr6f0Tvx-TuhTmBPBHHS5T@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Tony Hansen <tony@att.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: Sieve mailing list <sieve@ietf.org>
Subject: Re: [sieve] Working Group Last Call: draft-ietf-sieve... autoreply, notify-presence, vacation-seconds
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: Fri, 15 Oct 2010 13:12:49 -0000

> < below; Note
>> below; note
> or
>> below. Note

Yeah, I forgot to change the semicolon to a period.  We'll get that in AUTH48.

> After status definition, add
>
> unknown - The correct availability status could not be determined.

I thought about that, but I don't think I like it.  This is a
human-readable field, and it's made clear that it's not for automated
processing.  It's plain text, most likely set by the user, and it
could be anything, including "unknown".  I don't want to try to
*reserve* the value "unknown" in any way -- we can't, anyway; we have
no control of it.

> If you add the unknown definition, the entire "Note that in addition"
> sentence phrase can be removed.

It can be, but I think it's worth pointing out separately.

Barry

v2.23.0 | Report a Bug | By Email