On 25Feb2016 20:50, Tim Chase <m...@tim.thechases.com> wrote:
On 2016-02-25 21:34, Patrick Shanahan wrote:
> Is there some setting I've missed, or some way around this to have
> mutt extract my From: address using the Envelope-To: header?
send-hook <mail-list> 'my_hdr From: Your Addr <your.addr...@123.us>'
It looks like that would require me to hand-specify every mailing
list's From: address. I was hoping to auto-extract it from the
Envelope-To: like the reverse_name=yes does with the To: headers.
While I can do that, I'd rather not dig into every From: address I've
sent from, and add my umpteen mailing-lists. If I can avoid it.
Especially since "reverse_name" is already doing mostly what I want.
Had you considered a message-hook based on the Envelope-To:? You might still
need to enumerate your alternate addresses (untested):
message-hook '~h ^Envelope-To: *<me@isp1>' 'my_hdr From: Your Addr
<your.addr...@123.us>'
A send-hook with the same pattern might be better.
Failing that, you can fairly easily write scripts which emit mutt directives
based on header contents. I have a script "mhdrs" which can emit message
headers as shell settings, which you can then source in a shell script
file, which you can then source. Round about, but (again untested):
Have a little shell script like this:
#!/bin/sh
#
# Compute and emit mutt settings for any message.
#
mhdrs=$( mhdrs -sh | sed 's/^/hdr_/' )
eval "$mhdrs"
if [ -n "$hdr_ENVELOPE_TO" ]
then
echo "my_hdr From: $hdr_ENVELOPE_TO"
fi
... whatever else ...
and then:
message-hook . '<pipe-message>compute_mutt_settings.sh
tempfile<enter><enter-command>source tempfile<enter>'
A little awkward. You can't just:
source `compute_mutt_settings.sh`
because you need to pipe the message into it, per message, first.
You can get mhdrs here:
https://bitbucket.org/cameron_simpson/css/src/tip/bin/mhdrs
Just a thought.
Cheers,
Cameron Simpson <c...@zip.com.au>
