On Tue, Jul 11, 2000 at 12:45:19PM -0400, David T-G wrote:
> As you can see, you can specify just about any mutt command in a
> send-hook and it's triggered by your recipient. The only thing about
> this that I don't like is that send-hooks (as well as fcc- and [-]save-
> hooks) don't have a way to differentiate between the "primary" recipient
> (that which would usually get the fcc, as it appears to me) and any other
> (To:|Cc:|Bcc:) recipients.
(I have a feeling that only the order of fcc-hooks influences this selection,
but since I do not use fcc-hooks, and save all outgoing mails to a
single folder, I cannot tell.)
> Thus, with the hooks above and a note
> addressed as
>
> To: joe, skip, jimh
> Cc: [EMAIL PROTECTED]
>
> my Fcc: would be reset to =APD/joe, autosigning would be turned off, and
> autoencryption would be turned on -- all of which are probably not what I
> really wanted. I'm still working on a proposal to the developers to get
> around this nut :-)
You can use the `^' modifier, e.g.
send-hook '^~C (jimh|kielsky)' set pgp_autoencrypt
Now pgp_autoencrypt will be set only if you send mail to
jimh/kielsky/both of them. By using (or not using) ^, you can
effectively choose whether your send-hook will be executed if ALL
(or, respectively, ANY of) recipients match the pattern.
That probably doesn't solve all the problems. (If I used fcc-hooks, I'd
want to have four copies of the message saved in folders for all four
recipients).
HTH,
Marius Gedminas
--
Some people around here wouldn't recognize
subtlety if it hit them on the head.
