🚀 go-pugleaf

In article <3376@sugar.uu.net> karl@sugar.uu.net (Karl Lehenbauer) writes:
>In article <2253@unmvax.unm.edu>, mike@unmvax.cs.unm.edu (Michael I. Bushnell) writes:
>> Hmmm...I disagree.  We are an "enlightened" site which lets people edit 
>> /usr/lib/aliases.  If someone f*cks up, then we have the simple solution
>> of asking "who changed the XXX alias to YYY?" and then we can explain to
>> them the necessity of being more careful in the future.
>
>Thus the cost of providing the flexibility of letting people edit 
>/usr/lib/aliases is that, when they screw up, mail screws up -- sometimes
>a little, sometimes a lot.  I don't know if I would call this policy 
>"enlightened."  I would say it balances things a little more toward 
>ease-of-use at the cost of reducing reliability.  Why do they need to
>edit /usr/lib/aliaes anyway?  How often does this happen?

They (the faculty) maintain several mail aliases for various groups.
They even *create* such aliases relatively frequently.  No one's
*ever* screwed up anyone else's mail.  This makes creating mailing
lists easy for arbitrary users.
  Michael I. Bushnell       \     This above all; to thine own self be true
         GIG!                \    And it must follow, as the night the day,
mike@turing.cs..unm.edu      /\   Thou canst not be false to any man.
  Hmmmm..............       /  \  Farewell:  my blessing season this in thee!