“Has anyone started having discussions with their CIO/CEO about moving back to an in-house mail server? I advocate for it” cbronline.com/opinion/microsof Heh heh. Yup.

@lightweight Mail servers are the last thing I think should be in house. Having a badly configured mail server for a few days can lead to years of mail delivery problems.
(This is advocating for contracting someone to run it for you, not to stick with MS)

@lightweight note my experience is in the small end of town.

@LovesTha sure. I agree, in general, although, to be fair, running a mailserver should be "IT Professional 101" level stuff. We have MSFT to thank for the fact that expectations of IT people are so desperately low... Running a mail server really isn't that hard. Been doing it consistently for the past 20+ years.

Follow

@LovesTha and, to be honest, we also have MSFT to thank for the fact that email has become such a complex beast (due, largely, to HTML email and historically poor security of MS Windows) and Windows botnets.

@lightweight I do think we could do with a fix for email.

And it isn't like we don't have a replacement for email already. We have so many replacements for email launching every month.

@LovesTha well, yes, email is a technology for an earlier, quainter time. The lack of in-built encryption is a problem. But its distributed model is crucial. Centralised services are exactly not what we need...

@lightweight There are modern solutions to distributed models. (we are using one right now, not an email replacement, but the distributed model of it could be used)

@LovesTha Indeed - messaging build on the Matrix open standard shows promise, as does the ActivityPub standard. Both have a variety of excellent implementations, all open source.

Sign in to participate in the conversation
Mastodon - NZOSS

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!