From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] GPG (outgoing)
Date: Wed, 14 Apr 2010 09:04:29 -0400 [thread overview]
Message-ID: <1271250134-sup-4282@masanjin.net> (raw)
In-Reply-To: <1270981813-sup-1681@baad>
Reformatted excerpts from Ian Smith's message of 2010-04-11:
> In particular, I can sign (I've been testing mostly with signatures,
> not encryption) using GPG, and send a message successfully; however,
> while sup verifies that it thinks the signature is good, hushmail
> doesn't recognize the message as having a signature (it sees
> signature.asc as an attachment, but doesn't read the message as being
> signed), and correspondents tell me that Enigmail flags my message as
> having a bad signature.
I would compare the output of sup, hushmail and enigmail on a similar
message, and see if there's anything obviously different in the MIME
structure. It's possible Sup is emitting something they don't like.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-04-14 13:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 10:30 Ian Smith
2010-04-14 13:04 ` William Morgan [this message]
2010-04-14 13:30 ` Sven Schober
2010-04-15 1:00 ` Ian Smith
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=1271250134-sup-4282@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-talk@rubyforge.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