4 ms·
So I did not realize this at first (would have helped if I were, you know, emailed some information about this), but my project was still using a free Postgres
by fireworks 4y ago
So I did not realize this at first (would have helped if I were, you know, emailed some information about this), but my project was still using a free Postgres addon despite being on a paid dyno setup. So that I suppose was nuked along with the general free tier deprecation.
- m00x 4y agoDid they explain why the notifications didn't work?
- fireworks 4y ago"I discussed this with our backend team and upon deeper investigation, we were able to confirm that there was some issue sending the notifications to your email." Nope.
- dboreham 4y agoGuesses 1, 2 and 3 are : their MTA's IP was black listed by a reputable mail hosting provider's spam filtering system (because they send spam).
- joemi 4y agoThat phrasing doesn't rule out an issue on your email server's end, like the email could have bounced. (Though I'm guessing that's unlikely.)
- fireworks 4y agoWould be surprised if that was this case - vanilla GSuite setup.
- joemi 4y agoAs I said, unlikely. But not impossible. My work has a GSuite setup and we've had a few verifiable bounces over the years, though they weren't google's fault but were the fault of glitches at our DNS provider (we don't use google for DNS).