On Mon, Jan 07, 2002 at 01:52:19AM +0300, Im Eunjea wrote: > * Tom Jones <[EMAIL PROTECTED]> [2002-01-06 00:53]: > > > > (2)when replying to a message, look at the delivered-to, to, cc, > > etc headers. If one of them is in the list from (1), set the From: header > > to that. Otherwise set the From: value to a default value.
> I think you can use "message-hook" with "~h" pattern. > something like this: > > message-hook '~h ^To:.*blah@blah\.org' \ > 'my_hdr From: someone <nobody@localhost>' I did a much expanded version of that, and it's fairly good, but sometimes I reply to messages directly from the list view. That will slip through. > message-hook ~p 'my_hdr From: someone <nobody@localhost>' No, because this need arises in the first place from the fact that reverse_name doesn't look at enough headers to see if they contain something from $alternates. ~p will surely suffer from the same problem. What I really need is either some sort of "reply-hook" or access to the "parent" message in send-hook. It looks like I will need to patch mutt one way or another to get what I want, which is surprising, because this seems like it should be a common user requirement. cheers, Tom.
