@L3s
@lemmy.worldGreetings everyone,
We wanted to take a moment and let everyone know about the !business@lemmy.world community on Lemmy.World which hasn't gained much traction. Additionally, we've noticed occasional complaints about Business-related news being posted in the Technology community. To address this, we want to encourage our community members to engage with the Business community.
While we'll still permit Technology-related business news here, unless it becomes overly repetitive, we kindly ask that you consider cross-posting such content to the Business community. This will help foster a more focused discussion environment in both communities.
We've interacted with the mod team of the Business community, and they seem like a dedicated and welcoming group, much like the rest of us here on Lemmy. If you're interested, we encourage you to check out their community and show them some support!
Let's continue to build a thriving and inclusive ecosystem across all our communities on Lemmy.World!
Seems that a lot of us have some funny Unity memes, which have been getting removed due to Rule 7.
Making this post and pinning it for everyone to share their Unity memes about this whole fiasco, please only comment the memes here, if you make a post with one it will be removed.
Hey everybody, feel free to post any tech support or general tech discussion questions you have right here.
As always, be excellent to each other.
Yours truly, moderators.
My company is just starting to utilize O365 email encryption for sensitive information, which I know a lot of people are already using.
One thing we've run into is when sending a sensitive email to a third-party vendor, a lot of them utilize shared mailboxes/distribution groups, so the encryption is not allowing the members of the external mailbox/group to open the encrypted email as their account doesn't have permissions (the group email address does, instead of their individual account).
The only way I've come up with to solve this issue is setting the encrypted emails to not allow a "social" sign-on for decryption, and instead only offer "send a one-time passcode" as the authentication method, then the group/mailbox receives the code to view the email.
Curious how others have combatted this issue if they've crossed it, this feature has been around a while and I am unable to find much on Google about it specifically.
For the moment, users are just re-sending the encrypted email to the external recipient that replies "We can't open this email", which solves the problem but creates more work and takes longer for everyone.
https://en.wikipedia.org/wiki/Grant_Hadwin
https://www.techradar.com/gaming/kissing-or-licking-a-microphone-is-now-considered-sexual-according-to-twitch
Label your licking