From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Indication of signed messages?
Date: Thu, 14 Mar 2002 19:35:55 +0100 [thread overview]
Message-ID: <iluit7zov3o.fsf@extundo.com> (raw)
In-Reply-To: <87elin2fzc.fsf@nwalsh.com> (Norman Walsh's message of "Thu, 14 Mar 2002 12:53:27 -0500")
Norman Walsh <ndw@nwalsh.com> writes:
> Article washing does such a good job of cleaning up the extra headers
> associated with signed messages that I can't even tell who's sending
> them to me.
>
> It does seem like I might want to know. Is there a setting that'll show
> me some subtle indication that a message was signed?
`gnus-buttonized-mime-types'
This is a list of regexps. MIME types that match a regexp from
this list will have MIME buttons inserted unless they aren't
displayed. This variable overrides
`gnus-unbuttonized-mime-types'. The default value is `nil'.
To see e.g. security buttons but no other buttons, you could set
this variable to `("multipart/signed")' and leave
`gnus-unbuttonized-mime-types' to the default value.
next prev parent reply other threads:[~2002-03-14 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 17:53 Norman Walsh
2002-03-14 18:35 ` Simon Josefsson [this message]
2002-03-14 18:36 ` Bjørn Mork
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=iluit7zov3o.fsf@extundo.com \
--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).