I have Exchange 2003 on a new server. I am looking for how I can have it pull the emails from our web server. We currently have all the computers receiving their emails via pop3 from our web server. I would like to keep them being sent there but have Exchange dowload them when it is running. I have read about this requesting ETRN/TURN from the web server. How can I verify if my webserver does or even can do this?

In order for ETRN/TURN commands to be used by exchange to download mail from a web server that server must be running as a SmartHost, basically an smtp server which has the ability to queue & relay messages for your domain. Check with your service provider if they can change the functionality of this server from a standard pop3/smtp server to a smarthost. Alternatively there are a number of 3rd Party POP3 connector utilities out there which can be used as an interface between Domain Pop accounts & an Exchange organization, (they usually download the mail through POP & pass it onto exchangevia SMTP)google would be your best resource here for finding the tool to suit your environment & budget. If you are running SBS 2003 version of Exchange then there is a native POP3 connector built in so you wont have to buy one, simply setup the native one with all the pop3 accounts & passwords as well as download schedule.

Thanks for the info Johan. The only downside to using the pop3 connector is that the most frequest setting for download is every 15 minutes, I wish we could have it faster.

you will encounter a similar limitation when it comes to automatically issuing etrn/turn commands, unless of course, you script this & set it to run every other minute or what ever your requirement. one of my clients is using pop beamer & this seems to have an open schedular, i.e. you can enter the number of minutes between download schedules manually. For others perhaps you can override this setting through a registry hack, be careful if trying this though and be sure to backup the registry first. as an alternative, should you have a static public ip on your server you could always register an additional mx record with higher priority allowing mail to be routed directly to exchange normally and only to your service provider for instances where your server becomes unavailable, ie use the service provider domain pop as secondary backup mx.