Inews and long headers

[Julien ÉLIE]

Hi Kamil,

>> I suggest the following patch for inews.  Do you happen to have
>> the possibility to test it and report if it solves your issue?
> 
> It looks it is better now.

OK, thanks for having tested.


> Now I have problem with lines
> 
> --8<---------------cut here---------------start------------->8---
> Header-name:
>   aaaaa
> --8<---------------cut here---------------end--------------->8---
> but I am not sure if this is properly formatted line.

Header-name:\r\n aaaaa\r\n
is malformatted.  A space is needed after the colon.


FYI, I quote Appendix C of RFC 5536:

    This appendix lists the differences between the syntax allowed by the
    Netnews article format (this document) as compared to the Internet
    Message Format, as specified in [RFC5322].

    The Netnews article format is a strict subset of the Internet Message
    Format; all Netnews articles conform to the syntax of [RFC5322].

    The following restrictions are important:

    o  A SP (space) is REQUIRED after the colon (':') following a header
       field name.

    o  A slightly restricted syntax of <msg-id> (to be used by the
       Message-ID, References, and Supersedes header fields) is defined.

    o  The length of a <msg-id> MUST NOT exceed 250 octets.

    o  Comments are not allowed in the Message-ID header field.

    o  The CFWS between <msg-id>s in the References header field is not
       optional.

    o  It is legal for a parser to reject obsolete syntax, except that:

       *  The <obs-phrase> construct MUST be accepted.

       *  The obsolete <zone> "GMT" MUST be accepted within a
          <date-time>.

    o  Every line of a header field body (including the first and any
       that are subsequently folded) MUST contain at least one non-
       whitespace character.  This means that an empty header field body
       is illegal.

-- 
Julien ÉLIE

« O fortunatos nimium, sua si bona norint, agricolas. » (Virgile)