We currently have an IronMail appliance who allow us to "insert a key word (secured) " on the subject line of any email and force that email out encypted."Ironmail will always deliver messages to or from the specified user, group or domain securely.First, Email Gateway will attempt to deliver the message using S/MIME. If S/MIME is not supported, Email Gateway will look for PGP certificates and attempt that secure method. If neither is available or neither is supported by the other mail server, Email Gateway will attempt SSL delivery. And if none of these methods can be supported, Email Gateway will deliver the message via HTTPS, it’s Secure Web Delivery"
Is there a similar feature or policy that can be created using FOPE?
In FOPE Encryption is a paid service addressed as Exchange Hosted Encryption.
In order to send an Encrypted email we can set an Outbound Policy Rule to encrypt outbound emails based on subject keywords, message keywords, or common expressions in addition to sender IP address, sender and recipient domain, or e-mail address.
We can also create a Button in Outlook to send an Encrypted email where button injects a header in an email and we create a Policy Rule stating that any Outbound Email having that header mentioned in it should get delivered as a Encrypted Email.
--------Pradeep Samant (FOPE ROCKS!!!)
In FOPE we an create a Policy Rule to Encrypt an email having specific word or character mentioned in Message body, subject or also depending upon the Headers.
For VIP in the org we can create a Buttonin Outlook to let them decide if they want that email to be sent in an Encrypted Format.
FOPE uses its own Gateway to deliver Encrypted emails. By the feature of ZDM and the PKI concept involved the recipient server configuration really doesnt matters when we send an encrypted email using FOPE.
The only concern is the Policy Rule configured; if we dont test it before sending an Business Prioirty Confidential Email then the email sent might not get delivered as Encrypted Email.
So in FOPE Encryption is totally dependent on Policy Configuration and not on the Recipients compatibility so that it can switch to some different Secured Mailing feature apart from sending it using FOPE Encryption Feature.
If we dont want to Invest in Encryption the best substitute would be Force TLS policy rule.
------- Pradeep Samant (FOPE ROCKS!!!)
I would like to add to Pradeep.... He has answered all the queries upto the mark, here is the supporting document for how Encryotion works in FOPE.
A video Encryption Policy Rules in Exchange Hosted Encryption:
Create an FOPE Encryption Button for Outlook:
Thanks & Regards, Ritesh Hegde, Exchange,BPOS, FOPE, O365.