Failing pim/messagelib tests for text/pgp data

[Sandro Knauß]

Hey,

> I have added a work around to kmime which ensures that text/pgp isn't
> decoded as text. https://invent.kde.org/pim/kmime/-/merge_requests/134

great - thanks.

> Your commit message points to https://phabricator.kde.org/D8521 which points
> to https://bugs.kde.org/show_bug.cgi?id=324365 where I don't see anything	
> about text/pgp. *shrug*

Finally a grep in my archive helped to found matches with Roundcube 1.1.7 and 
1.1.9 all sent in 2017.

With the mail address I remember the person and how they do encrypted mail 
communication. The person used RCube to send/receive mails, but do the 
encryption on a air gaped device and used openpgp to encrypt the files on that 
device and send those encrypted files as attachment named xx.pgp. Those files 
were are not armored. 

RCube interpreted those attachments as text/PGP instead of application/octet-
stream. So it is not a client that used those content-type but a php mimetype 
parser function that returned text/pgp for an encrypted data blob.

Because I didn't wanted to use the commandline too - I added the support to 
handle text/pgp successfully.

Regards,

hefee

PS: a sample:

Subject: ...
X-PHP-Originating-Script: 1008:rcube.php
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="BBBBB"
Date: Sat, 25 Feb 2017 01:12:34 +0000
From: mail at rcube.example
Message-ID: <XXX at rcube.example>
X-Sender: mail at rcube.example
User-Agent: Roundcube Webmail/1.1.7

--BBBBB
Content-Transfer-Encoding: base64
Content-Type: text/PGP;
 name=test.text.pgp
Content-Disposition: attachment;
 filename=test.text.pgp;
 size=1890

ENCRYPTEDCONTENTBASE64ENCODED
--BBBBB--
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20250827/a63999a4/attachment.sig>