From: Andrey Melnikov <temnota.am@gmail.com>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] nntp: delimit Newsgroup: header with commas
Date: Thu, 5 Nov 2020 00:01:00 +0300 [thread overview]
Message-ID: <CA+PODjpd6f1q-LUkcKtJbcowV3x8QOYmiqKuhJ9nK4ot1mUNjQ@mail.gmail.com> (raw)
In-Reply-To: <20201104194706.GA24387@dcvr>
ср, 4 нояб. 2020 г. в 22:47, Eric Wong <e@80x24.org>:
>
> Andrey Melnikov <temnota.am@gmail.com> wrote:
> > ср, 4 нояб. 2020 г. в 13:44, Eric Wong <e@80x24.org>:
> > > I suppose a few extra bytes won't hurt, too much :x
> >
> > Current:
> > Path: y
> > org.linuxdriverproject.driverdev-devel:35214
> > org.kernel.vger.linux-devicetree:433117
> > org.kernel.vger.linux-kernel:3765410
> > org.kernel.vger.linux-media:192196
>
> Huh? From what I can see, the last 4 lines are part of the
> Xref: header, which is unchanged atm (I plan on speeding it up
> with extindex, though).
Yeah, leafnode rewrite Xref: header..
-- raw --
Sender: "devel" <driverdev-devel-bounces@linuxdriverproject.org>
Path: y
Xref: nntp://nntp.lore.kernel.org
org.linuxdriverproject.driverdev-devel:35265
org.kernel.vger.linux-devicetree:433316
org.kernel.vger.linux-kernel:3766059
org.kernel.vger.linux-mmc:59564
org.kernel.vger.linux-wireless:204883
org.kernel.vger.netdev:733193
Newsgroups: org.linuxdriverproject.driverdev-devel
org.kernel.vger.linux-devicetree
org.kernel.vger.linux-kernel org.kernel.vger.linux-mmc
org.kernel.vger.linux-wireless org.kernel.vger.netdev
Archived-At: <https://lore.kernel.org/driverdev-devel/20201104191554.GA3972736@bogus/>
List-Archive: <https://lore.kernel.org/driverdev-devel/>
-- on disk --
Sender: "devel" <driverdev-devel-bounces@linuxdriverproject.org>
Path: y
org.linuxdriverproject.driverdev-devel:35265
org.kernel.vger.linux-devicetree:433316
org.kernel.vger.linux-kernel:3766059
org.kernel.vger.linux-mmc:59564
org.kernel.vger.linux-wireless:204883
org.kernel.vger.netdev:733193
Newsgroups: org.linuxdriverproject.driverdev-devel
org.kernel.vger.linux-devicetree
org.kernel.vger.linux-kernel org.kernel.vger.linux-mmc
org.kernel.vger.linux-wireless org.kernel.vger.netdev
Archived-At: <https://lore.kernel.org/driverdev-devel/20201104191554.GA3972736@bogus/>
List-Archive: <https://lore.kernel.org/driverdev-devel/>
Xref: news.localnet org.linuxdriverproject.driverdev-devel:4323
---
Haha. It simply does not expect folded multiline Xref: header. And
generate by itself a new (unfolded, separated by space) header when
storing article on disk.
Is really Newsgroups: & Xref: headers need folding?
> > and new:
> > Path: nntp.lore.kernel.org!not.for.mail
> > save more extra bytes...
> >
> > Hehe... yet another cosmetic thing:
> > $ telnet nntp.lore.kernel.org 119
> > Trying 54.189.247.149...
> > Connected to korg-lkml-1-news-lb-839eef9f3a4cef4e.elb.us-west-2.amazonaws.com.
> > Escape character is '^]'.
> > 201 nntp://nntp.lore.kernel.org ready - post via email
> > quit
> > Connection closed by foreign host.
> >
> > 'nntp://nntp.lore.kernel.org' is not a node name per RFC... But this
> > is a configuration problem on nntp.lore.kernel.org side.
>
> You can notify helpdesk@kernel.org to get it fixed.
This is cosmetics. nntp readers do not use this hostname.
> Though I suppose the public-inbox code could warn or extract the
> hostname out of it.
>
> (NNTPS support would be nice, but maybe OpenSSL or O::Socket::SSL
> on RHEL/CentOS 8 is too old)
next prev parent reply other threads:[~2020-11-04 21:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 12:29 nntpd generate wrong headers Andrey Melnikov
2020-11-03 22:55 ` [PATCH] nntp: delimit Newsgroup: header with commas Eric Wong
2020-11-03 23:11 ` Andrey Melnikov
2020-11-03 23:59 ` Eric Wong
[not found] ` <CA+PODjr0NcFBu42mOdFnmf4vvxb3YZ+nUt=GqWEq+agXa8Au0Q@mail.gmail.com>
2020-11-04 10:44 ` Eric Wong
2020-11-04 11:46 ` Andrey Melnikov
2020-11-04 19:47 ` Eric Wong
2020-11-04 21:01 ` Andrey Melnikov [this message]
2020-11-05 7:50 ` Eric Wong
2020-11-06 11:57 ` Andrey Melnikov
Reply instructions:
You may reply publicly 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=CA+PODjpd6f1q-LUkcKtJbcowV3x8QOYmiqKuhJ9nK4ot1mUNjQ@mail.gmail.com \
--to=temnota.am@gmail.com \
--cc=e@80x24.org \
--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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).