Well, there are two possibilities. Deleting the BITNET node entry will cause all the Revised LISTSERVs to quickly and efficiently remove all BITNET subscriptions for the NJE addresses, but that does have side effects that you probably don't want (eg, loss of BITNET connectivity). The other alternative is to put a :newnode. tag in your BITEARN NODES entry with a domain name of a host willing to accept the mail; it could be the domain name of the BITNET node if it's also on the Internet. This has the effect of forcing all the Revised LISTSERVs to change the address entries for the affected UNL nodes to that FQDN, and thus, forcing delivery via SMTP instead of NJE. It also disallows further subscriptions to mailing lists with the NJE address, so you may need to do some user education on how to subscribe to lists since TELL won't work any more. It can take several cycles of the BITEARN NODES database to get this accomplished, as some sites don't update their nodes tables immediately, but it should handle the problem neatly. > Our Unix-based > one doesn't. You should investigate getting Revised Listserv for Unix. 'Free' means you get exactly what you paid for, in this case.