what lists are in apps.ietf.org?

James Galvin <galvin+discuss@elistx.com> Fri, 15 February 2008 16:40 UTC

Return-Path: <discuss-bounces@ietf.org>
X-Original-To: ietfarch-discuss-archive@core3.amsl.com
Delivered-To: ietfarch-discuss-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E622C28D260; Fri, 15 Feb 2008 08:40:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.265
X-Spam-Level:
X-Spam-Status: No, score=-0.265 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZWSfX9l7YBA6; Fri, 15 Feb 2008 08:40:45 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B636D3A6AAE; Fri, 15 Feb 2008 08:40:45 -0800 (PST)
X-Original-To: discuss@core3.amsl.com
Delivered-To: discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D90963A6AAE for <discuss@core3.amsl.com>; Fri, 15 Feb 2008 08:40:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h1dKS7lUk6fM for <discuss@core3.amsl.com>; Fri, 15 Feb 2008 08:40:43 -0800 (PST)
Received: from ee01.elistx.com (ee01.elistx.com [67.155.182.182]) by core3.amsl.com (Postfix) with ESMTP id F2B053A6874 for <discuss@apps.ietf.org>; Fri, 15 Feb 2008 08:40:42 -0800 (PST)
Received: from CONVERSION-DAEMON.elistx.com by elistx.com (PMDF V6.3-2x2 #31546) id <0JWA00901GXLPY@elistx.com> for discuss@apps.ietf.org; Fri, 15 Feb 2008 11:39:21 -0500 (EST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by elistx.com (PMDF V6.3-2x2 #31546) with ESMTP id <0JWA007MMGXL0G@elistx.com> for discuss@apps.ietf.org; Fri, 15 Feb 2008 11:39:21 -0500 (EST)
Date: Fri, 15 Feb 2008 11:40:14 -0500
From: James Galvin <galvin+discuss@elistx.com>
Subject: what lists are in apps.ietf.org?
To: discuss@apps.ietf.org
Message-id: <CBB7CB3AE279CC3B47302CE9@[192.168.1.3]>
MIME-version: 1.0
X-Mailer: Mulberry/4.0.7 (Win32)
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-BeenThere: discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@ietf.org>
List-Help: <mailto:discuss-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@ietf.org?subject=subscribe>
Sender: discuss-bounces@ietf.org
Errors-To: discuss-bounces@ietf.org

First let me apologize that email to apps.ietf.org stopped working. 
It certainly was not planned that way.  Worse, there was an early 
ticket from Dave Crocker pointing out there was an issue but even 
this got overlooked in the stream of issues that cried out for 
attention.

Unfortunately, since apps.ietf.org is a delegated domain, the 
default action for tickets of this type was to defer to those third 
parties.  This actually worked until we looked closer at what was 
going on with email and realized that the DNS configuration was 
part of the problem.  apps.ietf.org was unique in this respect 
compared to all the other "third party domains".  Sorry, but that 
contributed to the oversight.  I could explain all this in way too 
much detail but, frankly, it would sound like an excuse and it's 
really not important right now.

The problem now is that there is no information as to what mailing 
lists are in the apps.ietf.org domain.  I am aware of the following 
three:

    discuss
    urn-nid
    w3c-policy

The discuss list now works and the other two will work soon 
(today).  There is a mapping rule that has to be added to the email 
system to make things work the way you would expect given the 
configuration of apps.ietf.org.

If you own a list in the apps.ietf.org domain would you please 
self-declare by sending a message to me and I'll make sure the 
mapping gets entered and your list starts working again.

Thanks,

Jim