---- BEGIN RANT ----
Microsoft Exchange
---- END RANT ----

I have to fix this fucking fucked up thing again. Fuck.
The dude who wanted to use it does not have the skills to fix it. Fuck off. This bullshit is going to get migrated asap

Exchange makes sense in large companies, otherwhise it is too much work

@Linux office365 makes even more sense because unlike exchange it works much more often, is easier to manage, etc

@arcadesdude
Just no, with office365 you have faaaaar less control. If you dont pay more money ofc.

@Linux well since I have to baby-sit countless failing exchange servers I'd take o365 any day. At least it doesn't require service restarts or reboots or prone to no email when the ISP has an outage.

@arcadesdude
Never had any issues really. It depends how good you are at managing it ;)
The "no-email internet is down" - easy solved with a backup MX

To speak from enduser side: It sucks. You can't even apply ingoing filters on received messages.

@daintycode
Blame the person who manage the server. It is possible.

@Linux rly?
I may have to correct: not filters, rules. The auto-move-to-folder stuff.

@Linux I assure you it is managed just fine. It is just a piece of crap software that is inherently prone to failure.

@arcadesdude
If it fails all the time - it is NOT managed "just fine".

@Linux Incorrect. It is managed fine but is just a piece of crap software. It would be better to get rid of it and get everyone on O365 which doesn't fail all the time but that isn't a decision which those who manage it can make in this case. But thanks for suggesting you can manage it better lol!

@arcadesdude
I dont managing the exchange environment, I do Linux stuff.

@Linux I'm just speaking from experience. I wouldn't manage it if I could as it isn't as grand an experience dealing with the constant issues as it is a decent experience from the user side. It's like that frontend backend photo where frontend is a pleasant appearance and backend is....well not :)

@arcadesdude
Lets hope that you will figure out the issues :)

@Linux issues are that when left running for an extended period of time the application has memory leaks that cause it to crash...either the services crash like the exchange replication or transport services or the servers lock up from only running exchange. I didn't set these up or configure them but haven't seen a single exchange server that was configured differently. Solution is constant restarting services or rebooting for some temporary time when it works.

@Linux It's like someone gave you a pile of garbage and said "please make sure this 7 year old pile of garbage continues to work"...and so you have to keep moving the garbage around so it doesn't stink up any one place for too long. This is what Exchange (2010) is.

It made me think about developing something as well. Of course, this can be a great way to benefit from it, but I'm sure I'm not capable of this. I could use this resource where I was able to find Microsoft product. It seems quite convenient to me.