EMail Alert not working

This is absolutely ridiculous! As a business owner, and one that has provided the service of installing this system into TWO other businesses in town, you better fix this issue or else I’m screwed out of $1000+ since I will soon have to refund their money, and spend money out of my own pocket to have my guys now take out these systems. And will most likely lose all business from them after this whole ordeal.

This is not a hard problem to fix! I can fix this myself within a few minutes if I had access. My business is a computer store, I’m a computer technician, with programming and hardware certifications.

As of right now, there are units available on Amazon, Newegg and I’m sure many other sites that still offer email notifications. In fact, even the zmodo site shows systems that offer email notification. This is false advertising and against the law.

I have to agree, that something like this is VERY easy to fix. I just don’t understand why it isn’t fixed. Nothing has changed as far as security for google, yahoo, etc. for quite a few months. Nothing magically happened other than something went wrong at the zmodo end.

Using Zviewer I can add the IPC cameras from my ZP-BE-14S. I can setup my yahoo account and it sends a test email successfully. The cameras sense motion correctly since I see an orange bar in the timeline. So why doesn’t it send an email when there is motion, only when performing a test.

That indicates the issue is not some email setting but rather something at my end. Suggestion?

You are incorrect, something did happen with the email providers. They updated their SMTP security requirements, and as a result, the email requests that were working previously, are no longer accepted by the servers, given their new security requirements.

The reason the test send from ZViewer works, and the send from the device itself does not work, is because the Zviewer software was developed in line with the new security requirements, so it is able to send, where the system is not.

The emails still send through servers with the older, outdated security profiles, unfortunately, most people do not have access to SMTP servers with the outdated security requirements.

1 Like


Your answer almost makes sense to me although something doesn’t sit quite right. However, since the real issue is getting emails working, what is being done about that?

If I leave Zviewer running all the time and recording to a PC HDD, can it send email notifications instead of the zmodo box? Are there other possibilities that might work?

The Zviewer software doesn’t detect motion, so it cannot send the alerts on its own. Currently there is not a solution to the email alerts not functioning beyond locating a server that will allow the older authentication types.


soory, I still have some doubts regarding the mail server protocol conspiration. Can you specify which kind of protocol change of all mail servers world wide has broken zmodos mail functionality?

For me the easiest fix would be to get rid of the stupid truncation of the “mail from”-field. Send the full user name instead of truncating @domain.tld - this is what most servers will accept. If you want to solve the issue correctly, just add a seperate user name field, which can be used for authentication.

And for sure get rid of the erroneous truncation of the base64 encoded password.

After that, everything will work as expected. For a experienced programmer both changes shouldn’t take more than one hour including testing. So what’s the problem implementing such a fix?


I got mine working by switching to my account. It may be that other cable providers also have allowances for legacy systems.

Their instructions call for a secure connection with port 465 like most others but they also allow for unsecure using port 587. It worked.

However the screenshot is useless. Any suggestions?

The update was to the SMTP request authentication requirements.
Below is a link to the Google forum thread where the issue is discussed. A Google representative explains the changes that they have made to the SMTP authentication requirements.!msg/gmail/2tK2fR7yW-k/CT5u-VBpgp8J

That almost looks like the motion was triggered by a video stream error. Could you forward the email over to with your username and attn:Patty as the subject line?


thanks for the information you’ve provided. But sorry, this change you’re referecning is a change in the MAIL FROM

Yes, in the past week we’ve rolled out a change which enforced validation of the MAIL FROM argument to be a valid RFC 5321 email address.

We’re experiencing authentication issues - MAIL FROM verification happens two or three steps after the authentication.

The issue ZMODO has, it strips the domain name during the authentication process. So imagine your email is the NVR just sends patty as user name. But as your email provider might host hundreds or thousands of other domain there might be also a user and/or So the mail providor needs the complete address to be able to find/match the account. So unfortunately your just delivering half of the required information.


Done. I also asked a little more about the setup. thanks.

MAIL FROM is a portion of the SMTP request. The entire communication is an SMTP request.

The change that Google made is in the MAIL FROM portion of the SMTP request authentication requirements.

The portion of our request that does not meet their authentication requirements is in the MAIL FROM portion of the SMTP request.

I’m not sure where what you are saying is different from what I have been saying.


Please read carefully, I will try to use your notation to explain what I mean.

As you stated the SMTP requests consists of several portions. I’ll use the following short description as a reference ( ).

  1. Open connection
  2. Send EHLO
  3. Send AUTH LOGIN to start authentication process
  4. Send User name (Base64 encoded)
  5. Send Password (Base64 encoded)
  6. Send Mail From - Sender Address
  7. Send RCPT To - Recipeint Adresses
  8. Send Data - email itself
  9. Commit Mail and Quit

So, what google changed is affecting step 6. At that step they’re expecting an existing mail address - if it’s not delivered the mail is refused. BUT, at least for me, the issue that I see already occurs in step 4 and step 5. In step 4 the NVR doesn’t send the complete user name, in step 5 the base64 encoded password is truncated at approx. 14 characters. Both take place BEFORE the Mail From verification, so it has absolutely nothing to do with it!!

Again, what I checked through dumping the mail communication is that in step 4 you’re taking the data which are entered in the mail from field of the mail setup and truncatiung everything including and behind the @-sign. So will result in patty which you will encode via base 64 as send over as a user name. This is not sufficient as most mail provider (including google) require the complete mail address there as well.

Single providers are working with unique IDs instead of real names. They will ensure that this name is unique through all domains they’re hosting (or they’re just hosting one single domain)., which was named a while ago is one of those. They say:

> 9.Under Logon Information, enter: ◦User Name: Enter your Optimum ID. (Your Optimum ID is the part of your e-mail address to the left of the "@" sign, for example: jsmith.)

In comparison, this is what google requires:

> Your full Gmail or Google Apps email address required for authentication 

So truncating the user name might work for single providers but is not a general solution. So pleas read my posts from before how to solve.


Yes, we already know why the SMTP request is failing.
We also know what the development team would need to change to fix it.
This is not new information.

so patty…is the “email/snapshot” feature going to be returned to us the user at some time or is it gone forever ? this will impact my customers/friends/family as well as future sales/installs…

The discussion on whether or not there will be a fix for the Email alerts implemented through a future firmware update is still ongoing. An official decision has not yet been made.

when i contacted zmodo via twitter, they said they are phasing out email alerts and we should just use the app to view alerts.
My problem with this is, what happens when your server goes down? I used to also get far more email alerts than app alerts, I don’t know why but the app doesn’t log half as many movements as the email system did.
why don’t you just open up your software so that someone who has the ability can fix this, as your development team clearly can’t.

Unfortunately that idea has already been rejected previously.

Well said. I 100% agree! I’m afraid I can’t recommend this product to others until that key feature is fixed.