# Email not being recognized as PGP encrypted

**URL:** <https://community.ciphermail.com/t/email-not-being-recognized-as-pgp-encrypted/476>\
**Category:** Gateway\
**Created:** [November 25, 2015, 1:46pm UTC](https://community.ciphermail.com/t/email-not-being-recognized-as-pgp-encrypted/476 "2015-11-25T13:46:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stefan\_Gunther](https://avatars.discourse-cdn.com/v4/letter/s/51bf81/32.png) [@Stefan\_Gunther](https://community.ciphermail.com/u/Stefan_Gunther)\
**Post date:** [November 25, 2015, 1:46pm UTC](https://community.ciphermail.com/t/email-not-being-recognized-as-pgp-encrypted/476/1 "2015-11-25T13:46:39Z")

</div>

Hi,

we have setup a PGP encryption between one of our customers (using ciphermail) and his tax accountant (using enigmail).

The tax accountant has to send loan reports only as an encrypted email.  
We exported the public pgp key of the customer and imported it successfully into enigmail. Did the same with my public key.  
The public key of the customer has been in use in our ciphermail installation for at least 4 months.

When the tax accountant sends an email to my address it is encrypted and decrypted.  
When the tax account sends an email to the customer it is encrypted but not decrypted:

25 Nov 2015 12:37:53 | INFO incoming; MailID: d958dba2-9d26-41d7-bbff-26f54c10d5bd; Recipients: [xxxxx(a)xxxx.com]; Originator: yyyy(a)yyyyy.com; Sender: yyyy(a)yyyyyy.com; Remote address: 217.72.192.zz; Subject: Re: Hurra; Message-ID: \<56559D7E.6000204(a)yyyyy.com\>; (mitm.application.djigzo.james.mailets.Log) [Spool Thread #2]  
25 Nov 2015 12:37:53 | INFO Subject filter is disabled for the sender; MailID: d958dba2-9d26-41d7-bbff-26f54c10d5bd; Recipients: [xxxx(a)xxxx.com] (mitm.application.djigzo.james.mailets.Default) [Spool Thread #2]  
25 Nov 2015 12:37:53 | INFO To internal recipient(s); MailID: d958dba2-9d26-41d7-bbff-26f54c10d5bd; Recipients: [xxxxx(a)xxxx.com] (mitm.application.djigzo.james.mailets.Default) [Spool Thread #2]  
25 Nov 2015 12:37:53 | INFO "add security info" is enabled for the recipient(s); MailID: d958dba2-9d26-41d7-bbff-26f54c10d5bd; Recipients: [xxxxx(a)xxxx.com] (mitm.application.djigzo.james.mailets.Default) [Spool Thread #2]  
25 Nov 2015 12:37:54 | INFO Message handling is finished. Sending to final recipient(s); MailID: d958dba2-9d26-41d7-bbff-26f54c10d5bd; Recipients: [xxxxx(a)xxxxx.com]; Originator: yyyyy(a)yyyy.com; Sender:yyyy(a)yyyyy.com; Remote address: 217.72.192.zz; Subject: Re: Hurra; Message-ID: \<56559D7E.6000204(a)yyyyyy.com\>; (mitm.application.djigzo.james.mailets.Log) [Spool Thread #2]

I have access to the customers emails and I see the encrypted email.

When I send an encrypted email to the customer, the log contains the line

25 Nov 2015 13:21:09 | INFO Message has been PGP decrypted; MailID: 9a6a2080-8a10-4aff-9370-3fab14845438; Recipients: [xxxx(a)xxxxx.com] (mitm.application.djigzo.james.mailets.PGPHandler) [Spool Thread #1]

There is one difference between the two ciphermail installations: Our customer has a user profile for the tax accountant, we do not. I therefore assume, that I made a mistake in the configuration of that profile. But which parameter could prevent an email from beeing decrytped? Why does one ciphermail installation recognize the encryption and the other one not?

Thanks for your help,

Stefan

---

<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:** [November 25, 2015, 1:58pm UTC](https://community.ciphermail.com/t/email-not-being-recognized-as-pgp-encrypted/476/2 "2015-11-25T13:58:58Z")

</div>

> we have setup a PGP encryption between one of our customers (using  
> ciphermail) and his tax accountant (using enigmail).
> 
> The tax accountant has to send loan reports only as an encrypted  
> email. We exported the public pgp key of the customer and imported it  
> successfully into enigmail. Did the same with my public key. The  
> public key of the customer has been in use in our ciphermail  
> installation for at least 4 months.
> 
> When the tax accountant sends an email to my address it is encrypted  
> and decrypted. When the tax account sends an email to the customer  
> it is encrypted but not decrypted:

[SNIP]

> I have access to the customers emails and I see the encrypted email.
> 
> When I send an encrypted email to the customer, the log contains the  
> line
> 
> 25 Nov 2015 13:21:09 | INFO Message has been PGP decrypted; MailID:  
> 9a6a2080-8a10-4aff-9370-3fab14845438; Recipients: [xxxx(a)xxxxx.com]  
> (mitm.application.djigzo.james.mailets.PGPHandler) [Spool Thread #1]
> 
> There is one difference between the two ciphermail installations: Our  
> customer has a user profile for the tax accountant, we do not. I  
> therefore assume, that I made a mistake in the configuration of that  
> profile. But which parameter could prevent an email from beeing  
> decrytped? Why does one ciphermail installation recognize the  
> encryption and the other one not?

Most likely, the email sent by the tax accountant is encrypted with  
PGP/INLINE but PGP/INLINE is not enabled for the recipient (either  
globally or on domain or for the individual recipient(s)).

Can you check the following:

1. Is the email that was not decrypted, encrypted with PGP/INLINE?

2. Is "Enable PGP/INLINE to internal" checked?

Kind regards,

Martijn Brinkers

> **···**
>
> On 11/25/2015 02:46 PM, Stefan Michael Guenther 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)
