Snow Leopard with Exchange support not working

Homerz, if you gave me Orville Wright's biplane with enough work I could make a space shuttle out of it. Your argiment is theoretically correct, I suppose, but it's not at all practical, and daming Apple with it is just silly. Not to overstate the obviouss, but Apple is not Microsoft. Apple has to work with the protocols Microsoft makes avaliable to them. That's what's going on here.

This topic is out of hand. It looks like the issue is both the lack of MSFT IT admins not keeping up with the times.

IMAP, IMO, is the worst option of them all. It is not as comprehensive while allowing security flaws.

Finally...all people are asking for is feature parity with the 2 year old iPhone2.0 software. That is the gist. THe underlying methods/protocols are of non-importance to me.

Also, the arrogance of A A P L is very disconcerting here. Use macrumors.com...your posts here are like a disease. They spread like wildfire and are most unwelcome.

No, what's unwelcome Seth is ignorant rants of people who do not understand the topic at hand and continue to blame everyone else for this "problem"
If you want to come here and have mommy cuddle you because you refuse to accept facts, then I'm not the guy for you.
If you want to come here and get real answers to questions, I do my best (as have others here)
If not succumbing to your rants means "arrogance", so be it.

There is no need for all the hostility.

There is an issue mentioned a few times here that no one is addressing - for many of us, when we try to add an exchange account to mail, ical, or address book in 10.6, the app just crashes. Very un-Apple like and kind of troubling. I'm seeing it posted on more and more forums and it seems no one knows what is causing it.

That's why new threads should be created.
The OPs topic is the one I'm replying to.
Mail crashing (which has happened in previous iterations) should be addressed in a new or continuing thread on that topic.
It's frustrating to explain why something is and continue to get ragged on over it because people don't either understand or like it.
I can't change it.
Apple can't change it.
They created different protocols for good reason.
Ask an Exchange admin.

The question that has not been answered is why is it Entourage Web services edition can access my NHS.net (Exchange 2007) without issue and SL Mail cannot? Surely this must mean that the problem is with Apple Mail.

I think the issue of mail, ical, and address book all crashing when trying to add an exchange account goes fine in this thread, titled "Snow Leopard with Exchange support not working". You don't agree??

This is not only the mail app I am talking about here, it is an example of exchange support not working in Snow Leopard. I have seen dozens of reports of it online now, and it is probably a pretty serious bug...

Exactly my problem too. Why does Entourage work, but Mail does not?

Your Exchange 2007 server must have service pack 1 and roll up 4 installed to work with Mail.

deh2k wrote:
Your Exchange 2007 server must have service pack 1 and roll up 4 installed to work with Mail.

And if it doesn't, mail will just crash violently and send a bug report to Apple? Something is clearly wrong here.

deh2k wrote:
Your Exchange 2007 server must have service pack 1 and roll up 4 installed to work with Mail.

Which is the exact same requirement for Entourage 2008 EWS and that works fine. This obviously must mean the problem is with Apple Mail as I said in my previous post.

This is terribly disappointing. My number one reason for upgrading was Exchange support... I was confident it would work because iPhone works fine with our system. This is the first time I have upgraded and felt I didn't get what I asked for and I have been using Mac's since mid-80s. Exchange support was the one main new feature and I believe Apple broke its "promise" to its loyal users by not articulating the limitations clearly. This feels like windows... "make sure you read the fine-print"...

Wow, what a thread. Look, I know this is an Apple support forum, but we obviously are all having issues surrounding Exchange in some way, shape, or form. In my case, we are a small operation, and therefore, I am the only one who researches this kind of stuff. We meet all the system requirements from what I can see, but this EWS thing is a mystery to me. Does anybody know what's entailed to "enable" this, for lack of a better word?

I'm not interested in discussing who is offending who, etc... I am interested in answers, just like most of you are too!

To quote Star Wars, "Stay on Target!" 🙂

May the Force be with us all. 🙂

The appropriate place for that kind of answer would be on Microsoft's knowledge base.
While an EXCH admin may pop in here, that's where I'd look, Luke 😉

SB

I agree, A A P L. Just trying to cover all my bases. Hoped I could find a Yoda on this board. 🙂