Re: [Tools-discuss] postconfirm

Robert Sparks <rjsparks@nostrum.com> Mon, 24 June 2019 18:23 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 DDD0212006B for <tools-discuss@ietfa.amsl.com>; Mon, 24 Jun 2019 11:23:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.679
X-Spam-Level:
X-Spam-Status: No, score=-1.679 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" 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 SCdAmNA1mTm5 for <tools-discuss@ietfa.amsl.com>; Mon, 24 Jun 2019 11:23:40 -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 37A9C1201E9 for <tools-discuss@ietf.org>; Mon, 24 Jun 2019 11:23:40 -0700 (PDT)
Received: from unultimate.local ([47.186.39.7]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x5OINbab028853 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 24 Jun 2019 13:23:38 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1561400619; bh=g8Uz5zK8b2Zm+sgxlgpbmnk4L0rej0arHDvCgWPWyLw=; h=Subject:To:References:From:Date:In-Reply-To; b=Y4avQJ6Re4g9abhmcMsJaWYkaSBDab/RAYaYm8xibQe7AiCvijdEAemLcU2j8maRC eRqjzCjBAwxixpIMeSFZg9gwvKJE2QABBwLRn84HAX6ICtF/FjPFK4zItQhk6xBMau 1t38v5NR/6rYVJkxOrPPg9cUEDJ/HmM8Xc+b9LRc=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.39.7] claimed to be unultimate.local
To: Henrik Levkowetz <henrik@levkowetz.com>, Mark Nottingham <mnot@mnot.net>, tools-discuss@ietf.org
References: <11E75566-9C0B-4A55-93BF-6D2AF3C013D2@mnot.net> <cff373e8-3631-1c04-b5ac-5b11d219d418@levkowetz.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <38e51d14-ff2e-209b-0707-2659e4967a02@nostrum.com>
Date: Mon, 24 Jun 2019 13:23:37 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <cff373e8-3631-1c04-b5ac-5b11d219d418@levkowetz.com>
Content-Type: multipart/alternative; boundary="------------7FE490745A0BD32A38EA5580"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/PxozEyLUBZi2P_TAf0fNw0aPNYI>
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: Mon, 24 Jun 2019 18:23:42 -0000

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