OK, we'll try to get our act cleaned up. However, how can you use the :lists. entry of PEERS NAMES to track peer lists when not all peers for a given list have the same list name? We are among the guilty, with our odd $$INFOPC list name, but other peers use I-IBMPC and PC-L in addition to the most common IBMPC-L. This is just an example; other lists have the same problem, especially ARPA redistributions. (INFO-MAC is MAC-L at some sites, etc.) In sum, will knowing all of the local list names really suffice for your application?