# Question on use with DLP

**URL:** <https://community.ciphermail.com/t/question-on-use-with-dlp/157>\
**Category:** Gateway\
**Created:** [January 27, 2011, 7:26pm UTC](https://community.ciphermail.com/t/question-on-use-with-dlp/157 "2011-01-27T19:26:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chuck\_Wagon](https://avatars.discourse-cdn.com/v4/letter/c/bcef8e/32.png) [@Chuck\_Wagon](https://community.ciphermail.com/u/Chuck_Wagon)\
**Post date:** [January 27, 2011, 7:26pm UTC](https://community.ciphermail.com/t/question-on-use-with-dlp/157/1 "2011-01-27T19:26:13Z")

</div>

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  
this addressed.  
Thanks.

---

<div class="post-metadata">

**Author:** ![martijn](https://dub1.discourse-cdn.com/flex017/user_avatar/community.ciphermail.com/martijn/32/127_2.png) [@martijn](https://community.ciphermail.com/u/martijn)\
**Post date:** [January 27, 2011, 7:33pm UTC](https://community.ciphermail.com/t/question-on-use-with-dlp/157/2 "2011-01-27T19:33:42Z")

</div>

Hi,

You should set the global setting "encrypt mode" to "mandatory" to make  
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.

Kind regards,

Martijn Brinkers

> **···**
>
> 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  
> > this addressed.  
> > Thanks.  
> > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_  
> > Users mailing list  
> > Users(a)lists.djigzo.com  
> > [http://lists.djigzo.com/lists/listinfo/users](http://lists.djigzo.com/lists/listinfo/users)
> 
> --  
> Djigzo open source email encryption