Lisa, It sounds like possibly a name resolution problem. First let's nail down the mapping you did. Ports 25 and 110 should be mapped to the NT server (assuming you're offering pop and smtp. The NT server should have the firewall set as the default gateway (as should be on all internal boxes). I'm assuming the firewall is acting as the router for everything. Make sure that the DNS servers listed in the IP stack of the NT server are workable. I prefer to use external DNS servers as my lan is much too small for my own bind server. If you are running a local DNS server, then use your local DNS server as the primary and an external one as the secondary. You didn't specify if you are running Exchange. If so, do you have an SMTP gateway (they call it Internet Mail Connector) running? If you're running Exchange 2000, it sets up by default. If it's 5.5, you'll need to set it up. Give these a look and let us know.
<<JAV>> -- ---------- Original Message ----------- From: "Lisa" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thu, 28 Nov 2002 15:47:44 -0000 Subject: problems setting up NT Mailserver inside linux firewall > I'm setting up a linux firewall and moving an NT Mail server onto a > new network behind this firewall. The machine where the firewall > resides has one internal interface and one external interface. Dummy > ip addresses are used for machines on the LAN inside the firewall. > > At the moment, we have just changed the mail mx record to > correspond to the new network address . > > In my firewall I have a rule that maps any traffic destined for the > mail address to the internal mail server dummy ip. When I email from > the mail account to any external mail addresses and vice versa it > doesn't work. > > can anyone help me as I have no idea what to do. ------- End of Original Message ------- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
