Injection-Date and Injection-Info in nnrpd

[Julien ÉLIE]

Hi Heiko,

> Injection-Date: will disclose
> the exact date and should be made configurable for privacy reasons.

The Injection-Date: header can be set by a client.
If not set by a client, the server will set it (if addinjectiondate
is set to true).

INN 2.5.2 -> only check the syntax (not the reality) of the Injection-Date:
header, if present.
INN 2.6.0 -> add the header and also check it, if already present.


>> * The Injection-Info: header cannot be set by a posting agent.
>>  It is always added with POST (not IHAVE).
>
> As mentioned above: IHAVE in nnrpd (not used very often) should be handled
> like POST because it is injection too.

IHAVE behaves like POST in INN 2.6.0.
No change in INN 2.5.2.

INN 2.5.2 -> only reject articles containing an Injection-Info: header field.
INN 2.6.0 -> add the header and also reject as INN 2.5.2 does.


>>  There may be posting-host="83.114.132.186:83.114.132.186" if reversing
>>  the IP address does not work.
>
> If not resolvable it should be just posting-host="83.114.132.186" as
> I understand RFC 5536.

OK, for INN 2.6.0.
Not used in INN 2.5.2.


>> * Go on rejecting articles whose Date: header is too far in
>>  the past, even though Injection-Date: is fine.
>
> This is already implemented in innd and should not be changed.

At some point in the future, innd will have to check both Date:
and Injection-Date: headers.  Probably for INN 2.6.0 too (not yet
implemented, contrary to the points above).

-- 
Julien ÉLIE

« Rien ni personne n'a tout à fait tort : même une horloge
  arrêtée a raison deux fois par jour. » (John Steinbeck)