Comment # 5 on bug 1093836 from Manfred Hollstein

(In reply to Andreas Stieger from comment #3)
> (In reply to Manfred Hollstein from comment #0)
> > When I click on an encrypted message received from someone whose public 
> > key is already stored in my keyring, I now only see the following:
> > 
> >   Enigmail: Error - no matching secret found to decrypt message
> 
> Someone's public key has nothing to do with decryption. The problem is
> locating the secret key to decrypt the message, usually your own.
> 
> > From reading the enigmail's changelog, it may be
> > caused by the old gpg2 version (2.0.24-8) available on Leap 42.3.
> 
> Which changelog entry is that exactly, please?

<https://www.enigmail.net/index.php/en/download/changelog#enig2.0> where it
talks about:

  Support for Web Key Directory (WKD) is implemented. Enigmail will try to
download unavailable keys during message composition from WKD. If you use GnuPG
2.2.x, and your provider supports the Web Key Service protocol, you can also
use Enigmail to upload your key to WKD.

which is just *some* reference (admittedly out of scope) to gpg-2.2