Bug#849762: [Pkg-mutt-maintainers] Bug#849762: closed by Elimar Riesebieter <riese...@lxtec.de> (Re: Bug#849762: mutt: complains about GPGME)

* Adam Borowski [2017-02-16 01:19 +0100]: > On Tue, Feb 14, 2017 at 11:51:11AM +, Debian Bug Tracking System wrote: > > * 積丹尼 Dan Jacobson [2017-02-14 07:50 +0800]: > > > No workarounds either perhaps. > > >

Bug#849762: closed by Elimar Riesebieter <riese...@lxtec.de> (Re: Bug#849762: mutt: complains about GPGME)

On Tue, Feb 14, 2017 at 11:51:11AM +, Debian Bug Tracking System wrote: > * 積丹尼 Dan Jacobson [2017-02-14 07:50 +0800]: > > No workarounds either perhaps. > > https://github.com/neomutt/neomutt/issues/398 > > > crypt_use_gpgme=yes is set by default in

Bug#849762: mutt: complains about GPGME

* 積丹尼 Dan Jacobson [2017-02-14 07:50 +0800]: > No workarounds either perhaps. > https://github.com/neomutt/neomutt/issues/398 crypt_use_gpgme=yes is set by default in /etc/Muttrc.d/gpg.rc. Users which don't use gpg can avoid the message by setting: set crypt_use_gpgme=no

Bug#849762: mutt: complains about GPGME

Version: 1.7.2-1 Hi. Adam Borowski: > Package: mutt > Version: 1.7.1-5 > Severity: normal > > Hi! > Every time stretch's mutt is started, it says: > GPGME: CMS protocol not available This message may seem harmless and only annoying, and as such get low priority. Unfortunately, it also happens

Bug#849762: mutt: complains about GPGME

Package: mutt Version: 1.7.1-5 Followup-For: Bug #849762 Hi, Mutt is printing this warning for me as well, but unlike OP, I do have gpg configured inside my mutt.rc for having my password encrypted. In my case, I have to enter passwords when launching mutt to enter my GMail Imap account, and

Bug#849762: mutt: complains about GPGME

Package: mutt Version: 1.7.1-5 Severity: normal Hi! Every time stretch's mutt is started, it says: GPGME: CMS protocol not available I have not a single gpg related option in .muttrc; despite that error message all gpg functionality (signing, encrypting, decrypting) works fine. Same on a