Okay, so I said I would report back when I had something to report.
ahem...I have something to report. 😉 It's fairly technical, so keep that in mind.
Here at the university, we run our Exchange server behind an ISA firewall and have different firewall rules for Outlook Web Access, ActiveSync, Outlook Anywhere, etc., with some rules configured for Basic authentication, some for NTLM authentication, and some for SPNEGO (Kerberos) authentication. (This is a normal, "best practice".) Which authentication mechanism is used depends on the service; for example, Outlook Web Access and ActiveSync both use forms-based authentication, but ActiveSync can only handle Basic auth whereas OWA can handle both Basic and NTLM auth. Outlook Anywhere / Exchange Web Services should be set up to use HTTP authentication and SPNEGO (or "Kerberos-constrained delegation") so that applications like Outlook don't have to ask for your password every time they start; it just passes your logon Kerberos ticket to the ISA box, and ISA authenticates you to the Client Access Server with that ticket. Anyway, both OA and EWS sit behind an ISA rule that requires SPNEGO and HTTP auth.
It seems that this was just too much for Snow Leopard's built-in Exchange support to handle. To test this, I decided to modify one of the rules using Forms-Based, NTLM auth to include the /EWS/* path. Once this was applied, I started Mail.app and gave it a bogus email address to "break" autodiscover. (I needed to specify a completely different FQDN, since in ISA a Forms-Based web listener and an SPNEGO web listener cannot use the same IP address and thus have two different FQDNs.) Mail.app then let me type in the "correct" server, etc., and everything verified correctly. I now have Mail.app, iCal.app, and Address Book.app running, and seeing all my Exchange data in each one.
Another scenario is that perhaps Snow Leopard needs Forms-Based authentication instead of HTTP authentication, which also applies to this set-up: OWA uses FBA auth, whereas OA and EWS use HTTP auth.
Summary (aka tl;dr): Somehow Snow Leopard's Exchange support breaks horribly if EWS is only configured for Kerberos authentication, as in my scenario, or perhaps because 10.6 needs to use forms-based authentication instead of HTTP authentication. Neither of these should cause this problem though, since Entourage handles SPNEGO/HTTP Auth properly, and Firefox can view the EWS WSDL file (
https://your_server/EWS/Services.wsdl) but Safari.app (on OSX) crashes hard, just like Mail.app.
One of our help desk analysts has been talking with an Apple support person, so the next time they communicate this issue will be raised.
Hope this helps someone else out there.
--seth