I have a weird Bug In KMail: An Attachment thats showing up on the Web UI (IServ) isn't showing up in KMail.

On IServ there is the actual attachment and a smime.p7s, while on KMail there is nothing and an error

Not enough information to check signature. 0x<hex number>
Status: No status information available.

Looks like eighter something is wrong with the certificate or KMail is falsely considering the attachment as certificate

If there is an Certificate error, maybe KMail should offer a mode where it shows certificate attachments as well and offer to switch t it on certificate errors.

I wonder if this is related to a problem I have been seeing with attachments. I have received several emails from Apple iPhone users which have attached JPG files. KMail shows the message size as (for example) 18M, but shows no attachments. If I right-click the message and choose "Save Attachments", I get a message that there are no attachments. I can view the message source and see the BASE64 embedded.

However, opening the same message in Thunderbird works as expected. The JPGs are displayed inline, and I can save them to local files.

Yet another KMail annoyance ...

Bill Gee

It actually shows a atachment symbol...

And It also recently got fixed on my arch PC, but still exist on my Opensuse Tumbleweed laptop, so look like it was fixed.

A "smime.p7s" attachment is a digital signature (similar to PGP/GPG).

Kmail won't show it as an attachment because it correctly identifies it as a signature and tries to verify it, but as you don't seem to have the public key stored for it, kmail shows an error "Not enough information to check signature" (the "0x<hex number>" I think is the fingerprint of the certificate, I'm not very familiar with S/MIME certificates).

LeSnake wrote:Looks like eighter something is wrong with the certificate or KMail is falsely considering the attachment as certificate

If there is an Certificate error, maybe KMail should offer a mode where it shows certificate attachments as well and offer to switch t it on certificate errors.

Somehow I missed this part when first reading your post, so it looks like I'm trying to tell you something you already knew, sorry for that.