On Wed, 16 Mar 1994 21:18:24 EST Eleftheria Maratos-Flier said: > >You can't stop the error messages as far as I know. You can only put >the list on hold. You might ask someone on the list to take error >messages while you are gone; you would have to add the person to your >header as an owner. > Not only would you have to add the person as an owner (probably under Quiet:), but you would also have to change the Errors-To= keyword to reflect to whom you want the errors sent--i.e.: * Errors-To: NEWOWNER@HISNODE * Owner= OLDOWNER@HISNODE * Quiet: * Owner= NEWOWNER@HISNODE If you simply add the new owner as a primary (i.e., non-Quiet:) owner and leave the Errors-To= set to Owner, you're <both> going to get the error messages--which would defeat the purpose. Conversely, you <could> add the new owner above your own entry and then insert a Quiet: between your entries, i.e.: * Owner= NEWOWNER@HISNODE (New Owner) * Quiet: * Owner= OLDOWNER@HISNODE (The Original Owner) If you do this, you can leave Errors-To= set to Owner. Also don't forget that if you have your list set to Validate= All Commands, the new owner will have to have your list password to set people to nomail, etc. Ah, for an option to set Errors= BITBUCKET... :) But then, that wouldn't be very helpful, would it? Nathan BITNET: NBRINDLE@INDYCMS ------------ Internet: [log in to unmask] Nathan C. Brindle, Administrative Specialist, Student Activities Office Indiana University Purdue University Indianapolis Staff Advisor, Alpha Phi Omega Nat'l Service Fraternity, Tau Omicron Chapter List Manager, STUACTS, APOSEC52, ACCESS-L, BRTHPRNT, EXCEL-L & STUDENT@INDYCMS Disclaimer: My opinions are my own. Indiana University can speak for itself. ------------------------------------------------------------------------------