On Wed, Mar 21, 2018 at 10:56:22AM -0700, Kevin J. McCarthy wrote:
> If you feel comfortable patching and testing, I'd appreciate to know if
> that fixes it for you. Regardless, I will take a closer look and apply
> that patch myself later today.
Hi Michael,
I'm attaching a patch that's just a
On Wed, Mar 21, 2018 at 02:14:00PM +0100, Michael Tatge wrote:
> * On Wed, Mar 21, 2018 12:45PM +0100 I (tatg...@gmail.com) muttered:
> > TL;DR i cannot decrypt messages that are encrypted for me.
> > Mutt 1.9.4 (2018-02-28) (debian package from testing)
>
> FWIW, tested against
> Mutt 1.9.4+99
* On Wed, Mar 21, 2018 12:45PM +0100 I (tatg...@gmail.com) muttered:
> TL;DR i cannot decrypt messages that are encrypted for me.
> Mutt 1.9.4 (2018-02-28) (debian package from testing)
FWIW, tested against
Mutt 1.9.4+99 (e250c602) (2018-03-15)
too. Same problem.
Michael
--
PGP-Key-ID:
Hi,
i'm trying to run mutt with s/mime and
$crypt_use_gpgme set, but i keep running into errors when it comes to
decryption. Signing / verifying works ok.
TL;DR i cannot decrypt messages that are encrypted for me.
[-- Begin signature information --]
Good signature from:
* Heinz Diehl [03-21-18 02:19]:
> On 13.03.2018, Moritz Barsnick wrote:
>
> > That's probably why these two mails slipped though my procmail filters.
> > Am I the 0.01 % still using that?
>
> Nope. Procmail rocks :-)
>
> > Would it be asking a lot to request an
On 13.03.2018, Moritz Barsnick wrote:
> That's probably why these two mails slipped though my procmail filters.
> Am I the 0.01 % still using that?
Nope. Procmail rocks :-)
> Would it be asking a lot to request an automatic "[mutt-dev] " subject
> prefix? It really makes identifying the