Re: Adding a Bcc in a send-hook
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday, February 28 at 01:05 PM, quoth Matthew R. Dempsky:
>> Sure. One way (this may seem pretty idiotic) is to use 'push' in
>> your hook, rather than trying to get the hook to do it itself. That
>> allows mutt to get around to changing the recipients when it is
>> convenient. Like this:
>>
>> send-hook '~t @utdallas\.edu$ !~t ^utdlug@utdallas\.edu$' \
>> 'push <edit-bcc>mrd033000@xxxxxxxxxxxx<enter>'
>
> This seems to have a nasty effect if I start composing an email and
> then decide to cancel it. (The pushed key presses get sent to the
> folder index.) If I could fix that I'd be happy.
Hmmm. I'm not quite sure what you're talking about. When I start
composing a mail, mutt first asks me who I'd like to send it to. If I
cancel out of that, the send-hook is not triggered. If I provide an
address, then it asks me what subject I'd like to use for my mail, and
if I cancel out of THAT, the send-hook is not triggered either. If I
do give it a subject, it launches my editor. I can decide "nah, didn't
want to send it" at that point, but when I exit my editor, I'm
presented the "compose" menu where I can see that the bcc has already
been set. If I cancel sending at that point, there's still no problem
because the push'd commands have already executed.
What method of cancelling sending a mail are you using that causes a
problem with this send-hook?
>> Also, my_hdr is a rather silly way to set your from address. Is
>> there a reason that you're not using $from? There may be a better
>> way to achieve what you're after.
[snip]
> Is there a different way you had in mind?
Nope, guess not. Nevermind then.
~Kyle
- --
Nip the shoots of arbitrary power in the bud, is the only maxim which
can ever preserve the liberties of the people.
-- John Quincy Adams
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iD8DBQFF5fHEBkIOoMqOI14RAmxoAKDLcePtJyCiOYXE87dJ+DRllxw9jACfYPin
r3lGKqHzMlh3iy8ahqlgVuY=
=Xo5j
-----END PGP SIGNATURE-----