Our institution is much the same ... Moving to Exchange 2003 while maintaining a front end EMWAC server.
- Exchange server was setup so as the “Virtual SMTP” service would only accept connections from the IP of the EMWAC server AND authenticated connections (covers future user connections).
- I allowed the Exchange server to deliver outgoing mail directly as it WILL eventually be our only mail system.
- Purchased and installed “F-Prot for Exchange” licensing and have had no trouble with it – from my research it is the lowest cost AV option that is directly integrated into the Exchange server (scans mail internally as well as incoming and outgoing).
- Added an additional default Exchange email address policy for all new mailboxes created (“forward”.domain.com) this allowed me to simply add additional DNS entries for the exchange server so the EMWAC could forward to these addresses without user intervention (DNS entry for the exchange IP = “forward”.server.com” AND of course a DNS MX entry for “forward.server.com”).
- When a user account is given an exchange mailbox an “ims.ctl” file is created in their EMWAC mailbox to forward all mail to their exchange mailbox “[EMAIL PROTECTED]” - users were directed to use “OWA” Outlook Web Access (also configured on the new exchange server) until a technician could either reconfigure their email client or as per our standardization on the Micro$oft platform setup Outlook to connect to the exchange server.
So to answer your questions:
- As above.
- In our case, incoming only.
- No change to port numbers, DNS as above ... The final stage is close at hand ... Once we’re ready to fully implement the exchange server I will simply be pointing the DNS entries for our primary address directly at the exchange server (“domain.com”). Before that point I will be completing the exchange configuration of filtering to use Realtime Block Lists (RBLs) and adding some form of spam filtering (still researching the later).
Regards
Don
Don R. Hill
Northern Lights College
Computer Systems Support Analyst
Regional Administration
11401 - 8 Street
Dawson Creek, BC, Canada V1G 4G2
[EMAIL PROTECTED] http://www.nlc.bc.ca
Ph. (250) 784-7558 Fax: (250) 782-5233
On 11/10/05 4:14 AM, "David West" <[EMAIL PROTECTED]> wrote:
Hi
I want to do this - IMS as a front end to Exchange 2003.
Sorry if it's a bit simple; but we are new to Exchange, the bosses are keen for us to move over to it, and I don't want to loose the filtering /antivirus capabilities of IMS and its add-ons.
- How do you configure IMS and Exchange so it works?
- Does IMS protect incoming mail only or both way traffic?
- What about port numbers and DNS registration, etc?
David
Don R. Hill wrote:
Our EMWAC, which was passing messages just fine to our Exchange 2003
server .......
