MX records

Hi all,

We have a couple of domains running as secondary MX (backup MX).

domain.com. IN MX 10 mx1.domain.com.

domain.com. IN MX 20 mx2.domain.com

mx1.domain.com is the primary mail server.

mx2.domain.com is the secondary mail server.

mx2.domain.com is pointing to a loadbalancer with 2 mta's behind it (mta1.dom.com and mta2.dom.com).

When mx1.domain.com is down all the mail is received by mx2.domain.com (which are mta1.dom.com and mta2.dom.com).

These mta's are trying to connect to mx1.domain.com because that is the primary MX but this is failing because mx1.domain.com is down. After this the mta's are trying to connect to mx2.domain.com but this is not correct because there are connection to it selfs (through the loadbalancer), this is also failing because they can not connect to the loadbalancer otherwise the mail will loop.

How can I prevent the mta's to connect to the mx2.domain.com, in other words how can I configure the mta in a way it also knows it is mx2.domain.com?

Kind Regards,

Bas Toonk

[1088 byte] By [stoonk] at [2007-11-26 11:33:04]
# 1

Hi,

Try adding a rewrite rule to imta.cnf for mx2.dot.com which points back to the host itself e.g.

mx2.domain.com $U%$D@mta1.dom.com

The mta1.dom.com should match the name of the local channel in your configuration i.e. you should already have a channel which looks like this:

!

! delivery channel to local /var/mail store

l subdirs 20 viaaliasrequired maxjobs 7 pool LOCAL_POOL

mta1.dom.com

Then run ./imsimta cnbuild;./imsimta restart

Regards,

Shane.

shane_hjorth at 2007-7-7 3:48:51 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...