Email is, fundamentally, a broken technology I feel I can no longer rely on.
Just today, I tried to send a reply to someone with a gmail address and gmail bounced it because some dns record somewhere lacked some now apparently essential magic words.
Later, I discovered the (completely separate) email account of our build bot had been deactivated by our provider because it was *checks notes* sending too many emails about builds...
:pint:
@sarahjamielewis that's a long story about email and how Google (and the other bigs) have seized control. I still run my own server but, yes, sometimes can get challenging.
@maddler @sarahjamielewis I have run my own mailserver for literal decades and email delivery is all but impossible these days, what with gmail and office365 shutting out the small players in the name of spam prevention.
Just last month my Google workspace domain was being spambinned because I used an s3 bucket to load logos in my signature.
Broken. Totally broken.
@iamjameshunt @sarahjamielewis Yes, and a lot of times the information on how to get delisted are non existent or useless. I had same issue as Sarah, with google complaining about a missing DNS config which was 100% there.
I think there was an interesting post about the shift of email toward big providers and what that meant for smaller/selfhosted instances, from a "social" perspective. I'll try to find it.
@maddler @sarahjamielewis even with proper SPF, DKIM, and DMARC, you can’t reliably send to the big providers because of volume.
That’s right: if you only average a few emails sent per day, Google can’t be sure you’re NOT a spammer, so they bin you.
You cannot make this stuff up.
@iamjameshunt @sarahjamielewis yep, I had everything 100% configured right, still... getting bounced for that...