On 2018-01-23 15:50:38 -0000, kevin8t8 wrote: [quoting from the manual:]
Also note that my_hdr commands which modify recipient headers, or the message's subject, don't have any effect on the current message when executed from a send-hook.
Is there any reasonable use case for send-hook modifying the MUA state for _subsequent messages only_, but not the current message? There are good _technical_ reasons due to data structures in mutt's source code, but I can't think of any good use cases. In fact, it seems to me that one of the most commonly desired state changes in a mail user agent is to change the sender (From: and/or Sender: fields), possibly also the Fcc:/Bcc:/Cc: fields, or even the arguments to the mail submission agent, to support multiple roles from a single mailbox. This allows sending to Alice using identity 1, sending to Bob via identity 2, and for everyone else using the default identity. Many mail clients support changing identities based on recipient. In contrast, the current semantics of send-hook seems to be nudging the user to use identities in a coarse-grained way, for instance by running multiple mutt instances, one for each identity. However, this seems to work best with multiple inboxes, something that seems less common nowadays than when I started using mutt twenty years ago. If there is a good use case for "change-state-on-subsequent-messages", I'd appreciate someone describing it. -- Andras Salamon and...@dns.net
