Re: [Tools-discuss] postconfirm

Robert Sparks <rjsparks@nostrum.com> Tue, 25 June 2019 02:36 UTC

Return-Path: <rjsparks@nostrum.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 988191201F0 for <tools-discuss@ietfa.amsl.com>; Mon, 24 Jun 2019 19:36:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level:
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
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 jlV3A_J-I33B for <tools-discuss@ietfa.amsl.com>; Mon, 24 Jun 2019 19:36:00 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 588EF1200B4 for <tools-discuss@ietf.org>; Mon, 24 Jun 2019 19:36:00 -0700 (PDT)
Received: from [192.168.3.102] ([47.186.39.7]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x5P2ZwFA009000 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 24 Jun 2019 21:35:59 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1561430159; bh=1bIWmYeESpCRofu5V3dHD5P5b3b7sBIfwCD3gw0gUw0=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=ZKGbrqGRk903cpRkBaFzCpMtjvzXF15XHeQZztnwaboO4+H+BFGv9bhI3hJXVig6h LipQ6W6ihP3qFzOUwfzlMSZDYp0DDFZHtb94DsJki0+tHbKSp+iZADHVvkN+x4pNAo cCsO/sZfXGxxkU4pe0Tk2G0LwRZjrI/bRqcQ004M=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.39.7] claimed to be [192.168.3.102]
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: iPhone Mail (16E227)
In-Reply-To: <156f4f16-ecfa-ca46-48c3-63ece3b1d575@levkowetz.com>
Date: Mon, 24 Jun 2019 21:35:57 -0500
Cc: Mark Nottingham <mnot@mnot.net>, tools-discuss@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <9F9AF464-7598-42F2-9EAF-DAE5353C5C24@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> <156f4f16-ecfa-ca46-48c3-63ece3b1d575@levkowetz.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/Sfo5LnsNjKrqBwXHENR74l5L-Lk>
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 02:36:03 -0000

I think mark’s point is that the people he was trying to reach triaged the mail on the subject and never looked at the body (so a body change would be a no-op). 

As an aside, we have other templates that pull the envelope into the template. Perhaps this one should go there too?

Sent from my iPhone

> On Jun 24, 2019, at 7:28 PM, Henrik Levkowetz <henrik@levkowetz.com> wrote:
> 
> 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
>> 
>