Google Is Eating Our Mail

Re:Google Is Eating Our Mail by Arnt on Friday April 26, 2019 @09:30AM (#19757214)

I too self-host and have done for decades. When I had a problem that may perhaps have been like this, Google disabled the relevant part of them spam filter and made an issue in some internal tracker. I write "Perhaps" because my report was a lot more specific.

Google sells mail+spam filtering+more as a product, with a seven-digit number of paying customers, each of which pay per month and user. What more incentive could they have?

[ Parent | on HN ]

Re:Google Is Eating Our Mail by CyberShadow on Friday April 26, 2019 @10:17AM (#19757736)

> I write "Perhaps" because my report was a lot more specific.

How did you even get your report to be read by an engineer at Google? This seems impossible unless you have some kind of business connection.

[ Parent | on HN ]

Re:Google Is Eating Our Mail by Arnt on Monday April 29, 2019 @09:35AM (#19778196)

That bit is easier for me than for you, perhaps, since gmail implements about four RFCs I've written ;)

That bit isn't the MSB, though. The MSB is that they do care about fixing interop problems with everyone, they just don't read mail from randoms. I think they assume is that if a problem is their fault it will show up on their monitoring graphs, and watch their error graphs instead of their postmaster inbox.

[ Parent | on HN ]