I run qmail on one IP on my server
I run Kerio on another IP on the same server
I have a number of domains running on qmail... and have just moved a couple to Kerio.
The problem now is that users on the qmail-hosted domains can't send to users on the Kerio domain. Qmail seems to think the MX records for the domain point to it's IP, when they actually point to the 2nd IP of the server.
Has anyone seen this before? Is there some hidden setting somewhere in qmail that's making it "remember" these old domains it used to look after? Running a dig mx <domain> lists the 2nd (Kerio) IP/hostname ... so I'm at a loss as to why it won't deliver there.
Maybe qmail thinks it's listening on the 2nd IP? How can I tell qmail it's NOT? (I'm using tcpserver to manage this)
Thanks all,
R.
I run Kerio on another IP on the same server
I have a number of domains running on qmail... and have just moved a couple to Kerio.
The problem now is that users on the qmail-hosted domains can't send to users on the Kerio domain. Qmail seems to think the MX records for the domain point to it's IP, when they actually point to the 2nd IP of the server.
Has anyone seen this before? Is there some hidden setting somewhere in qmail that's making it "remember" these old domains it used to look after? Running a dig mx <domain> lists the 2nd (Kerio) IP/hostname ... so I'm at a loss as to why it won't deliver there.
Maybe qmail thinks it's listening on the 2nd IP? How can I tell qmail it's NOT? (I'm using tcpserver to manage this)
Thanks all,
R.