From: Charles Sebold <csebold@ezl.com>
Subject: Re: Canonical methods for digitally signing and verifying
Date: 17 Dec 2000 14:55:05 -0600 [thread overview]
Message-ID: <m33dfmsr86.fsf@broadsword.zancanda.com> (raw)
In-Reply-To: <ltu283c5f0.fsf@asfast.com>
On 20 Kislev 5761, Lloyd Zusman wrote:
> Well, I was thinking of configuring gnus to always sign my outgoing
> emails, but I guess that isn't a good idea. I suppose that I'll
> have to put something into my gnus setup to make the decision on a
> group-by-group basis as to whether a message gets signed or not.
>
> It doesn't appear that `gnus-posting-styles' can help me with this,
> right?
If all you have to do to auto-sign a message is add the #part bit, you
could do this with posting-styles and the signature, possibly. It may
not handle multi-parts intelligently, though. If you never attach and
you never use more than one coding system in replies in that group,
that might work OK for you.
--
Charles Sebold
--
20th of Kislev, 5761
--
Tech Support Excuse of the Day:
routing problems on the neural net
prev parent reply other threads:[~2000-12-17 20:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-15 17:39 Lloyd Zusman
2000-12-15 18:01 ` Kai Großjohann
2000-12-15 18:50 ` Lloyd Zusman
2000-12-15 18:57 ` ShengHuo ZHU
2000-12-15 21:08 ` Lloyd Zusman
2000-12-15 21:30 ` ShengHuo ZHU
2000-12-15 21:45 ` Lloyd Zusman
2000-12-17 14:04 ` Simon Josefsson
2000-12-17 17:40 ` Lloyd Zusman
2000-12-17 20:55 ` Charles Sebold [this message]
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=m33dfmsr86.fsf@broadsword.zancanda.com \
--to=csebold@ezl.com \
/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).