timestamp out of range for Mimo NZBs

[FuzzyOne]

When using Mimo usenet browser with Giganews you can create an NZB by right clicking on an item and choosing "Copy NZB to Clipboard" which can then be pasted into Notepad and saved.

However SABnzbd comes up with the error:
WARNING: Invalid NZB file ??.nzb, skipping (reason=timestamp out of range for platform time_t, line=0)
I notice that the timestamps are a lot longer from Mimo than usual?
eg:
File dated about 05 Apr 2009 01:28 AM Mimo generates:

Code: Select all

<file poster="Unspecified" date="1321996583378" ...

or File dated about 12 Nov 2011 11:20PM Mimo generates:

Code: Select all

<file poster="Unspecified" date="1321996714125" ...

Manually searching and replacing the dates in the NZB file with a reasonable guess from some other NZB allows the NZB to be processed and the files downloaded.

Any chance that SABnzbd can cope with the Mimo generated date formats pls? I find SABnzbd much more reliable for downloading .

Win7-64 Pro with setup, SABnzbd v 0.6.10, Mimo Beta v 0.2.4.3858, IPv4, no firewall, is reproducible.

[shypike]

Giganews should just use standard NZB files, it's a very well defined format.
Please complain to them (too).

[FuzzyOne]

Now also submitted the bug to www.goldenfrog.com who makes Mimo for Giganews.

Any chance to have an option to ignore or turn off timestamp checking if it's not possible to get a compatability fix pls?

[jcfp]

The date they give is almost 42000 years in the future. Seems there's 3 digits too many, probably caused by a programming error on the side of giganews/mimo. After loosing the last 3 digits, both "1321996583378" and "1321996714125" are unix times representing dates around Tue, 22 Nov 2011 21:16 GMT.

[shypike]

I'll see if there's a quick fix possible.
BTW: this is not a SABnzbd bug.