From before - I decided that My Real Problem with Outlook having a single delivery location is the speed of that location vs the accessibility. A local PST is relatively quick, but it's inaccessible except via Remote Desktop (not terrible, but not Webby). An RPC/HTTP based mailbox on a remote host in the US is
Delivering from one or more POP3 accounts directly to a US-based server didn't inspire me with Local Data Confidence, so the answer is to - yet again - run up a server at home, and use it as my storage location, albeit a relatively useless one at this point. I have some smart host-y ideas on how I can get around the work mail issue.
The notional layout is:
Outlook 2003 -MAPI> SBS/Exchange 2003 (Domain A) -> POP3 Connector (Domain B (and ISP?))Outlook 2003 -POP3> ISP mail (stored on above Exchange box)
And I get to use OWA to quickly read email at home if I can't use Remote Desktop. Plus, I get to use a Real, Live SBS box.
This time, I'm going back to a Virtual Server-based solution, and I'm going to give SBS2003 my first production run, to see how it shakes out. Kids, don't try this at home. And the VHD will be portable, which might be useful at some point (I toyed with the idea of using the physical disk, but eventually settled on file-level portability).
Yes, my hosting server is called "Misery". It's traditional.
Next time, run the setup on a fast machine, then port the Additions-installed VHD over. Duh.
I truly believe Virtual Server is one of Microsoft's best products.
And it's one of the best Microsoft products I'll be able to run under x64, to boot! :) (using the sp1 beta, natch)