I'm running Bind for my domain. I do not have a zone for 192.168.0. setup in bind. However, I do have some entries in the /etc/hosts file on the email server for the machines on my private network. Will turning off DNS lookups for ESMTP in the webadmin interface be a way to check if this is the problem? Do I need to hack in a 192.168.0. zone? I assumed that the DNS lookup was on the domain in the TO and FROM addresses not the connecting machine... am I wrong here?
Michael Carmack <kar...@karmak.org> 03/04/02 03:00PM >>>
On Mon, Mar 04, 2002 at 07:04:43AM -0800, Nathan Harris wrote:
I have Courier (the whole suite) running on a server with two Ethernet cards. One is on a private network (with IP 192.168.0.254) and the other is on a valid Internet IP address. The server name resolves via DNS to the valid Internet IP. Clients can access everything perfectly from outside on the Internet (POP3, IMAP4, ESMTP, Webmail). However, clients on the private network can access POP3, IMAP4, and Webmail but not ESMTP. Our clients are running Outlook 2000 (yea I know!), so there may be some relation there, but it appears to be a general problem with the private network setup. There is nothing helpful in the Courier log. It appears that the connection is being made (log entry for esmtp connection is there), however, after quite a while, the connection is dropped with an unsuccessful delivery reported by Outlook. Unfortunately, I'm not on site right now, and I can't use any other client (Mozilla, telnet, etc...) on one of the Windows boxes to try to get more info. By the way, all email clients running locally on the machine work fine.
Do I need to add two names/IP addresses to the "me" file? Any idea on how I can get this working?
Are you running a local nameserver, and/or do you have entries in /etc/hosts
for the local machines? This might be an issue with DNS lookups.