Following a problem recently reported to me, I would like to suggest that some changes be made. The problem: On a Listserv list, mail went via distribute, as normal. One of the jobs came to PUCC. PUCC handles most of the DIST traffic for the CUNY area. In this area is a node at Hunter College, called HUNTER. This is HUNTER.BITNET. At Princeton is a node called HUNTER. This is HUNTER.PRINCETON.EDU. SMTP @ PUCC tries to send mail to userid@hunter (the address of the person on the list), but doesn't find the user since it has the wrong node to begin with. One solution: DOMAIN everything. Listserv should put .BITNET on the end of every address that it not already domained. This is NOT a permanent solution, since .BITNET is a kludge. With 1.6c, or perhaps a FIX for 1.6b, an exec could do this to all old lists and it would be the default from now on. Note: This is not the only place that this happens/will happen. Any site can have this problem if it has duplicate names in its domain and out when the outside uses inside software. In this case, MAILER using SMTP when Listserv acts as a sort of gateway. Listserv should be all inside or all out of a domain. Those are my thoughts. I bring them to you with lots of courage as I know this could start a war. With that in mind, comments are encouraged. If I haven't been perfectly clear, I can post a more lengthy discussion with examples. I don't claim that Listserv is a culprit, just that it may be the easiest thing to work on to solve the problem short term. Thanks. /Geert