Steve is waxing lyrical over Office 2003. I don't think he's using IMAP.

Outlook has always had problems with IMAP. It doesn't cope with the IDLE command well, there's no immediate delete options (you have to mark as deleted, then purge), it used to connection per subscribed folder, instead of using one connection and iterating and using secure IMAP causes my wireless connection to drop, poll for APs and then reconnect. None of this appears to have changed with Outlook 2003 (although it might be using less connections). They have added another "feature", spam trapping. I do my spam filtering at the server level, using various spam lists to check incoming connections and drop them if they look like spammers. Outlook 2003 has a new, improved, whiter than white spam filter, which works on the client side (if you're using POP, IMAP or WebDAV). It creates a "Junk mail" folder, with its own snazzy icon. Wonderful, very pretty. Except I don't want this folder. Even if you turn off the spam filtering the folder stays there, un-deletable. Even "better" it's created the folder on the IMAP server. If you delete it off the server, next time Outlook runs it recreates it. You can't rename it either, or unsubscribe from it, it keeps coming back. I still can't use secure IMAP, wireless drops (this does not appear limited to my hardware, it happened with a different network card, and different chipset too) so if I'm on a public wireless network my mail is recieved in plain text and you can read the username and hashed password.

You have to add manual rules to get the new, transparent new popup mail notifier working for IMAP folders, double clicking the new mail icon in the system tray takes you to your local inbox, not the IMAP folder containing the new message, you can't set followups on IMAP messages which trigger reminders, search doesn't work (limited to local copies), but hey, image supression is nice.

Finally, as usual, PGP stops working, and the PGP support staff are as much use as a chocolate teapot. They won't even confirm or deny if an update to support 2003 is coming.

But I did steal his idea on aspx wildcards, with an adjustment.

String sParams = Request.RawUrl.Substring(Request["URL"].Length);

actually is prefixed by the / in the URL, so you may need to drop the first character

sParams = sParams.Substring(1);

Your paths also change, so no more relative links to stylesheets, absolute only please.