Marcelo Magallon <[EMAIL PROTECTED]> wrote:
>
> I have a better idea of what I want now...
>
> * Use reverse_name when replying, always. For example, if
> [EMAIL PROTECTED] sends me an email to [EMAIL PROTECTED], but my send hook
> says mutt should use [EMAIL PROTECTED] when sending mail to
> [EMAIL PROTECTED], I want [EMAIL PROTECTED] to be used, not
> [EMAIL PROTECTED] (reverse_name does this, but not quite)
>
> * I want to use my bigfoot address with friends and such, because
> it's easier for them to remember (send-hook does this, and it seems
> to take precedence over reverse_name, am I wrong?)
>
> * Use my university's address otherwise ("send-hook ." takes care of
> this, but it overrides reverse_name, it seems)
Did you see my other post to this forum, regarding the use of the "from"
variable, as opposed to "my_hdr From:"? I think it has the answer to
this dilemma.
Most people on this list, when you ask them how to set up different
identities, will tell you to use send-hooks with a my_hdr From: command.
That's because, until recently, that was the only way to do it. But Mr.
Roessler added a feature that some people seem to have missed: A "from"
variable that gives the default for the "From:" header, if none is
determined by any other means. This is the key, I think.
So you could have a setup like this:
set reverse_name # From: chosen from sent address on replies
send-hook ~A 'set from="My Default Address <[EMAIL PROTECTED]>"'
send-hook ~C joe 'set from="Address for Joe <[EMAIL PROTECTED]>"'
send-hook ~C mutt 'set from="Address for Mutt Lists <for_mutt>"'
Do you get the idea? The send-hooks will set the $from variable, but
$reverse_name will still apply, since it takes precedence on replies.
--
David DeSimone | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED] | that there is no man really clever who has not
Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson
UX WTEC Engineer | PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44