Forum Discussion
Junk E-mail Settings for Shared Mailboxes
Hi, We started to receive all email for our shared inbox to junk folder. I have set some of them as safe senders, but it didn't help. How can I check/amend junk settings for our shared mailboxes ...
TonyRedmond If this is the easiest method, then there is something seriously wrong with the implementation. The average end user is not going to know, or even want to know PowerShell. This is fine for system Admins and developers, but the average user in accounting will not do this. As a system admin, my life should not be delegated for managing junk email. This is why Microsoft keeps falling flat on it's face, dumb down interfaces so it's impossible to use unless you are a developer and find a way to "hack it". That's exactly what PowerShell is to the end user, a hack.
No one is advocating that normal users run PowerShell commands to update junk email settings. Administrators should do this for them.
- This is my point. In Microsoft's view, Administrators are for managing junk email. We have better things to do, like read license agreements.
- Implementing a common set of blocked sites is quick and easy for an administrator to do with PowerShell and is a better use of their time than mastering the archaic details of licensing. Or better again, don't allow end users to maintain safelists and depend on tenant-wide blocklists instead. https://practical365.com/junk-email-options/
- Apparently my sarcasm has eluded you. My time is better spent on fixing broken Microsoft patches that take down domain controllers, not managing end user emails. Why can't Microsoft implement a way in Outlook for a shared mailbox junk email options to be managed the end user? You may not trust your users that much, but I like giving them options. I don't need to micromanage my users, I need to micromanage my servers, firewalls, switches, you know, the things that help my users stay productive. I find it annoying that MS constantly moves more and more to the admins, simply because they refuse to complete and test their applications and patches. You are correct on one thing, their licensing is archaic.
All of that said, Your solution for administrators is commendable, workable and useful. It's just a shame that this is another responsibility dumped on admins due to lack of care and completeness by the developers at Microsoft.