At 7:07 AM -0500 12/19/01, Tapani Tarvainen is rumored to have typed:
Could anyone suggest what'd be the easiest way to modify the Reply-To: -field so that it'd contain both (1) either the original sender _or_ original Reply-To: and (2) the list address?
Yuck.
This is for special lists where most people sending aren't on the list (small teams handling, e.g., webmaster addresses and the like: replies should go also to others in the team so they know it's been taken care of).
If these are highly-trained professionals, they should easily be able to handle sending a Bcc: to the "team" without munging the Reply-To: header field; if they aren't and can't, you might want to get more highly-trained staff. And while I'm on the subject, unless you have a few _hundred_ support people who are constantly changing on a day-to-day basis, why are you using a mailing list manager for this purpose? Wouldn't a simple sendmail alias be a whole lot less trouble? Or even a simple set of procmail recipies, if you're absolutely determined to munge header fields until the cows come home? I don't see where SmartList, or _any_ mailing list manager for all that, wouldn't be _extreme_ overkill for such a purpose.
I'd argue that using one of the many web-based support systems would make a whole lot more sense, but since I prefer email to the web, I won't.
Charlie (who's always confused when mailing lists are shoehorned into internal support tasks...shooting mosquitios with elephant guns is always more difficult than using a fly swatter)