Re: Changes needed to Last Call boilerplate

Willie Gillespie <> Fri, 13 February 2009 02:34 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E5DED3A695E for <>; Thu, 12 Feb 2009 18:34:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vXWFxRM9FzjD for <>; Thu, 12 Feb 2009 18:34:08 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 0A4AA3A6A90 for <>; Thu, 12 Feb 2009 18:34:08 -0800 (PST)
Received: from (localhost []) by (SMTP Server) with ESMTP id 8D28A1B400C; Thu, 12 Feb 2009 21:34:09 -0500 (EST)
Received: by (Authenticated sender: with ESMTPSA id 5643A1B4002; Thu, 12 Feb 2009 21:34:09 -0500 (EST)
Message-ID: <>
Date: Thu, 12 Feb 2009 19:34:08 -0700
From: Willie Gillespie <>
Organization: Engineering System Solutions
User-Agent: Thunderbird (X11/20090105)
MIME-Version: 1.0
To: David Morris <>
Subject: Re: Changes needed to Last Call boilerplate
References: <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 13 Feb 2009 02:34:09 -0000

David Morris wrote:
> Seems like a unique mailbox per lastcall would be very helpful all around.
> Right now, gathering and evaluating comments must be a nightmare. An 
> alternative, would be a single LC mailbox as suggested, but require EVERY
> subject line to carry the last call ID, preferable in a form sensible to
> current mail clients.
> In the case of unique lists per lastcall, provide an opt-in metasubcribe 
> to make it easy for folks who generally want to follow last call 
> discussions to just be subscribed.
> *AND* require subscribe to post ... no cute confirm reply to bypass. I 
> strongly believe that anyone who wants to provide feedback should want
> to see the comments on their feed back. [If the cute confirm created
> an automatic 48 hour subscription as per my next point, that would
> work too.]
> *AND* no unsubscribe or post only for 48 hours after initial subscription.
> For real participants, this wouldn't be an issue and for email campaigns,
> well they just need to experience the same disrruption their campaign
> causes.
> David Morris

Not a bad idea.  In fact, it may be useful to have a unique "list" per 
draft, so every comment relating to a particular draft can be tracked 
historically.  This example is how I understand your suggestion: will automatically be set up with 
the initial ID submission.  E-mails sent to it will be regarded as 
discussion pertaining to the draft.

Individuals interested in following the draft may subscribe to that list 
simply by sending an e-mail to it.  (However, e-mails with simply the 
word "subscribe" in the body or subject line won't be forwarded to 
everyone.)  They are also allowed to unsubscribe (perhaps following
  the 48-hour waiting period of initial subscription as David suggested).

Note also that e-mails sent to would not be 
sent to the general list of

I doubt this sort of functionality currently exists in Mailman, but 
perhaps it could be implemented.