From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: pgg doesn't seem to like me
Date: Wed, 09 Oct 2002 23:59:19 +0200 [thread overview]
Message-ID: <iluadlni894.fsf@latte.josefsson.org> (raw)
In-Reply-To: <y1yofa7khfo.fsf@fly.verified.de> (Raymond Scholz's message of "Sun, 06 Oct 2002 12:14:20 +0200")
Raymond Scholz <rscholz@zonix.de> writes:
> * Simon Josefsson <jas@extundo.com> wrote:
>
>> Uhm, are there any other outstanding PGG problems? I may have missed
>> them. Or PGP/MIME and S/MIME problems in general?
>
> Trying to send something with "method=pgp mode=signencrypt" and
> (mml-signencrypt-style "pgp" 'combined) gives me the following backtrace:
>
> Debugger entered--Lisp error: (wrong-number-of-arguments #[(cont) "Á\b! ÂÃ!" [cont mml1991-encrypt error "Encryption failed... inspect message logs for errors"] 2] 2)
Do you still see this? I can't reproduce it. Can you M-x
load-library RET mml1991.el RET to get a better backtrace?
> BTW: after seeing this I'm unable to send any _news_ posting?!
>
> message-send-mail-with-sendmail: Sending...failed to No recipient addresses found in header;
This is weird, the MML1991 stuff shouldn't leave any permanent state
that can affect future messages. Hm. Could you edebug m-s-m-w-s to
see what happens to the headers? Or debug sendmail somehow, to see
what data is piped to it.
next prev parent reply other threads:[~2002-10-09 21:59 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 17:27 John A. Martin
2002-10-01 18:56 ` John A. Martin
2002-10-01 19:16 ` Josh Huber
2002-10-01 20:11 ` John A. Martin
2002-10-01 20:58 ` Josh Huber
2002-10-01 21:21 ` John A. Martin
2002-10-01 21:38 ` Josh Huber
2002-10-01 21:50 ` Jesper Harder
2002-10-01 23:32 ` John A. Martin
2002-10-02 18:36 ` John A. Martin
2002-10-02 19:20 ` John A. Martin
2002-10-03 0:22 ` Clemens Fischer
2002-10-03 23:00 ` Simon Josefsson
2002-10-03 23:04 ` Simon Josefsson
2002-10-05 4:45 ` John A. Martin
2002-10-05 11:24 ` Simon Josefsson
2002-10-05 15:12 ` John A. Martin
2002-10-05 21:22 ` Raymond Scholz
2002-10-06 0:03 ` Simon Josefsson
2002-10-06 10:14 ` Raymond Scholz
2002-10-09 21:59 ` Simon Josefsson [this message]
2002-10-10 0:15 ` Simon Josefsson
2002-10-10 17:36 ` Raymond Scholz
2002-10-06 19:46 ` John A. Martin
2002-10-10 0:13 ` Simon Josefsson
2002-10-10 4:55 ` John A. Martin
2002-10-10 14:18 ` Josh Huber
2002-10-10 15:18 ` Simon Josefsson
2002-10-10 14:55 ` John A. Martin
2002-10-10 15:54 ` Simon Josefsson
2002-10-07 16:23 ` Andreas Fuchs
2002-10-07 23:58 ` Clemens Fischer
2002-10-10 0:34 ` Simon Josefsson
2002-10-10 0:32 ` Simon Josefsson
2002-10-10 10:42 ` Andreas Fuchs
2002-10-10 15:00 ` Simon Josefsson
2002-10-10 18:28 ` Andreas Fuchs
2002-10-10 23:24 ` Simon Josefsson
2002-10-08 2:11 ` John A. Martin
2002-10-10 0:42 ` Simon Josefsson
2002-10-08 13:37 ` John A. Martin
2002-10-08 14:18 ` Simon Josefsson
[not found] ` <gd.y1yr8f6yp8y.fsf@fly.verified.de>
[not found] ` <iluofa94z60.fsf@latte.josefsson.org>
2002-10-05 11:58 ` Raymond Scholz
2002-10-05 14:17 ` John A. Martin
2002-10-05 21:21 ` Raymond Scholz
2002-10-01 22:54 ` Simon Josefsson
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=iluadlni894.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--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).