Dahua IPC-EBW81200 mail timestamp issue (reception date 6 hours behind ...)

fa355115

Getting the hang of it
Joined
Oct 7, 2016
Messages
204
Reaction score
18
Hi there,

I just got a Dahua IPC-EBW81200 and configured the SMTP to send notifications by mail, but although mails are sent straight after trigger when they appear in the inbox they do with 6 hours difference (reception date).
Initially I thought the GMT (timezone) parameter was not taken into account (not saved), because the time was not changing when I was changing the GMT (then Save then refresh) ... then I figured out the GMT was taken into account ONLY when the NTP is checked.

Still, it looks like whatever GMT you set, the one taken in the mail notifications is GMT +8:00, and as I am in a GMT +2:00 timzone, all mails I receive are displayed with a 6 hours differnce ...

Anyone experiencing the same issue ?

Many thanks !
 

fa355115

Getting the hang of it
Joined
Oct 7, 2016
Messages
204
Reaction score
18
I do not understand anymore ... I just tried sending mails from the GMAIL smtp as well ...and there no issues ... reception hour is correct
Passing through proximus SMTP, reception hour is incorrect :


SMTP GMAIL on the camera :




mail received with correct timestamp :




SMTP proximus on the camera :



... mail received with incorret timestamp :




I do not understand ...why passing through proximus as sender the reception hour is incorect ???
 
Last edited by a moderator:

nayr

IPCT Contributor
Joined
Jul 16, 2014
Messages
9,329
Reaction score
5,325
Location
Denver, CO
because its modifying the time in the mail header to its local time, camera is perfectly fine.. your mail server is the culprit.
 

fa355115

Getting the hang of it
Joined
Oct 7, 2016
Messages
204
Reaction score
18
Sorry I do not get you ....
proximus is my official internet provider .... and I only have the 6 hours issue with the camera ...

do you mean gmail is working fine because it modifies the header mail header to its local time ?
But then it means the mail header the camera send i s incorrect ??
 

nayr

IPCT Contributor
Joined
Jul 16, 2014
Messages
9,329
Reaction score
5,325
Location
Denver, CO
no im meaning your internet provider is modifying the mail headers when its relaying it out, and gmail is not.

the mail header is correct as proven by when you used gmail.

proximus is the problem here, not gmail, not dahua.
 

fa355115

Getting the hang of it
Joined
Oct 7, 2016
Messages
204
Reaction score
18
I try to understand you ... but why do I only have the issue with mails sent by the Dahua Camera ?
Why do you say proximus is modfying the mail header ? I mean see the source of the mail se via proximus :

Code:
Return-Path: <Dahua@skynet.be>
Received: from mailsec111.isp.belgacom.be ([195.xxx.20.xxx])
          by mailfep017.skynet.be
          (InterMail vM.8.04.03.21.1 201-2389-100-165-100-20151028)
          with ESMTP
          id <20161007193851.AKA7128.mailfep017.skynet.be@mailsec111.isp.belgacom.be>
          for <xxx@skynet.be>; Fri, 7 Oct 2016 21:38:51 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
  d=skynet.be; i=@skynet.be; q=dns/txt; s=securemail;
  t=1475869131; x=1507405131;
  h=date:from:to:subject:mime-version:message-id;
  bh=NpN79r0YF2wk0R5grMyf2lHQoN5o5YZl6ojM4L4U6L4=;
  b=WoDioN20S/sToBSIiugUtLh8jyRcjVIBC+CnsBVACHy+MukguY9TiGn3
   zuITPOStpK0wa9UfHP4Gxg6ZJJ7DMg==;
Message-Id: <0c25d5$d5n9dh@relay.proximus.be>
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2BEQgC8+PdX/2+Ns1tcHAEBFgEBBQEBB?=
 =?us-ascii?q?jqCNR8cAQEBAQEeSXunEwGNEYRIgguGGgQCHQGBYjsSAQIBAQEBAQEBXidBDoQ?=
 =?us-ascii?q?8Ghk7RQIENxMRiGejQ49snRU1gjgPgkwFjjp3ik6RUwGOG0mMLoN/JQEuhTIxg?=
 =?us-ascii?q?WGGYgECAw?=
