i wrote:
||>> is it possible, when using S/MIME, to sign the mail only sometimes?
||>> (Mostly, it is redundant, only sometimes it's really wanted.)
||>
||> Are you aware of `asksign' in mail(1)? Also, smime-sign-cert-USER@HOST
||> means it can be turned on for particualar `From:', or `Sender:',
||> addresses.
|So i have implemented two new hooks, *on-compose-enter* and
|*on-compose-leave*, which will set some variables so that at least
|a little bit of knowledge of the composed message is available,
|namely *compose-{from,sender,to,cc,bcc,subject}*.
|best that is possible today. *from* and *sender* isn't yet so
|bright, currently i hope i can improve this a bit until the v14.9
I've reorganized that a bit, too, and it now initializes the
mentioned fields (if possible) in case a hook (as above) is to be
called. That changes behaviour (even more), but i think this is
ok since that (crap) depended on wether you'd ~p(rint) the message
or not for example, anyway (in respect to initialization time of
the mentioned fields and thus the interaction with things like,
say, "~:set from").
That is to say that the new behaviour should match some more what
is to be expected for v15 (init as much as possible according to
context, enter (interactive) compose mode, re-evaluate and
update). All on [next] now (fixup'd to the same commit that
credits Rudolf).
| LC_ALL=C printf 'm bob\n~s ubject\nText\n~.\nx\n' |
| LC_ALL=C ./s-nail -:/ -d# \
| -Son-compose-enter=oncomp -Son-compose-leave=oncomp \
| -X 'define oncomp {' \
| -X ' echo compose-from ${compose-from}' \
| -X ' echo compose-sender ${compose-sender}' \
| -X ' echo compose-to ${compose-to}' \
| -X ' echo compose-cc ${compose-cc}' \
| -X ' echo compose-bcc ${compose-bcc}' \
| -X ' echo compose-subject ${compose-subject}' \
| -X ' if ${compose-to} =@ s-mailx' \
| -X ' set message-inject-tail="--\nMercy, Mercy Me"' \
| -X ' endif' \
| -X '}'
Ah ya, and that works on [crawl] now, too, which was a one-line (a
one bit) fix. But it will take some weeks before it ends up on
[next]. Siiiiiiiiiigh. So much to do. ^.^
It would be great if someone could test (read: use) this feature
and complain on oddities in behaviour, i wouldn't know what, but
this is why. ^.^ Just in case you use things like *bsdcompat*,
*asbcc*, *askattach* etc., it all had to be reordered a bit to
make the above work. I bet you won't realize the difference.
^_^ (Recall that -d / *debug* is a dry-runner, if in doubt.)
Ciao!
--steffen
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
__________________________________
[email protected]