I have just learned that, beginning in 3 days, my employees will no longer be able to receive their work email. Apparently Google is dropping support for Gmail accounts being able to fetch mail from outside accounts. At all. And they announced this change less than 60 days ago. (The announcement was in the basement, stairs, leopard, etc.) What I want to accomplish is simple: When email ...
I think it’s more about making things easy for his employees. His comment is just recognising that they already have personal gmail accounts so he’d like to allow them to use the same client for work email. Data privacy doesn’t seem to be an issue for him.
I do the same thing for my mail - rather than juggle between accounts I can just select from a dropdown which account to send as, and I see all my mail in one inbox.
His setup is complicated because he’s doing additional processing on the incoming mail for his domain - he can’t just hand it over to gmail, he wants to relay it. And because SPF breaks mail relaying he’s been relying on a workaround - he’ll just move on to implement RFC8617 instead now (assuming that gmail supports it - it’s still listed as experimental).
Sure, as a good admin he should certainly implement all industry best practices.
Of course, once he did that he’d still have the same fucking problem as unless he convinced the rest of the world to drop SPF the relayed messages would still be rejected.
I think it’s more about making things easy for his employees. His comment is just recognising that they already have personal gmail accounts so he’d like to allow them to use the same client for work email. Data privacy doesn’t seem to be an issue for him.
I do the same thing for my mail - rather than juggle between accounts I can just select from a dropdown which account to send as, and I see all my mail in one inbox.
His setup is complicated because he’s doing additional processing on the incoming mail for his domain - he can’t just hand it over to gmail, he wants to relay it. And because SPF breaks mail relaying he’s been relying on a workaround - he’ll just move on to implement RFC8617 instead now (assuming that gmail supports it - it’s still listed as experimental).
Honestly if anything he should focus on creating a solution where he can have DKIM active. He has dmarc and SPF, but not DKIM.
Sure, as a good admin he should certainly implement all industry best practices.
Of course, once he did that he’d still have the same fucking problem as unless he convinced the rest of the world to drop SPF the relayed messages would still be rejected.