From: Fabien Penso <penso@linuxfr.org>
Cc: ding@gnus.org
Subject: Re: Mailcrypt and gpg > v1.0.4
Date: Mon, 13 Aug 2001 15:14:57 +0200 [thread overview]
Message-ID: <plop87pua0xfse.fsf@linuxfr.org> (raw)
In-Reply-To: <87k8085qiu.fsf@alberti.gnupg.de> (Werner Koch's message of "13 Aug 2001 10:10:33 +0200")
>> mails, it fails to find my key when i issue C-c / e, I've came so far
>> that I understand that it is probably a regexp trying to match a
>> string whose output have changed from 1.0.4 to 1.0.6 (--list-keys or
>> --list-secret-keys probably). I've tried to check mc-gpg.el for a
> There is a regex which tries to match a fixed amount of colons, but
> GnuPG recently introduced a new field and with it another colon. The
> regex should only check that there are at _least_ this amount of
> colons. The new fields are optional.
> Fix is trivial and may already be in the latest mailcrypt.
Hi all,
I don't know if it's the same problem, but I can't encrypt neither sign
messages with my key.
I just compiled the latest cvs (oort 0.4) from today. I am using gnupg
1.6 from debian/sid.
I use Mime -> Security -> Sign PGP/Mime (C-c RET s p), it adds a line
like "#part sign=pgpmime" at the beginning of the mail, but when I hit
C-c C-c I got
Sending...
mc-get-pgp-keydir: Search failed: "^Key ring:\\s *'\\(.*\\)'"
I tried to remove mailcrypt 3.5.6 (just to see) and I have the same
problem. Any idea is welcome.
Another question, I received a signed mail, I had to manually ask for
sign checking, but I am sure I can ask Gnus to do that automaticly,
can't I ?
Thanks.
--
Fabien Penso <penso@linuxfr.org>
http://perso.LinuxFR.org/penso/
GnuPG key: 1024D/22F38AF3
next prev parent reply other threads:[~2001-08-13 13:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-12 22:49 Mattias Ahnberg
2001-08-13 8:10 ` Werner Koch
2001-08-13 9:17 ` Mattias Ahnberg
2001-08-13 17:03 ` Werner Koch
2001-08-13 13:14 ` Fabien Penso [this message]
2001-08-13 15:44 ` Kai Großjohann
2001-08-13 16:19 ` Fabien Penso
2001-08-13 18:51 ` Kai Großjohann
2001-08-14 9:39 ` Fabien Penso
2001-08-15 22:51 ` Fabien Penso
2001-08-15 23:11 ` Fabien Penso
2001-08-16 7:36 ` Vincent Bernat
2001-08-16 14:08 ` Fabien Penso
2001-08-16 23:57 ` Colin Marquardt
2001-08-17 12:19 ` Fabien Penso
2001-08-17 6:43 ` Felix Hagemann
2001-08-17 8:06 ` Robin S. Socha
2001-08-20 18:52 ` Felix Hagemann
2001-08-16 9:49 ` Kai Großjohann
2001-08-16 10:03 ` Fabien Penso
2001-08-13 16:37 ` Steve Youngs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=plop87pua0xfse.fsf@linuxfr.org \
--to=penso@linuxfr.org \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).