disable gpg in mutt

[Fourhundred Thecat]

 > On 2021-08-27 18:17, Kevin J. McCarthy wrote:
> On Fri, Aug 27, 2021 at 07:33:52AM +0200, Fourhundred Thecat wrote:
>>> On 2021-08-26 18:34, Kevin J. McCarthy wrote:
>>
>>  [-- PGP output follows (current time: 2021-08-27T07:31:42 CEST) --]
>>  [-- Error: could not create a PGP subprocess! --]
>
> Double check you are invoking the mutt you reconfigured and compiled.
> Those messages come from a part of the code which isn't compiled when
> configured with --disable-pgp.
>
> Check the output of mutt -v and look for -CRYPT_BACKEND_CLASSIC_PGP and
> -CRYPT_BACKEND_GPGME in the output.

This is strange. I have compiled mutt with "--disable-gpgme", and I can
see that it is no longer linked with the gpg library:

$ ldd /usr/bin/mutt
	linux-vdso.so.1
	libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6
	libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2
	/lib64/ld-linux-x86-64.so.2

But "mutt -v" still shows the CRYPT_BACKEND variables:

$ /usr/bin/mutt -v | grep CRYPT_BACKEND
+CRYPT_BACKEND_CLASSIC_PGP  +CRYPT_BACKEND_CLASSIC_SMIME
-CRYPT_BACKEND_GPGME

and I am sure I am invoking the same mutt, the one that I compiled.

do you understand why?

thank you,