# Decrypt of PGP/INLINE encrypted mails not work in 6.2.5
**URL:** https://community.ciphermail.com/t/decrypt-of-pgp-inline-encrypted-mails-not-work-in-6-2-5/1042
**Category:** Gateway
**Tags:** pgp
**Created:** [January 22, 2026, 11:20am UTC](https://community.ciphermail.com/t/decrypt-of-pgp-inline-encrypted-mails-not-work-in-6-2-5/1042 "2026-01-22T11:20:08Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@ETES](https://community.ciphermail.com/u/ETES)
#### Post date: [January 22, 2026, 11:20am UTC](https://community.ciphermail.com/t/decrypt-of-pgp-inline-encrypted-mails-not-work-in-6-2-5/1042/1 "2026-01-22T11:20:08Z")
Hello,
We are facing a problem where emails from a partner are not being decrypted.
The emails are PGP/INLINE encrypted, so we have also activated PGP/INLINE support for the domain, but this has not made any difference. In the logs, we can see that the email is being processed (like an unencrypted email), but no decryption is started.
After switching to PGP/MIME at the email partner, decryption worked immediately. The log then also showed that the email had been decrypted.
So it’s probably down to the recognition of PGP/INLINE encrypted emails, right?
During the analysis, we would have liked to have a debug mode that gives us a little more information about the email, what it does with which email. However, we couldn’t find any information on how to adjust the log level in the new version. Did I overlook something?
Kind regards,
Paul
---
### Author:  [@martijn](https://community.ciphermail.com/u/martijn)
#### Post date: [January 22, 2026, 12:18pm UTC](https://community.ciphermail.com/t/decrypt-of-pgp-inline-encrypted-mails-not-work-in-6-2-5/1042/2 "2026-01-22T12:18:50Z")
Are you absolutely certain you enabled **PGP/Inline For Incoming Email** instead of **PGP Encoding**?
> **[PGP/Inline For Incoming Email Enabled - Settings — CipherMail Documentation](https://www.ciphermail.com/documentation/gateway-administration-guide/settings.html#pgp-inline-for-incoming-email-enabled-recipient-p)**
>
> This section provides an overview of configuration options dedicated to PGP encryption and digital signing.
---
### Author:  [@ETES](https://community.ciphermail.com/u/ETES)
#### Post date: [January 22, 2026, 4:07pm UTC](https://community.ciphermail.com/t/decrypt-of-pgp-inline-encrypted-mails-not-work-in-6-2-5/1042/3 "2026-01-22T16:07:16Z")
Hello Martijn,
yes, we enabled pgp-incoming-inline-enabled on domain level:
---
### Author:  [@martijn](https://community.ciphermail.com/u/martijn)
#### Post date: [January 22, 2026, 4:25pm UTC](https://community.ciphermail.com/t/decrypt-of-pgp-inline-encrypted-mails-not-work-in-6-2-5/1042/4 "2026-01-22T16:25:12Z")
Did you enable this for the recipient domain? Or sender domain?
---
### Author:  [@ETES](https://community.ciphermail.com/u/ETES)
#### Post date: [January 23, 2026, 7:39am UTC](https://community.ciphermail.com/t/decrypt-of-pgp-inline-encrypted-mails-not-work-in-6-2-5/1042/5 "2026-01-23T07:39:09Z")
We enabled this feature for the sender domain.
---
### Author:  [@martijn](https://community.ciphermail.com/u/martijn)
#### Post date: [January 23, 2026, 1:34pm UTC](https://community.ciphermail.com/t/decrypt-of-pgp-inline-encrypted-mails-not-work-in-6-2-5/1042/6 "2026-01-23T13:34:30Z")
This option is a recipient setting and therefore need to be set on the recipient domain (or globally). In hindsight, this should have been a sender setting instead of a recipient setting because that makes more sense. I have changed this in the mail flow configuration file. This is a breaking change if you have changed this setting for a recipient domain.
For a diff of the new and old mailetcontainer.xml file see:
> **[Update PGP configuration (e00ff144) · Commits · CipherMail B.V. /...](https://gitlab.com/ciphermail/ciphermail-community-backend/-/commit/e00ff14474b3f833724badc50fb645b17c8669e4)**
>
> The settings pgp-incoming-inline-enabled, pgp-scan-html-for-pgp, and pgp-skip-non-pgp-extensions have moved from recipient-level configuration to sender-level configuration. If you previously set any of these options for a recipient domain, you must...
Download link to updated mailetcontainer.xml:
[https://gitlab.com/ciphermail/ciphermail-community-backend/-/raw/main/ciphermail-gateway-backend/conf/etc/james/conf/mailetcontainer.xml?ref\_type=heads&inline=false](https://gitlab.com/ciphermail/ciphermail-community-backend/-/raw/main/ciphermail-gateway-backend/conf/etc/james/conf/mailetcontainer.xml?ref_type=heads&inline=false)
---
### Author:  [@ETES](https://community.ciphermail.com/u/ETES)
#### Post date: [January 26, 2026, 7:56am UTC](https://community.ciphermail.com/t/decrypt-of-pgp-inline-encrypted-mails-not-work-in-6-2-5/1042/7 "2026-01-26T07:56:01Z")
Thank you very much for your quick solution.
When reading the documentation, one can guess, but it is not clear.
Focusing on the sender makes much more sense in order to only generate the load when it is necessary. Will the change come with the next version, or does the breaking change need a little more time? Can a short note be added to the documentation in the meantime?
Is there a way to adjust the log level so that this information could also be found in the logs? A log line such as ‘PGP/INLINE skipped because it is not enabled for the recipient’ would certainly have helped.
---
### Author:  [@ETES](https://community.ciphermail.com/u/ETES)
#### Post date: [February 12, 2026, 1:58pm UTC](https://community.ciphermail.com/t/decrypt-of-pgp-inline-encrypted-mails-not-work-in-6-2-5/1042/8 "2026-02-12T13:58:40Z")
@martijn Did you see my last post?
Is there a way to adjust the log level so that this information could also be found in the logs?