On Mon, 27 Jan 1997 11:00:13 Christian J Reichetzeder said: >On Mon, 27 Jan 1997 10:03:09 -0500 Terry A Moore said: >>I'd like to figure out if the key to the error is the "MX records will >>cause loop" or the "User unknown" message. I've never understood the >>MX loop issue. Perhaps one of the gurus here can enlighten me. ... >Second, I wonder where the TWO recipients come from. Wild guess: the >gateway sees [log in to unmask] and expands to [log in to unmask] Yes, that is one of the things that the gateway does. >for which it finds an MX to lmail.vm.timken.com. Now it MAY be that this >name has changed recently from lmail.timken.com to lmail.vm.timken.com. >Unfortunately lmail.timken.com is not aware of this change, i.e. it does >not think it should deliver lmail.vm.timken.com locally - this it looks for >an MX for lmail.vm.timken.com which perhaps has none and uses a generic MX >which points to the gateway. >it's name and tries to find MX records for this name. In doing so it Exactly right. The name was changed on the gateway and the listserv host back on January 8 while trying to solve another problem. No problem until this weekend. I'm guessing that the change never really took affect until the gateway was upgraded this weekend; then, voila, we had a problem because -- as you say -- the listserv host and lmail did not recognize the domain as a local one. I added the additional domain to the list of local delivery domains and traffic to the listserv started flowing again. Thanks for the push in the right direction. ------------------------------------------------------------------------- Terry A. Moore | The best job Sr. I/S Tech Specialist | is a quality job. The Timken Co. | Autograph your work with QUALITY. [log in to unmask] |