# Message: There are no roots.

**URL:** https://community.ciphermail.com/t/message-there-are-no-roots/598
**Category:** Gateway
**Created:** [February 14, 2018, 7:59pm UTC](https://community.ciphermail.com/t/message-there-are-no-roots/598 "2018-02-14T19:59:48Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Gabi\_Munteanu](https://avatars.discourse-cdn.com/v4/letter/g/96bed5/32.png) [@Gabi\_Munteanu](https://community.ciphermail.com/u/Gabi_Munteanu)
#### Post date: [February 14, 2018, 7:59pm UTC](https://community.ciphermail.com/t/message-there-are-no-roots/598/1 "2018-02-14T19:59:48Z")

</div>

Hi,I'm having some issues while trying to send an email to a specific address, if sometimes fails to send the email and in the log I see this.13 Feb 2018 23:59:38 | WARN Error while building path for certificate. Certificate: Issuer: CN=CA xx BT 98, O=xx eG, C=xx; Subject: OID.1.3.6.1.5.5.7.9.3=M, EMAILADDRESS=info(a)xxx, GIVENNAME=xxx, SURNAME=xxx, CN=xxx, SERIALNUMBER=00000000015038638001, C=DE; Serial: 70F82D24FC0561EB; Thumbprint: 8047A76666C97E003E6671F9268049643877959118E5DD801366543D1E1218016ED4D0387B909DBC8F3102DA765D3C971D5B1A24BF855139BAAE80F806164869; SHA1: 974E2E84650CF628954BB0F56858431A0BAFFB1D. Message: There are no roots. (mitm.common.security.crl.CRLStoreUpdaterImpl) [CRL Updater thread]

The problem is that if I try again after a while it works.  
Checked the certificate for this email address and it is valid. What else should I check?  
Thank you !

---

<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: [February 15, 2018, 11:53am UTC](https://community.ciphermail.com/t/message-there-are-no-roots/598/2 "2018-02-15T11:53:50Z")

</div>

Hi Gabi,

> Hi,I'm having some issues while trying to send an email to a specific  
> address, if sometimes fails to send the email and in the log I see  
> this.13 Feb 2018 23:59:38 | WARN Error while building path for  
> certificate. Certificate: Issuer: CN=CA xx BT 98, O=xx eG, C=xx;  
> Subject: OID.1.3.6.1.5.5.7.9.3=M, EMAILADDRESS=info(a)xxx,  
> GIVENNAME=xxx, SURNAME=xxx, CN=xxx,  
> SERIALNUMBER=00000000015038638001, C=DE; Serial: 70F82D24FC0561EB;  
> Thumbprint:  
> 8047A76666C97E003E6671F9268049643877959118E5DD801366543D1E1218016ED4D0387B909DBC8F3102DA765D3C971D5B1A24BF855139BAAE80F806164869;  
> SHA1: 974E2E84650CF628954BB0F56858431A0BAFFB1D. Message: There are no  
> roots. (mitm.common.security.crl.CRLStoreUpdaterImpl) [CRL Updater  
> thread]
> 
> The problem is that if I try again after a while it works. Checked  
> the certificate for this email address and it is valid. What else  
> should I check? Thank you !

The WARN message from the MPA log tells you that you do not have any  
root certificates installed. This however only means that S/MIME  
certificates are not trusted (unless you add them to the CTL). Email is  
therefore not S/MIME encrypted. This however does not impact email  
delivery unless you require email to be encrypted and then the email  
will be bounced.

What do you actually mean with "sometimes fails to send the email"? The  
actual delivery of the email to the recipient?

Kind regards,

Martijn Brinkers

> **···**
>
> On 14-02-18 20:59, Gabi Munteanu via Users wrote:
> 
> --  
> CipherMail email encryption
> 
> Email encryption with support for S/MIME, OpenPGP, PDF encryption and  
> secure webmail pull.
> 
> > **[CipherMail email encryption and digital signatures](https://www.ciphermail.com)**
> >
> > Easy to use server-side email encryption for automatic encryption and digital signing of email.
> 
> Twitter: [http://twitter.com/CipherMail](http://twitter.com/CipherMail)

---

<div class="post-metadata">

### Author: ![Gabi\_Munteanu](https://avatars.discourse-cdn.com/v4/letter/g/96bed5/32.png) [@Gabi\_Munteanu](https://community.ciphermail.com/u/Gabi_Munteanu)
#### Post date: [February 15, 2018, 5:07pm UTC](https://community.ciphermail.com/t/message-there-are-no-roots/598/3 "2018-02-15T17:07:40Z")

</div>

Hi Martijn,  
Thank you for your reply!  
Yes, the actual delivery of the emial.  
Best regards,Gabi

Hi Gabi,

> Hi,I'm having some issues while trying to send an email to a specific  
> address, if sometimes fails to send the email and in the log I see  
> this.13 Feb 2018 23:59:38 | WARN Error while building path for  
> certificate. Certificate: Issuer: CN=CA xx BT 98, O=xx eG, C=xx;  
> Subject: OID.1.3.6.1.5.5.7.9.3=M, EMAILADDRESS=info(a)xxx,  
> GIVENNAME=xxx, SURNAME=xxx, CN=xxx,  
> SERIALNUMBER=00000000015038638001, C=DE; Serial: 70F82D24FC0561EB;  
> Thumbprint:  
> 8047A76666C97E003E6671F9268049643877959118E5DD801366543D1E1218016ED4D0387B909DBC8F3102DA765D3C971D5B1A24BF855139BAAE80F806164869;  
> SHA1: 974E2E84650CF628954BB0F56858431A0BAFFB1D. Message: There are no  
> roots. (mitm.common.security.crl.CRLStoreUpdaterImpl) [CRL Updater  
> thread]
> 
> The problem is that if I try again after a while it works. Checked  
> the certificate for this email address and it is valid. What else  
> should I check? Thank you !

The WARN message from the MPA log tells you that you do not have any  
root certificates installed. This however only means that S/MIME  
certificates are not trusted (unless you add them to the CTL). Email is  
therefore not S/MIME encrypted. This however does not impact email  
delivery unless you require email to be encrypted and then the email  
will be bounced.

What do you actually mean with "sometimes fails to send the email"? The  
actual delivery of the email to the recipient?

Kind regards,

Martijn Brinkers

> **···**
>
> On Thursday, February 15, 2018, 12:52:37 PM GMT+1, Martijn Brinkers via Users \<users(a)lists.djigzo.com\> wrote:  
> On 14-02-18 20:59, Gabi Munteanu via Users wrote:
> 
> --  
> CipherMail email encryption
> 
> Email encryption with support for S/MIME, OpenPGP, PDF encryption and  
> secure webmail pull.
> 
> > **[CipherMail email encryption and digital signatures](https://www.ciphermail.com)**
> >
> > Easy to use server-side email encryption for automatic encryption and digital signing of email.
> 
> Twitter: [http://twitter.com/CipherMail](http://twitter.com/CipherMail)
> 
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_  
> Users mailing list  
> Users(a)lists.djigzo.com  
> [https://lists.djigzo.com/lists/listinfo/users](https://lists.djigzo.com/lists/listinfo/users)

---

<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: [February 21, 2018, 9:29am UTC](https://community.ciphermail.com/t/message-there-are-no-roots/598/4 "2018-02-21T09:29:41Z")

</div>

> &nbsp;&nbsp;Hi Martijn,  
> Thank you for your reply!  
> Yes, the actual delivery of the emial.  
> Best regards,Gabi

The log entry from your previous email is not related to delivery  
failures. The MPA log only shows logs from the internal  
encryption/decryption engine. The MTA (Mail Transfer Agent) logs show  
logs related to mail delivery (incoming and outgoing).

There can be all kinds of reasons why your email is not delivered  
immediately. For example the big mail providers (Gmail, Hotmali etc.)  
quite often throttle receiving of email. Especially if they do not  
"trust" your IP address.

Check the MTA logs (or MTA queue) for information of why your email is  
not always delivered immediately (in most cases email is delivered in  
the end, only with a delay).

Kind regards,

Martijn Brinkers

> **···**
>
> On 15-02-18 18:07, Gabi Munteanu via Users wrote:
> 
> > On 14-02-18 20:59, Gabi Munteanu via Users wrote:
> > 
> > > Hi,I'm having some issues while trying to send an email to a specific  
> > > address, if sometimes fails to send the email and in the log I see  
> > > this.13 Feb 2018 23:59:38 | WARN Error while building path for  
> > > certificate. Certificate: Issuer: CN=CA xx BT 98, O=xx eG, C=xx;  
> > > Subject: OID.1.3.6.1.5.5.7.9.3=M, EMAILADDRESS=info(a)xxx,  
> > > GIVENNAME=xxx, SURNAME=xxx, CN=xxx,  
> > > SERIALNUMBER=00000000015038638001, C=DE; Serial: 70F82D24FC0561EB;  
> > > Thumbprint:  
> > > 8047A76666C97E003E6671F9268049643877959118E5DD801366543D1E1218016ED4D0387B909DBC8F3102DA765D3C971D5B1A24BF855139BAAE80F806164869;  
> > > SHA1: 974E2E84650CF628954BB0F56858431A0BAFFB1D. Message: There are no  
> > > roots. (mitm.common.security.crl.CRLStoreUpdaterImpl) [CRL Updater  
> > > thread]
> > > 
> > > The problem is that if I try again after a while it works. Checked  
> > > the certificate for this email address and it is valid. What else  
> > > should I check? Thank you !
> > 
> > The WARN message from the MPA log tells you that you do not have any  
> > root certificates installed. This however only means that S/MIME  
> > certificates are not trusted (unless you add them to the CTL). Email is  
> > therefore not S/MIME encrypted. This however does not impact email  
> > delivery unless you require email to be encrypted and then the email  
> > will be bounced.
> > 
> > What do you actually mean with "sometimes fails to send the email"? The  
> > actual delivery of the email to the recipient?
> > 
> > Kind regards,
> > 
> > Martijn Brinkers
> 
> --  
> CipherMail email encryption
> 
> Email encryption with support for S/MIME, OpenPGP, PDF encryption and  
> secure webmail pull.
> 
> > **[CipherMail email encryption and digital signatures](https://www.ciphermail.com)**
> >
> > Easy to use server-side email encryption for automatic encryption and digital signing of email.
> 
> Twitter: [http://twitter.com/CipherMail](http://twitter.com/CipherMail)
