Re: send-hook and aliases

Jon LaBadie <[email protected]>
Newsgroups gmane.mail.mutt.user
Message-ID <[email protected]>
On Thu, Feb 13, 2025 at 04:22:04PM -0800, [email protected] wrote:
>On Wed, Feb 12, 2025 at 11:34:11AM -0500, Jon LaBadie wrote:
>
>> While composing a message (in vi) I add the alias name
>> to the Bcc: line and also set the Fcc: line to a mailbox
>> dedicated to the club's messges (i.e. "=club").
>
>> I regularly forget to make the two additions so I thought I'd create
>> send-hooks for them.  No problem for the Fcc: but I've not been able
>> to set the Bcc: line to an alias.
>
>Can you post an exact example of the send-hook command that seems to
>fail? Maybe change names to protect the guilty.

First what works, the send hook for Fcc:

send-hook       '[email protected]'    my_hdr Fcc: =part
send-hook       '[email protected]'    'my_hdr Fcc: =part'

quoted or unquoted, both work and Fcc: is set to "=part".

But if I try to use an alias for the save box:

alias   partbox =part
send-hook       '[email protected]'    my_hdr Fcc: partbox

"partbox" does not get replaced with "=part".

While I do not need an alias for Fcc:, I do for Bcc:.
My alias looks like:

alias dbpart \
         "Andy Griffin" <[email protected]>, \
             <100+ more lines like above>
         "Vivian Leigh" <[email protected]>

The corresponding send-hook that DOES NOT work would be:

send-hook       '[email protected]'    my_hdr Bcc: dbpart

The Bcc: line in my vi compose session is blank (i.e. only
the "Bcc: " is present).

NOTE, if I manually edit the Bcc: line and add the alias
"dbpart", the alias is substituted upon exiting vi and the 100+ 
addresses are present in the "ask send" screen of mutt.  It is
this manual edit requirement that I often forget and would
like to replace with an automated technique.


-- 
Jon H. LaBadie                 [email protected]
  154 Milkweed Dr                 (540) 868-8052 (H)
  Lake Frederick, VA 22630        (703) 935-6720 (M)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.