We had the same situation at GW, when the LISTSERV on our VM system got
into a cat fight with some cruddy majordomo implementation. I think I
ended up blocking this by putting the naughty address in question under
both TRAPIN and TRAPOUT variables in the configuration file, and then
restarting the LISTSERV process.

                                --Jeff B.