Received: from 111.141-179-91.adsl-dyn.isp.belgacom.be (HELO localhost_GNT) (xxx.179.xxx.111])
  by relay.proximus.be with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Oct 2016 21:38:50 +0200
Date: Fri, 07 Oct 16 21:38:50 +0800
From: <Dahua@skynet.be>
To: <xxx@skynet.be>
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

QWxhcm0gRXZlbnQ6IE1haWxfVGVzdA0KQWxhcm0gSW5wdXQgQ2hhbm5lbDogMQ0KQWxhcm0gU3Rh
cnQgVGltZShEL00vWSBIOk06Uyk6IDA3LzEwLzIwMTYgMjE6Mzg6NTANCkFsYXJtIERldmljZSBO
YW1lOiBJUEMtRUJXODEyMDANCkFsYXJtIE5hbWU6IA0KSVAgQWRkcmVzczogMTkyLjE2OC4xLjUN
Cg==



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

... on top see the +8:00 in the mail header ? Where is that coming from ?
 

nayr

IPCT Contributor
Joined
Jul 16, 2014
Messages
9,329
Reaction score
5,325
Location
Denver, CO
yeah its telling it +8h, which is 6h advance of your +2h.. if you look at your gmail header it wont have that.

for some reason proximus does not like the email.. a firmware update wont do anything for you.
 

fa355115

Getting the hang of it
Joined
Oct 7, 2016
Messages
204
Reaction score
18
here is the gmail source code :

Code:
Return-Path: <xxx@gmail.com>
Received: from mailgate127.isp.belgacom.be ([xxx.xxx.20.92])
          by mailfep015.skynet.be
          (InterMail vM.8.04.03.21.1 201-2389-100-165-100-20151028)
          with ESMTP
          id <20161007191856.YXRA7039.mailfep015.skynet.be@mailgate127.isp.belgacom.be>
          for <xxx@skynet.be>; Fri, 7 Oct 2016 21:18:56 +0200
Authentication-Results: mx101.skynet.be; spf=Pass smtp.mailfrom=xxx@gmail.com; dkim=pass (signature verified) header.i=@gmail.com; dmarc=pass (p=none dis=none) d=gmail.com
X-IPAS-Result: =?us-ascii?q?A0DdjAAq8vdXhilSfUpcHhgHgzABAQEBAYFxpFskBB6GdgJ?=
 =?us-ascii?q?cg3UMgyCESYIKCIYYHQGBYz4OAQIBAQEBAQEBEwEBAQgLCwkZL0EMAYQsERoDA?=
 =?us-ascii?q?RseAxJHAgQhEQEFARERNYgTAQMXBKM2ggiBMj4yi0KBa4JfBYNrChknDVODEQE?=
 =?us-ascii?q?BAQcBAQEBGwMGEI9fNYI4KIIzBYEhAY0YeIpDCAEBgSaQLQGIAoYZSYwugj0xg?=
 =?us-ascii?q?RE4BoNdgX5SgXiGFwEBAQ?=
Received: from mail-wm0-f41.google.com ([74.125.82.41])
  by mx101.skynet.be with ESMTP/TLS/AES128-GCM-SHA256; 07 Oct 2016 21:18:56 +0200
