Previous 1 40 41 42 43 44 Next 717 Replies Latest reply: Nov 5, 2014 1:53 AM by StueyBhoy Go to original post Branched to a new discussion.
  • inked at dolltattoos Level 1 Level 1 (30 points)

    In Safari: See if is there. It should prompt you for credentials.  You'll get dumped to services.wsdl if successful.


    If not there...the Exchange server might have been reconfigured to no longer have web access.

  • inked at dolltattoos Level 1 Level 1 (30 points)

    I have found that my iPad will get messages before my MBP.   I have a feeling the messages get pulled into the file system but it takes a couple of minutes for Mail to refresh itself. 


    This entire thread points to permission issues on the various Mail folders (on disk) getting screwed up.  That's why changes to any parameter seem to clear the issues.  The permissions get refreshed, then everything works.  It also explains the databases getting out of sync.


    Hmm... Maybe I'll do some process watching tonight to see if a Mail cron task needs a more frequent interval.

  • Laurent Daudelin Level 1 Level 1 (50 points)



    It seems to be there because I get a prompt from Microsoft Forefront Threat Management Gateway to authenticate. After authenticating, it indeed displays the services.wsdl.


    So, what does that mean?

  • inked at dolltattoos Level 1 Level 1 (30 points)

    It means you have outlook web access.


    Set your exchange accounts's external server to


    Over in the Advanced tab, external server path should be: ews/exchange.asmx

    External port:443

    Make sure use ssl is checked.


    Think of that wsdl page as a menu of functions the exchange server offers.  Mail uses that to talk to exchange. Using that, anyone can write a client to talk to exchange. 

  • Laurent Daudelin Level 1 Level 1 (50 points)

    After I changed the internal server for the Outlook URL, it seems to work, more or less, from work. I say more or less because sometimes I get the messages sent to me, sometimes I don't. When I try to send a message, sometimes it gets through, sometimes Mail displays the SMTP server list and says that it cannot use the Exchange server to send. Not sure why it's not reliable...


    But thanks for your help, that got me somewhere.

  • pnoble Level 1 Level 1 (0 points)

    "seems to work more or less"...."sometimes it gets through".....And this is what we should accept in our corporate email?


    On the eve of the 100,000th view of this particular discussion: Earth to Apple!!  Anyone there? Any plans to fix this?

  • inked at dolltattoos Level 1 Level 1 (30 points)

    If you're interested in solving the problem, or even helping identify the reasons behind it, I think we'd all welcome your input.


    However, if all you wish to do is complain, please allow me to direct you to Microsoft's Windows operating system and any number of vendors who sell Windows-compatible PCs.  I'm certain you'll find bliss there.

  • inked at dolltattoos Level 1 Level 1 (30 points)

    If you get a chance, fill in that same information for the External servers and try it from home.  I wouldn't be surprised if you reported back that Mail was rock solid at home.


    Note: that is, of course, if is accessible from outside the corporate network.  If your company offers it, you may have to use VPN to access it.


    Good luck!

  • bradhs Level 1 Level 1 (0 points)



    I doubt there's anything wrong with Mail 10.9.2, most likely an issue with your Exchange setup.  I'll help you, but I need more details.



  • pnoble Level 1 Level 1 (0 points)



    Thank you for your kind offer. What details do you need?  Our sys admin, Peter, can provide.


    To reiterate:


    We are using Exchange '07 and there were no synchronization issues whatseover (neither with prior OS X releases) up until the minute I personally upgraded to Mavericks, with no change whatsoever to Exchange or Mac Mail setup, at which point: a) emails began to appear in my in box much delayed unless the app was reopened, b) email deleted via iOS devices only deletes in Mac Mail when one clicks on it and c) sending attachments frequently cause(d) a can't send with this server error but a second attemp would always work.


    The only thing that may have been resolved by the latest release is c). A workaround for a) is setting check for email to every minute from automatically. b) doesn't seem to have a work around and is a bit of an annoyance.


    I must say that I spoke with our sys admin just this morning and he told me that he has not read anything so far in this thread that has suggested to him an approach that he has not already tried. But I greatly appreciate your offer of help and we will be pleased to provide whatever info you need.


    From my perspective: if Apple had fixed what is obviously a problem (based on my personal experience and many of the 623 messages and nearly 100,000 views on this discusion so far), why wouldn't they announce it in the release notes? The word Exchange has not been once mentioned in any of them. And there is still a link on this page to an article describing the problem and an akward workaround only.


    If however, it is simply a matter of requiring a change of setup in Exchange (or Mac Mail) to enable Mavericks compatibility, why wouldn't Apple simply have published such instructions? To replace the article linked on this page, last updated on February 7, that suggests that there is none?


    Again, thank you for your kind offer of help!

  • bradhs Level 1 Level 1 (0 points)

    Hello pnoble,


    Mac Mail and Outlook for Mac both use a different path to access your Exchange server.  This is called EWS.  iPhone and Outlook for PC use something different.


    Do you mind proviging me the domain name of your email address?


    I tried posting my email address here a few time and Apple just deletes it.  If you have subscribed to this thread and have received email notifications there is a chance that you have my email address in one of those.  Please search for it.  It starts has the word bradish in it. 

  • peter_watt Level 3 Level 3 (905 points)

    There may be nothing "wrong" with Mail 10.9.x, but there is something "different" about it, in that people now have to scrabble around tweaking Exchange settings that were fine with 10.8

    Like the man said, where is the technical brief from Apple for Exchange admins?

  • NemesysSoft Level 1 Level 1 (10 points)

    I'm outside the corporate network where I work (I'm a consultant), so it should be the same whether I access the Exchange server from where I work or from home but, for some reasons, I can't get it at home.

  • bradhs Level 1 Level 1 (0 points)



    Publically this is all you are going to get.  See item #5.


    • Adds the ability to make and receive FaceTime audio calls
    • Adds call waiting support for FaceTime audio and video calls
    • Adds the ability to block incoming iMessages from individual senders
    • Improves the accuracy of unread counts in Mail
    • Resolves an issue that prevented Mail from receiving new messages from certain providers
    • Improves AutoFill compatibility in Safari
    • Fixes an issue that may cause audio distortion on certain Macs
    • Improves reliability when connecting to a file server using SMB2
    • Fixes an issue that may cause VPN connections to disconnect
    • Improves VoiceOver navigation in Mail and Finder
    • Provides a fix for SSL connection verification
  • peter_watt Level 3 Level 3 (905 points)

    If item 5 is code for "fixed the bugs that screwed up mail for a small but significant number of business users" then there should not be any new posters coming here and continuing to complain that all was well on ML but now is still not working on Mavericks

Previous 1 40 41 42 43 44 Next