From: Eric Wong <e@80x24.org>
To: Dave Taht <dave@taht.net>
Cc: meta@public-inbox.org
Subject: Re: interop with leafnode
Date: Thu, 13 Jun 2019 07:00:31 +0000
Message-ID: <20190613070031.GA9743@dcvr> (raw)
In-Reply-To: <87tvlkbkrk.fsf@taht.net>
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).
next prev parent reply index
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 16:28 Dave Taht
2018-10-27 0:10 ` Eric Wong
2018-10-27 0:33 ` Dave Taht
2018-10-27 0:43 ` Eric Wong
2018-10-27 16:07 ` Dave Taht
2019-05-05 21:40 ` Eric Wong
2019-06-13 7:00 ` Eric Wong [this message]
2019-06-13 17:52 ` Dave Taht
2019-06-13 20:46 ` [PATCH] nntp: ensure Message-ID is not folded for leafnode Eric Wong
Reply instructions:
You may reply publically to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190613070031.GA9743@dcvr \
--to=e@80x24.org \
--cc=dave@taht.net \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
user/dev discussion of public-inbox itself
Archives are clonable:
git clone --mirror https://public-inbox.org/meta
git clone --mirror http://czquwvybam4bgbro.onion/meta
git clone --mirror http://hjrcffqmbrq6wope.onion/meta
git clone --mirror http://ou63pmih66umazou.onion/meta
Newsgroups are available over NNTP:
nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta
nntp://ou63pmih66umazou.onion/inbox.comp.mail.public-inbox.meta
nntp://czquwvybam4bgbro.onion/inbox.comp.mail.public-inbox.meta
nntp://hjrcffqmbrq6wope.onion/inbox.comp.mail.public-inbox.meta
nntp://news.gmane.org/gmane.mail.public-inbox.general
note: .onion URLs require Tor: https://www.torproject.org/
AGPL code for this site: git clone https://public-inbox.org/ public-inbox