When "openPGPEncryptedMessageDataWithEncryptedData" function in src/core/rfc822/MCMessageBuilder.mm adds the encrypted attachment, it should also add a filename, content-transfer-encoding, and content-disposition so mail clients that dont handle PGP directly can at least display the contents in a text file.
For example, currently the encrypted part looks like this in the message that the MessageBuilder generates:
Most PGP/MIME clients generate the PGP attachment with a filename such as "encrypted.asc" so that the recipient knows which part contains the PGP message, otherwise it can be confusing.
When "openPGPEncryptedMessageDataWithEncryptedData" function in src/core/rfc822/MCMessageBuilder.mm adds the encrypted attachment, it should also add a filename, content-transfer-encoding, and content-disposition so mail clients that dont handle PGP directly can at least display the contents in a text file.
For example, currently the encrypted part looks like this in the message that the MessageBuilder generates:
It should look something like this:
Most PGP/MIME clients generate the PGP attachment with a filename such as "encrypted.asc" so that the recipient knows which part contains the PGP message, otherwise it can be confusing.