Re: [lemonade] SUBMITTED keyword, Outbox and Sent folders, and CATENATE/BURL

Dave Cridland <dave@cridland.net> Fri, 22 February 2008 12:00 UTC

Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: ietfarch-lemonade-archive@core3.amsl.com
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5B3DC3A6C88; Fri, 22 Feb 2008 04:00:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.707
X-Spam-Level:
X-Spam-Status: No, score=-0.707 tagged_above=-999 required=5 tests=[AWL=-0.270, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
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 Z77Aee0MPm5J; Fri, 22 Feb 2008 04:00:47 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C44528C218; Fri, 22 Feb 2008 04:00:47 -0800 (PST)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B40883A682B for <lemonade@core3.amsl.com>; Fri, 22 Feb 2008 04:00:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 MulchSQ2hKT9 for <lemonade@core3.amsl.com>; Fri, 22 Feb 2008 04:00:40 -0800 (PST)
Received: from turner.dave.cridland.net (unknown [IPv6:2001:838:378:0:211:9ff:fe2c:e28e]) by core3.amsl.com (Postfix) with ESMTP id D241C3A6C60 for <lemonade@ietf.org>; Fri, 22 Feb 2008 04:00:39 -0800 (PST)
Received: from invsysm1 (shiny.isode.com [62.3.217.250]) by turner.dave.cridland.net (submission) via TCP with ESMTPA id <R765VABdxa-u@turner.dave.cridland.net>; Fri, 22 Feb 2008 12:00:20 +0000
X-SMTP-Protocol-Errors: PIPELINING
References: <033901c874d3$bb7bbfb0$32733f10$%coates@sun.com>
In-Reply-To: <033901c874d3$bb7bbfb0$32733f10$%coates@sun.com>
MIME-Version: 1.0
Message-Id: <6978.1203681612.492066@invsysm1>
Date: Fri, 22 Feb 2008 12:00:12 +0000
From: Dave Cridland <dave@cridland.net>
To: Peter Coates <peter.coates@sun.com>
Cc: lemonade@ietf.org
Subject: Re: [lemonade] SUBMITTED keyword, Outbox and Sent folders, and CATENATE/BURL
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service enivronments <lemonade.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/lemonade>, <mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/lemonade>, <mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

In the light of Peter's comments, I'd like to outline how Polymer is  
currently handling similar functionality.

Polymer doesn't use special purpose folders, although it can do.  
Instead its approach is based on using the INBOX primarily.

It's sending pattern is, roughly:

1) If it is helpful to stage the message on the server, do so, using  
tag APPEND (\Draft) ... - for reasons of my own bad programming, it  
will do this even when the message has already been saved - ie,  
multiple sending attempts cause multiple copies of the message, which  
is inarguably wrong. (It creates the new copies quite efficiently,  
using a copy-via-catenate construct, but still).

2) It then creates a signed URL, and submits the message via BURL.

3) Once it receives the final 2xx from the BURL, it marks the message  
with a $submitted flag that I vaguely intended mentioning at some  
point.

So \Draft's meaning is essentially unchanged - "this message has been  
created by the MUA, and may be incomplete". $submitted's meaning is  
obvious.

This yields a state table for messages of something like:

\Draft	$Submitted		State
0		0				Inbound message.
1		0				Message requires further action.
0		1				Message has been resubmitted.
1		1				Message has been "sent".

What I actually do, given this, is to set a viewing filter on DRAFT  
UNKEYWORD $Submitted to colour such messages in violent red, telling  
me that either the submission failed, or hasn't been attempted yet.  
Either way, I probably want to do something about it. (Like, finish  
editing, or attempt to submit it, or something).

Given this, my comments (in another message) which pick on Peter's  
points may be more understandable.

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@jabber.org
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
_______________________________________________
lemonade mailing list
lemonade@ietf.org
http://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade