Of course it is nearly impossible to trouble shoot this from here w/o add'l info including RECEIVED: headers and victim's host. One possible scenario is to issue the following LISTSERV commands: SET listname SHORT822 FOR *@* QUIET SET listname SHORT FOR *@* (this will change all users back to SHORT, some of whom might not have been setup that way so you might want to do this scenario more conprehensively by doing a Q listname FOR *@* first and abstracting those userids that are not already SHORTHDR and SET them accordingly). The result is that LISTSERV will generate one informational message to each current subscriber (regardless of MAIL/DIGEST/INDEX/NOMAIL setting). The victim should then receive a posting UNLESS the perpetrator's remailer has been programmed for the specific list. In that case, before your reset the SHORT option, you would also want to generate a real list posting and have LISTSERV go through the "normal" distribution process, albeit using more network bandwidth since it is generating individualized e-mails (though I'm not sure where those individualized e-mails are actually "exploded" in the LISTSERV Peer network). -- co-owner: INFOSYS, TQM-L, CPARK-L, ERAPPA-L, JANITORS, LDBASE-L, et -L URL:mailto:[log in to unmask] "BEEP if you luv LDBASE"