On Saturday, January 28 at 05:04 PM, quoth Alain Bench:
| send-hook . 'set from=standardfrom@xxxxxxxx' | send-hook ~l 'set from=altfrom@xxxxxxxx'Unfortunately, at mail compose time when send-hooks are triggered, it is too late for $from to have an effect on the *current* mail. But the code is crafted so that an override is still possible. Thus in send-hooks, and only in send-hooks, you must use "my_hdr From:". Just as Michael said.
Yup, my mistake.
While at it, may I suggest a $send_charset review? You use "mac" MIME charset in your most recent mails. It’s perfectly readable with Mutt and its iconv magic. But I believe "mac" is not a common MIME charset, which might reduce readability on other mailers… Looking at IANA assigned charsets, "mac" exists as an alias of "macintosh", together with "csMacintosh" at MIBenum 2027, but doesn’t seem to be noted as suitable for MIME…
Picky picky… ;)Sorry, that was a hold-over from an attempt to encode things in a way that would work for my pine-using friends (which throws up its hands in disgust at anything that isn’t us-ascii, it appears). Normally I just leave it as utf-8 (from mutt’s default $send_charset). Aside from saving a few extra bits, is there any reason to put cp1252/windows-1252 in my $send_charset?
~Kyle
--
Die for the person who will catch a cold for you.
-- Persian saying
Attachment:
pgpLY96OJU3MH.pgp
Description: PGP signature