Email envelope time zone wrong IP2M-841

[knute]

Return-Path: <xxxx@xxxx.com>
Received: from localhost ([192.168.3.23])
(authenticated bits=0)
by xxxx.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id u8R4r5Fg001945
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT)
for <xxxx@xxxx.com>; Mon, 26 Sep 2016 21:53:06 -0700 <------------------------------------------------------
Message-Id: <201609270453.u8R4r5Fg001945@xxxx.com>
Date: Mon, 26 Sep 2016 21:53:06 +0800 <-------------------------------------------------------------------
From: <>
To: <xxxx@xxxx.com>
Subject: =?UTF-8?B?TWFpbF9UZXN0?=
MIME-Version: 1.0
Content-type: multipart/mixed;boundary="======DAHUA_TECH======"

This is a multi-part message in MIME format.

--======DAHUA_TECH======
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: base64

QWxhcm0gvweINPopnONUNGYUxfVGVzdA0KQWxhcm0gSW5wdXQgQ2hhbm5lbDogMQ0KQWxhcm0gU3Rh
cnQgVGltZShEL00vWSBIOk06Uyk6IDI2LzA5LzlaksjeJLLKEjNNTM6MDQNCkFsYXJtIERldmljZSBO
YW1lOiBBTUMwMDBROF8wWTQ3RTkNCkFsYXJtIE5hbWU6IA0KSVAgQWRkc4k3nNPOvbyqoUIObyjE2OC4z
LjIzDQo=

--======DAHUA_TECH======--

As you can see, the envelope is marked with +0800 timezone. I set the timezone in the setup as -0800 with daylight savings enabled. It is currently daylight savings time here so the actual time difference is -0700, the same as the receiving server marked the email.

This apparently changed in an update from version 4 to version 8 of the firmware. I looked in old posts and found it reported back as far as April 26th of this year.

I called tech support in India today and Vincent told me that nobody had reported this problem but I found two instances on the forum in about 10 minutes. Clearly this is a known issue.

Is there a known workaround?

Is the bug going to be fixed?

When?

Thanks,

knute...

[Melvin]

Hello knute,

We are aware of this issue and will have a fix for this. I dont have the exact time frame for a fix at the moment.

Workaround: Can you disable the NTP under time settings and just manually set the camera timezone and see if that fixes the issue.

[knute]

The software appears to completely ignore the timezone that is set in the setup page. No matter what setting I use, the email header is always +0800. I can set the clock ahead 15 hours and then the email sorts correctly according to time because I am in -0700 and it puts +0800 in the email but then the time in the email is off by 15 hours. Also I can't run NTP to keep the clock accurate or it resets the clock.

This problem has been known for at least 5 months. Is there an earlier firmware version where the clock works correctly and can we install it?

[Rick]

Is there a work around at least?

[robpet]

Amcrest Engineering, any update on this (yet another) bug????????

[Bill48105]

Oh I see there are multiple reports of this issue, I just responded to a different one.

Yes the Date header is always +0800 no matter which TZ is selected in System->General Date/time. You can trick it to show right date/time in email by putting the wrong date & time in and adjusting to an incorrect timezone until it DISPLAYS right but then all other places where date/time are shown/used on cam are wrong. Obviously that isn't ideal. Amcrest just needs to read in the TZ set by the user & use that instead of +0800. That seriously can't be a difficult task for their coders.. I mean it's shown as GMT-04:00 when setting it. Worst case strip off 1st 3 chars, replace : with "" and voila you're left with -0400 to be used instead of +0800 lol

Is there an ETA on this Amcrest?
Bill

[Bill48105]

FYI I posted a python proxy script that works as a temp fix until the firmware is updated:
https://amcrest.com/forum/technical-dis ... t1713.html