Just for the record (and this might be helpful for others), it turned
out that the email was encrypted with a different certificate than the
certificate for which there was a private key available.
The easiest way to check with what certificate the email is encrypted is
by looking at the X-Djigzo-Info-Encryption-Recipient-x-x headers. They
should match the certificate for which there is a private key.
Kind regards,
Martijn Brinkers
On 08/13/2013 02:04 PM, Stefan Michael Guenther wrote:
Hi,
we have just setup the currrent vmware appliance for one of our clients,
created the local CA and a certificate for the local it administrator.
After this we imported the certificate for the CA and the user into our Djigzo
installation.
When I send an email, I get the notification, that the email has been
encrypted, but the problem is, that it is not decrypted on the recipient's side:
13 Aug 2013 13:53:14 | INFO incoming | MailID:
42f7e940-6aa3-4e00-80f9-fc4a061a94e6; Originator: [email protected];
Sender: [email protected]; Remote address: 10.56.253.10; Recipients:
[[email protected]]; Subject: test 4; Message-ID:
<[email protected]>;(mitm.application.djigzo.james.mailets.Log) [Spool
Thread #2]
13 Aug 2013 13:53:14 | INFO Subject filter is disabled for the sender; MailID:
42f7e940-6aa3-4e00-80f9-fc4a061a94e6
(mitm.application.djigzo.james.mailets.Default) [Spool Thread #2]
13 Aug 2013 13:53:14 | INFO postSubjectFilter state | MailID:
42f7e940-6aa3-4e00-80f9-fc4a061a94e6; Originator: [email protected];
Sender: [email protected]; (mitm.application.djigzo.james.mailets.Log)
[Spool Thread #2]
13 Aug 2013 13:53:14 | INFO internal state | MailID:
42f7e940-6aa3-4e00-80f9-fc4a061a94e6; Originator: [email protected];
Sender: [email protected]; (mitm.application.djigzo.james.mailets.Log)
[Spool Thread #2]
13 Aug 2013 13:53:14 | DEBUG internalHandlePart
(mitm.common.security.smime.handler.RecursiveSMIMEHandler) [Spool Thread
#2]
13 Aug 2013 13:53:14 | DEBUG Handling encrypted message.
(mitm.common.security.smime.handler.SMIMEHandler) [Spool Thread #2]
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
13 Aug 2013 13:53:14 | WARN A decryption key for the message could not be
found. (mitm.common.security.smime.handler.SMIMEHandler) [Spool
Thread #2]
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
13 Aug 2013 13:53:14 | INFO postDecrypt state | MailID:
42f7e940-6aa3-4e00-80f9-fc4a061a94e6; Originator: [email protected];
Sender: [email protected]; (mitm.application.djigzo.james.mailets.Log)
[Spool Thread #3]
How can we debug the step where the decryption should happen?
We already checked the date on the machine, to make sure, that keys and
certificates are valid.
Regards,
Stefan
_______________________________________________
Users mailing list
[email protected]
https://lists.djigzo.com/lists/listinfo/users
--
DJIGZO email encryption
_______________________________________________
Users mailing list
[email protected]
https://lists.djigzo.com/lists/listinfo/users
