S/MIME Problems in "Content-Type: multipart/mixed" mails

I could
open all Emails with S/MIME decryption from my organisation in the last version of emClient.
Now I see only the smime.p7m attachment although I have the right keys.

My Smartphone and Thunderbird can future more open and decrypt the mail.

I think you change something which had impact on mails with the Content-Type “multipart/mixed”

If I send mails without multipart/mixed then it works
Is it possible to fix it?

Content-Type: multipart/mixed; boundary="===============1121897824565136284=="
MIME-Version: 1.0
From: “Meier, MC-TX” <MC-TX.Meier@So-Unternehmen.com>
To: “MC-TX@dieMeiers.com” <MC-TX@dieMeiers.com>
Subject: rw
Thread-Topic: rw
Thread-Index: AdMqb04URLg4+83tRAKVP1C9Qv+6Tg==
Date: Sun, 10 Sep 2017 19:59:32 +0000
Message-ID: <e80e6dd031f74e58a9cecc33470451cb@as3s…>
Accept-Language: de-DE, en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
MIME-Version: 1.0

–===============1121897824565136284==
Content-Language: de-DE
Content-Type: application/pkcs7-mime; smime-type=enveloped-data;
name=“smime.p7m”
Content-Disposition: attachment; filename=“smime.p7m”
Content-Transfer-Encoding: base64

MIAGC…crypt…QAAAAAAAAAAAAA=

–===============1121897824565136284==
Content-Type: multipart/alternative; boundary="===============3236752810525126923=="
MIME-Version: 1.0
Content-Disposition: inline

–===============3236752810525126923==
Content-Type: text/plain; charset=“utf-8”
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

…content…
–===============3236752810525126923==
Content-Type: text/html; charset=“utf-8”
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable


…content…
–===============3236752810525126923==–

–===============1121897824565136284==–

I have the same issue. Is there any news here?

The first thing you could check is that you are using the latest version of eM Client available for download at http://www.emclient.com/release-history.

Matthias did not say which previous version it was working with. It would be interesting to know.

I don’t really remember. I think it was version 6.0.24316.0
The check with version 7.1.33101.0 is not possible, either.
If you have a beta version or with a more detail log, I would test it!

Thanks for the reply Matthias. 

Really this needs to be passed on the the developers, so if you and Richard have Pro Licenses, you should open support tickets. I would open one myself, but I have not personally experienced this problem and I regularly receive S/MIME encrypted messages.