Try New Technology

I manage a private server that starting in late 2015 started having many of there e-mails for Invoice, Sign-ups, Lost Password Requests, or even support e-mail replies get put directly into the SPAM folder of the @gmail.com recipient with the notice of

“Why is this message in Spam? …” and some more about the content looking like it was spam (I have lost the exact wording).

In the past I had tried to adjust wording in the e-mail templates, but there are only so many ways to say what needed said. We have SPF, DKIM, and DMARC records which were soll perfect, but one thing was causing all of the problems. We also are only, currently, using IPv4 for e-mail. This server uses WHM/cPanel on the back-end and the site is WordPress/WooCommerce.

Cause: The sending server address was the main IP of the private server (X.X.A.X) vs. the static IP of the domains (X.X.C.X). Therefor the sending IPs PTR record didn’t match the domain the e-mail came from.
Fix: Change it so e-mail sent from a domain with a static IP (X.X.C.X) is also sent from that IP (X.X.C.X) vs. the servers default mail IP address (X.X.A.X).

I’ve seen messages about being able to better optimize .jpg files from Google PageSpeed Insights and could never find a way to get the kind of reduction on .jpg file types they talk about. Today I found Compressor.io – optimize and compress your images and photos that did the job perfectly!

I used Lossy to get 60%-80% compression and really shrink the file. They support JPEG, PNG, GIF, and SVG.

I have seen this a few times while supporting some Mac machines (mostly wireless, so I’m not sure if this applies to wired connections) at a local business. I find that after many major updates to the OS that the users report they are unable to login when the login is a Network User. In these cases you need to login as a local user (hopefully you have an admin or roaming account with a local copy of the user profile) and let it finish all the update/questions and once to the home screen, just log out and you should be able to login as your Network User.

NOTE: I first saw this in early 2016 and again just a few days ago. It doesn’t seem to effect every machine, but just randomly.

If you are like me and found that Windows 10 Update 1607 (aka Anniversary) from 2016 broke your webcam, then the below registry setting should fix it. If you don’t know how to use the Registry Editor, please talk with someone who does as doing things wrong in the Windows Registry can cause several problems with your computer!!!!

ALWAYS BACKUP YOU REGISTRY BEFORE MAKING ANY CHANGES!

Because of the recent issues with a Microsoft update to at least Windows 10 (and maybe 8.0/8.1) I am posting the “winsock” fix below…it’s mostly so I can find it online if people ask: