On Nov 29, 2007 7:33 PM, Sean Donelan <sean@donelan.com> wrote:
Yes, I understand that people who have never worked in a large providers won't get it. Nevertheless, I still think it is a good idea for folks to have separate infrastructure for contacts such as abuse, security, postmaster so they can work even when other groups in a large company make changes to their corporate gateways, routers, etc.
Sean, What's to get? If a particular error is easy to make (applying a large-system mail policy that fouls up the abuse desk is an easy mistake to make) and there's a relatively easy alternate system design which discourages that mistake (a separate RHS for the abuse desk that doesn't go through the primary mail path is an easy alternate system design) then when the mistake is made, the ROOT CAUSE is the design error (unified mail system) rather than the instant operator error which revealed it. Two errors but only one root cause. It seems perfectly straightforward to me. Regards, Bill Herrin -- William D. Herrin herrin@dirtside.com bill@herrin.us 3005 Crane Dr. Web: <http://bill.herrin.us/> Falls Church, VA 22042-3004