On 22 Jan 2025, at 10:06, akierig wrote:
> if you install gnupg2 with MacPorts, ie., the current standard version of
> GPG/PGP/whatever-the-hell-its-called, it installs to /opt/local/bin/gpg.
> There's nothing stopping you from just doing something like sudo ln -s
> $(which gpg) /usr/local/bin/
On 2025-01-21 (KW 04) at 15:52:07 (-0600) Ben Hyde wrote:
1. “Gpg” eh? What about “gpg2” … my memory is that last
time I did this I used gpg2.
2. “/usr/local/bin” eh? I thought the brew folks moved to
/opt/homebrew/bin on Apple Silicon.
3. I seem to remember solving this, at last once, with a
Hi,
Interesting points made by everybody — I just looked at my setup and I found
that I actually have (and use both). That is, the GPG Suite (which is very
useful on occasion for its key management tool, if nothing else) and the
command line tools from Homebrew. This gives me `/usr/local/bin/gp
+1 for GPG Suite by GPGTools, works like a charm with MailMate. Do use Homebrew
to install it. With the cask `gpg-suite-no-mail`, you get the free version
without the Apple Mail plugin (which I suppose you don’t need since you have
MailMate).
On 21 Jan 2025, at 23:07, Eric Sharakan via mailmate
Hi Oliver, FWIW I get my 'gpg' utility and related tools from
https://gpgtools.org, rather than Homebrew. It all just works with
MailMate, no need for symlinks or other workarounds.
This is what it reports about itself:
```
esharaka% where gpg
/usr/local/bin/gpg
/usr/local/MacGPG2/bin/gpg
esha
Oliver, thanks for looking at my problem. More details follow. That
said I sense the answer to my question is “Nope there isn’t…”
I get emails from many vintage correspondents who sign all their emails.
That triggers MailMate to complain it can’t find the
/usr/local/bin/gpg. That opens pop
I’m moving over to a new M2 Mac. So PGP encryption stopped working.
I see plenty of discussion about this the archives of this esteemed mailing
list.
Is this documented some place? - ben
___
mailmate mailing list
Unsubscribe: https://lists.freron.co
Thanks. That worked.
On 22 Oct 2023, at 14:09, Robert Goldman wrote:
The GPG bundle has strong assumptions about where it will find the gpg
command and does not (AFAIK) use your `PATH`. If I recall correctly
(please check this!) it expects to find gpg in `/usr/local/bin/` and
recent versions
The GPG bundle has strong assumptions about where it will find the gpg
command and does not (AFAIK) use your `PATH`. If I recall correctly
(please check this!) it expects to find gpg in `/usr/local/bin/` and
recent versions of MacPorts and Homebrew do _not_ put it there. Adding a
symlink shoul
I get messages occasionally that have gpg encoded contents. When that happens I
get a warning “OpenPGP: Unable to locate the command (gpg) needed to work with
an OpenPGP message”.
I have gpg installed, it is available from shell command line (macOS). Per the
instructions I’ve installed pinentry
Very old topic, but still relevant. Has anybody an idea how to get rid of the
ASC attachment containing the GPG/PGP signature? Robert
On 26 Nov 2020, at 12:42, Robert M. Münch wrote:
> Hi Benny, is there any chance to use the standard PGP mail structure with:
>
> ```
> BEGIN PGP SIGNED MESSA
Hi Stephan
I’m wondering if the variable response to your message’s signature could be
related to it’s being considered expired (at least at the time I last updated
from the server).
Mailmate supplied diagnostics on your original message—
/usr/local/bin/gpg --no-verbose --batch --no-tt
I did search the keyserver using your name, and the key wasn't found,
but when I searched by your email address, it did find and download it.
-Eric
On 24 Apr 2022, at 17:36, Stephan Bösebeck wrote:
Hi Eric,
thanks for checking. But no, you need to open GPG Keychain (part of
gpg suite, click
Hi Eric,
thanks for checking. But no, you need to open GPG Keychain (part of gpg suite,
click on "search for key") and add the key first. My key should be available in
most of the keyservers though ;-)
Problem is, that MailMate does not automatically download any keys (how should
it?), as this
Hi Stephan, I do have GPGSuite installed (2022.1), and your emails
generate a red banner at top that says:
OpenPGP: No public key could be found for verifying the message
signature
I think that might be part of your problem.
-Eric
On 24 Apr 2022, at 17:21, Stephan Bösebeck wrote:
Just an a
Just an addition: when reading my last email in canaryMail for iOS (or Mac) it
states "invalid signature".
On 24 Apr 2022, at 23:17, Stephan Bösebeck wrote:
> Hi Henry,
>
> because the mail for this mailinglist was not encrypted, it was only signed.
> So you can check, if the mail was tempere
Hi Henry,
because the mail for this mailinglist was not encrypted, it was only signed. So
you can check, if the mail was tempered with on the way to you or if it is the
same, as I sent it.
You cannot encrypt an email to more than one recipient with PGP. you'd have to
encrypt it for every recip
Stephen,
So, why can I read it, without OpenPGP installed?
Respectfully,
Henry Seiden
- -
Techworks Pro Co.
E: infotechworksprocom
W: http://techworkspro.com
On 24 Apr 2022, at 17:08, Stephan Bösebeck wrote:
Hi Henry,
in your case, the GPG-Support seems not to be installed on your mac.
You
Hi Henry,
in your case, the GPG-Support seems not to be installed on your mac. You need
to install GPGSuite for GPG to work.
if it works, the banner should be green with the text: `OpenPGP: This message
is trusted to have been signed by the sender (EMAIL).`
So, unfortunately, your error is not
Hey Stephan,
Funny, but I get the same message in Mailmate on this message, even
though it seems I can read (all of) the contents?!?
Your message shows the following banners at top, which says, “OpenPGP
unable to locate the command (gpg) needed…” (in red background)
And the banner below that, “
Hi,
I have some trouble using the GPG encryption support in MailMate. I'll try to
explain:
I created an encrypted email, sent it to me and tried to decrypt it on iOS
using different mechanisms, iPGMail and CanaryMail - both worked fine.
I tried the same with an encrypted and signed Email and bo
> I'm experimenting with GPG. I successfully encrypted a message to
> myself, and received it okay, but all I see is a green banner saying
> "Successfully decripted OpenPGP message."
>
> Where is the decrypted version?
maybe you need to View/MessageBodyParts/...?
_
I'm experimenting with GPG. I successfully encrypted a message to
myself, and received it okay, but all I see is a green banner saying
"Successfully decripted OpenPGP message."
Where is the decrypted version?
Martin S Taylor
___
mailmate mailing list
On 15 Jan 2021, at 8:34, Jolin Warren wrote:
On 15 Jan 2021, at 5:48, Bill Cole wrote:
The explanation is long and it's late, so here's a link to something
I worked out some time back:
https://lists.freron.com/mailmate/2015-April/004195.html
Following that thread through shows a possible so
On 15 Jan 2021, at 5:48, Bill Cole wrote:
The explanation is long and it's late, so here's a link to something
I worked out some time back:
https://lists.freron.com/mailmate/2015-April/004195.html
Following that thread through shows a possible solution for Steven,
provided by Benny. There’s
On 14 Jan 2021, at 19:50, Steven M. Bellovin wrote:
This worked but raises more questions.
I verified that I could find gpg from the shell. In other words, it
was in my $PATH. I then fired up MailMate from an iTerm2 window—
and it still couldn't find gpg. However, the symlink in /usr/local/bin
This worked but raises more questions.
I verified that I could find gpg from the shell. In other words, it
was in my $PATH. I then fired up MailMate from an iTerm2 window—
and it still couldn't find gpg. However, the symlink in /usr/local/bin
did work. This suggests that either MailMate or someth
Probably, whatever method you're using to set your path (shell startup files?)
is not making it through to Mailmate.
A couple minutes of searching doesn't show me how to set the environment on my
actual login session.
If I were in your shoes I'd symlink gpg into /usr/local/bin; Mailmate wil
When I receive signed messages, MailMate 5757 (on Big Sur) says
"OpenPGP: Unable to locate the command (gpg) needed". However, it is
there:
$ which gpg
/usr/local/MacGPG2/bin/gpg
I installed the gpgtools (this is a fresh installation of it and
MailMate on a new laptop, though
Is there any chance to past the signature below the email instead of having it
attached?
I have a lot of recipients in the business world that try to open the
attachment and don’t know what to do with it.
--
Robert M. Münch
signature.asc
Description: OpenPGP digital signature
__
I installed the GPG Suite from https://gpgtools.org.
I did a custom install and deselected GPG Mail, as that's not needed for
MailMate.
-Eric
On 27 Jun 2020, at 20:55, Steve wrote:
Hi Thomas,
You'll just need to have gpg installed, as this is an issue with
Mailmate trying to verify my gpg
On 17 Apr 2020, at 0:10, Philip Paeps wrote:
On 2020-04-17 11:46:05 (+0800), Steven M. Bellovin wrote:
On 16 Apr 2020, at 22:20, Philip Paeps wrote:
On 2020-04-12 12:04:50 (+0800), Steven M. Bellovin wrote:
I found at least part of the problem: I’m running gpg via
homebrew, and it doesn’t u
On 2020-04-17 11:46:05 (+0800), Steven M. Bellovin wrote:
On 16 Apr 2020, at 22:20, Philip Paeps wrote:
On 2020-04-12 12:04:50 (+0800), Steven M. Bellovin wrote:
I found at least part of the problem: I’m running gpg via
homebrew, and it doesn’t understand the —compliance option. Is
there a w
On 16 Apr 2020, at 22:20, Philip Paeps wrote:
On 2020-04-12 12:04:50 (+0800), Steven M. Bellovin wrote:
I found at least part of the problem: I’m running gpg via homebrew,
and it doesn’t understand the —compliance option. Is there a
workaround? (Aside: it would be nice if MailMate captured std
On 2020-04-12 12:04:50 (+0800), Steven M. Bellovin wrote:
I found at least part of the problem: I’m running gpg via homebrew,
and it doesn’t understand the —compliance option. Is there a
workaround? (Aside: it would be nice if MailMate captured stderr from
gpg invocations.)
I'm also running g
I found at least part of the problem: I’m running gpg via homebrew, and it
doesn’t understand the —compliance option. Is there a workaround? (Aside: it
would be nice if MailMate captured stderr from gpg invocations.)
--Steve Bellovin
Sent from an electronic toy.
> On Apr 11, 2020, at 3:12 PM,
I'm on the 2.0beta track, because of some odd problems a few
years ago…
On 11 Apr 2020, at 23:20, Denis Ricard via mailmate wrote:
Where are you getting these versions? I thought I was getting alpha
builds but I’m only getting 5682! You’re 466 versions ahead of me?
You’re really living the edg
Where are you getting these versions? I thought I was getting alpha
builds but I’m only getting 5682! You’re 466 versions ahead of me?
You’re really living the edge!
On 11 Apr 2020, at 22:21, Steven M. Bellovin wrote:
FWIW, 6147 works just fine for me. I just discovered that it is
having trou
On 11 Apr 2020, at 21:49, Bill Cole wrote:
On 11 Apr 2020, at 15:12, Steven M. Bellovin wrote:
MailMate Build 6146 is unable to send GPG-encrypted or signed email,
and it can't decrypt stuff sent to me. It says
Unable to decrypt OpenPGP message.
Verify that you have the key n
On 11 Apr 2020, at 15:12, Steven M. Bellovin wrote:
MailMate Build 6146 is unable to send GPG-encrypted or signed email,
and it can't decrypt stuff sent to me. It says
Unable to decrypt OpenPGP message.
Verify that you have the key necessary for decryption.
FWIW, 6147 works j
> MailMate Build 6146 is unable to send GPG-encrypted or signed email,
> and it can't decrypt stuff sent to me.
i am at Version 1.13.1 (5671) and can not repro; i.e. it works
randy
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.frer
MailMate Build 6146 is unable to send GPG-encrypted or signed email, and
it can't decrypt stuff sent to me. It says
Unable to decrypt OpenPGP message.
Verify that you have the key necessary for decryption.
"Show Details" just gives a blank box. However, if I ⌘C the message
and
On 28 May 2019, at 21:57, Mark Allman wrote:
So, I checked and sure enough I have /usr/local/bin/gpg and it seems
to work from the command line.
It might point to the wrong location. Try this:
ls -al /usr/local/bin/gpg
/usr/local/bin/gpg --version
I suggest you try to delete
Hi!
I upgraded to 1.12.5 this morning (under macOS 10.14.5). Now, every
time I try to send an email I get an error dialog that says:
OpenPGP signing failed
The following details might help you fix the problem:
Signing or encryption failed for unknown reasons.
Any idea why?
I see the f
On 26 Sep 2016, at 16:22, Richard Rettke wrote:
On 26 Sep 2016, at 9:05, Sean Johnson s...@ttys0.net wrote:
That is actually helpful. It shows that MailMate appears to update
the view twice every time - losing the OpenPGP banner temporarily.
Just an FYI, I too see the same flickering. I hav
On 26 Sep 2016, at 9:05, Sean Johnson s...@ttys0.net wrote:
That is actually helpful. It shows that MailMate appears to update the
view twice every time - losing the OpenPGP banner temporarily.
Just an FYI, I too see the same flickering. I have not had an
opportunity to test with signing off
Do you also see flickering if signing/encryption is disabled?
Yep, unfortunately.
https://ttys0.net/images/Preview_Pane_Flicker_Without_GPG.mov
On 24 Sep 2016, at 7:24, Benny Kjær Nielsen wrote:
On 24 Sep 2016, at 2:45, Sean Johnson wrote:
Let me know if you find some pattern to this beh
On 24 Sep 2016, at 2:45, Sean Johnson wrote:
Let me know if you find some pattern to this behavior…
It’s whenever the preview pane is up. I’ve tried changing
different styles and whatnot, but to no avail.
It's not related to that.
Just so you can see what it looks like, here’s a screen cap
At some point I need to look into this, but it's not going to be soon.
No worries. It’s just a cosmetic thing. I’ve disabled the preview
pane by default for the time being. :)
Let me know if you find some pattern to this behavior…
It’s whenever the preview pane is up. I’ve tried changing d
On 22 Sep 2016, at 0:51, Sean Johnson wrote:
Typically I leave the preview pane visible at the bottom of the
compose window so I can see how things will look as I’m going along.
I also use GPG, which works fine for signing, etc. The problem is that
while typing the green bar for the “Trusted s
Typically I leave the preview pane visible at the bottom of the compose window
so I can see how things will look as I’m going along. I also use GPG, which
works fine for signing, etc. The problem is that while typing the green bar for
the “Trusted signature for OpenPGP message.” piece keeps flic
On 2 Sep 2015, at 15:17, Philip Paeps wrote:
On 2015-09-01 12:01:04 (+0200), Benny Kjær Nielsen
wrote:
The `gpg2` command uses `gpg-agent` as far as I understand, but to be
honest I don't know how or if it can be used directly. I also think
GPGMail, more or less, does the same as MailMate (
On 2015-09-01 12:01:04 (+0200), Benny Kjær Nielsen
wrote:
On 31 Aug 2015, at 20:11, Philip Paeps wrote:
Would it be possible for MailMate to rely on gpg-agent if it's
running? The GPGTools package for MacOS X enables the agent at
startup and the GPGMail bundle for Mail.app appears to use i
On 31 Aug 2015, at 20:11, Philip Paeps wrote:
Would it be possible for MailMate to rely on gpg-agent if it's
running? The GPGTools package for MacOS X enables the agent at
startup and the GPGMail bundle for Mail.app appears to use it nicely.
The `gpg2` command uses `gpg-agent` as far as I un
On 2015-08-31 15:38:19 (+0200), Benny Kjær Nielsen
wrote:
On 29 Aug 2015, at 4:33, Christopher LILJENSTOLPE wrote:
I've flipped over to using a yubico neo usb 'smartcard' as my GPG
keychain. It works fine, but there's a problem with MailMate's GPG
support. Everytime the neo gets asked to
On 29 Aug 2015, at 4:33, Christopher LILJENSTOLPE wrote:
I've flipped over to using a yubico neo usb 'smartcard' as my GPG
keychain. It works fine, but there's a problem with MailMate's GPG
support. Everytime the neo gets asked to sign/encrypt a message, I
get prompted for a PIN (that's just
I may be wrong but I believe that's a timeout set by GPG itself. You can
actually change that in
System Preferences -> GPG -> Remember passphrase for [ seconds ]
Hope this helps.
On 29 Aug 2015, at 4:33, Christopher LILJENSTOLPE wrote:
Greeitngs,
I've flipped over to using a yubico neo u
Greeitngs,
I've flipped over to using a yubico neo usb 'smartcard' as my GPG
keychain. It works fine, but there's a problem with MailMate's GPG
support. Everytime the neo gets asked to sign/encrypt a message, I get
prompted for a PIN (that's just the way it works). The problem is that
it
On 11 Sep 2013, at 21:37, Christopher LILJENSTOLPE wrote:
On 11 Sep 2013, at 12:20, Benny Kjær Nielsen wrote:
In your case it means you need to have something like
`".*@cdl\.asgaard\.org"`. Using `.` instead of `\.` would also work
although it's not the same thing.
That worked (after a fash
On 11 Sep 2013, at 20:39, Christopher LILJENSTOLPE wrote:
Since we've been talking about GPG recently, here are two
enhancements/annoyances for thought:
1) Pinentry get's popped up some random time after you start composing
your message. Since this steals focus, all of a sudden, your message
On 11 Sep 2013, at 12:00, Benny Kjær Nielsen wrote:
On 11 Sep 2013, at 20:39, Christopher LILJENSTOLPE wrote:
Since we've been talking about GPG recently, here are two
enhancements/annoyances for thought:
1) Pinentry get's popped up some random time after you start
composing your message.
On 11 Sep 2013, at 21:02, Christopher LILJENSTOLPE wrote:
On 11 Sep 2013, at 12:00, Benny Kjær Nielsen wrote:
It is triggered by the first time the preview is updated. I can
perhaps change this such that the signing/encryption is only done if
explicitly saving the draft (or sending). I'll loo
On 11 Sep 2013, at 12:20, Benny Kjær Nielsen wrote:
On 11 Sep 2013, at 21:12, Christopher LILJENSTOLPE wrote:
Another thing I noticed. I have an e-mail pattern setup for one
account along the lines of *@cdl.asgaard.org. My address here,
mailm...@cdl.asgaard.org matches that. However, when
On 11 Sep 2013, at 21:12, Christopher LILJENSTOLPE wrote:
Another thing I noticed. I have an e-mail pattern setup for one
account along the lines of *@cdl.asgaard.org. My address here,
mailm...@cdl.asgaard.org matches that. However, when I reply to a
message that was sent to that address, I
Greetings,
Since we've been talking about GPG recently, here are two
enhancements/annoyances for thought:
1) Pinentry get's popped up some random time after you start composing
your message. Since this steals focus, all of a sudden, your message
you were typing away at is now being input a
On 8 Sep 2013, at 11:29, Felix Kling wrote:
On 7 Sep 2013, at 23:29, l...@felix-kling.de wrote:
So, the problem seems to be the option `--digest-algo SHA1` (sha1
generates a 160 bit hash). If I remove it, I can sign a file
successfully. This might be because my key is 2048 bit, I don't
really
On 7 Sep 2013, at 23:29, l...@felix-kling.de wrote:
Detail: gpg: DSA key 2ADC63E5 requires a 224 bit or larger hash
Detail: gpg: signing failed: General error
So, the problem seems to be the option `--digest-algo SHA1` (sha1
generates a 160 bit hash). If I remove it, I can sign a file
succe
On 7 Sep 2013, at 23:29, l...@felix-kling.de wrote:
The command that MailMate executes is:
gpg2 --no-verbose --batch --no-tty --openpgp --status-fd 2
--digest-algo SHA1 --textmode --armor --detach-sign --local-user
"<…>"
and the full error message is:
Result: Failure
Output
On 7 Sep 2013, at 22:13, Benny Kjær Nielsen wrote:
You can enable some related debug output from MailMate like this:
defaults write com.freron.MailMate MmDebugSecurity -bool YES
Then launch MailMate from the Terminal to see the output when MailMate
tries to sign a message:
On 7 Sep 2013, at 11:59, l...@felix-kling.de wrote:
On 6 Sep 2013, at 21:31, Benny Kjær Nielsen wrote:
MailMate expects the GPGTools install and is hardcoded to the
location used by GPGTools. Unfortunately GPGTools recently changes
its installer. MailMate expects to find gpg2 here:
Thanks for the quick reply!
On 6 Sep 2013, at 21:31, Benny Kjær Nielsen wrote:
MailMate expects the GPGTools install and is hardcoded to the location
used by GPGTools. Unfortunately GPGTools recently changes its
installer. MailMate expects to find gpg2 here:
/usr/local/bin/gpg2
But
On 6 Sep 2013, at 19:21, l...@felix-kling.de wrote:
I have tried several things but I cannot get MailMate to work with
GPG.
Approach 1: Homebrew (which I prefer)
Approach 2: GPGTools (MacPGP) (I deinstalled the homebrew packages
beforehand)
MailMate expects the GPGTools install and is hardc
Hi,
I have tried several things but I cannot get MailMate to work with GPG.
Approach 1: Homebrew (which I prefer)
I used homebrew to install gnupg2 (which also includes the dependencies
gpg-agent and pinentry). While the applications by themselves work fine
(I can sign files from the command
On 26 Jul 2013, at 12:27, Benny Kjær Nielsen wrote:
On 26 Jul 2013, at 18:30, Christopher LILJENSTOLPE wrote:
I am using GPG signatures, and, occasionally, I will fat-finger my
pass phrase 3 times in a row (it's usually just once or many).
However, after three times, and you get the "invali
On 26 Jul 2013, at 18:30, Christopher LILJENSTOLPE wrote:
I am using GPG signatures, and, occasionally, I will fat-finger my
pass phrase 3 times in a row (it's usually just once or many).
However, after three times, and you get the "invalid pass phrase"
error, I can't re-send without uncheck
Greetings,
I am using GPG signatures, and, occasionally, I will fat-finger my pass
phrase 3 times in a row (it's usually just once or many). However,
after three times, and you get the "invalid pass phrase" error, I can't
re-send without unchecking the GPG signature button, and then
re-sele
76 matches
Mail list logo
