On Wed, Dec 19, 2001 at 12:29:40PM -0500, Charlie Summers wrote:
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.
That was uncalled for. OK, "webmaster" was a poor example, in some cases the people are highly trained in things that have nothing to do with computers (including treating people politely and with respect), and in any case having to add Bcc: (or Cc:) manually every time is a nuisance that tends to be forgotten in a hurry.
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?
I'm not -- yet, but since I already have SmartList I thought it'd be the easiest way to accomplish what I need (which includes archiving messages and providing means for selected (but not all) people to get in and out of the list easily).
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?
Perhaps you could suggest a suitable procmail recipe instead of badmouthing me?
I don't see where SmartList, or _any_ mailing list manager for all that, wouldn't be _extreme_ overkill for such a purpose.
Given that there are several such groups (typically created for projects that last 4-12 months), some of them understand rather little about computers, and I want to delegate their management out (at least let people get out of the list and back again as need be without involving sysadmin), how would you do it?
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.
Good. At least we agree on something. -- Tapani Tarvainen