I'm in the middle of our migration and I have an issue with how Scalix is reading our MX records.
Our webhost hosts our MX records, they are very slow to enact changes.
We started off with just one MX record before the migration, that MX pointed to server we host internally (mail1.domain.com).
Friday night we added a second MX record for Scalix (host150.domain.com) and blocked SMTP to Scalix from the 'net - internal users could still see it, we did this to test groups etc but we didn't want new mail going to Scalix until we shut down the old mail server on Saturday.
The MX records look like this (from dnsreport):
30 mail1.domain.com. [TTL=86340] IP=XXX.XXX.XX.35 [TTL=86340] [AU]
20 host150.domain.com. [TTL=900] IP=XXX.XXX.XXX.150 [TTL=900] [AU]
However when sending mail through Scalix it accepts delivery and then tries to send in on to mail1 (old server). I took mail1 offline so Scalix would try to send to itself, however it just keeps trying the old server. Below is from maillog:
Oct 14 06:45:56 host150 sendmail[5682]: k9DKjtWe005682: to=<james@domain.com>, delay=00:00:01, xdelay=00:00:00, mailer=relay, pri=30784, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (k9DKju1w005698 Message accepted for delivery)
Oct 14 06:47:56 host150 sendmail[5704]: k9DKju1w005698: to=<james@domain.com>, delay=00:02:00, xdelay=00:02:00, mailer=esmtp, pri=120991, relay=mail1.domain.com. [XXX.XXX.XX.35], dsn=4.0.0, stat=Deferred: Connection timed out with mail1.domain.com.
Have I missed something really simple? Sorry if I have (damn headcold).