Re: [sieve] New Version Notification for draft-george-sieve-vacation-time-00

Derek Diget <derek.diget+ietf-mta-filters@wmich.edu> Thu, 04 February 2010 23:43 UTC

Return-Path: <derek.diget+ietf-mta-filters@wmich.edu>
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 C8A3E3A69A3 for <sieve@core3.amsl.com>; Thu, 4 Feb 2010 15:43:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 3WVz9xfju4vC for <sieve@core3.amsl.com>; Thu, 4 Feb 2010 15:43:53 -0800 (PST)
Received: from mx-tmp.wmich.edu (mx-tmp.wmich.edu [141.218.1.43]) by core3.amsl.com (Postfix) with ESMTP id C4D243A6949 for <sieve@ietf.org>; Thu, 4 Feb 2010 15:43:53 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: TEXT/PLAIN; charset="US-ASCII"
Received: from spaz.oit.wmich.edu (spaz.oit.wmich.edu [141.218.24.51]) by mta01.service.private (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 64bit)) with ESMTPSA id <0KXC005QNCM42C50@mta01.service.private> for sieve@ietf.org; Thu, 04 Feb 2010 18:44:31 -0500 (EST)
X-WMU-Spam: Gauge=X, Probability=10% on Thu Feb 4 18:44:31 2010, Report=' WMU_MSA_SMTP+ 0, TO_IN_SUBJECT 0.5, BODY_SIZE_2000_2999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, FROM_EDU_TLD 0, SPF_NEUTRAL 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CT_TEXT_PLAIN 0, __FRAUD_SUBJ_A 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __URI_NS '
X-WMU-PMX-Version: 5.5.9.388399, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.2.4.233027 - Thu Feb 4 18:44:29 2010
Date: Thu, 04 Feb 2010 18:44:28 -0500
From: Derek Diget <derek.diget+ietf-mta-filters@wmich.edu>
X-X-Sender: diget@spaz.oit.wmich.edu
To: Sieve mailing list <sieve@ietf.org>
In-reply-to: <6c9fcc2a1002041101v49670ddfg8e8344bffc34c05f@mail.gmail.com>
Message-id: <Pine.GSO.4.62.1002041746130.6571@spaz.oit.wmich.edu>
References: <20100130143437.BBE563A683B@core3.amsl.com> <9abf48a61001300646g712fe589uceff1033063c71cd@mail.gmail.com> <4B6984EC.1040807@aegee.org> <4B6989FA.6080206@gulbrandsen.priv.no> <6c9fcc2a1002031318l3b5afddoa895e292fadb0ff6@mail.gmail.com> <01NJ8NX41PDW004042@mauve.mrochek.com> <6c9fcc2a1002040707m78bd7e52u344df0497d3e9c7a@mail.gmail.com> <1629dc8c1002041033g4a2010c1i1cc5a9622d0220c0@mail.gmail.com> <6c9fcc2a1002041101v49670ddfg8e8344bffc34c05f@mail.gmail.com>
Cc: Ned Freed <ned.freed@mrochek.com>, barryleiba@computer.org
Subject: Re: [sieve] New Version Notification for draft-george-sieve-vacation-time-00
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: Thu, 04 Feb 2010 23:43:55 -0000

On Feb 4, 2010 at 14:01 -0500, Barry Leiba wrote:
=>
=>> Thought experiment: what if :time referred to a time of day? All
=>> vacation notices would be batched and sent at that time of day. What
=>> might be a use case for this?
=>
=>Mm.  ":time 00:00:00" to send the (de-duped) batch at midnight.  I
=>can't really see the need for that.  For the most part, you'd want the
=>first notice ASAP, and just have duplicates suppressed after that,
=>until the interval expires.
=>
=>The only reason I could see for delaying even the first notice until a
=>designated time would be if you wanted to be able to cancel them if
=>something has changed.  Like, maybe, "Don't tell people I'm gone
=>unless I'm not back by 3:00."  Even with that, what happens when you
=>get back at 3:01?  No, that just seems like a solution no one's asked
=>for nor needs.

De-lurking...I am not the experts you all are.


Should there be something said on how implementations handle deltas to the 
:time (or :seconds) window with respect to the previous response history 
database?  Does a change to the sieve remove/wipe the previous response 
tracking history?  I don't see any mention of that in RFC 5230.  For 
example...

Fred has a vacation rule with responses set for every 10800 seconds (he 
is in a morning meeting).  Wilma sends a message to Fred at 10:30 and 
receives a vacation response since it is the first message she has sent 
to Fred that day.  Fred gets out of his meeting and modifies his 
vacation sieve at 11:50 as he heads out to lunch with a :time now set to 
5400.  (He might or might not change the reason string.)  Wilma sends 
another message to Fred at 12:00 that would "match" her first message 
and not have caused a response under the original rule.  Does Fred's 
modification of the filter cause the sieve system to remove/wipe/clean 
its response tracking history and thus cause a new response to Wilma's 
12:00 message?

The reason I ask is that I see with user's being able to set vacation 
replies using seconds they might connect their 
Twitter/MySpace/Facebook/etc account status with vacation rules.  They 
update their ${SOCIALSITE} status and it updates their vacation sieve 
rule with their new status message. :) or :( depending our the side of 
fence you stand.  And I could see same thing in the IM/presence world, 
too.


If this is addressed somewhere sorry for wasting your time.

-- 
***********************************************************************
Derek Diget                            Office of Information Technology
Western Michigan University - Kalamazoo  Michigan  USA - www.wmich.edu/
***********************************************************************