Hi again :-)
I just thought of a simpler and potentially easier answer to this whole
thing. Since you've already stepped up to the work of configuring *your*
environment (the aliases file) for these folks who can't get it together,
why not just configure your procmail setup to recognize any of the
addresses in the pattern list and write a Reply-To: header, perhaps
making the old one Old-Reply-To: on the way?
Something that looks vaguely like the ABSOLUTELY UNTESTED code
:0 f
* ^From: ([EMAIL PROTECTED]|[EMAIL PROTECTED])
| $FORMAIL -i 'Reply-To: Joe Cool <[EMAIL PROTECTED]>'
ought to recognize any mail from one of Joe's bogus addresses, pass the
email through formail and create a Reply-To: header pointing to the right
spot (while moving any old one to Old-Reply-To:), and then had the email
off for further sorting down the line.
No bloat, nothing really more than you would have done with the new mutt
code (though perhaps not as pretty), and it might even handle aliases
(just have to try this one)... No, it doesn't look like you get that
last bit, but it's still not so bad.
HTH & HAND
:-D
--
David T-G * It's easier to fight for one's principles
(play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie
(work) [EMAIL PROTECTED]
http://www.bigfoot.com/~davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
The "new millennium" starts at the beginning of 2001. There was no year 0.
Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh*
PGP signature
