Only problem is when I attempt to send a message from one account on Imail server A to an email account on Imail server B. It will fail. As well, if I try to send a message to another server within the same network (not an Imail server, but an email receiving server) I also fail. Now, all 3 machines accept messages from the outside world just fine. It's only when I'm trying to send messages internally that they fail. This was never a problem before.
That's because before you had public IPs, and your IMail servers could reach other public IPs. However, after switching to NAT:
In the logs, I just get:
20030723 084428 127.0.0.1 SMTP (147) Trying epage.gabrielwireless.com (0)
20030723 084507 127.0.0.1 SMTPD (00A2011A) [10.1.1.10] connect 10.1.1.10 port 3525
20030723 084513 127.0.0.1 SMTP (147) MX connect fail "216.199.154.53"
IMail still sees the public IP of the other mailserver, but it really needs to know the private IP. I'll bet that if you use a workstation with an IP of 10.x.x.x, and try telneting to 216.199.154.53 on port 25, you'll have the same problem.
What you need to do here is make it so that the IMail server sees the internal IPs. This can be done a number of ways, such as having a separate DNS server that returns internal IPs, using HOSTS files, or I believe the latest version of BIND has "views" that could be used for this.
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers.
Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection.
Find out what you have been missing: Ask for a free 30-day evaluation.
--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
