Re: [coman] Is Coman maillist still needed? WAS:FW: coman post from mailer-daemon@ietfa.amsl.com requires approval
Benoit Claise <bclaise@cisco.com> Tue, 23 January 2018 11:16 UTC
Return-Path: <bclaise@cisco.com>
X-Original-To: coman@ietfa.amsl.com
Delivered-To: coman@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71D161200FC for <coman@ietfa.amsl.com>; Tue, 23 Jan 2018 03:16:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 7n6wqa4dbMyi for <coman@ietfa.amsl.com>; Tue, 23 Jan 2018 03:16:10 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 772251200C1 for <coman@ietf.org>; Tue, 23 Jan 2018 03:16:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1751; q=dns/txt; s=iport; t=1516706169; x=1517915769; h=subject:from:to:references:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=mifIYWa3bzDcDitKe67YhIBm3G3ePikZkgSacK5l/e8=; b=hwhXEANVw5GObWezXzzMacNLccc/jtihNdfidrvhBwzyW9O7Tx2vZPRS ADQ37z2tkuX3yenm1L+hSDAOToVFFG7sG0gDOM/8JV3VXswEtZe+UdtXr pUpQOFFzELUX7mKOmuFPQWlWz2HbXK02SgK5H9oBECZWTXP0TCNwuiNMy M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B0AQB0Emda/xbLJq1eGQEBAQEBAQEBAQEBAQcBAQEBAYQodCeDXYsYj3SXU4ICChgLhRgChUwUAQEBAQEBAQEBayiFIwEBAQQBASEPAQU2FwQJAg4DBAEBAwIfBAMCAicfCAEIBgEMBgIBAYoxEJU0nXCCJ4o3AQEBAQEBAQEBAQEBAQEBAQEBAQEZBYEPgzqDbIIRgwWDLwEBAoE3GAEBgzWCZQEEhUueMpVdghuGH4Nxh3QrAY8PhF6DNYE8NiKBUDMaCBsVPYIqgk86GIE3QDeIMoI8AQEB
X-IronPort-AV: E=Sophos;i="5.46,400,1511827200"; d="scan'208";a="1550269"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Jan 2018 10:48:32 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id w0NAmVkZ014519; Tue, 23 Jan 2018 10:48:31 GMT
From: Benoit Claise <bclaise@cisco.com>
To: Mehmet Ersue <mersue@gmail.com>, coman@ietf.org
References: <030001d266c1$f17e1920$d47a4b60$@gmail.com> <477f9b39-c62a-f5fa-9ecc-c6b28ae91560@cisco.com>
Message-ID: <5b0bd30f-8ea6-ee31-42b2-98365507603c@cisco.com>
Date: Tue, 23 Jan 2018 11:48:31 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <477f9b39-c62a-f5fa-9ecc-c6b28ae91560@cisco.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/coman/4gx1FfR0wiqegIUoZuXPhuZs1Q4>
Subject: Re: [coman] Is Coman maillist still needed? WAS:FW: coman post from mailer-daemon@ietfa.amsl.com requires approval
X-BeenThere: coman@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Management of Constrained Networks and Devices <coman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/coman>, <mailto:coman-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/coman/>
List-Post: <mailto:coman@ietf.org>
List-Help: <mailto:coman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/coman>, <mailto:coman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jan 2018 11:16:11 -0000
Test. Disregard. Regards, Benoit > Dear all, > > I requested the coman mailing list closure. > > Regards, B. >> Dear All, >> >> Coman maillist has been established some years ago for the discussion >> of the >> so called Coman drafts on the "Management of Networks with Constrained >> Devices". >> In the meantime the Coman drafts have been published as RFC 7547 and >> 7548. >> >> Other than some spam mails there is no traffic on the maillist. >> >> We assume the maillist is not needed anymore. >> If there is no request or discussion started within one week the >> maillist is >> proposed to close. >> Please let us know otherwise. >> >> Thanks, >> Mehmet >> >> -----Original Message----- >> From: coman [mailto:mailman-bounces@mail.ietf.org] On Behalf Of >> coman-owner@ietf.org >> Sent: Tuesday, December 13, 2016 6:35 PM >> To: coman-owner@ietf.org >> Subject: coman post from mailer-daemon@ietfa.amsl.com requires approval >> >> As list administrator, your authorization is requested for the following >> mailing list posting: >> >> List: coman@ietf.org >> From: mailer-daemon@ietfa.amsl.com >> Subject: Undelivered Mail Returned to Sender >> Reason: Post by non-member to a members-only list >> >> At your convenience, visit: >> >> https://www.ietf.org/mailman/admindb/coman >> to approve or deny the request. >> >> _______________________________________________ >> coman mailing list >> coman@ietf.org >> https://www.ietf.org/mailman/listinfo/coman >> . >> > > _______________________________________________ > coman mailing list > coman@ietf.org > https://www.ietf.org/mailman/listinfo/coman > . >
- [coman] Is Coman maillist still needed? WAS:FW: c… Mehmet Ersue
- Re: [coman] Is Coman maillist still needed? WAS:F… Benoit Claise
- Re: [coman] Is Coman maillist still needed? WAS:F… Benoit Claise