Netgear DG834G Date of Email Woes Continue

To those struggling to find the log files from their DG834G this
morning, the 'date of email' bug has now run out of subscripts for the
array. So instead of simply being a month ahead of themselves the emails
are now showing up as 1/1/70.

Presumably everything will work again once we hit January!

David.

In article <43940a7a$0$18545$(E-Mail Removed)>,
David <(E-Mail Removed)> writes:
> To those struggling to find the log files from their DG834G this
> morning, the 'date of email' bug has now run out of subscripts for the
> array. So instead of simply being a month ahead of themselves the emails
> are now showing up as 1/1/70.
>
> Presumably everything will work again once we hit January!

What version or versions is this a problem with? Will it go away if I
update from 2.10.22 to 3.01.25?
--
SAm.

Sam Nelson wrote:
> In article <43940a7a$0$18545$(E-Mail Removed)>,
> David <(E-Mail Removed)> writes:
>
>>To those struggling to find the log files from their DG834G this
>>morning, the 'date of email' bug has now run out of subscripts for the
>>array. So instead of simply being a month ahead of themselves the emails
>>are now showing up as 1/1/70.
>>
>>Presumably everything will work again once we hit January!
>
>
> What version or versions is this a problem with? Will it go away if I
> update from 2.10.22 to 3.01.25?

AFAIK it's been there since version 1.0.5, so unless you go back to that
version you're stuck I'm afraid. Certainly all the latest versions have
the problem.

Thanks, David

In article <43941025$0$82655$(E-Mail Removed)>,
David <(E-Mail Removed)> writes:
> Sam Nelson wrote:
> > In article <43940a7a$0$18545$(E-Mail Removed)>,
> > David <(E-Mail Removed)> writes:
> >>To those struggling to find the log files from their DG834G this
> >>morning, the 'date of email' bug has now run out of subscripts for the
> >>array. So instead of simply being a month ahead of themselves the emails
> >>are now showing up as 1/1/70.
> >>
> >>Presumably everything will work again once we hit January!
> >
> > What version or versions is this a problem with? Will it go away if I
> > update from 2.10.22 to 3.01.25?
>
> AFAIK it's been there since version 1.0.5, so unless you go back to that
> version you're stuck I'm afraid. Certainly all the latest versions have
> the problem.

Marvellous. Thanks.
--
SAm.

On Mon, 05 Dec 2005 09:36:55 +0000, David <(E-Mail Removed)> wrote:

> To those struggling to find the log files from their DG834G this
> morning, the 'date of email' bug has now run out of subscripts for the
> array. So instead of simply being a month ahead of themselves the emails
> are now showing up as 1/1/70.

It's a big improvement for me. Before those incompetent programmers at
Netgear put that wrong and quite unnecessary Date: line in, my email
client figured out the time and date from the Received: lines. Now that
the line is gibberish, the mail client is doing it correctly once again.

> Presumably everything will work again once we hit January!

Maybe, for some weird non-standard Netgear meaning of the work "work" :-(

Tony

On Mon, 05 Dec 2005 09:36:55 +0000, David <(E-Mail Removed)> wrote:

> So instead of simply being a month ahead of themselves the emails
> are now showing up as 1/1/70.

BTW, what do you mean by "showing up" and where is that "/70" being
generated? Your email client? My various Netgear routers this morning
sent me emails looking like this:

Received: from unknown (unknown [81.187.***.***])
by mailspool2.panix.com (Postfix) with ESMTP id B7C1230A3A2
for <*****@*******.****.co.uk>; Mon, 5 Dec 2005 02:00:34 -0500 (EST)
Date: Mon,5 (null) 2005 07:00:11 -0000
From: *****@*******.****.co.uk
Subject: NETGEAR Security Log [13:d4:17]
To: *****@*******.****.co.uk

Where did you see that "1/1/70"?

Tony

David wrote in
43940a7a$0$18545$(E-Mail Removed):

> To those struggling to find the log files from their DG834G this
> morning, the 'date of email' bug has now run out of subscripts for the
> array. So instead of simply being a month ahead of themselves the
> emails are now showing up as 1/1/70.
>
> Presumably everything will work again once we hit January!

It's also a problem with the DG834GT, using firmware V1.01.28. However in
this case, at least it gets the year correct: for example, the date of
today's email is "Date: Mon,5 (null) 2005 09:00:00 -0000" which Outlook
Express displays as "05/01/2005". Sadly this means that the log entry for 1
Dec does not follow the one for 30 Nov but is at the beginning of the year!
I'm intrigued to see what happens after the end of December: will the 1 Jan
2006 email be timestamped 1 Jan 2006 or 1 Feb 2006?

I've resigned myself to my router always being one month ahead of itself, so
I display the Received date rather than the Sent date. I wonder why Netgear
have never fixed it. The date is displayed correctly within the log file (eg
"Sun, 2005-12-04 09:00:00") so why is it wrong in the email header. With the
original firmware that the router was supplied with, the Date line in the
header was missing altogether (I'm surprised that the RFCs for email allow
this - I'd have thought that From, Date and Subject would be mandatory); the
V1.01.28 upgrade fixed the swapping of attentuation and noise margin values
(very confusing!) but when they added the Date field, it was not the correct
date.

Anthony R. Gold wrote:
> On Mon, 05 Dec 2005 09:36:55 +0000, David <(E-Mail Removed)> wrote:
>
>
>>So instead of simply being a month ahead of themselves the emails
>>are now showing up as 1/1/70.
>
>
> BTW, what do you mean by "showing up" and where is that "/70" being
> generated? Your email client? My various Netgear routers this morning
> sent me emails looking like this:
>
> Received: from unknown (unknown [81.187.***.***])
> by mailspool2.panix.com (Postfix) with ESMTP id B7C1230A3A2
> for <*****@*******.****.co.uk>; Mon, 5 Dec 2005 02:00:34 -0500 (EST)
> Date: Mon,5 (null) 2005 07:00:11 -0000
> From: *****@*******.****.co.uk
> Subject: NETGEAR Security Log [13:d4:17]
> To: *****@*******.****.co.uk
>
> Where did you see that "1/1/70"?
>
> Tony

Yes Tony, you are quite right, my headers are the same as yours will the
(null) month in and the date I see is a function of my mail client.
I'm using Thunderbird, which obviously displays invalid dates as 1/1/70
(which I didn't know as it happens) rather than using a received date.
I've become so used to the date being wrong, I didn't investigate it as
far as you!! Shame on me.

David.