At my workplace, we're currently using Mimecast for email security and archiving, but we're planning to switch over to Microsoft since we have E5. A key feature we rely on from Mimecast is their secure messaging platform. It allows users to send sensitive information without including it in the email directly; instead, the recipient receives a link where they can log in and access the message or file. Additionally, I'm interested in features similar to self-destruct messaging, like what is offered by PasswordState. I've been searching for alternatives that provide just this type of secure messaging without the extra email security features that come with platforms like Mimecast. Does anyone know of a standalone secure messaging service I could use? Or will I have to compromise by buying a more comprehensive product or lose this feature when we transition to Microsoft for our email security?
4 Answers
Have you thought about sending messages on a type of paper that catches fire after reading? Just kidding, but it’s a fun concept to think about!
Just a caution—self-destructing emails might raise some flags regarding compliance and audit trails. Make sure you're aligned with your compliance requirements before moving forward.
Absolutely! We're examining all our tools in relation to our corporate compliance standards right now, but I'm just trying to gather potential options.
You might want to check out LiquidFiles; it has features that could match your needs for secure messaging. It's focused on that specific function, unlike many larger platforms that bundle additional services.
MS365 does have some secure messaging options, which is how some professionals share sensitive info, like police officers do with district attorneys. Just a heads up though, its expiration settings might be pretty rigid across your organization, and you might need to look into specific licensing details.
You're right about the tenant-wide settings. While you can encrypt emails internally, it doesn’t extend to sharing with external parties unlike what Mimecast offers.
Lol! I’d prefer a method that ‘takes care’ of both the sender and receiver after reading, though!