1. Forum
  2. Usenet
  3. NEWS.SOFTWARE.NNTP

  • Headers that exceed the length of 998 characters.

    From // My2Cents@21:1/5 to All on Sun Nov 8 08:31:00 2020
    Hello,


    When client use the IHAVE command (a feed) or ARTICLE (a suck feed),
    it's différent because article was already injected even if the 998/78 character limitations per line is not respected (no folding used).

    You have to read :

    When client use the IHAVE command (a feed) or a server use ARTICLE to
    suck news from another server (suck feed), it's different because
    article was already injected even if the 998/78 character limitations
    per line is not respected (no folding used).

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Julien_=c3=89LIE?=@21:1/5 to All on Sun Nov 8 09:54:06 2020
    Bonjour Franck,

    In this article, the header 'References' has a length of 1642 characters
    and should have been folded to comply with RFC 5322.
    [...]
    In the same way, if you look article <ro7hlp$jaf$[email protected]>, you
    will see that 'References' is correctly folded BUT at least one line of
    the body has a length of more than 998 characters, which goes against
    the second limit imposed by RFC 5322.
    [...]
    So, my question was here. Does a server have to accept articles that do
    not comply with certain RFCs without considering them as "junk" (Either
    by using the POST command or the IHAVE command)?

    When using POST for injection, a server should reject a malformed
    article. Once injected, relaying with IHAVE should be done. I do not
    believe such articles should be considered as "junk".


    RFC 5537:

    3.1. General Principles

    There are two important principles that news implementors and
    administrators need to keep in mind. The first is the well-known
    Internet Robustness Principle:

    Be liberal in what you accept, and conservative in what you send.

    As applied to Netnews, this primarily means that unwanted or non-
    compliant articles SHOULD be rejected as early as possible, but once
    they are in general circulation, relaying and serving agents may wish
    to accept them where possible rather than lose information. Posting
    agents and injecting agents SHOULD therefore be maximally strict in
    their application of both this protocol and [RFC5536], and reading
    agents SHOULD be robust in the presence of violations of the Netnews
    article format where possible.

    --
    Julien ÉLIE

    « Le sel de l'existence est essentiellement dans le poivre qu'on y
    met. » (Alphonse Allais)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Franck@21:1/5 to All on Sun Nov 8 13:29:45 2020
    Le 08/11/2020 à 09:54, Julien ÉLIE a écrit :

    When using POST for injection, a server should reject a malformed
    article.  Once injected, relaying with IHAVE should be done.  I do not believe such articles should be considered as "junk".

    In fact, until now I used to accept and move them into the "junk"
    newsgroup because I was wondering what was the best action to take.

    RFC 5537:
          Be liberal in what you accept, and conservative in what you send.

    That's the best answer you could give me!

       As applied to Netnews, this primarily means that unwanted or non-
       compliant articles SHOULD be rejected as early as possible, but once
       they are in general circulation, relaying and serving agents may wish
       to accept them where possible rather than lose information.  Posting
       agents and injecting agents SHOULD therefore be maximally strict in
       their application of both this protocol and [RFC5536], and reading
       agents SHOULD be robust in the presence of violations of the Netnews
       article format where possible.

    So, no matter how much we read them, often the answers are in the RFCs!

    Thanks Julien!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Julien_=c3=89LIE?=@21:1/5 to All on Sun Nov 8 14:35:25 2020
    Bonjour Franck,

    RFC 5537: Be liberal in what you accept, and conservative in
    what you send.

    That's the best answer you could give me!

    You're welcome :)



    So, no matter how much we read them, often the answers are in the RFCs!

    Another pretty useful document to read is that Internet Draft:
    https://tools.ietf.org/html/draft-ietf-usefor-useage-01

    Unfortunately, USEAGE did not reach the RFC status like USEFOR (5536)
    and USEPRO (5537) because of lack of time and energy after all the NNTP
    and article format standardization at that time, but is really
    worthwhile reading.

    --
    Julien ÉLIE

    « Sol lucet omnibus. »

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)