# Problem with the encryption on domain rule

**URL:** <https://community.ciphermail.com/t/problem-with-the-encryption-on-domain-rule/337>\
**Category:** Gateway\
**Created:** [October 29, 2012, 10:57am UTC](https://community.ciphermail.com/t/problem-with-the-encryption-on-domain-rule/337 "2012-10-29T10:57:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Testuser\_SST](https://avatars.discourse-cdn.com/v4/letter/t/bc79bd/32.png) [@Testuser\_SST](https://community.ciphermail.com/u/Testuser_SST)\
**Post date:** [October 29, 2012, 10:57am UTC](https://community.ciphermail.com/t/problem-with-the-encryption-on-domain-rule/337/1 "2012-10-29T10:57:08Z")

</div>

-------- Original-Nachricht --------

> Datum: Fri, 26 Oct 2012 18:02:54 +0200  
> Von: Martijn Brinkers \<martijn(a)djigzo.com\>  
> An: users(a)lists.djigzo.com  
> Betreff: Re: Problem with the encryption on domain rule

> \> -------- Original-Nachricht --------  
> \>\> Datum: Fri, 26 Oct 2012 16:49:13 +0200  
> \>\> Von: Martijn Brinkers \<martijn(a)djigzo.com\>  
> \>\> An: users(a)lists.djigzo.com  
> \>\> Betreff: Re: Problem with the encryption on domain rule  
> \>  
> \>\>\> I´m using the latest djigzo on a CentOS 6.3. I have a domain with a  
> \>\> certificate to encrypt, but none of the mails which are going through  
> the  
> \>\> gateway are encrypted. Here is the log output, maybe somebody can tell  
> me why  
> \>\> it´s not working:  
> \>\>\>  
> \>\>\> 26 Oct 2012 16:09:43 | INFO incoming | MailID:  
> \>\> 0121f9cf-f632-4077-a39e-ce065089269c; Originator: name.name(a)company.de;  
> Sender:  
> \>\> name.name(a)company.de; Remote address: 192.168.1.35; Recipients:  
> [test(a)encrypt.de]; Subject:  
> \>\> test ; Message-ID:  
> \>\> \<EB6653A813FDF14F96405E552D11AC860277DBCE(a)server.internal.lan\>;  
> (mitm.application.djigzo.james.mailets.Log) [Spool Thread #2]  
> \>\>\> 26 Oct 2012 16:09:43 | INFO Subject filter is disabled for the sender;  
> \>\> MailID: 0121f9cf-f632-4077-a39e-ce065089269c  
> \>\> (mitm.application.djigzo.james.mailets.Default) [Spool Thread #2]  
> \>\>\> 26 Oct 2012 16:09:43 | INFO postSubjectFilter state | MailID:  
> \>\> 0121f9cf-f632-4077-a39e-ce065089269c; Originator: name.name(a)company.de;  
> Sender:  
> \>\> name.name(a)company.de; (mitm.application.djigzo.james.mailets.Log)  
> [Spool Thread  
> \>\> #2]  
> \>\>\> 26 Oct 2012 16:09:43 | INFO external state | MailID:  
> \>\> 0121f9cf-f632-4077-a39e-ce065089269c; Originator: name.name(a)company.de;  
> Sender:  
> \>\> name.name(a)company.de; (mitm.application.djigzo.james.mailets.Log)  
> [Spool Thread #2]  
> \>\>\> 26 Oct 2012 16:09:43 | INFO DLP is disabled for the sender; MailID:  
> \>\> 0121f9cf-f632-4077-a39e-ce065089269c  
> \>\> (mitm.application.djigzo.james.mailets.Default) [Spool Thread #2]  
> \>\>\> 26 Oct 2012 16:09:43 | INFO postDLP state | MailID:  
> \>\> 0121f9cf-f632-4077-a39e-ce065089269c; Originator: name.name(a)company.de;  
> Sender:  
> \>\> name.name(a)company.de; (mitm.application.djigzo.james.mailets.Log)  
> [Spool Thread #2]  
> \>\>\> 26 Oct 2012 16:09:43 | INFO "subject trigger" is disabled for the  
> \>\> sender; MailID: 0121f9cf-f632-4077-a39e-ce065089269c  
> \>\> (mitm.application.djigzo.james.mailets.Default) [Spool Thread #2]  
> \>\>\> 26 Oct 2012 16:09:43 | INFO checkForceEncryptHeader state | MailID:  
> \>\> 0121f9cf-f632-4077-a39e-ce065089269c; Originator: name.name(a)company.de;  
> Sender:  
> \>\> name.name(a)company.de; (mitm.application.djigzo.james.mailets.Log)  
> [Spool  
> \>\> Thread #2]  
> \>\>\> 26 Oct 2012 16:09:43 | INFO "force encrypt header trigger" is disabled  
> \>\> for the sender; MailID: 0121f9cf-f632-4077-a39e-ce065089269c  
> \>\> (mitm.application.djigzo.james.mailets.Default) [Spool Thread #2]  
> \>\>\> 26 Oct 2012 16:09:43 | INFO checkEncryptMode state | MailID:  
> \>\> 0121f9cf-f632-4077-a39e-ce065089269c; Originator: name.name(a)company.de;  
> Sender:  
> \>\> name.name(a)company.de; (mitm.application.djigzo.james.mailets.Log)  
> [Spool Thread  
> \>\> #2]  
> \>\>\> 26 Oct 2012 16:09:43 | INFO "encrypt mode" is force for the  
> \>\> recipient(s); MailID: 0121f9cf-f632-4077-a39e-ce065089269c  
> \>\> (mitm.application.djigzo.james.mailets.Default) [Spool Thread #2]  
> \>\>\> 26 Oct 2012 16:09:43 | INFO checkSMIME state | MailID:  
> \>\> 0121f9cf-f632-4077-a39e-ce065089269c; Originator: name.name(a)company.de;  
> Sender:  
> \>\> name.name(a)company.de; (mitm.application.djigzo.james.mailets.Log)  
> [Spool Thread #2]  
> \>\>\> 26 Oct 2012 16:09:43 | INFO checkPDFEncrypt state | MailID:  
> \>\> 0121f9cf-f632-4077-a39e-ce065089269c; Originator: name.name(a)company.de;  
> Sender:  
> \>\> name.name(a)company.de; (mitm.application.djigzo.james.mailets.Log)  
> [Spool Thread  
> \>\> #2]  
> \>\>\> 26 Oct 2012 16:09:43 | INFO PDF encryption is disabled for the  
> \>\> recipient(s); MailID: 0121f9cf-f632-4077-a39e-ce065089269c  
> \>\> (mitm.application.djigzo.james.mailets.Default) [Spool Thread #2]  
> \>\>\> 26 Oct 2012 16:09:43 | INFO checkMustEncrypt state | MailID:  
> \>\> 0121f9cf-f632-4077-a39e-ce065089269c; Originator: name.name(a)company.de;  
> Sender:  
> \>\> name.name(a)company.de; (mitm.application.djigzo.james.mailets.Log)  
> [Spool Thread  
> \>\> #2]  
> \>\>\> 26 Oct 2012 16:09:43 | INFO Force signing not allowed for sender;  
> \>\> MailID: 0121f9cf-f632-4077-a39e-ce065089269c  
> \>\> (mitm.application.djigzo.james.mailets.Default) [Spool Thread #2]  
> \>\>\> 26 Oct 2012 16:09:43 | INFO checkSMIMESign state | MailID:  
> \>\> 0121f9cf-f632-4077-a39e-ce065089269c; Originator: name.name(a)company.de;  
> Sender:  
> \>\> name.name(a)company.de; (mitm.application.djigzo.james.mailets.Log)  
> [Spool Thread #2]  
> \>\>\> 26 Oct 2012 16:09:43 | INFO "only sign when encrypt" is enabled for  
> the  
> \>\> sender. S/MIME signing will be skipped; MailID:  
> \>\> 0121f9cf-f632-4077-a39e-ce065089269c  
> (mitm.application.djigzo.james.mailets.Default) [Spool Thread #2]  
> \>\>\> 26 Oct 2012 16:09:43 | INFO transport state | MailID:  
> \>\> 0121f9cf-f632-4077-a39e-ce065089269c; Originator: name.name(a)company.de;  
> Sender:  
> \>\> name.name(a)company.de; Remote address: 192.168.1.35; Recipients:  
> [test(a)encrypt.de];  
> \>\> Subject: test ; Message-ID:  
> \>\> \<EB6653A813FDF14F96405E552D11AC860277DBCE(a)server.internal.lan\>;  
> (mitm.application.djigzo.james.mailets.Log) [Spool Thread #2]  
> \>\>\> 26 Oct 2012 16:09:47 | INFO Cleaning Key Cache. Cache size: 0  
> \>\> (mitm.common.cache.KeyCacheImpl) [KeyCacheImpl Thread]  
> \>\>  
> \>\> A couple of questions  
> \>\>  
> \>\> 1. Can you check whether you have selected the certificate as  
> encryption  
> \>\> certificate for the external domain?  
> \>\>  
> \>\> 2. Is the domain certificate trusted? i.e., not shown with a gray  
> \>\> background but with a white background?  
> \>\>  
> \>\> 3. I see that you have set encrypt mode to "Force". That might be on  
> \>\> purpose but if your intention is to have mandatory encryption when  
> \>\> sending to that domain, you should set encrypt mode to "Mandatory"  
> \>\>  
> \>\> Kind regards,  
> \>\>  
> \>\> Martijn  
> \>\>  
> \> Hi Martijn,  
> \>  
> \> thanks for your fast reply :o)  
> \>  
> \> 1.yes ist is as encryption used, not for signing  
> \>  
> \> 2. as you mentioned it now, the background is grey. how can I make it a  
> white one ? (I wasn`t aware of it)
> 
> If you click the certificate subject and view the certificate it tells  
> you why it's not trusted.
> 
> If it is because the complete cert chain cannot be found (i.e. an  
> intermediate or root is missing) and you cannot install the intermediate  
> or the root, you can manually make a certificate valid by white listing  
> the certificate. You can do this by placing the certificate on the  
> certificate trust list (CTL) with white listing selected. CLick the  
> certificate, on the certificate view page, click "add to CTL". Then set  
> the status to "White list".
> 
> regards,
> 
> Martijn

Hi Martijn,

yes, there was a problem in the certification path, but know with the whitelisting everything runs fine.

Thanks for your support and your great gateway !

fatcharly

> **···**
>
> > On 10/26/2012 05:03 PM, fatcharly(a)gmx.de wrote:  
> > \>\> On 10/26/2012 04:33 PM, fatcharly(a)gmx.de wrote:
> 
> > --  
> > DJIGZO email encryption  
> > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_  
> > Users mailing list  
> > Users(a)lists.djigzo.com  
> > [http://lists.djigzo.com/lists/listinfo/users](http://lists.djigzo.com/lists/listinfo/users)

---

<div class="post-metadata">

**Author:** ![Christine](https://avatars.discourse-cdn.com/v4/letter/c/8491ac/32.png) [@Christine](https://community.ciphermail.com/u/Christine)\
**Post date:** [October 29, 2012, 2:14pm UTC](https://community.ciphermail.com/t/problem-with-the-encryption-on-domain-rule/337/2 "2012-10-29T14:14:36Z")

</div>

Martijn and his team work hard to keep everyone happy. I'm glad they are  
successful in this 🙂

dagdag  
Christine

> **···**
>
> On 10/29/2012 11:57 AM, fatcharly(a)gmx.de wrote:
> 
> > Hi Martijn, yes, there was a problem in the certification path, but  
> > know with the whitelisting everything runs fine. Thanks for your  
> > support and your great gateway !
> 
> --  
> dagdag is just a two character rotation of byebye
