On Mon, Jun 4, 2012 at 5:04 PM, Tom Limoncelli <[email protected]> wrote:
> This is a classic example of a situation where you need to tell the > customer "no". > I can see where you'd say that but I'm not sure that is exactly the case here. You could consider this list I'm talking about to be a tool that I want customers to use. Over several years, we have managed to create a sufficient amount of publicity and momentum in the use of this list/tool for sending info into my organization. I worry that if we tell customers to use a new email list to reach us, some folks just won't ever learn about the new email address (or they will learn of it slowly) and we will compromise some of our internal branding that is based on this list. I agree that having two separate email addresses/lists for the two separate functions is ideal. But there's a cost (to me, not really to the customer) for that transition and I'm not convinced it is the right thing to do in this case. So I'm exploring my options. Matt
_______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
