Hey all,
I'm an MCSE 2003 (Messaging) certified Network Administrator and planning/testing (in vmware) the rollout of Exchange Server 2003.
I have the first exchange server online on the production network with basic setup i.e. recipient policies, SMTP virtual server settings, mailbox policy settings and other such things.
The plan of action is to get the exchange system working alongside the existing Ipswitch Imail system. The existing Ipswitch system is on its own DSL line, we have a separate DSL line for the exchange system, same ISP.
Objective is to have email delivery to both mailing systems. I first approached the ISP, investigating the options of creating an additional MX record for same domain, different public IP address (other DSL line) but same metric value...! But then discovered that an incoming email will choose either of the two routes! It cannot get delivered to both mailing systems this way!
soooo,
Second solution I have is to leave all incoming email on the Ipswitch system, but setup forwarding, on a per user basis, to the exchange system. I have the following documented for this:
DNS:
Configure a new Sub Zone, exchange.domain.co.uk.
Set MX record for exchange.domain.co.uk to the exchange server.
Make sure exchange can resolve the MX record to domain.co.uk and that it points to the mail gateway or the ipswitch box.
Exchange Settings:
Add new address, @exchange.domain.co.uk which is in addition to @domain.co.uk address in the recipient policy.
Ensure exchange is responsible for all mail sent to @exchange.domain.co.uk but not for @domain.co.uk.
Ensure that @domain.co.uk is the primary SMTP address for the internal recipients.
IPSwitch:
Setup IPSwitch IMail for peering so that IMail and Exchange can serve user accounts on the same domain.
I have this setup in VMware right now and experiencing problems.
Does anyone have any experience with getting exchange to work with other mailing systems and can you recommend another way forward.
Many Thanks
I'm an MCSE 2003 (Messaging) certified Network Administrator and planning/testing (in vmware) the rollout of Exchange Server 2003.
I have the first exchange server online on the production network with basic setup i.e. recipient policies, SMTP virtual server settings, mailbox policy settings and other such things.
The plan of action is to get the exchange system working alongside the existing Ipswitch Imail system. The existing Ipswitch system is on its own DSL line, we have a separate DSL line for the exchange system, same ISP.
Objective is to have email delivery to both mailing systems. I first approached the ISP, investigating the options of creating an additional MX record for same domain, different public IP address (other DSL line) but same metric value...! But then discovered that an incoming email will choose either of the two routes! It cannot get delivered to both mailing systems this way!
soooo,
Second solution I have is to leave all incoming email on the Ipswitch system, but setup forwarding, on a per user basis, to the exchange system. I have the following documented for this:
DNS:
Configure a new Sub Zone, exchange.domain.co.uk.
Set MX record for exchange.domain.co.uk to the exchange server.
Make sure exchange can resolve the MX record to domain.co.uk and that it points to the mail gateway or the ipswitch box.
Exchange Settings:
Add new address, @exchange.domain.co.uk which is in addition to @domain.co.uk address in the recipient policy.
Ensure exchange is responsible for all mail sent to @exchange.domain.co.uk but not for @domain.co.uk.
Ensure that @domain.co.uk is the primary SMTP address for the internal recipients.
IPSwitch:
Setup IPSwitch IMail for peering so that IMail and Exchange can serve user accounts on the same domain.
I have this setup in VMware right now and experiencing problems.
Does anyone have any experience with getting exchange to work with other mailing systems and can you recommend another way forward.
Many Thanks