

No autosaving?
No autosaving?
This will get extended until he can make it someone else’s problem.
I don’t disagree that you should set up retention policies to delete old email, I disagree that you should remove old emails from primary service/storage.
I actually did need a 15 year old email a few months ago. I don’t recall what I needed, but I then set up a retention policy to delete old stuff.
Not true.
It’s much easier to keep old data in active storage where it can be classified, searched, and have retention/deletion policies applied. Moving it elsewhere makes it more likely you’ll just hang onto it forever while not using it at all.
lol @ ftp client
I wasn’t just a user, I was an admin of BES and UEM and all mobile devices. Nearly ever enterprise user had awful Android experience.
I had a few, not hard to get.
Hub was a good idea but they didn’t keep up with modern enterprise security features.
The hardware was below BlackBerry’s average, especially coming from a bb10 device like the passport.
The Android phones were rubbish.
There was no os11. There was bbx/bb10
Nope.
The qnx os was the modern blackberry phone. They lost the plot moving to android.
MS knows any data within your tenant. It doesn’t train on it or use it for other purposes outside of your tenant.
The data is still harvested but it stays within their own tenant.
Why? Dumping that shitty code as fast as possible is a win for everyone. It’s been completely capable as a mail app for over a year. It’s barely-used functions that are missing.
It’s webmail with an offline mode, of course it’s collecting data.
This was already happening for most of their paying customers, and the data they connect is retained on a per-tenant basis.
It’s a necessity. It’s too different. It won’t ever have feature parity, and you need to give companies time to adapt their edge case uses.
They did the same thing with Teams and did worse with OneNote.
They did themselves a favor and killed off the Mail app ahead of time at least.
I think calling one “new” and the other “classic” is easy enough. The only alternative is to use a different name entirely.
As someone that maintains Outlook users, I can’t wait. Dumping decades of garbage code is a godsend.
Most businesses will be fine. The edge case scenarios will bitch and moan but will get over it by the following fiscal quarter.
New outlook will be easier than ever to upgrade. Code security will be better than ever before. Also no more unique software for non-Windows OS’s. OSX and Linux support will be a good feature that’s missing today.
What’s the replacement? Quark express?
Deduplication is trivial when applied at the block level, as long as the data is not encrypted, or is encrypted at rest by the storage system.