From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
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,AWL,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 4D7C51F609;
	Thu, 13 Jun 2019 07:00:31 +0000 (UTC)
Date: Thu, 13 Jun 2019 07:00:31 +0000
From: Eric Wong <e@80x24.org>
To: Dave Taht <dave@taht.net>
Cc: meta@public-inbox.org
Subject: Re: interop with leafnode
Message-ID: <20190613070031.GA9743@dcvr>
References: <87tvlkbkrk.fsf@taht.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87tvlkbkrk.fsf@taht.net>
List-Id: <meta.public-inbox.org>

Dave Taht <dave@taht.net> wrote:
> For most (not all) traffic, leafnode does this:
> 
> > Oct 16 22:08:01 spaceheater fetchnews[3045]: lwn.kernel.lkml:
> > considering articles 200621 - 200643
> > Oct 16 22:08:01 spaceheater fetchnews[3045]: Discarding article 200621
> > - no Path:  found

So yeah, I Cc-ed you on <20190613065413.4705-1-e@80x24.org>.
Apparently leafnode doesn't need any real Path:, and just a
single byte seems to work.

However, I've also noticed leafnode (finally tried it) also
fails if a Message-ID is too long and spans multiple lines
(those were from outlook.com, go figure).