Chrome 68 will mark all HTTP sites as “not secure”

Re:Chrome 68 will mark all HTTP sites as “not secure” by trav4225 on Thursday February 08, 2018 @03:23PM (#16335277)

Probably the dozens of various DNS, DKIM, SPF, SMTP behavior config, non-consumer-IP, etc., etc. boxes that must be ticked just right in order to not be considered a spammer these days. It's very difficult to get it all correct enough to keep a significant portion of the email sent through your SMTP site from being considered spam by mainstream email providers such as Google.

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by newman314 on Thursday February 08, 2018 @07:59PM (#16337028)

I agree that for most people, that's probably an exhausting list to go through.

I'm a fan of Hardenize. I like using that site to help people understand what needs to be done.

https://www.hardenize.com

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by trav4225 on Friday February 09, 2018 @03:29PM (#16343577)

Interesting. Thanks for the tip!

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by wpietri on Thursday February 08, 2018 @08:21PM (#16337138)

I can confirm that this is a giant pain in the ass. I use a non-standard address scheme (instead of the plus character as a tagged-address delimiter, I use the qmail approach, a dash character), so I can't easily move my domain to GMail. I occasionally end up in spam folders for reasons I can't discern, despite years of puzzling and discussion with a number of experts.

The especially frustrating thing is that there's no way to find out why you've been binned. Even my friends who work at Google can't find out for me, much less get me whitelisted.

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by Silhouette on Thursday February 08, 2018 @09:35PM (#16337472)

It's very difficult to get it all correct enough to keep a significant portion of the email sent through your SMTP site from being considered spam by mainstream email providers such as Google.

This doesn't change the problems of unreliable email because mail services are too aggressive, unfortunately.

We recently got a bounced mail (not dumped in a spam folder, actively rejected) from a major university, telling us that the message looked like unsolicited bulk mail. The message was sent directly to a specific single customer in response to a purchase they had just made, contained information that we were required by law to provide to them, and was sent from a reputable host with things like SPF properly set up. That is simply broken, and it is 100% the fault of the mail service admins at the university.

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by jacquesm on Thursday February 08, 2018 @10:46PM (#16337754)

If it was just the occasional small site it would not be such a problem, but even iCloud (Apple) and Outlook (Microsoft) get it wrong with some regularity from hosts that check all the right boxes.

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by trav4225 on Friday February 09, 2018 @03:27PM (#16343566)

Yeah, agreed: it's all pretty broken, unfortunately.

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by agentdrtran on Thursday February 08, 2018 @05:23PM (#16336136)

yeah, but all of these things exist becuase of the sheer amount of spam that gets sent to people.

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by amelius on Thursday February 08, 2018 @05:34PM (#16336202)

And it still doesn't work as desired.

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by Avamander on Saturday February 10, 2018 @08:32PM (#16350660)

Gmail seems to filter all spam of mine though.

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by gsich on Thursday February 08, 2018 @08:26PM (#16337165)

It's not hard.

[ Parent | on HN ]