From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: Encrypting outgoing message but not Gcc?
Date: Sun, 07 Dec 2003 11:50:14 -0500 [thread overview]
Message-ID: <m3k7584lo9.fsf@asfast.com> (raw)
In-Reply-To: <iluzne5zvma.fsf@latte.josefsson.org>
Simon Josefsson <jas@extundo.com> writes:
> Lloyd Zusman <ljz@asfast.com> writes:
>
>> Is there a way to configure Gnus to encrypt an outgoing message, but not
>> its Gcc?
>
> It should be easy to add that functionality by writing a function,
> similar to mml-tweak-externalize-attachments, and it to
> mml-tweak-sexp-alist.
Thanks. I've looked through mml.el, and I get the general idea about
`mml-tweak-sexp-alist'. However, I don't know enough about the internal
logic of this whole mml thing to see how this can be used to prevent
encryption of messages destined to Gcc.
Specifically, I have the following questions:
1. When the specifed sexp is being invoked, what variables do I look at
which will tell me that the part is on its way to a Gcc destination,
as opposed to somewhere else?
2. Once I determine the answer to number 1, what should this sexp do to
tell the mml system not to do any encryption on this part?
--
Lloyd Zusman
ljz@asfast.com
prev parent reply other threads:[~2003-12-07 16:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-06 16:17 Lloyd Zusman
2003-12-06 16:46 ` Adam Sjøgren
2003-12-06 18:35 ` Lloyd Zusman
2003-12-07 1:54 ` Adam Sjøgren
2003-12-07 2:09 ` Lloyd Zusman
2003-12-07 2:25 ` Adam Sjøgren
2003-12-07 2:37 ` Lloyd Zusman
2003-12-07 11:07 ` Nathan Sullivan
2003-12-07 11:35 ` Adam Sjøgren
2003-12-07 13:08 ` Lloyd Zusman
2003-12-06 17:24 ` Reiner Steib
2003-12-06 17:58 ` Lloyd Zusman
2003-12-07 13:35 ` Lloyd Zusman
2003-12-07 13:45 ` Lloyd Zusman
2003-12-07 15:16 ` Lloyd Zusman
2003-12-07 15:44 ` Simon Josefsson
2003-12-07 16:28 ` Lloyd Zusman
2003-12-06 17:47 ` Simon Josefsson
2003-12-07 16:50 ` Lloyd Zusman [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=m3k7584lo9.fsf@asfast.com \
--to=ljz@asfast.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).