At 09:44 08/28/2004 Saturday, Paul Russell wrote: >The intentional routing of error messages to a black hole, or to an >address which causes them to bounce to the site administrator, is not >the action of a responsible list owner. If your list is generating an >unreasonably large volume of legitimate delivery error messages, then >there is a problem with your list and you, as a responsible list owner, >ought to be interested in resolving that problem, rather than burying it. >If you, as a list owner, are unwilling to handle the responsibilies that >come with list ownership, then you need to find a replacement who will >do the job right. Though Paul has previously expressed a LISTSERV design recommendation on more granularity in list operation roles, it is possible to make good use of existing roles: 1) primary [1st'], secondary [other than 1st] -- primary and secondary receive listname-REQUEST mail, and ["quite:] owners; owners can be expressed as role or subscribers of other host-resident lists e.g., list A definition could have OWNER= rfc822_A_address,OWNER(B) where list B has OWNER= rfc822_B1_address,rfc822_B2_address 2) editor= 3) moderator= 4) list-bounce via ERRORS-TO= either to explicit address[es] or other role e.g., OWNER (primary) or OWNERS (all non-quiet:)