--
This is our setup:
(Running Debian and Exim 4)
We have a firewall with an IP : 207.139.193.66 tunneling port 25 to
10.10.6.70 (our mail server)
Our mail server is secondary for some domains, and it is
relaying/accepting the mail fine for those domains.
As soon as it gets the mail and accepts it, it appears to check DNS for
the MX records, and sees that the next one from the primary (which is
down) is address 207.139.193.66 and tries to send it there. The
firewall receives it and sends it back to 10.10.6.70, this process goes
on until it detects the loop and the message is dropped.
Our machine is machine.packetworks.net
The DNS entry is mail.packetworks.net
I have mail.packetworks.net and machine.packetworks.net in the local
domains.
I tried setting the machine hostname to mail.packetworks.net
I put in the exim config the FQDN is mail.packetworks.net
It seems to ignore all these and check by the DNS. How can I get this
server to know to hold the mail for MX pointing to
207.139.193.66/mail.packetworks.net or any domain in our domain list of
secondaries?
Is this problem because it.s internal IP is 10.10.6.70?
Thanks
--
\Steven.
/*
| Steven R. Bourque, CCNA
/"\ | Network Engineer
\ / ASCII ribbon campaign | Packet Works Inc.
X against HTML email | p: 519.579.4507. f: 519.579.8475.
/ \ | http://www.packetworks.net
| PGP ID: 0x373AB23B
*\
--
[ Content of type application/pgp-signature deleted ]
--
