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: Fri, 6 Nov 2020 14:57:34 +0300 [thread overview]
Message-ID: <CA+PODjr0y+mzquNzMT4uX1jxQNbwBLb8k4==4D778m-MLjxwww@mail.gmail.com> (raw)
In-Reply-To: <20201105075021.GA83277@dcvr>
чт, 5 нояб. 2020 г. в 10:50, Eric Wong <e@80x24.org>:
>
[...]
> > 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?
>
> Nope, but currently PublicInbox::Eml folds by default
> (and Email::MIME/Email::Simple did in ->as_string, too).
>
> I didn't expect clients to have problems with folded lines since
> Received: and Cc: are often folded, anyways.
>
> Does leafnode struggle with those headers? Or just Newsgroups/Xref?
There are two versions of leafnode - leafnode1 (1.11.11) and leafnode2
(2.0.0.alpha20140727b).
The first version correctly parses headers (it knows about folding),
the second version - not. At least Xref: is affected. Newsgroups:
header is expected to be folded.
> We may need a separate API method for setting NNTP-only headers
> to appease leafnode...
Or write in docs a big fat warning about using leafnode2.
> > > > 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.
>
> It may be nice to extract hostname from URI, anyways, since it
> should be possible to advertise NNTPS endpoint in the WWW UI.
=~ s|[^:]+://||; ?
prev parent reply other threads:[~2020-11-06 11:57 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
2020-11-05 7:50 ` Eric Wong
2020-11-06 11:57 ` Andrey Melnikov [this message]
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+PODjr0y+mzquNzMT4uX1jxQNbwBLb8k4==4D778m-MLjxwww@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).