Re: [ftpext] RFC 2640

"TJ Saunders" <tj@castaglia.org> Tue, 21 December 2010 23:40 UTC

Return-Path: <tj@castaglia.org>
X-Original-To: ftpext@core3.amsl.com
Delivered-To: ftpext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 17D003A6910 for <ftpext@core3.amsl.com>; Tue, 21 Dec 2010 15:40:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 DV8Itge-l+eQ for <ftpext@core3.amsl.com>; Tue, 21 Dec 2010 15:40:42 -0800 (PST)
Received: from new1.smtp.messagingengine.com (new1.smtp.messagingengine.com [66.111.4.221]) by core3.amsl.com (Postfix) with ESMTP id BAAED3A67FA for <ftpext@ietf.org>; Tue, 21 Dec 2010 15:40:41 -0800 (PST)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 23DD5200E1; Tue, 21 Dec 2010 18:42:38 -0500 (EST)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Tue, 21 Dec 2010 18:42:38 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=date:from:to:cc:subject:in-reply-to:message-id:references:mime-version:content-type; s=smtpout; bh=4INnRT1oCkGYzEXlqPyiMMkNchc=; b=R2jclLdmny202ok1XLkZYBHuE3/bUHwUap0Xb3CAu35iqzU0yrMii4SoPjewXnZ4gHXEnAYbuLNDCTS8DMV53xgT3hLqfjFgm9BSB+BmTluciC8xaGmxaPlZ17iKbSALA2sV1YGyaI8BD2muzNw6KvQAMg3Qk68wSvOanjtgjVM=
X-Sasl-enc: 8ERYVHsF15ZW+oinPDgcRKH+yb/YAQHJ22VNXM14uP6c 1292974957
Received: from familiar.netflix.com (lg-nat.corp.netflix.com [208.75.77.65]) by mail.messagingengine.com (Postfix) with ESMTPSA id 84051443F13; Tue, 21 Dec 2010 18:42:37 -0500 (EST)
Date: Tue, 21 Dec 2010 15:42:36 -0800 (PST)
From: "TJ Saunders" <tj@castaglia.org>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <C04E4326-D403-4B8F-B6E2-506B1FECB4FE@muada.com>
Message-ID: <alpine.DEB.2.00.1012211542050.12930@familiar.castaglia.org>
References: <C04E4326-D403-4B8F-B6E2-506B1FECB4FE@muada.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ftpext@ietf.org
Subject: Re: [ftpext] RFC 2640
X-BeenThere: ftpext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ftpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ftpext>, <mailto:ftpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ftpext>
List-Post: <mailto:ftpext@ietf.org>
List-Help: <mailto:ftpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ftpext>, <mailto:ftpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Dec 2010 23:40:45 -0000

> My questions:
> 
> - are there any RFC 2640-compliant implementations out there?

Yes.  ProFTPD, when built with NLS support, implements RFC 2640.

Cheers,
TJ

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   Much of your pain is self-chosen.

     -Kahlil Gibran

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~