I have run a private mailserver for over 20 years, and I have the same problem. There's no telling what Google will let through. I have a second account at a medium-sized email provider, basically paying them for access to the email deliverability cartel.
We need a new message protocol
Google Is Eating Our Mail
61–70 of 720 posts
Re: Google Is Eating Our Mail
#62Earlier quoted context omitted.
They don't even have to be doing it deliberately; as you say, the lack of incentives to fix such issues will cause a gradual evolution in that direction.
I feel like as they leave more and more up to the algorithms, we suffer. I've been having this ever increasing in frequency issue where Gmail Search just doesn't working. Not that it doesn't return search results but rather that it returns what I know to be incorrect results. I have an email with some account information that I access a couple times a year at most but will consistently need at least once a year. Just…
Seems like it ends up working somewhat like China's social credit policy, but without specific intent. As long as you always conform enough to fall into the normal area of the algorithm you're good, but get off towards one edge for any reason and you quietly get [effectively] booted off the 'net.
Re: Google Is Eating Our Mail
#63Google has no incentive to fix these kinds of problems. It's big enough that when someone complains that a message sent wasn't received, the intended recipient will say, "I never have problems with my Gmail account. It must be you." And the sender has to switch to Gmail to reliably communicate with the outside world. I wish this was just paranoia, but we've seen multiple discussions on HN about Google programs and po…
Define 'people'. We're already there IMO. The kids today don't have any particular understanding of what the internet is and how it works. They view it through walled gardens via the app store.
Re: Google Is Eating Our Mail
#64Re: Google Is Eating Our Mail
#65In the end I just gave up and started using mailgun as a relay.
Re: Google Is Eating Our Mail
#66Re: Google Is Eating Our Mail
#67Google has no incentive to fix these kinds of problems. It's big enough that when someone complains that a message sent wasn't received, the intended recipient will say, "I never have problems with my Gmail account. It must be you." And the sender has to switch to Gmail to reliably communicate with the outside world. I wish this was just paranoia, but we've seen multiple discussions on HN about Google programs and po…
Whatever lead to Microsoft being sued for pushing Internet Explorer in Europe and whatnot? Shouldn’t that kick in already for at least some of the recent Google bullshit?
Re: Google Is Eating Our Mail
#68A couple of things that regularly seems to trigger false positives in spam algorithms:
- no or misconfigured SPF and/or DKIM
- no or misconfigured reverse-DNS
- automatically included footer texts (confidentiality, copyright, safe a tree don't print, etc)
- regular automatic replies from the domain (such as out of office notifications)
- the use of embedded images (logos, human signatures, etc)
We sometimes joke that these triggers were built in by the algorithm developers as a means of punishing those who litter their email with pointless texts and images.
Re: Google Is Eating Our Mail
#69Add another perspective to this. Once I updated my phone, and google would not accept new google Authenticator codes after set up. Locked out of 15 years of email.
I had a fright last time I changed phones. After restoring my backup onto the new phone, I was about to wipe the old one; I did a final pass through my apps just in case... and saw that Google Authenticator configuration did not carry over to the new phone (which makes sens from a security perspective but is a PITA to manage). I had to re-enroll my device with all the services on which I use MFA. After this episode I…
The procedures for doing so seemed to be unnecessarily complicated and difficult to find when starting, ironically, from a Google search on another device.
Worse, the security policies seemed to be fundamentally flawed, because they kept insisting on some form of authentication based on a trusted device when the purpose of the transaction was to notify them that the trusted device had been stolen.
There has been an unhealthy trend recently of assuming that everyone has a mobile phone and that communications to that phone/number are a good method of authentication, without adequate thought to what happens if the physical device and/or the associated phone number are compromised, or to whether protocols like SMS are really suitable for this sort of application. And some of the really important things, like banks and government services and email providers (which are in practice a gateway to everything else you do online) are often among the worst offenders. I don't know what to do about this, but certainly raising awareness of this kind of problem would be a good start.