The best way to trouble shoot this is to FIRST use the Listserv DISTRIBUTE MAIL DEBUG=YES facility. Unfortunately at this time, I am unable to subscribe (actually confirm my subscription by OK xxxxxx) so I can't do a REVIEW of your subscribership in order to build the "job" to send to Tulsa's LISTSERV. Once the DISTRIBUTE DEBUG output is analyzed viz the non-receiving subscribers (assuming of course that there wasn't a massive SET CDR-L NOMAIL FOR *@fqdn), you then follow the route, one process node at a time, including DNS lookups, MX hosts, mailers, re-routing for NJE users. These techniques aren't taught when you signup to be a list-owner ;-) -- co-owner INFOSYS, TQM-L, CPARK-L, ERAPPA-L, JANITORS, LDBASE-L, et -L URL:mailto:[log in to unmask] "I've fallen and can't reach my keyboard" 31 Shields Bldg. -- Penn State -- University Park, PA 16802-1202 USA