Re: Failing pim/messagelib tests for text/pgp data

--nextPart27024894.1r3eYUQgxm
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Ingo =?UTF-8?B?S2zDtmNrZXI=?= <[email protected]>
To: KDE PIM <[email protected]>
Cc: Sandro =?UTF-8?B?S25hdcOf?= <[email protected]>
Subject: Re: Failing pim/messagelib tests for text/pgp data
Date: Sun, 24 Aug 2025 20:13:30 +0200
Message-ID: <4983270.OV4Wx5bFTl@daneel>
In-Reply-To: <6016692.zQ0Gbyo6oJ@tuxin>
References: <3211802.KVeVyVuyWN@daneel> <6016692.zQ0Gbyo6oJ@tuxin>
MIME-Version: 1.0

On Donnerstag, 21. August 2025 23:09:07 Mitteleurop=C3=A4ische Sommerzeit S=
andro=20
Knau=C3=9F wrote:
> > @Sandro: Do you know of any clients that create such messages? I guess =
all
> > sensible clients produce proper OpenPGP/MIME messages nowadays.
>=20
> Nope I don't know any client but I normally do not track the clients  - I
> only have a look if anything goes wrong ;)
>=20
> Did you check the git history, when this test was introduced you should
> properly find a bug with the relevant information.

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

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

Regards,
Ingo
--nextPart27024894.1r3eYUQgxm
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iJEEABYKADkWIQTbjgIOMowwlCBgvyGxb1mVFkdKugUCaKtWShsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMSwyLDIACgkQsW9ZlRZHSrr1BwD/RP7R3VObNioLX4kLeQEP
7Vys+SjCvds9LKugEFBumX8A/3KnXvwEi+2F0WGZjHrf9yxhjEyq0KfpgCcjP4oV
98wL
=fU8s
-----END PGP SIGNATURE-----

--nextPart27024894.1r3eYUQgxm--