From: Lars Ingebrigtsen <larsi@gnus.org>
To: Christoph Groth <christoph@grothesque.org>
Cc: ding@gnus.org
Subject: Re: bug: S/MIME and gnus-message-replyencrypt
Date: Tue, 27 Jan 2015 14:07:55 +1100 [thread overview]
Message-ID: <87ppa0c450.fsf@building.gnus.org> (raw)
In-Reply-To: <87fvfh71pi.fsf@grothesque.org> (Christoph Groth's message of "Wed, 24 Sep 2014 12:27:37 +0200")
Christoph Groth <christoph@grothesque.org> writes:
> There seems to be a problem, however: When replying to such a message
> with gnus-message-replyencrypt set to t, the reply is not being marked
> for encryption automatically by the function
> gnus-summary-handle-replysign. If I understand the code correctly this
> happens because the function gnus-mime-display-part does not recognize
> the message as encrypted and does not (gnus-add-wash-type 'encrypted).
>
> Would someone who knows the code care to fix this issue?
I'm not familiar with this code, either. Could you submit a bug report
with `M-x report-emacs-bug', and perhaps that will get a response...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
prev parent reply other threads:[~2015-01-27 3:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 10:27 Christoph Groth
2015-01-27 3:07 ` Lars Ingebrigtsen [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=87ppa0c450.fsf@building.gnus.org \
--to=larsi@gnus.org \
--cc=christoph@grothesque.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).