On Tue, Sep 20, 2016 at 10:51:01AM +0200, Christian Pietsch wrote:
> Dear Maintainer,
>
>* What led up to the situation?
>
> Version 1.7.0-5 enabled GPGME for PGP handling by default.
>
>* What exactly did you do (or not do) that was effective (or
> ineffective)?
>
> After
On Tue, Sep 20, 2016 at 02:58:48PM +0200, Christian Pietsch wrote:
> On Tue, Sep 20, 2016 at 10:02:13AM +, Antonio Radici wrote:
> > In this particular case I believe that the behavior is the correct one,
> > once we
> > switched to gpgme all pgp_* commands are ignored, if people want to
Control: forwarded -1 http://bugs.mutt.org/2973
Control: tag -1 +confirmed upstream
On Tue, Sep 20, 2016 at 10:02:13AM +, Antonio Radici wrote:
> In this particular case I believe that the behavior is the correct one, once
> we
> switched to gpgme all pgp_* commands are ignored, if people want to encrypt to
> themselves, then they should use the proper configuration option
Control: tag -1 +pending
On Tue, Sep 20, 2016 at 10:51:01AM +0200, Christian Pietsch wrote:
> Package: mutt
> Version: 1.7.0-5
> Severity: normal
>
> Dear Maintainer,
>
>* What led up to the situation?
>
> Version 1.7.0-5 enabled GPGME for PGP handling by default.
>
>* What exactly
Package: mutt
Version: 1.7.0-5
Severity: normal
Dear Maintainer,
* What led up to the situation?
Version 1.7.0-5 enabled GPGME for PGP handling by default.
* What exactly did you do (or not do) that was effective (or
ineffective)?
After updating to version 1.7.0-5, when I sent an
6 matches
Mail list logo