Not to mention that he's complaining about an SPF record for his own domain. Dude, change your SPF record.
I think this is a case of "knows enough to be dangerous".
Comment on Today in “Google Broke Email”
Zak@lemmy.world 17 hours ago
He’s being a bit whiny here. He was having employees use Gmail as a client for his self-hosted POP mail, which is a niche use case that likely has a brittle implementation and doesn’t make any money for Google. Gmail offers a paid product for this kind of use case, but it won’t integrate with the rest of his (likely custom) automation. He wants to self-host parts of the system and have Google do the messy bits, but he’s not their customer and probably isn’t a very good product either.
He then complains that to solf-host IMAP:
My server is now responsible for storing all of their messages, including all of their spam. It is a vast amount of data. I will have to implement quotas.
It’s 2025 and that’s a silly claim. A 12Tb HDD costs the same as a couple bottles of booze, and it’s not hard to write a script that clears out spam after 30 days. The other complaints are basically UX.
Normally saying a small business owner should self-host IMAP and write scripts would be a bit unreasonable, but this is JWZ.
Not to mention that he's complaining about an SPF record for his own domain. Dude, change your SPF record.
I think this is a case of "knows enough to be dangerous".
I think this is a case of “knows enough to be dangerous”.
en.wikipedia.org/wiki/Jamie_Zawinski
At Netscape, he developed the Unix release of Netscape Navigator 1.0,[4][5] and later, Netscape Mail, the first mail reader (or Usenet reader) to natively support HTML.[6]
This guy should be smart enough to realize he’s complaining about not getting free storage from Google. You can’t just run a business off other people’s infrastructure and expect it to work out without any business agreement or contract. Google Workplace is a thing, and it sounds like this guy is just cheap.
Agreed. I said it elsewhere, but despite his technical knowledge, he appears to be a terrible admin, one that I would only being on as a junior if I was hiring.
I’ve met (and been) this admin before, and a lot of the time it’s because they stepped up, are learning on the job, and don’t know what standard build/tool chains are. But when stuff breaks, it always ends up sounding like this blog post
I have definitely been this admin before, but when shit doesn't go right, I always first went to "Okay, what did I fuck up?"
wizardbeard@lemmy.dbzer0.com 17 hours ago
Also his claim that email chains end up creating an extra copy of an attachment every time? That’s not how most email clients handle attachments. They usually only carry forward in forwards.
And even if his idea is true for his setup somehow, data deduplication at the storage level isn’t particularly difficult to set up, and I would argue is table stakes for any business doing self hosting.
Similar when it comes to data retention policies.