Signed emails displayed as having no parts

[fr]

Hi,

When I have a signed email (see Header 1 below) on my university's new IMAP server (some Microsoft exchange server), Mulberry displays the header but then insists the "message does not contain any parts that Mulberry can display". Other clients display the email fine.

When I try to verify the signature, Mulberry says "Failed to Verify/Decrypt:" with no further error explanation.

I have a similar problem on other IMAP servers. But there, Mulberry always displays the full email (see Header 2 below) together with a warning that it hasn't been verified.

So it might be a server problem. But since other clients don't show problems, it might also be Mulberry-related.

When you compare the headers below, you see that the main difference seems to be that Header 1 (nothing is displayed) contains signature headers that are not present in Header 2 (message is displayed with verification warning).

---

Header 1

MIME-Version: 1.0 [...] domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;

h=sender:from:organization:to:subject:date:user-agent:references

:in-reply-to:mime-version:content-type:content-transfer-encoding :message-id;

b=OLSh85ulYXUOuZSha1KkicJFKkTHrbqGaYgj14VZiIuIXZNganct8XX/t915DIsFUQ

h9IX7me07N9DZLhilQJ2Q2/JD0WlmV1rdy4TKBZt5SMtc8TsytqXqjJfCPnCJPeWgDKm b9CqxBVH1EWqFjTrSXfxTyaPzkOBZLE1+nzBs=

dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed;

d=googlemail.com; s=gamma; h=domainkey-signature:received:received:sender:from:organization:to

:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:message-id;

bh=lctfSQYQORxfXHwwqPtL87FOHSOrmA+/Dz3Dj9/espI=; b=JhUnCsobDwZU8gyme0mEbAzkIec7t1ALMJkMnV3d68p8HuQRjL1BbHExGwQ7VRvpVF

bxUs5rGwMuFLOxSqdv3HV7tNNldTJdMkm32iwaOOMJauF234xwM1Wj7gDao6T/09wKln jal4i/7OnfV2qfV9POKEynXFNtpCl/gewNbWk=

[...] Content-Type: multipart/signed; boundary="nextPart2453646.SsCLyJFrDZ";

protocol="application/pgp-signature"; micalg=pgp-sha1

[...]

---

Header 2

[...] MIME-Version: 1.0 Content-Type: multipart/signed;

boundary="nextPart2715928.osA6Okg73K"; protocol="application/pgp-signature"; micalg=pgp-sha1

[...]