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).
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$1@gioia.aioe.org>, 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:
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.
RFC 5537: Be liberal in what you accept, and conservative in
what you send.
That's the best answer you could give me!
So, no matter how much we read them, often the answers are in the RFCs!
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 293 |
Nodes: | 16 (2 / 14) |
Uptime: | 225:54:33 |
Calls: | 6,624 |
Calls today: | 6 |
Files: | 12,171 |
Messages: | 5,318,613 |