Received: by mail-wm0-f41.google.com with SMTP id f193so50005281wmg.0
        for <xxx@skynet.be>; Fri, 07 Oct 2016 12:18:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=message-id:date:from:to:subject:mime-version;
        bh=CRBfnBLbshfWlEysSPakr1vLD04EYiJWRpJ/BfNwyq8=;
        b=x7nBsaYa0oC70lH273/m4eWDHJWXllBgVkOxpD4VOjmxJRzjJ7/xkmH6VsVz2IZitW
         0y4Cer2h5qtIsL4LSnWuK51dJ58Z/TlXjUbRfVa9L2brjCYFbax+8QdpzeBjJ4TRGahX
         F5iP1iUOjBZ32An0Vh1ctfdFpc0nLDKUQ0W07FyGVBiahrbSvKfmnzLyJofVrr4f3yte
         3JjBnL4n7vzClCOtuIee7A6JJv2+zpZiNUcahJYjMwfgYUUpLKbCb470nMeKtN95OEs0
         LsInPcFcKS/AVr88LpBZYUXYQ4DZIWkSMN9UMZ4FvpIb1TCmFfuT0vdCnmic+566UeyE
         2nSQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:message-id:date:from:to:subject:mime-version;
        bh=CRBfnBLbshfWlEysSPakr1vLD04EYiJWRpJ/BfNwyq8=;
        b=kZPHp5f8P5nSRdHziEfMz2hAm6U+34tdbTC3BrRl4nvcmrBho9RUk6ANLzLiuDz7h/
         OYRowLaeiswhKFHa9M2YX9p0ybqkuKzSG5xIirEr9U5LKXnjWxD/E0M2Pwp9kGElk++2
         wHyKkr1MPnzuVK3dNklt/xf5V5eZvBDaIPydudDtMOO/TmNZNrk0J7OoEnEzNVwTHaOj
         NI1NEjeJDUcYaB8DvLCVBokEsfSITHV7raMJp0NjTjeWtnVlUh92hjLSU7b+CM0ILD9E
         qeY5ppR4sJsiIpDDG+VFDGjHV0/9U6uL/jcxHcL2Dh7dKbs7svEUXX9uRSWvtOHVHbUC
         8D/g==
X-Gm-Message-State: AA6/9Rkn/LJ8tW53/VZ/LIAluH3A0xLdSluDkBnD2O6BKgiGMrVTNDS6FXrn59J5iBCULg==
X-Received: by 10.194.51.37 with SMTP id h5mr17558930wjo.171.1475867935973;
        Fri, 07 Oct 2016 12:18:55 -0700 (PDT)
Return-Path: <xxx@gmail.com>
Received: from localhost_GNT ([xxx.179.xxx.111])
        by smtp.gmail.com with ESMTPSA id e2sm6568094wjw.14.2016.10.07.12.18.55
        for <xxx@skynet.be>
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Fri, 07 Oct 2016 12:18:55 -0700 (PDT)
Message-ID: <57f7f51f.c24bc20a.94335.5db0@mx.google.com>
Date: Fri, 07 Oct 2016 12:18:55 -0700 (PDT)
X-Google-Original-Date: Fri, 07 Oct 16 21:18:55 +0800
From: xxx@gmail.com
X-Google-Original-From: <Dahua@skynet.be>
To: <xxx@skynet.be>
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

QWxhcm0gRXZlbnQ6IE1haWxfVGVzdA0KQWxhcm0gSW5wdXQgQ2hhbm5lbDogMQ0KQWxhcm0gU3Rh
cnQgVGltZShEL00vWSBIOk06Uyk6IDA3LzEwLzIwMTYgMjE6MTg6NTQNCkFsYXJtIERldmljZSBO
YW1lOiBJUEMtRUJXODEyMDANCkFsYXJtIE5hbWU6IA0KSVAgQWRkcmVzczogMTkyLjE2OC4xLjUN
Cg==



--======DAHUA_TECH======--
as you can see there is also the +8:00... according me this is incorrect ... where the hell is this coming from ???
 

fa355115

Getting the hang of it
Joined
Oct 7, 2016
Messages
204
Reaction score
18
I have in the mean time tested with a NAS set to GMT+5:00 sending notifications as well .... here again the time is CORRECTLY displayed, although in the mail source code you see the +5:00 mentioned :

Code:
Return-Path: <Synology-DS211@skynet.be>
Received: from mailrelay116.isp.belgacom.be ([xxx.238.20.143])
          by mailfep012.skynet.be
          (InterMail vM.8.04.03.21.1 201-2389-100-165-100-20151028)
          with ESMTP
          id <20161008122026.IBVB7155.mailfep012.skynet.be@mailrelay116.isp.belgacom.be>
          for <xx@skynet.be>; Sat, 8 Oct 2016 14:20:26 +0200
