mutt and S/SMIME

[isdtor]

Kevin J. McCarthy writes:
> On Sun, Jun 14, 2020 at 12:20:22PM +0100, isdtor wrote:
> >Two questions remain now. The first, when using mutt with gpgme, are 
> >any of the gpg/gpg/certificate/smime related configuration variables 
> >still relevant? And if so, which? The question arises from this 
> >comment,
> 
> I don't use S/MIME myself, although I've made some fixes and 
> improvements to the code.  So I'll leave it to others discuss practical 
> usage.
> 
> When using GPGME, most of the $smime_* config variables are not used.  I 
> believe the only relevant ones are:
[...]

Thanks, Kevin, that makes perfect sense - any options that detail commands etc. are not relevant, top level and UI settings still are.

My research has also unearthed the final piece in the puzzle, how to send S/MIME encrypted email in a corporate environment when the recipient's key is not in the keybox. The answer is: LDAP query for the recipient's userCertificate attribute in AD, save in PEM format and import with gpgsm. PEM is the best option if the certificate data is provided in base64 format (I don't think other formats are supported in AD anyway, but I'm not an expert).