You should set the global setting "encrypt mode" to "mandatory" to
sure that all outgoing email will be encrypted. The main question now is
what password should be used for the PDF encryption. You can setup a
static password, let Djigzo generate a password and send by SMS to the
recipient or let Djigzo generate a password and send the password back
to the sender. The sender should then make sure the recipient gets the
password. By default a new password will be generated for every new
message. You can however change the password validity interval to make a
password valid for a longer period.
On 01/27/2011 08:26 PM, Chuck Wagon wrote:
Just found Djigzo and am looking at potentially using
it as part of a DLP
solution. The way I am envisioning it is this:
DLP detects something that should be encrypted and inserts an X-Header
DLP hands the email off to our MTA, which is configured to route any email
with the X-Header in it to the Djigzo to be encrypted as an encrypted PDF.
ANY email sent to Djigso will be PDF encrypted and sent outbound. We may or
may not allow reply, most likely not.
What would be the best way to accomplish this? Djigzo will not need a
"trigger" as anything it gets should be PDF encrypted and sent out.
We don't want to have to specify senders or recipients... again, everything
will get PDF encrypted.
Is this easy to do? I've read the manuals but did not see any scenarios like
Users mailing list
Djigzo open source email encryption