Caaaaarn (that's Australian for "come on") - you don't run firewall-less servers on the Internet, really, do you? Smiley

I'll preface all this with: I haven't supported Exchange/Outlook for A Long Time. So grains of salt may be required.

135 (the RPC endpoint mapper) was the port associated with the Blaster attack, and we typically recommend that it's blocked at the perimeter (btw, ISA can do RPC publishing for MAPI, there, that's my sales pitch for the year done!).

Outlook can be configured in several different ways, but if your mail profile tells it that it's going to be using an Exchange Server, it'll try to use that as the primary store.

If you're happy using just IMAP, delete the contents of the current mail profile (eg, remove all the accounts, or delete the profile through Control Panel/Mail), then create a new profile with just IMAP and a Personal Folders (PST) file.

That'll probably work, but as you mentioned, you don't get the full Everything Experience.

Back on MAPI (eg, regular client access): My $0.02 - get the client computer on the same LAN as the server. If it works there, you're good. If it doesn't work there, troubleshoot it as a local connectivity/settings issue, without The Internet in the picture.

Once you've got it working on the LAN, set up RPC/HTTP, and go roaming. Exchange/Outlook aren't configured/optimized for Internet Roaming out of the box (the out of box experience is primarily focused on users on a LAN with Exchange - that may change...?) so some assembly is required for RPC/HTTPs.

Once it's set up, it's fantastic, and it works from basically anywhere. Until then, don't expect the Internet to be port 135-friendly, and as a plea to all troubleshooters out there - please, please, please, don't be turning off any firewalls between the Internet and your server - even for testing, it's probably going too far. Just work out what you need to expose, and expose only the minimum amount of surface area possible.