Hello Kevin,

Thank you for reaching out with this question. We made the decision to remove the feature of sorting users by disk usage in 2021 due to performance concerns. However, there is a workaround available. As a domain administrator, you can use the disk usage domain report to filter by disk usage.

I hope this information helps. Since you submitted this as a feature request it will be added to our backlog for further discussion. 

Kind Regards, 

Zach, thanks for reply. Couple comments...

It looks like I have to impersonate the domain admin to see the disk usage domain report. This seems awkward. Would be nice to let the server admin view users and disk usage.

I impersonated a domain admin with 1000 users, clicked on Disk Usage, and it just spun for 20 minutes. I got tired of waiting and closed the browser tab. Maybe this could be optimized to only have to look up the 20 or so users on the first screen?

Thanks,
Kevin

SM V15.x has this feature, and the user results by usage within a domain are instant.

It was inefficient the way it looked up the data. We have instantaneous ways of pulling this info now it would be cool to fix the UI to use the new way to get user sizes. Before we had to pull it from each user but we now store a cached user size in accounts.json.

Bump.

Really need this feature to show which users are consuming all the disk space on the server. Then you could clean up those users instead of buying more disk space.

Bump as there's a similar request:

Disk space will be able to be sorted on Domain and Users page in an upcoming BETA build.

Great! Every day a step forward to make SmarterMail better and better.

I have to say you guys are doing a good job, keep it up.

Appreciate the kind words.

Would it make sense to mark this thread as "In Progress" then when the build with this feature is released, mark as Completed?  Just an idea that someone suggested in another post to improve communication...

It sure would be nice if we had Unlimitted resources to change statuses in a public community whenever anything changes in our development process.

But since we are in BETA and the task is DONE and in QC and will be in an upcoming BETA, changing it now makes a lot of sense so it doesn't get stuck in an improper state for the rest of time.