On 10 Nov 2017, at 9:06, Benny Kjær Nielsen wrote:

On 10 Nov 2017, at 11:50, Robert M. Münch wrote:

The sender uses GnuPG v2. The message shows up still encrypted, which is fine.

Why is this fine? IMO if the message can be encrypted by the command line tools, MM should be able to do it too.

When the command line behaves differently then make sure it's the same `gpg2` command used:

        which gpg2

The one used by MailMate is here:

        /usr/local/MacGPG2/bin/gpg2

To see exactly how MailMate calls `gpg2` you can enable a debug variable:

        defaults write com.freron.MailMate MmDebugSecurity -bool YES

Then launch from a Terminal window:

        /Applications/MailMate.app/Contents/MacOS/MailMate

I hope this helps.

I have this in my configuration:
```
    environmentVariables =     (
                {
            enabled = ":true";
            name = "MM_GPG";
            value = "/opt/local/bin/gpg";
        }
    );
```
and it works fine to invoke the `gpg` that I have as part of MacPorts. Note that it *does* behave differently, if you are used to Enigmail. Seems like Enigmail was more permissive about trust, which took some getting used to, but this works fine for me (I had found that having MacGPG2 *and* MacPorts gpg installed on the same machine gave odd and unhappy results).

HtH,
r
_______________________________________________
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate

Reply via email to