From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 6E7301F461 for ; Sun, 30 Jun 2019 22:36:35 +0000 (UTC) From: Eric Wong To: meta@public-inbox.org Subject: [PATCH 0/2] nntp: cleanup and support CAPABILITIES Date: Sun, 30 Jun 2019 22:36:33 +0000 Message-Id: <20190630223635.4687-1-e@80x24.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: I haven't noticed people using STARTTLS on public-inbox.org, but I do notice CAPABILITIES being issued. Maybe clients want to check it before trying STARTTLS? This will also be required to advertise COMPRESS in the future. Eric Wong (2): nntp: remove DISABLED hash checks nntp: add support for CAPABILITIES command lib/PublicInbox/NNTP.pm | 26 ++++++++++++++++++++------ t/nntpd-tls.t | 18 ++++++++++++++++++ t/nntpd.t | 5 +++++ 3 files changed, 43 insertions(+), 6 deletions(-) -- EW