This is awful, but while I see the huge impact for personal users, I’m not sure I see the business case for his current setup. I’m sure this will inpact business setups, but his specific use case just seems off.
He really buries the lede about why the weird setup of why address@businessdomain.com (to my mind the professional business email) had to be accessible from businessname_address@gmail.com (to my mind a misused personal email) in the first place. It’s down in the comments:
You can’t be serious. Especially for a company he runs, this is silly. Just tell them they have to use the business domain for business email. The whole @gmail.com thing also opens up potential regulatory issues depending on the details of the business.
With his current setup Google is already accessing all his company mail data. I don’t really get his objection to having the MX record directly route to them at this point.
I’m probably missing some big detail, but I don’t get why he has his current setup to begin with.
Zak@lemmy.world 3 weeks 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:
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.
wizardbeard@lemmy.dbzer0.com 3 weeks 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.
Triumph@fedia.io 3 weeks ago
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".
tal@lemmy.today 2 weeks ago
en.wikipedia.org/wiki/Jamie_Zawinski
asret@lemmy.zip 2 weeks ago
It’s not his SPF record.
The forwarding he’s talking about isn’t the same as you hitting forward in your mail client.
SPF only authenticates the first hop from the origin MTA. If you put a relay server in then you either need to disable SPF checking on subsequent MTAs or implement RFC8617. If you don’t then when subsequent MTAs check the original sender’s SPF it will fail because the message came from your relay.
Passerby6497@lemmy.world 2 weeks ago
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
eleitl@lemmy.zip 2 weeks ago
Dude, it’s jwz. You can assume he forgot more than you know.