Message-Id: <f88ce9$36g7a8@relay.skynet.be>
X-Belgacom-Dynamic: yes
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2BGEABO5PhX/2+Ns1tcHAEBBAEBCgEBg?=
 =?us-ascii?q?zwBAQEBAR1JDl0QD40zmU4IAYMugWeDXnQMIQOCfYEsNYJnggsihEpVWQSBfTk?=
 =?us-ascii?q?UAQIBAQEBAQEBXidBEIQ6DwEZCh0eFgcCJgInFBMRiF4Jon6PbIVRiFuEOnyIb?=
 =?us-ascii?q?hEBBmKCOA+CTAWBIQGOD4pECAEBAYYmhQiDb4I3ARVOhBmJHQKJC4drHjaCZAE?=
 =?us-ascii?q?BAQcBAQEBAQE9gXs3NYFhg3qCIAECAw?=
Received: from 111.141-179-91.adsl-dyn.isp.belgacom.be (HELO DiskStation) ([91.9.1x1.11])
  by relay.skynet.be with SMTP; 08 Oct 2016 14:20:13 +0200
Date: Sat, 08 Oct 2016 17:20:13 +0500
From: "Synology-DS211@skynet.be" <Synology-DS211@skynet.be>
To: <xx@skynet.be>
Subject: =?UTF-8?B?TkFTIC0gIFRlc3QgTWVzc2FnZSBmcm9tIERpc2tTdGF0aW9u?=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

Dear User,

Congratulations! You have successfully set up the email notification on DiskStation.
For further system configurations, please visit http://192.168.1.2:5000/, http://xxx.be:5000/.
(If you cannot connect to the server, please contact the administrator.)

Sincerely,
Synology DiskStation
 

nayr

IPCT Contributor
Joined
Jul 16, 2014
Messages
9,329
Reaction score
5,325
Location
Denver, CO
why dont you just signup for a gmail account just for your surveillance system, then just use gmail servers and get this over with... they are the biggest email provider in the world now, going to be the quickest and most reliable just by nature.
 

fa355115

Getting the hang of it
Joined
Oct 7, 2016
Messages
204
Reaction score
18
Sure I could use the GMAIL SMTP and it will work ... but by nature I want to understand what is wrong ...
If i is a "bu"on the Camera I wn to know ....
 

fenderman

Staff member
Joined
Mar 9, 2014
Messages
36,897
Reaction score
21,250
Sure I could use the GMAIL SMTP and it will work ... but by nature I want to understand what is wrong ...
If i is a "bu"on the Camera I wn to know ....
It'd not the camera as it's been explained to you and evident because Gmail works...
 

fa355115

Getting the hang of it
Joined
Oct 7, 2016
Messages
204
Reaction score
18
no, sorry not so evident ...
All my other ails works with Pooximus.
Ieven tried cofiguring a NAS with a GMT +5:00 and here a well the displayed reeption hour is correct !

If I set my camera on GMT +2:00 .. why the hell is she continuing to send mails mentioning +8:00 in their source code ??
I know using GMAIL SMTP it will display correct timesamp but this is maybe GMAIL simply taking the current date for reception !!!

Code:
Received: from 111.141-179-91.adsl-dyn.isp.belgacom.be (HELO localhost_GNT) ([91.1xxx.xxx.112])
  by relay.proximus.be with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Oct 2016 14:49:05 +0200
Date: Sat, 08 Oct 16 14:49:06 +0800
From: <Dahua@ced.be>
To: <xxx@skynet.be>
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

QWxhcm0gRXZlbnQ6IE1haWxfVGVzdA0KQWxhcm0gSW5wdXQgQ2hhbm5lbDogMQ0KQWxhcm0gU3Rh
cnQgVGltZShEL00vWSBIOk06Uyk6IDA4LzEwLzIwMTYgMTQ6NDk6MDUNCkFsYXJtIERldmljZSBO
YW1lOiBJUEMtRUJXODEyMDANCkFsYXJtIE5hbWU6IA0KSVAgQWRkcmVzczogMTkyLjE2OC4xLjUN
Cg==



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

fenderman

Staff member
Joined
Mar 9, 2014
Messages
36,897
Reaction score
21,250
This will end poorly, with a firmware update attempt and a bricked/chinese camera...
 

nayr

IPCT Contributor
Joined
Jul 16, 2014
Messages
9,329
Reaction score
5,325
Location
Denver, CO
its not a critical bug if you have a work around, and you do.. so move on and leave your firmware alone.
 

fa355115

