Re: GPGME S/MIME expired flag support?

"Kevin J. McCarthy" <[email protected]> Wed, 8 Jul 2026 11:23:07 +0800
Newsgroups gmane.mail.mutt.devel
Message-ID <[email protected]>
--sXhBCicmX9ozLVgM
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 07, 2026 at 09:21:37PM +0200, Robert J=C3=A4schke via Mutt-dev =
wrote:
>Dear Kevin,
>
>Am 04.07.2026 schrieb Kevin J. McCarthy:
>> >          if (key->expired)
>> >            flags |=3D KEYFLAG_EXPIRED;
>> >
>> > to the corresponding S/MIME loop and it works as expected (although the
>> > option pgp_show_unusable seems to be ignored but I have to further che=
ck
>> > that).
>>
>> I'm glad that is working.  That's good in that it means the S/MIME GPGME
>> backend flags are set.  So it's just a matter of hooking them up.
>
>OK. So I can produce a patch for that, however:

Just FYI I added the flags already in commit 4fc103f0.

--=20
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA

--sXhBCicmX9ozLVgM
Content-Type: application/pgp-signature; name=signature.asc

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

iQIzBAEBCgAdFiEEiXWpszqjeRA4XFMIre92hIAxa9oFAmpNwpsACgkQre92hIAx
a9o7zxAAsXiB3BjCqL6hzQmByxhvlsq+qbVrAMZ7OTbn2twu3S6cQzUCobygi73B
SMJ3nU2ub2045Bfd2stNZNzfzOzsszBkd792nHCpHHLiqX/HEGFsPaP8xTp2yNYr
hF+DdP+iwOatVXrw23PLKx8wG5LPN2REsRgQfA9OpoqrQj7e3A9zchYC5NdJ4BBa
3/dyqHIBuIxxvdh7rQOOJ8wXneRmDNWPmJJSRooKTAW26NR9Jvcf/x/XhtHRsdQ+
bdV4YJSdHs+cAHo59q5MWiscrHajQSu+kEBpHlpyIahq68Ald0Jc1/4RUe/4Unp5
J8dOVqtGQDVQHwsT8y/0Ea4dRvlEredEt7jwQkSlZO9dGfPelYBzghD0c1CO/Fbk
R5d45e1iaqcKDRoxFxAcLAjumeisnuBZftFvCoXBSqGKlkMITcdU4AFnh35BpO1A
qXr+0YZPBPx9ELHYzNmH8SKgvA3361cxYE0JMdPIBlrZcoEdLOK4oNWy9S2GbFk8
ehfRvp8CoOzszKndBdWxDG/gVzi0GrFDXVPVy+HYNHBwRb4pXXAtqtEf58K8vmMV
XCnfMVT27pGaKAt19FTmpCvbhJJ+wthpnHKLPYUi4aGziUTxcnlqtnLHRcjP7Vlr
AHfSpyY5fMSWEJYnWOhKRVOv/07udkBKEqN3Ol9QhBixnjDye2Q=
=oQ45
-----END PGP SIGNATURE-----

--sXhBCicmX9ozLVgM--