4.4.8 - November 12, 2016

100.000% on YOUR unique installation? Never. The same as with anything that is mission-critical, always have backups and a way to easily revert to the way you were before before changing. If it is working great now then you have to balance any possible risks or learning curve with what you want to have for new features.
 
When I searched here, I didn't expect this problem to be posted in the release thread so I missed it. I posted mine in the main Blue Iris forum but I spend hours trying to figure this one out. The garbage characters before the "In-Reply-To" field are causing me the same problem. My email client doesn't even recognize the header as an email header: it puts it in the mail body. Gmail bounces it with a "no from field in header" type message because it can't read the "From" field due to the header corruption. Went back to the version posted above and all works fine again.

Thanks for the link above BTW. Lesson learned. I'm going to save versions and install manually from now on.

Mike
 
100.000% on YOUR unique installation? Never. The same as with anything that is mission-critical, always have backups and a way to easily revert to the way you were before before changing. If it is working great now then you have to balance any possible risks or learning curve with what you want to have for new features.

When I searched here, I didn't expect this problem to be posted in the release thread so I missed it. I posted mine in the main Blue Iris forum but I spend hours trying to figure this one out. The garbage characters before the "In-Reply-To" field are causing me the same problem. My email client doesn't even recognize the header as an email header: it puts it in the mail body. Gmail bounces it with a "no from field in header" type message because it can't read the "From" field due to the header corruption. Went back to the version posted above and all works fine again.

Thanks for the link above BTW. Lesson learned. I'm going to save versions and install manually from now on.

Mike

Mike, it has to be your "UNIQUE" installation. :)
 
I am having the same issue with my 'UNIQUE' installation although I am using time warner cable to send the emails. I did notice a new version 4.4.8.1 out which did not fix the problem. THe problem only occurs when the alert is actually sent from a trigger. If I send an email using the test link from the alert it works fine. I am currently back to 4.4.7. I did email support and got the same 'dont care' generic response back about how my email server must be configured incorrectly. I have not tested this out yet but those people who are working are you emailing just one email address or multiples separated by semicolons?
 
Had the same problem with only one address in play on the camera triggers. Had to revert back to 4.4.7. BI obviously messed something up with 4.4.8 and they should stop trying to deflect it onto their customers email setup.

That said, looks like they updated to 4.4.8.2 today. Anyone know if it fixes the problem?
 
Had the same problem with only one address in play on the camera triggers. Had to revert back to 4.4.7. BI obviously messed something up with 4.4.8 and they should stop trying to deflect it onto their customers email setup.

That said, looks like they updated to 4.4.8.2 today. Anyone know if it fixes the problem?
There was only one user who reported that he was told it was an email provider issue..likely because he was one of the first to report it. Try the latest update or revert back. Next time, dont update the immediately after a release is available. This need to update is a disease many users here have. If you follow common sense you wont have this issue. Also note there is no "they" in blue iris. Its developer by a single person.
 
Eh, water under the bridge by now. Obviously the developer is dedicated and will fix it. 4.8.8.3 is out now with mention of email changes so that might fix it. Haven't had time to test it yet. Maybe tomorrow. I'm a developer myself and my opinion is that we've been spoiled: we just take the updates because 99.9% of the time there is never a problem. The fact that one bug (that actually affected reliability for me) made it through in the last ~3 years of me using BI doesn't bother me. :)

Mike
 
  • Like
Reactions: fenderman
4.4.8.1 and newer broke the "Dahua PTZ" ptz profile, causing repeated login failures leading to the account being locked out by the camera. I have let Ken know about this. If this affects you, a temporary solution is to revert to 4.4.8.0 or older.
 
  • Like
Reactions: nayr
I'm one of those people with a compulsion to always update and try out the latest. :p

That said, I always have my backup ready to go, so... no harm, no foul. ;)

This isn't mission critical for me, it's all part of the fun of having what I have.
 
This need to update is a disease many users here have.

the best cure to that disease is an outage on a critical production system that either costs you your job and/or alot of money.
 
  • Like
Reactions: fenderman
I would think that a software update pushed out as a minor release 4.4.7 to a major release 4 would be stable and some form of testing quality control would have been done ahead of time. I understand some bugs might show up in special situations but with a proper testing plan features that are used most, like email triggers should not suffer.
 
Is anyone being able to access the latest version 4.4.8.3 over http? Seems to be broken on our setups.
 
Last edited:
On 4.8.8.3, the email problem is fixed. I also tested the web server and I can access it via both the local and remote IP. It's working for me.

Mike
 
I responded "yes" to the upgrade notification 2 days ago, and BI wont even start on my computer any more. I had to uninstall and reinstall an older version (4.3.5.0) in order for it to run. When I try to start it, I see the "busy circle" for about 1 - 2 seconds, and then nothing happens. I downloaded a version from BI website (4.4.8.3) and installed it and I get the same response, Nothing. Now I don't know exactly which version was working just before this happened.
 
I can access the web page if I go to http://dnsname:port/login.htm/?page=/ if I just use http://dnsname:port I am redirected to http://login.htm/?page=/ which throws a page not found.

The alert triggered emails do appear to be fixed now. Looks like I pulled the trigger back to 4.4.7 earlier to quick as the email did arrive but was delayed during the first test. It arrived after reverting back.

I am no on 4.4.8.3 as I have a workaround for the website.