Eugenio offers good advice about setting up a separate userid to reference via the ERRORS-TO= list definition keyword. This is especially useful if it can be directed to a shared account where responsibilities for processing bounces are ... shared. (Regardless of sharing, sometimes (other) bounces do NOT identify the offending account since LISTSERV has essentially used BCC: to distribute to all recipients. In this case, it is sometimes useful to temporarily set each co-located user with the SHORT822 option. In fact, the mere SETting of this option (in non-QUIET mode) might be sufficient to "trigger" the bounce for a user with sufficient info to set NOMAIL (or DELETE).) /Pete Weiss at Penn State