mu verify --use-agent --decrypt error

[Fr. John Jenkins]

Hello everyone on the list.

I am very happy with the mu program and mu4e. However recently I discovered a minor problem with encrypted messages. They no longer show up, but only state "Decryption: 1 parts(s) failed". It is obvious that it attempts to decrypt it automatically but times out [the viewing buffer locks for several seconds on selecting the message].

I did some research and tried on the command line:

mu verify --use-agent --decrypt [raw email file in ~/Maildir]

It then gives me the following error:

Password requested for *****@****** (you need a passphrase to unlock the key for user: ****).
mu: error decrypting part: failed to get password
verdict: no signature found.

What is strange is that to encrypt an email I don't have any problems. My gpg keys are usually unlocked at login. I can encrypt files using gpg without any difficulties. The agent program is running and I can connect to it with gpg-connect-agent.

I set up GNUS and I can read the emails fine, it asks me if I want to decrypt the part and it shows it too me. Obviously GNUS has no problems with this.

Also, if I look at the raw message in mu4e (with '.') I can do M-x epa-mail-decrypt and it works perfectly.

Thus it seems there is something not right in mu4e as it times out - I think in waiting for the password. The automatic decryption is perhaps waiting for a password? but it doesn't ask me for one either.

How to set out to debug this problem? I have setq epg-debug to t but I don't get any debugging buffer. I also have the latest mu (0.9.17). I have looked at one thread that speaks about this, but it seems that the problem was fixed by a patch. However I am using the latest version and this problem seems a bit different.

To have messages decrypted automatically is quite necessary. I don't want to go back to GNUS but I might have to if I can't figure this out.

[Dirk-Jan C. Binnema]

Hi Fr John,

Sorry for the somewhat belated reply.

If gnus can do, it suppose mu4e should be able to do it as well... can
you file an issue at the github issue tracker? Then we won't
forget.

Most of the above is already good information to put there, but please
add the versions of mu/mu4e you are using -- thanks!

Kind regards,
Dirk.

--
Dirk-Jan C. Binnema Helsinki, Finland
e:dj...@djcbsoftware.nl w:www.djcbsoftware.nl
pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C