NOT speaking for PSUVM: To reduce server load (in NO particular order): 1) default list distribution options * Default-Options= SHORT (you might need to issue a QUIET SET listname SHORT FOR *@* after you update the headers) 2) don't use archives (but that is a useful feature) 3) use a REPLY-TO: SENDER,RESPECT 4) have a DIGEST distribution for those who want it 5) use auto-deletion methods e.g., * Auto-Delete= Yes,Semi-Auto,Delay(3),Max(25) 6) have a WELCOME file (listname WELCOME) that answers most questions that new subscribers will most likely have; also netiquette guidelines that are clearly articulated and enforced in order to reduce meta list traffic 7) only allow subscribers to post (this cuts down on SPAM) 8) followup on subscriber distribution bounces (these techniques have been discussed continually right here) 9) encourage responders to the list to edit original postings judiciously (or simply use a significant SUBJECT: RE: original subj) 10) provide a Bottom_Banner template that gives instructions on how to contact the list-admistrator for help (instead of broacasting to the list) 11) require new subscribers to use the CONFIRMation process * Subscription= Open,CONFIRM * Confirm-delay= 71 h 12) encourage survey requests to have responses sent directly to the surveyor who then should summarize the results and make them available to the subscribership (perhaps via list distribution, file stored in the list's archives, FTP, WEB, etc) 13) have a co-owner who can take over when you're on vacation, away from your terminal, etc. 14) limit the number of daily postings (if necessary) 15) limit the size of any one posting (no xxENCODED files) -- co-owner: INFOSYS, TQM-L, CPARK-L, ERAPPA-L, JANITORS, LDBASE-L, et -L URL:mailto:[log in to unmask] "Never confuse the messenger with the message"