tom_szabo
asked on
How can email end up on the wrong server?
Hi All,
I have a rather angry client that had a SmallBusiness Server 2003 in his head office, running exchange as their mail server. Due to some logistic consideration, we have created a new server ( it was a little more complicated but in essence) and placed an EXSi dual quad server into a Data Centre.
From this moment we started to have wierd problems. Some of the problems were caused by me overlooking new factors introduced by being on an open WAN. In any case, the final setup is:
Debian firewall with IPTables as the gateway.
SBServer as the exchange and file server
Terminal Server ( windows XP running RDPlus)
The apropriate ports are forwarded to the two servers throung IPTables. The two Windows servers sit on a local IP range not accessable from the WAN
This above is what is in the data-centre.
In the Head office:
The original Linux box, SmallBusiness Server and same XP Running RDPlus
The delegation is set to point to the new server, but the emails are still ending up on the old server in the Head office
Thedelegation has been checked a number of times, just to see if we missed anything... no, all looks ok. We have done the same kind of delegation for years for many clients, never had any similar issues.
If I check the domain name/ IP address, all looks good. nslookup returns the correct setup, ping returns the correct IP, but when the email leaves, it goes straight to the OLD server in HO.
I thought maybe some forwarding, we chaked over and over again, no pop 3 connector, no forwarding...
To make sure it is not something "hidden" I set up an account called mlog, and forwared all incoming and outgoing emails on both servers to the respective mlog account.
Guess what? The emails don't even touch the server in the DC. They only appear to show up on the HOffice. So we are stuck.
How can this happen?
TIA,
Tom
I have a rather angry client that had a SmallBusiness Server 2003 in his head office, running exchange as their mail server. Due to some logistic consideration, we have created a new server ( it was a little more complicated but in essence) and placed an EXSi dual quad server into a Data Centre.
From this moment we started to have wierd problems. Some of the problems were caused by me overlooking new factors introduced by being on an open WAN. In any case, the final setup is:
Debian firewall with IPTables as the gateway.
SBServer as the exchange and file server
Terminal Server ( windows XP running RDPlus)
The apropriate ports are forwarded to the two servers throung IPTables. The two Windows servers sit on a local IP range not accessable from the WAN
This above is what is in the data-centre.
In the Head office:
The original Linux box, SmallBusiness Server and same XP Running RDPlus
The delegation is set to point to the new server, but the emails are still ending up on the old server in the Head office
Thedelegation has been checked a number of times, just to see if we missed anything... no, all looks ok. We have done the same kind of delegation for years for many clients, never had any similar issues.
If I check the domain name/ IP address, all looks good. nslookup returns the correct setup, ping returns the correct IP, but when the email leaves, it goes straight to the OLD server in HO.
I thought maybe some forwarding, we chaked over and over again, no pop 3 connector, no forwarding...
To make sure it is not something "hidden" I set up an account called mlog, and forwared all incoming and outgoing emails on both servers to the respective mlog account.
Guess what? The emails don't even touch the server in the DC. They only appear to show up on the HOffice. So we are stuck.
How can this happen?
TIA,
Tom
ASKER
I am happy to give it to you directly, but prefer not to give details publicly: my email is tom -at- intersoft.net.au - send me an email and I will send you the details
TIA,
Tom
TIA,
Tom
ASKER
Hi Oklit, Your server rejected my email! >>Client host rejected: I don't want emails from APNIC<<
Heh.. antispam rule ;) This will be my first nonspam email from APNIC's IP range ;)
I've added your email to whitelist - try again.
I've added your email to whitelist - try again.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the help, as it turned out it was an issue with the Postini system, all sorted now, Thanks again
Can you write here what is your domain so we can check it (as well as your old and new server's name/ip)?