googly.negotiator...@aceecat.org (12024-05-21):
> > The problem with any automation, anyway if with GnuPG or not, is how
> > to enter the passphrase or PIN to get access to the private key.
> Does the gpg-agent help with that? It is supposed to, I think.
Makes it worse. Without
entering a 6 digit PIN:
For interactive basic use, GPG is fine.
> The problem with any automation, anyway if with GnuPG or not, is how to
> enter the passphrase or PIN to get access to the private key.
For automation, the key must be unencrypted during the operation. Or the
process must ha
On Tue, May 21, 2024 at 05:57:00PM GMT, Matthias Apitz wrote:
> The problem with any automation, anyway if with GnuPG or not, is how
> to enter the passphrase or PIN to get access to the private key.
Does the gpg-agent help with that? It is supposed to, I think.
--
Ian
El día martes, mayo 21, 2024 a las 10:49:08a. m. +0200, Nicolas George escribió:
> Matthias Apitz (12024-05-21):
> > How could we expand this for signing mails on the fly?
>
> Hi.
>
> ...
>
> - Ditch GPG. GPG has been increasingly incapable of deciding if it is a
&
Matthias Apitz (12024-05-21):
> How could we expand this for signing mails on the fly?
Hi.
For fine control, I would suggest:
- Build your mail entirely yourself without relying on a MUA like mutt
and inject it directly into the MTA local injector /usr/lib/sendmail.
- Ditch GPG. GPG has b
__)}: {subject}'
body = f'{body}\n\n{now}'
base_charset = charset.Charset('utf-8')
base_charset.body_encoding = charset.QP
basemsg = Message()
basemsg.set_payload(body, charset=base_charset)
gpg = gnupg.GPG(gpgbinary='/opt/homebrew/bin/gpg')
Hello,
Our Library Management System sends mails to patrons and media vendors
which are assembled in a shell script with all data (Subject, body, To,
attachments, etc) by a call to the MUA mutt 2.1.1 which pipes the mail
to sendmail:
#!/bin/sh
#
# $Id: sisis2mail.sh 381380 2020-11-06 07:49:50Z
the entire message in raw form, you can use '|' in
the pager or message index, and pipe it to less, for example.
--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
ND_CLASSIC_PGP, meaning you haven't disabled
classic pgp mode (using --disable-pgp).
indeed, I did have only --disable-gpgme. Now I recompiled with both
--disable-gpgme and --disable-pgp
When I open gpg encrypted message, I see this:
[-- Attachment #1: PGP/MIME version identification --]
[-
ed
classic pgp mode (using --disable-pgp).
--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
> On 2021-08-29 03:13, Kevin J. McCarthy wrote:
On Sat, Aug 28, 2021 at 06:31:12AM +0200, Fourhundred Thecat wrote:
$ /usr/bin/mutt -v | grep CRYPT_BACKEND
+CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME
-CRYPT_BACKEND_GPGME
Note the "-" prefix in front of CRYPT_BACKEND_GPGME. That
On Sat, Aug 28, 2021 at 06:31:12AM +0200, Fourhundred Thecat wrote:
This is strange. I have compiled mutt with "--disable-gpgme", and I can
see that it is no longer linked with the gpg library:
$ ldd /usr/bin/mutt
linux-vdso.so.1
libncursesw.so.6 => /lib/x86
ave compiled mutt with "--disable-gpgme", and I can
see that it is no longer linked with the gpg library:
$ ldd /usr/bin/mutt
linux-vdso.so.1
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6
On Fri, Aug 27, 2021 at 07:33:52AM +0200, Fourhundred Thecat wrote:
On 2021-08-26 18:34, Kevin J. McCarthy wrote:
If that doesn't help, you could try recompiling mutt using the
'--disable-pgp' and '--disable-gpgme' configure options.
Now when I open gpg encrypted message, I get this error
> On 2021-08-26 18:34, Kevin J. McCarthy wrote:
On Thu, Aug 26, 2021 at 08:41:56AM -0700, Will Yardley wrote:
On Thu, Aug 26, 2021 at 03:06:18PM +0200, Fourhundred Thecat wrote:
how can I completely disable gpg integration in mutt ?
Either way, I think first try checking the "fine
On Thu, Aug 26, 2021 at 03:06:18PM +0200, Fourhundred Thecat <400the...@gmx.ch>
wrote:
> Hello,
>
> how can I completely disable gpg integration in mutt ?
>
> If message happens to be encrypted, I would like mutt to simply show me
> the source (encrypted).
>
&g
On Thu, Aug 26, 2021 at 08:41:56AM -0700, Will Yardley wrote:
On Thu, Aug 26, 2021 at 03:06:18PM +0200, Fourhundred Thecat wrote:
how can I completely disable gpg integration in mutt ?
If message happens to be encrypted, I would like mutt to simply show me
the source (encrypted).
[...]
I
On Thu, Aug 26, 2021 at 03:06:18PM +0200, Fourhundred Thecat wrote:
>
> how can I completely disable gpg integration in mutt ?
>
> If message happens to be encrypted, I would like mutt to simply show me
> the source (encrypted).
[...]
> I don't know how that happened. I am usi
Hello,
how can I completely disable gpg integration in mutt ?
If message happens to be encrypted, I would like mutt to simply show me
the source (encrypted).
I thought, I don't have gpg configured, but when I wanted to compose new
message, this happened:
Recall postponed message? ([yes
mode.
I thought I had added a note to the manual about this, but I only see it
in the "batch composition flow" section (in git). I'll add a note to
the "encryption and signing" section too.
--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031
Dear mutt community,
I am trying to use a GnuPG key without a passphrase to send *signed*
mails from a cron job for some non-critical, internal reporting.
Searching the archives did not give me the answer.
I'd like to use something along the lines of
|echo "this is my body text" | mutt -s
On Fri, Jul 19, 2019 at 06:25:02AM -0700, Kevin J. McCarthy wrote:
> On Fri, Jul 19, 2019 at 12:54:47PM +0530, Pankaj Jangid wrote:
> > > > The help (?) indicates that ^K is the default key to extract keys from a
> > > > message.
> > >
> > > The function will try to import keys that have been
>
yours, where signature is attached, I am getting
the same output on ":exec extract-keys".
The signature is not the same as an attached public key.
will only work if a sender explicitly attaches their key to the email.
--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 530
> > The help (?) indicates that ^K is the default key to extract keys from a
> > message.
>
> The function will try to import keys that have been attached
> to an email, for instance by in the compose menu.
>
Even in this email of yours, where signature is attached, I am getting
the same
On Thu, Jul 18, 2019 at 02:17:24PM +0530, Pankaj Jangid wrote:
The help (?) indicates that ^K is the default key to extract keys from
a message.
The function will try to import keys that have been
attached to an email, for instance by in the compose menu.
--
Kevin J. McCarthy
GPG
Hi,
I have configured GnuPG for signing and encrypting messages. It is
working perfectly fine. But I want to import keys of known people in my
gpg keys. The help (?) indicates that ^K is the default key to
extract keys from a message. But when I am pressing ctrl+k, mutt is
emitting this message
> If you see this mail PGP-signed, then your advice has helped, thank
> you!
Mail was PGP-signed and my own mutt recognized it as such.
--
· Patrice Levesque
· http://ptaff.ca/
· mutt.wa...@ptaff.ca
--
signature.asc
Description: Digital signature
Kevin J. McCarthy wrote:
> >I swear I did not modify the vanilla /usr/local/share/examples/mutt/gpg.rc
> >(and frankly did not even look inside this file for many years).
> >
> >How can I fix this new trouble with signing?
>
> If you are using a pre-2.1 version of
On Tue, Jun 18, 2019 at 12:31:34AM +0700, Victor Sudakov wrote:
I swear I did not modify the vanilla /usr/local/share/examples/mutt/gpg.rc
(and frankly did not even look inside this file for many years).
How can I fix this new trouble with signing?
If you are using a pre-2.1 version of gpg
Dear Colleagues,
I've been using gpg with Mutt for many years (like maybe 20 years) with
a simple line in muttrc: "source /usr/local/share/examples/mutt/gpg.rc"
However, after the recent upgrade to Mutt 1.12.0 (from the FreeBSD ports
collection) I started getting this error when tryi
IIRC this is *mostly* true--except that some versions (and some key
servers) support subkeys, while others do not, and this mismatch could
break verification.
But aside from that, and aside from signature-related bugs like what
we were just discussing in that other thread, verifying a message with
server pool,
though it also has some extra features, including the new Web Key
Directory service. WKD support can be compiled in with current
versions of GPG using the "--enable-wks-tools" flag with configure
step. Then gpg will be able to use the "--locate-keys" flag in p
On 2018-08-30, nunojsi...@ist.utl.pt wrote:
> I've been sending GPG-encrypted e-mails with mutt, and I've noticed that
> the key ID selection menu, the one that shows up when there is more than
> one identity in a given recipient's key, is a bit too long for 80
> columns.
&g
I've been sending GPG-encrypted e-mails with mutt, and I've noticed that
the key ID selection menu, the one that shows up when there is more than
one identity in a given recipient's key, is a bit too long for 80
columns.
This means that, when I send encrypted e-mails from an 80-column
terminal
On Monday 13 August 2018 20:22,
Matthias Apitz put forth the proposition:
> On Monday, 13 August 2018 18:59:38 CEST, David Woodfall
> wrote:
> > On Monday 13 August 2018 13:46,
> > Matthias Apitz put forth the proposition:
> > > El día Monday, August 13, 2018 a las 12:34:08PM +0100, David
On Thu, May 24, 2018 at 08:15:17PM +0100, Dominik Vogt wrote:
> When I send a GPG-encrypted mail to, say "Foo Bar ",
> and there is a public key for that address in the GPG keyring,
> mutt still asks for a key to use for encryption. Can I tell mutt
> to use the key matchin
Hello,
mutt 1.5.21 under Centos 7
gpg 2.0.22 under Centos 7
I have been trying to send encrypted messages via mutt in command line.
The email arrives at destination but is never encrypted.
If I send the same thing using mutt interactively, the message arrives
encrypted.
Any idea where I could
When I send a GPG-encrypted mail to, say "Foo Bar <f...@bar.org>",
and there is a public key for that address in the GPG keyring,
mutt still asks for a key to use for encryption. Can I tell mutt
to use the key matching the receiver address automatically?
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
On 2017-05-16 09:09, Michelle Konzack wrote:
> you should correct your GPG signature.
IMO signing unencrypted email is of limited value. See the link below
the fold.
--
Please *no* private Cc: on mailing lists and newsgroups
Personal signed mail: please _encrypt_ and sign
Don't clear-t
Hello Feng,
you should correct your GPG signature.
--
Michelle KonzackMiila ITSystems @ TDnet
GNU/Linux Developer 00372-54541400
signature.asc
Description: Digital signature
On 17-03-06 16:23, Alexander Gattin wrote:
> Hello,
>
> On Sun, Mar 05, 2017 at 08:35:59PM -0600, Derek
> Martin wrote:
> > It's sad to see this question still popping up.
> > Inline PGP is a hack that should have died at
> > least a decade ago, and more like two decades.
>
> My friend used to
Hello,
On Sun, Mar 05, 2017 at 08:35:59PM -0600, Derek
Martin wrote:
> It's sad to see this question still popping up.
> Inline PGP is a hack that should have died at
> least a decade ago, and more like two decades.
My friend used to send inline PGP messages until
half a year ago, and I'm sure
opping up. Inline PGP is a hack
that should have died at least a decade ago, and more like two decades.
--
Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02
-=-=-=-=-
This message is posted from an invalid address. Replying to it will result in
undeliverable mail due to spam
On 17-02-22 12:01, Michelle Konzack wrote:
> Hello,
>
> I get every day GPG signed and crypted messages, but these are always as
> attachment. However, two days ago, I have gotten a message with INLINE
> crypting like
>
> -BEGIN PGP MESSAGE-
> Charset: windows-
On 2017-02-22 12:58:17 Francesco Ariis hacked into the keyboard:
> Hello Michelle,
> P (check-traditional-pgp) should do the trick, but I never
> tested it. Inline messages and signatures are discouraged for a bunch
> of reasons, maybe your contact misconfigured their client.
I tried it
On Wed, Feb 22, 2017 at 12:01:11PM +0100, Michelle Konzack wrote:
> Hello,
>
> I get every day GPG signed and crypted messages, but these are always as
> attachment. However, two days ago, I have gotten a message with INLINE
> crypting like [...]
>
> and I can not open it
Hello,
I get every day GPG signed and crypted messages, but these are always as
attachment. However, two days ago, I have gotten a message with INLINE
crypting like
-BEGIN PGP MESSAGE-
Charset: windows-1252
Version: GnuPG v2
hQIMA4/WG/fTbdX8ARAAw0CwUeDUpr34bVyIdOv+S32F8sMeCogqz0VIeKe
Michelle,
> Currently not possibel, because the script is on my server @home which
> I can not access trough the Internet and I work currently 600km far
> away.
Would've been neat, but I think you gave me enough pointers so far that
I can manage on my own for a bit. Thanks again for your time
osition: attachment; filename="mutt.png"
Content-Transfer-Encoding: base64
--All_the_parts--
8<------
> I get that, but I'd prefer dealing with GPG inside mutt, I want to avoid
> recreating mutt's perfectly fin
ially from a script.
I get that, but I'd prefer dealing with GPG inside mutt, I want to avoid
recreating mutt's perfectly fine interface for it (selecting keys for
instance).
Thanks, and have a nice day,
--
· Patrice Levesque
· http://ptaff.ca/
· mutt.wa...@ptaff.ca
--
signature.asc
Description: Digital signature
On 2017-01-25 07:55:05 Patrice Levesque hacked into the keyboard:
> - multipart/mixed
> - multipart/alternative
> - text/plain
> - multipart/related
> - text/html
>
- text/plain
- multipart/related
- text/html
- inline image
- attachments
4) Message returns to mutt, which handles GPG
an the one
specified in ~/.gnupg/gpg.conf
I've read there should be a patch enabling:
"pgp_encrypt_self" - but, this is not legal in my muttrc.
Is there any way to pass a different "encrypt-to" to gpg
according to the .muttrc I'm running ?
(I've tried using gpg.rc - but the
On Thu, Sep 22, 2016, Ian Zimmerman wrote:
> mutt gpg
> http://marc.info/?l=mutt-users=147417425713497=rawBAD GOOD
Verifies fine for me (in mutt).
Now the question is: is it "just" your setup, or does it fai
really need to set crypt_use_gpgme, unless you specifically
want to use PKA.
> instead of defining the various pgp_* variables (usually shipped in
> gpg.rc)? Do they have any effect, then? Thanks, again.
When you are using the gpgme backend, those variables don't have any effect.
--
Kevin J.
On Jul 27 19:19 -0700, Kevin J. McCarthy wrote:
> I think I see the problem. Mutt is using a fixed buffer of size 1024
> when expanding the %r parameter. I think when the system was designed,
> no one anticipated expanding 50+ keys in a single gpg invocation. :-)
Yes, I was s
On Tue, Jul 26, 2016 at 03:43:41PM +0200, Steve Schmerler wrote:
> * stops at the third[**] key 74464897317CDA88 (length 16) and
> * passes a truncated version 74464897317CDA (length 14) to pgpewrap
>
> which then gives me a "gpg: skipped: Invalid user ID". The
[**] key 74464897317CDA88 (length 16) and
* passes a truncated version 74464897317CDA (length 14) to pgpewrap
which then gives me a "gpg: skipped: Invalid user ID". The related pgp
setting is
set pgp_encrypt_sign_command="/usr/lib/mutt/pgpewrap gpg2
%?p?--passphrase-fd 0?
On Jul 14 07:07 -0700, Kevin J. McCarthy wrote:
> crypt-hook mailing.l...@company.com key1
> crypt-hook mailing.l...@company.com key2
> crypt-hook mailing.l...@company.com keyN
> unset crypt_confirmhook
That's much better, indeed. I'm now using something like this
https://dev.mutt.org/doc/manual.html#crypt-hook
So instead, you can just:
# muttrc
crypt-hook mailing.l...@company.com key1
crypt-hook mailing.l...@company.com key2
crypt-hook mailing.l...@company.com keyN
unset crypt_confirmhook
--
Kevin J. McCarthy
GPG Finge
-- this is really
awkward (I literally used 0x12345678).
Are there other workarounds in use? The solution above can't be the only
one.
Apart from the gpg group thing, I would have been fine with the option
of interactively selecting the keys to encrypt to in the PGP menu,
independently from the actual
and decprypting it.
Thanks for the reply.
That's what I always do.
I'll check out your link when I get some time.
I have just about come to the conclusion that this isn't a mutt problem
but a gpg problem.
Opinions?
--
Bob Holtzman
A man is a man who will fight with a sword or
conquer Mt. Ev
ideas?
Here's some good info on Mutt/Gpg interaction:
https://sanctum.geek.nz/arabesque/linux-crypto-email/
The whole Crypto series from Tom Ryder I found to be a great help.
All the best
Wim
--
|\ _,,,---,,_
ZZZzz /,`.-'`'-. ;-;;,_
|,4- ) )-,_. ,\ ( `'-'
'---''(_/--' `-'\_)
> outbox and trying to decrypt it, it throws an error about the passphrase
> being invalid. A search turned up nothing applicable.
>
> I'm at a loss to know where to start trying to troubleshoot this.
> Any ideas?
>
This might be stupid and or too obvious but do you have
On Fri, May 13, 2016 at 10:15:25PM +0200, Wim wrote:
> Hi,
>
> On Thu, 12.05.16, at 14:28, Bob Holtzman wrote:
> > In my plain vanilla setup "p" in the compose window prints out "set
> > pgp_encrypt = yes" in the headers although that's not set i
On Fri, May 13, 2016 at 10:15:25PM +0200, Wim wrote:
> Hi,
>
> On Thu, 12.05.16, at 14:28, Bob Holtzman wrote:
> > In my plain vanilla setup "p" in the compose window prints out "set
> > pgp_encrypt = yes" in the headers although that's not set i
Hi,
On Thu, 12.05.16, at 14:28, Bob Holtzman wrote:
> In my plain vanilla setup "p" in the compose window prints out "set
> pgp_encrypt = yes" in the headers although that's not set in ~/.muttrc.
> No gpg/pgp menu appears at the bottom of the window.
No idea w
" in the compose window prints out "set
pgp_encrypt = yes" in the headers although that's not set in ~/.muttrc.
No gpg/pgp menu appears at the bottom of the window.
> >
> > set pgp_verify_sig=yes
> > set pgp_use_gpg_agent = yes
> > set pgp_auto_decod
Of them, only verify_sig functions.
>
> I used to invoke the gpg menu at the bottom of the
> window with one key stroke, not "p"(?), but my memory, among other things,
> is failing due to age, and I can't recall it. At the time I had nothing
> more referring to gpg in
According to the help file "p" invokes encryption options. When I try it
I get nothing. I have
set pgp_verify_sig=yes
set pgp_use_gpg_agent = yes
set pgp_auto_decode = yes
in my ~/.muttrc file. Of them, only verify_sig functions.
I used to invoke the gpg menu at
On 05/09, mhk wrote:
Hi,
I can't decrypt any messages. Debug log shows the following (I hope I
pasted the relevant part):
just a shot in the dark but did you try: crypt-use-gpgme?
- https://dev.mutt.org/doc/manual.html#crypt-use-gpgme
A good setup:
.com>"" doesn't match regexp.
pgp_check_decryption_okay() is checking with value of
$pgp_decryption_okay against the output from gpg.
I believe this relies on '--status-fd=2' being in your
$pgp_decrypt_command. If you don't have it there, you'll need to add
it, or else unset $pgp_de
tato-1000-16219-17938587841422928928".
[2016-05-09 20:40:10] pgp.c:899: mutt_mktemp returns
"/tmp/mutt-velocitato-1000-16219-1336261536948383003".
[2016-05-09 20:40:10] mutt_pgp_command: gpg --passphrase-fd 0
--no-verbose --batch --output -
/tmp/mutt-velocitato-1000-16219-1336261536
On 30/06 16:47, Jon LaBadie wrote:
On Tue, Jun 30, 2015 at 10:11:53PM +0200, jonas hedman wrote:
On 15-06-30 22:00:27, Niels Kobschaetzki wrote:
Hi,
is it possible to use with one account PGP and S/Mime? I found a how-to
for using S/Mime or using mutt with one account with PGP and one
On 01Jul2015 20:12, Ian Zimmerman i...@buug.org wrote:
On 2015-07-02 12:20 +1000, Cameron Simpson wrote:
I keep a little maildb which assigns group names to addresses, and
autogenerate mutt aliases formed like the above from it. Why the
maildb? Because my mail filing also uses these groups in
On 2015-07-02 12:20 +1000, Cameron Simpson wrote:
I keep a little maildb which assigns group names to addresses, and
autogenerate mutt aliases formed like the above from it. Why the
maildb? Because my mail filing also uses these groups in its rules.
Excuse my ignorance, but what is a maildb?
On 30Jun2015 16:47, Jon LaBadie mut...@jgcomp.com wrote:
On Tue, Jun 30, 2015 at 10:11:53PM +0200, jonas hedman wrote:
On 15-06-30 22:00:27, Niels Kobschaetzki wrote:
is it possible to use with one account PGP and S/Mime? I found a how-to
for using S/Mime or using mutt with one account with
On 15-06-30 22:00:27, Niels Kobschaetzki wrote:
Hi,
is it possible to use with one account PGP and S/Mime? I found a how-to
for using S/Mime or using mutt with one account with PGP and one account
S/Mime. But I want to use my main account with both and would like to
choose on a per user
On Tue, Jun 30, 2015 at 10:11:53PM +0200, jonas hedman wrote:
On 15-06-30 22:00:27, Niels Kobschaetzki wrote:
Hi,
is it possible to use with one account PGP and S/Mime? I found a how-to
for using S/Mime or using mutt with one account with PGP and one account
S/Mime. But I want to use
Hi,
is it possible to use with one account PGP and S/Mime? I found a how-to
for using S/Mime or using mutt with one account with PGP and one account
S/Mime. But I want to use my main account with both and would like to
choose on a per user basis whether I encrypt via PGP or S/Mime. I know
people
* Jon LaBadie mut...@jgcomp.com [2015-06-30 16:53]:
On Tue, Jun 30, 2015 at 10:11:53PM +0200, jonas hedman wrote:
On 15-06-30 22:00:27, Niels Kobschaetzki wrote:
Hi,
is it possible to use with one account PGP and S/Mime? I found a how-to
for using S/Mime or using mutt with one
On Sun, Jun 21, 2015 at 02:42:25PM +0200, jonas hedman wrote:
I think I have to convince my friends to get decent email clients =)
Hey, at least you have managed to get them to try and use encryption!
My friends and family can't be bothered. :-(
--
John
and you are also
encrypting the message (which ascii-armors the output), then Mutt allows
the 8-bit encoding.
--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
http://www.8t8.us/configs/gpg-key-transition-statement.txt
Thank you so much for your
On 15-06-21 09:36:53, Heinz Diehl wrote:
On 21.06.2015, jonas hedman wrote:
I'm from Sweden and I occasionally communicate with other swedish people
using pgp and I've stumbled upon this problem:
If I encrypt a message containg any of the swedish letters åÅäÄöÖ
using inline format
On 21.06.2015, jonas hedman wrote:
I'm from Sweden and I occasionally communicate with other swedish people
using pgp and I've stumbled upon this problem:
If I encrypt a message containg any of the swedish letters åÅäÄöÖ
using inline format everythings works just fine but when I encrypt it
as far as I know. But something goes wrong.
I basically have two questions,
1. How to fix this?
2. Why doesn't this problem show up when encrypting inline style?
I'm sorry if this is stupid, I know very little about charsets and
encodings.
My cryptopart of .muttrc looks like this:
#gpg
set
the output), then Mutt allows
the 8-bit encoding.
--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
http://www.8t8.us/configs/gpg-key-transition-statement.txt
signature.asc
Description: PGP signature
Name name@test.invalid
[ about 20 other keys with names and email adresses]
Some of the keys are missing, although gpg --list-keys clearly shows that they
are there. The above shown keys also seems to be duplicates of the keys listed
with names and email addresses.
The sourced gpg.rc looks like
On 14.03.2015, Peter P. wrote:
how can I configure mutt to always attach my public GPG key to signed
messages without manually having to ESC-k and selecting the correct key?
Besides exploring mutts macro functionality already mentioned in this thread,
it could be an idea to copy your pubkey
* On 17 Mar 2015, Will Yardley wrote:
I've seen other mail clients (Evolution, I think) send the public key
with every message, but seems a bit of a wste of bndwdth to me. Just put
a link to your key (or your key-id and keyserver address) in your sig.
+1, if even that. Don't all mail
* Peter P. peterpar...@fastmail.com wrote:
* Francesco Ariis fa...@ariis.it [2015-03-14 19:58]:
On Sat, Mar 14, 2015 at 11:14:37AM +0100, Peter P. wrote:
how can I configure mutt to always attach my public GPG key to signed
messages without manually having to ESC-k and selecting
On Sat, Mar 14, 2015 at 11:14:37AM +0100, Peter P. wrote:
how can I configure mutt to always attach my public GPG key to signed
messages without manually having to ESC-k and selecting the correct key?
Maybe a macro [1] (exploiting attach-key) could do?
Have you considered uploading your key
* Francesco Ariis fa...@ariis.it [2015-03-14 19:58]:
On Sat, Mar 14, 2015 at 11:14:37AM +0100, Peter P. wrote:
how can I configure mutt to always attach my public GPG key to signed
messages without manually having to ESC-k and selecting the correct key?
Maybe a macro [1] (exploiting attach
Hi list,
how can I configure mutt to always attach my public GPG key to signed
messages without manually having to ESC-k and selecting the correct key?
thank you,
P
A small update on the matter. John was kind enough the send me a
encrypted test email from the iphone app and it worked
perfectly. I could verify signatures and and decrypt it properly from
within mutt automatically without any trouble.
With this in mind I just realized that my friend for weird
from commandline so
there seems to be nothing wrong with the encryption.
I would really appreciate if someone could help me out and make this
work.
Here is my config related to gpg:
In mutt.rc:
source ~/.gpg.rc
set pgp_use_gpg_agent = yes
set pgp_sign_as = ...
set pgp_timeout = 3600
set
++ 07/04/14 13:36 +0200 - Patrick Ben Koetter:
is it possible to automatically send encrpyted messages to GnuPG groups?
Maybe you are looking for the solution I am using.
I am sending lots of encrypted e-mail to a number of mailinglist with a
list of subscribers that doesn't change frequently.
Greetings,
is it possible to automatically send encrpyted messages to GnuPG groups?
From gpg(1):
--group name=value1
Sets up a named group, which is similar to aliases in email
programs. Any time the group name is a recipient (-r or --recipient
On Tuesday, 28 January, 2014 at 07:31:33 GMT, Izzy wrote:
I would like to know if it's possible to get rid of the Enter PGP
passphrase: dialog when sending signed/encrypted emails. The thing is
that use a GPG key _without_ a passphrase; nevertheless, mutt asks for
it every time, and I have
On Tue, Jan 28, 2014 at 08:31:33AM +0100, Izzy wrote:
Hi, everyone.
I would like to know if it's possible to get rid of the Enter PGP
passphrase: dialog when sending signed/encrypted emails. The thing is
that use a GPG key _without_ a passphrase; nevertheless, mutt asks for
it every time
1 - 100 of 999 matches
Mail list logo
