innd and rejects of dates

[Julien ÉLIE]

Hi Russ,

> I would reject articles with Date headers that cannot be parsed.  I don't
> see any good reason to accept those any more than we do already (we're
> already lax about what we accept).

Speaking about dates, I see that nnrpd generates by default a UTC date:

    Date: Sun, 26 Sep 2010 11:44:33 +0000 (UTC)

If I set localtime to true in readers.conf, nnrpd generates:

    Date: Sun, 26 Sep 2010 13:44:33 +0200 (CEST)



I remember having discussed the question with Adam for signcontrol.py
in news.admin.hierarchies, but we did not speak about INN:
    http://groups.google.fr/group/news.admin.hierarchies/browse_thread/thread/c0016c36ccd7b391
    <news:hgl1ur$3lj$1 at news.trigofacile.com> in December 2009


According to RFC 5322:

3.3. Date and Time Specification

   The form "+0000" SHOULD be used to indicate a time zone at
   Universal Time.  Though "-0000" also indicates Universal Time, it is
   used to indicate that the time was generated on a system that may be
   in a local time zone other than Universal Time and that the date-time
   contains no information about the local time zone.



Then nnrpd should generate "-0000" instead of "+0000" on my system.

Should we put "-0000" when (localtime != gmtime)?
or something else should be done to deal with that?

-- 
Julien ÉLIE

« -- Vite, vous deux ! Allez ouvrir les portes !
  -- D'accord chef !
  -- Tenez bien le bouclier chef ! » (Astérix)