On 22-05-18 21:12, lists via Users wrote:> 22 May 2018 20:58:46 | INFO
incoming; MailID: d6c60f00-eefe-47d9-be9e-cd8fc989034b; Recipients:
[recipent(a)dest-domain.com]; Originator: sender(a)sender-domain.com;
Sender: sender(a)sender-domain.com; Remote address: 192.168.100.252;
Subject: test; Message-ID: > 22 May 2018 20:58:46 | INFO S/MIME message
has been decrypted. MailID: d6c60f00-eefe-47d9-be9e-cd8fc989034b;
(mitm.application.djigzo.james.mailets.SMIMEHandler) [Spool Thread #3]
22 May 2018 20:58:46 | WARN Signature could not be
verified. Message: Message content cannot be verified with the signers public key.
(mitm.common.security.smime.handler.SMIMEInfoHandlerImpl) [Spool Thread #3]
22 May 2018 20:58:46 | WARN S/MIME signature was not valid; Signer IDs: CN=D-TRUST CA 2-1
2015, O=D-Trust GmbH, L=Berlin, C=DE/715FBC297CC280DEF937EF0AF42176B6/; MailID:
All certificates and chains are present in certificate store. Wy does the signature not
There can be all kinds of reasons why a signature does not validate. In
this case the validation failure seems not to be caused by a missing
certificate. It's hard to analyze without more information. From the
logs it looks like you remove the signature. If possible, it would be
helpful to get a message with signature attached so you can check
whether some S/MIME email client things the signature is correct.
Which version of CipherMail are you using? 3.3.1-0 introduced support
for RSASSA-PSS signing. If you use an older version and the message is
RSASSA-PSS signed, verification will probably fail.
CipherMail email encryption
Email encryption with support for S/MIME, OpenPGP, PDF encryption and
secure webmail pull.