attachments with s/mime produce garbled messages

[tomholub]

When opening an s/mime message on a client without s/mime (tried Gmail), it just shows the bytes.

I would have expected it to show as an attachment (I vaguely recall trying to open such message before). Can you have a look?

Also, have you tried to open such message in an s/mime client, after integrating it?

We're getting there.

Originally posted by @tomholub in #2712 (comment)

[wiktor-k]

Hmm... upon initial investigation I see this just fine on the receiving end: (my gmail with no flowcrypt extension):

And it looks OK on the sending end (with flowcrypt):

S/MIME examples in the RFC also mention one inline message instead of encrypted attachment: https://tools.ietf.org/html/rfc4134#section-5.3

I'll need to investigate this further. Could you send me the raw message that you saw (via e-mail or so...).

[tomholub]

Cannot reproduce when emailing myself

I'll email you the problematic message. You can drag it into Thunderbird from your desktop, which will save it on imap, which will allow you access the message from Gmail interface (even if this is not really a message for your account).

[wiktor-k]

You can drag it into Thunderbird from your desktop, which will save it on imap, which will allow you access the message from Gmail interface (even if this is not really a message for your account).

👍 Did the same trick when working on K9 :)

[tomholub]

I could not reproduce it.

The one that messed up included an attached public key, but even if I choose to attach a public key now, it won't attach it anyway (with s/mime message). Which it should. So I'm having a hard time trying to reproduce it.

[wiktor-k]

I don't think attachments work with S/MIME, maybe they produced garbled messages. This is a good ticket to keep. I'll investigate it further after I'm done with other "actionable" tickets.

[tomholub]

closing in favor of #2734