Freron MailMate

Comments and changes to this ticket

• You flagged this item as spam.
  

  TB November 23rd, 2018 @ 05:55 PM

  This is with Mailmate 1.12.2 (5568) and GPG Tools 2.0 build 887 (according to the System Prefs pane).

  I read through ticket #2092, but I'm still having the same problem. On sending a mail, I get a dialog box that says "Signing or encryption failed for unknown reasons," with "Cancel" or "Send Unencrypted" as the options. Error output (fter launching MM via Terminal) is:

  • - - - - - - - - - - - 8< SNIP! 8< - - - - - - - - - - - - OpenPGP
    gpg2 --no-verbose --batch --no-tty --compliance "openpgp" --status-fd 2 --textmode --armor --recipient "tbyfield@panix.com" --recipient "tedbyfield@gmail.com" --encrypt Input string (7): "\r\n..." Result: Failure Output string (0): "" Detail: gpg: invalid option "--compliance"
  • - - - - - - - - - - - 8< SNIP! 8< - - - - - - - - - - - -

  It's the "--compliance" flag, as others saw, but I have the latest GPG release. Any suggestions would be warmly welcome. Thanks!

• 

  benny December 11th, 2018 @ 01:26 PM

  Sorry about the very late response.

  Are you sure you don't have multiple versions of gpg2 installed. what do these commands tell you:

  which gpg2
  gpg2 --version
  

• You flagged this item as spam.
  

  TB December 11th, 2018 @ 01:52 PM

  Thanks, Benny — Does it look like I do?

  • - - - - - - - - - - - 8< SNIP! 8< - - - - - - - - - - - - USER$ which gpg2
    /usr/local/bin/gpg2 USER$ gpg2 --version
    gpg: keyserver option 'ca-cert-file' is obsolete; please use 'hkp-cacert' in dirmngr.conf
    gpg: keyserver option 'debug' is unknown
    gpg: keyserver option 'verbose' is unknown
    gpg (GnuPG) 2.2.11
    libgcrypt 1.8.4
    Copyright (C) 2018 Free Software Foundation, Inc.
    Home: /Users/USER/.gnupg
    Supported algorithms:
    Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
    Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
    CAMELLIA128, CAMELLIA192, CAMELLIA256 Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
    Compression: Uncompressed, ZIP, ZLIB, BZIP2USER$
    
  • - - - - - - - - - - - 8< SNIP! 8< - - - - - - - - - - - -
• 

  benny December 11th, 2018 @ 03:04 PM

  That looks ok, but you have some strange errors there you should look into. Maybe it's somehow related:

  gpg: keyserver option 'ca-cert-file' is obsolete; please use 'hkp-cacert' in dirmngr.conf  
  gpg: keyserver option 'debug' is unknown  
  gpg: keyserver option 'verbose' is unknown
  

  Also, this is where MailMate expects to find gpg2: /usr/local/MacGPG2/bin/gpg2

  (MailMate isn't very flexible in this regard yet.)

• You flagged this item as spam.
  

  TB December 11th, 2018 @ 03:10 PM

  Yes. This doesn't solve the problem — that's for me to do, not you — but it's extremely helpful. Once again, it's a treat to use Mailmate, so thank you Benny.

• 

  benny December 14th, 2018 @ 09:56 AM

  • State changed from “new” to “cantreproduce”

  That wasn't 100% clear to me. Let me know if you think MailMate is doing something wrong?

• You flagged this item as spam.
  

  TB December 14th, 2018 @ 12:29 PM

  !!! Zero irony intended. I can't focus on trying to solve this right now, but I wanted to take it off your queue and thank you.

• 

  benny December 14th, 2018 @ 02:38 PM

  Thanks for the clarification :)

• You flagged this item as spam.
  

  Patrice Lazareff October 31st, 2019 @ 01:05 PM

  Hello,

  Having the same issue, and if I follow the instructions as per GNUPG instructions at
  https://www.gnupg.org/documentation/manuals/gnupg/Compliance-Option...

  It seems that the --compliance "openpgp" should in fact be --openpgp

  The odd thing in my case is that the problem arose apparently out of nowhere as I did not update anything before it showed up :-/ (or maybe I did unknowingly... Mac OS 10.14.6 or Mailmate seem the most recent ones)

  [EDIT] : in fact, I misread the DOC but it clearly states that : « --compliance string This option can be used instead of one of the options above. Valid values for string are the above option names (without the double dash) and possibly others as shown when using "help" for value. » so the commend line should be --compliance openpgp and not --compliance "openpgp" :-)

  [EDIT-2] I just tried the command line without double quotes but it does not work either :

  Mac-mini:~ patrice$ /usr/local/bin/gpg --no-verbose --batch --no-tty --compliance openpgp --status-fd 2 --textmode --armor --local-user "<test@example.com>" --detach-sign
  gpg: Invalid option "--compliance"
  

  where --openpgp yields no error :
  

  Mac-mini:~ patrice$ /usr/local/bin/gpg --no-verbose --batch --no-tty --openpgp --status-fd 2 --textmode --armor --local-user "<test@example.com>" --detach-sign
  [GNUPG:] USERID_HINT ...SNIP...
  [GNUPG:] NEED_PASSPHRASE ...SNIP...
  gpg: impossible de demander la phrase de passe en mode automatique
  [GNUPG:] MISSING_PASSPHRASE
  [GNUPG:] BAD_PASSPHRASE...SNIP...
  gpg: « <test@example.com> » a été ignoré: mauvaise phrase de passe
  gpg: signing failed: mauvaise phrase de passe
  

  [EDIT 3] I found the issue. I had an old version of gpg in /usr/local/bin that seemed to have precendence over /usr/local/MacGPG2/bin/gpg

  Sorry for the multiple edits, I just hope it may help someone :-)

  Kind regards,
  p@T