Your message dated Tue, 14 Feb 2017 12:49:32 +0100
with message-id <[email protected]>
and subject line Re: Bug#849762:  mutt: complains about GPGME
has caused the Debian Bug report #849762,
regarding mutt: complains about GPGME
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
849762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849762
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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 headless server or on a GUI desktop.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(150, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0+ (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages mutt depends on:
ii  libassuan0        2.4.3-2
ii  libc6             2.24-8
ii  libcomerr2        1.43.3-1
ii  libgnutls30       3.5.7-3
ii  libgpg-error0     1.26-1
ii  libgpgme11        1.8.0-3
ii  libgssapi-krb5-2  1.15-1
ii  libidn11          1.33-1
ii  libk5crypto3      1.15-1
ii  libkrb5-3         1.15-1
ii  libncursesw5      6.0+20161126-1
ii  libnotmuch4       0.23.4-1
ii  libsasl2-2        2.1.27~101-g0780600+dfsg-1
ii  libtinfo5         6.0+20161126-1
ii  libtokyocabinet9  1.4.48-11

Versions of packages mutt recommends:
ii  libsasl2-modules  2.1.27~101-g0780600+dfsg-1
ii  locales           2.24-8
ii  mime-support      3.60

Versions of packages mutt suggests:
ii  aspell                                     0.60.7~20110707-3+b1
ii  ca-certificates                            20161130
ii  exim4-daemon-light [mail-transport-agent]  4.88-2
ii  gnupg                                      2.1.17-2
pn  mixmaster                                  <none>
ii  openssl                                    1.1.0c-2
pn  urlview                                    <none>

Versions of packages mutt is related to:
ii  mutt  1.7.1-5

-- no debconf information

--- End Message ---
--- Begin Message ---
* 積丹尼 Dan Jacobson <[email protected]> [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

as mentioned in https://github.com/neomutt/neomutt/issues/398

The manpage has to be adapted accordingly. One has to file a
sepearted bug for that.

Elimar
 One has to file a sepearted bug for that.-- 
  "Talking much about oneself can also
   be a means to conceal oneself."
         -Friedrich Nietzsche

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to