Getting the hang of it
Joined
Oct 7, 2016
Messages
204
Reaction score
18
Guys I have done some more testing and I have also contacted the Thunderbird dvlp team to understand how it works.
From my investigaion it really shows as a bug on the Dahua camera .... in fact the camera is not using its defined timezone (for example +5:00) when sending mail, but instead +8:00 as default !!
See ...

So bottom line the issue is that the camera, if I understand correctly, is not applying the correct timezone and even though the timezone is set to GMT +5:00, the camera is sending the mail with a GMT +8:00 ...

I did a test again from :
a NAS set to GMT +5:00 and clock set to 21:30:32
the camera set to GMT +5:00 and clock set to 21:30:32

... so both defined with the same timezone and clock, and send a mail test using Skynet SMTP.


'''The NAS mail source code shows :'''
Return-Path: <Synology-DS211@skynet.be>
Received: from mailrelay103.isp.belgacom.be ([195.xxx.20.xxx])
by mailfep012.skynet.be
(InterMail vM.8.04.03.21.1 201-2389-100-165-100-20151028)
with ESMTP
id <20161009163019.RXWO7155.mailfep012.skynet.be@mailrelay103.isp.belgacom.be>
for <xxx@skynet.be>; '''Sun, 9 Oct 2016 18:30:19 +0200'''
[...]
Received: from 111.141-179-91.adsl-dyn.isp.belgacom.be (HELO DiskStation) ([91.xxx.141.xxx])
by relay.skynet.be with SMTP; 09 Oct 2016 18:30:19 +0200
Date: '''Sun, 09 Oct 2016 21:30:19 +0500'''
From: "Synology-DS211@skynet.be" <Synology-DS211@skynet.be>
To: <xxx@skynet.be>
Subject: =?UTF-8?B?TkFTIC0gIFRlc3QgTWVzc2FnZSBmcm9tIERpc2tTdGF0aW9u?=
[...]


'''The Camera mail source code shows :'''
Return-Path: <Dahua@ced.be>
Received: from mailsec104.isp.belgacom.be ([195.xxx.20.xxx])
by mailfep012.skynet.be
(InterMail vM.8.04.03.21.1 201-2389-100-165-100-20151028)
with ESMTP
id <20161009163017.RXDN7155.mailfep012.skynet.be@mailsec104.isp.belgacom.be>
for <xxx@skynet.be>; '''Sun, 9 Oct 2016 18:30:17 +0200'''
[...]
Received: from 111.141-179-91.adsl-dyn.isp.belgacom.be (HELO localhost_GNT) ([91.xxx.141.xxx])
by relay.proximus.be with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Oct 2016 18:30:17 +0200
'''Date: Sun, 09 Oct 16 21:30:17 +0800'''
From: <Dahua@ced.be>
To: <xxx@skynet.be>
Subject: =?UTF-8?B?TWFpbF9UZXN0?=
[...]


So I understand correctly''' the issue is '''that the camera, although set to a GMT+5:00 timezone, use a GMT+8:00 ...

... Thunderbird displays a received time of 18:30 for the mail sent my the NAS and 15:30 for the mail sent by the camera.

Therefore the Camera is not using the defined GMT for the mails she is sending.
I will report this as a bug to Dahua.
 

fa355115

Getting the hang of it
Joined
Oct 7, 2016
Messages
204
Reaction score
18
why lol ?
Do you think it is not a bug or do you think Dahua will not care ?
 

fenderman

Staff member
Joined
Mar 9, 2014
Messages
36,897
Reaction score
21,250
why lol ?
Do you think it is not a bug or do you think Dahua will not care ?
Its a terrible bug, dahua will get their engineers on it as soon as they secure their cameras properly..
 

TVT73

Pulling my weight
Joined
Aug 29, 2016
Messages
406
Reaction score
108
Location
Germany
Hello together, i can agree that this bug is also on 4431 ones. I postet it also as a bug. And i am sure, that this belongs only to the newer series. Because with my other setups and the older 4421er i had never this behavior! with the same mail providers and so one.
I also send a bug report to dahua, together with my dealer, but nothing happend till now. I didn´t know whats wrong there, but it a really ugly bug.
 
Top