Re: [Tools-discuss] postconfirm

Henrik Levkowetz <henrik@levkowetz.com> Tue, 25 June 2019 00:29 UTC

Return-Path: <henrik@levkowetz.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B838D1201E8 for <tools-discuss@ietfa.amsl.com>; Mon, 24 Jun 2019 17:29:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6LpETjBrqUNY for <tools-discuss@ietfa.amsl.com>; Mon, 24 Jun 2019 17:28:59 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EDB41201EC for <tools-discuss@ietf.org>; Mon, 24 Jun 2019 17:28:59 -0700 (PDT)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:59364 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1hfZKS-0003os-EH; Mon, 24 Jun 2019 17:28:58 -0700
To: Mark Nottingham <mnot@mnot.net>, Robert Sparks <rjsparks@nostrum.com>
References: <11E75566-9C0B-4A55-93BF-6D2AF3C013D2@mnot.net> <cff373e8-3631-1c04-b5ac-5b11d219d418@levkowetz.com> <38e51d14-ff2e-209b-0707-2659e4967a02@nostrum.com> <1F2CA98A-E689-4955-8AE0-BC1F4B9E9F9A@mnot.net>
Cc: tools-discuss@ietf.org
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <156f4f16-ecfa-ca46-48c3-63ece3b1d575@levkowetz.com>
Date: Tue, 25 Jun 2019 02:28:48 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <1F2CA98A-E689-4955-8AE0-BC1F4B9E9F9A@mnot.net>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="av0Air813kg7orTXJQPV41m7TkHqWaIMV"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, rjsparks@nostrum.com, mnot@mnot.net
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/CuWXJV9pbpqQa0X3PweoHHM-An4>
Subject: Re: [Tools-discuss] postconfirm
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jun 2019 00:29:01 -0000

Hi Mark, Robert,

On 2019-06-25 01:52, Mark Nottingham wrote:
> That would really help. Could we also start the mail with something like:
> 
> "Attention: your message has not been posted to the list yet. Please confirm your posting by..."?

The body is based on a template, so easily changed.  Changing the subject
line has repercussions on the code, so let's see if a body change would
be enough.  So, the proposal is to change the body as follows:

Old template text:

  Confirmation of list posting -- confirmation ID: $filename
  
  The ietf.org mailing-list server has received a list posting from 
  $sender to $recipient with the subject 
  '$[msg["subject"]]'
  
  As the sender address isn't subscribed to the list, and has not been
  confirmed earlier, we have to request a confirmation of the address.
  To confirm the address, send a message to $recipient,
  with the same subject line as this message.
  
  (Simply sending a 'reply' to this message should work from most email
  interfaces, since that usually leaves the subject line in the right
  form.  The reply's additional "Re:" is ok.)
  
  If you do not wish your posting to the list to go through, simply
  disregard this message.  Questions to $[conf.admin_address].

New template text:

  Attention: your message has not been posted to the list yet.
  Please confirm your posting by responding to this message:
  
  The ietf.org mailing-list server has received a list posting from 
  $sender to $recipient with the subject 
  '$[msg["subject"]]'

  As the sender address isn't subscribed to the list, and has not been
  confirmed earlier, we have to request a confirmation of the address.
  To confirm the address, send a message to $recipient,
  with the same subject line as this message.

  (Simply sending a 'reply' to this message should work from most email
  interfaces, since that usually leaves the subject line in the right
  form.  The reply's additional "Re:" is ok.)

  If you do not wish your posting to the list to go through, simply
  disregard this message.  Questions to $[conf.admin_address].

Does that match your proposal?


	Henrik


> 
> Cheers,
> 
> 
> 
>> On 25 Jun 2019, at 4:23 am, Robert Sparks <rjsparks@nostrum.com> wrote:
>> 
>> Perhaps start the subject with "Action Required:" ?
>> 
>> RjS
>> 
>> On 6/23/19 9:28 PM, Henrik Levkowetz wrote:
>>> Hi Mark,
>>> 
>>> On 2019-06-24 03:05, Mark Nottingham wrote:
>>> 
>>>> Hello,
>>>> 
>>>> For the escape-workshop-pc mailing list, we had a number of
>>>> submissions from non-IETF people get stuck at the confirmation stage,
>>>> because people who were not familiar with postman norms didn't
>>>> realise they had to respond to the confirm message.
>>>> 
>>>> In particular, the Subject of the e-mail is "Confirm: ...", and the
>>>> most prominent line is "Confirmation of list posting -- confirmation
>>>> ID: ..." -- which can be read to say that THIS e-mail is confirming
>>>> that posting has already occurred.
>>>> 
>>>> Would it be possible to rewrite the confirmation message to make it
>>>> more clear to busy readers that they need to act on the message?
>>>> 
>>> Certainly.
>>> 
>>> Do you have a proposal for the changed message?
>>> 
>>> 
>>> Regards,
>>> 
>>> 	Henrik
>>> 
>>> 
>>> 
>>> 
>>> ___________________________________________________________
>>> Tools-discuss mailing list
>>> 
>>> Tools-discuss@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tools-discuss
>>> 
>>> 
>>> Please report datatracker.ietf.org and mailarchive.ietf.org
>>> bugs at 
>>> http://tools.ietf.org/tools/ietfdb
>>> 
>>> or send email to 
>>> datatracker-project@ietf.org
>>> 
>>> 
>>> Please report tools.ietf.org bugs at
>>> 
>>> http://tools.ietf.org/tools/issues
>>> 
>>> or send email to 
>>> webmaster@tools.ietf.org
> 
> --
> Mark Nottingham   https://www.mnot.net/
> 
> ___________________________________________________________
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss
> 
> Please report datatracker.ietf.org and mailarchive.ietf.org
> bugs at http://tools.ietf.org/tools/ietfdb
> or send email to datatracker-project@ietf.org
> 
> Please report tools.ietf.org bugs at
> http://tools.ietf.org/tools/issues
> or send email to webmaster@tools.ietf.org
>