email notify

I used a little python script I found online to send a couple emails from my pc using the non-working-on-the-camera gmail address to another email address and it even works fine. So that email address/port works from other email clients, web mail and now python scripts, just not the camera. Whatever is wrong is camera specific. I'm going to re-consider my router as a cause and look there next even though my isp said they did nothing on their end and I know I didn't change anything. Also, it's suspicious that all of ours (fellow posters) gmails all quit on the same day.
 
I have 2 dahua cameras also with this problem (purchased from Andy).

I'm now using my Hotmail account settings as a work around.
 
Yeah, mine are from Andy too. Can't be my router as the two other stmp servers I tried work fine on the cams, just not google's.
 
Agreed. New gmail account didn’t work even when trying 2 step and generate app specific pw ( Dahua documentation says this won’t work anyway) but either did less secure method. Used my web server account for my website without a problem. My problem began one day I had a contractor working outside the house and there were nonstop emails all day. In my case maybe gmail picked up my NVR as a spam machine and somehow blocked it. I switched to from SSL 465 to TLS 587 and it worked temporarily until recently. Or it could be just highly coincidental because gmail changed security settings.

Google Adds Better Transport Security for Gmail
 
If there is any way you could sniff the traffic when doing an email test - that would explain the cause of the problem.
But unless you have a switch that does port replication, the traffic will not be seen by the PC running the browser.
 
  • Like
Reactions: mikeynags
If there is any way you could sniff the traffic when doing an email test - that would explain the cause of the problem.
But unless you have a switch that does port replication, the traffic will not be seen by the PC running the browser.

I’m not sure how I can do that. I’m open to trying if there’s a way but I’m using a Dahua 5216 NVR and I’m pretty sure I don’t have the hardware required to check. My switch is unmanaged.
 
Without a managed switch that has the ability to duplicate traffic from one port to another port for monitoring, the PC will not see the traffic between the Gmail servers and the NVR or camera.
 
That's regarding G Suite user accounts, and not regular Gmail though.
Yeah - I saw that too. My assumption is that it is the same limit given the fact that the address is the same and you can send to any address. I would think that most of us wouldn't send 2000 messages a day :)

That was the closest article I could find.
 
Yeah - I saw that too. My assumption is that it is the same limit given the fact that the address is the same and you can send to any address. I would think that most of us wouldn't send 2000 messages a day :)

That was the closest article I could find.
I'm in the middle of setting up a G Suite account. Hold my beer...

.

Edit: Too hard. Don't want to mess up my domain and email stuff.
 
If a brand new gmail account doesn’t work I don’t think a gsuite one will either but I might try it later after breakfast as I have one for work.

Tried it, gsuite didn’t work.
 
Last edited:
  • Like
Reactions: Barboots
If there is any way you could sniff the traffic when doing an email test - that would explain the cause of the problem.
But unless you have a switch that does port replication, the traffic will not be seen by the PC running the browser.

You inspired me to improve my network skills, thanks. I set up port mirroring on my switch and ran wireshark to trace some packets. Unfortunately something is not quite right and i'm not seeing what I would expect. I don't see the correct source address of my camera appearing in the list and neither does SMTP appear in the protocol list when I try an email test from the camera's web interface. I'm pretty new to wireshark but it's been a worthwhile exercise.
 
I got a capture by using my windows machine by using and iphone hotspot and enable internet sharing, seems google indeed denies the TLS CLient hello from the Dahua.
After which the session is closed. So either they broke something or they are no longer supporting a certain cipher not present on the dahua.
capture1.png capture2.png