MarkElliott1010

Q: Exchange servers and Mavericks Mail

It loads it when you open the Mail app, but then no new messages will appear in the Exchange inbox while app is open - fetch new mail and the Activity Window show "Synchronizing Inbox" and jsut sits there and waits.. Close the app and reopen - New Mail appears.  Another  bug?

Mac mini (Mid 2011), OS X Mavericks (10.9)

Posted on Oct 23, 2013 7:42 AM

Close

Q: Exchange servers and Mavericks Mail

  • All replies
  • Helpful answers

first Previous Page 25 of 50 last Next
  • by Ray-Monde,

    Ray-Monde Ray-Monde Jan 15, 2014 12:43 PM in response to Foil Man
    Level 1 (5 points)
    Desktops
    Jan 15, 2014 12:43 PM in response to Foil Man

    @foil man

    thanks: I am not an IT expert, and I have exact same issues. Could you please help by explaining how to" remove all of the passwords related to e mail from keychain access" as you suggest. Thks

  • by Foil Man,

    Foil Man Foil Man Jan 15, 2014 1:11 PM in response to Ray-Monde
    Level 1 (0 points)
    Jan 15, 2014 1:11 PM in response to Ray-Monde

    Hello Ray-Monde,

    I am not an expert either but this seemed to work for me.

     

    First step: Go to the Finder and click on applications

    Second step: Find Keychain Access, click on it, probably have to enter your password.

    Third step: go to the login on the left and click on it.

    This will show a list of passwords that it is storing.

    I found ones from the last 5 years that I know I didn't use anymore and deleted them.

    I highly recomend seeing what the password is before you delete it. This way if you still need it you have it.

    Fourth step: Click on Local items and do the same thing that you just did in the login folder.

     

    Then you can exit the Keychain.

    If you have removed the passwords for your email program it will ask you if mail can access your Keychain.

    This requires your password for Keychain

    Enter that and it will take your password from your macmail and store that.

     

    Then I would quite mail and reopen it to make sure it works. Send yourself an email to test.

    Good luck

  • by bradhs,

    bradhs bradhs Jan 15, 2014 2:09 PM in response to MarkElliott1010
    Level 1 (0 points)
    Jan 15, 2014 2:09 PM in response to MarkElliott1010

    Is anyone is having issues with Mail and is on Exchange 2010? My issue is that it won't receive new emails consistently. I'm looking for others that are having this issue.

  • by pnoble,

    pnoble pnoble Jan 15, 2014 2:33 PM in response to bradhs
    Level 1 (0 points)
    Jan 15, 2014 2:33 PM in response to bradhs

    Most people are and it doesn't seem to matter which Exchange release and though some are suggesting and describing solutions as many posts are suggesting that fixes are not permanent.

     

    There are a lot of frustrated Exchange users on this and at least two dozen other discussions: more than 500 posts in all and around 100,000 views, with Apple saying nothing publicly though they seem to have admitted privately to some that there is an issue- so far unresolved despite two Mavericks updates so far, and several months since its initial release.

     

    A lot of frustrated Mail/Exchange users. Outlook is certainly an option. And other mail apps. iOS continues to work perfectly and it has certainly pushed me to rely more on my iPad which isn't such a bad thing.

     

    Does surprise me Apple would be so cavalier with an issue affecting the corporate market they seem so interested in engaging with.

     

    BTW, when using my Mac I monitor inbound email with my iPad and closing and opening Mail tends to fully update the inbox. Re attachments, typically a second attempt to send works. I have Outlook loaded but just prefer using Mail and am really fighting the urge (and pressure) to give up on Mail and switch.

     

    Our sys admin just doesn't want to deal with Apple issues at this point.

  • by randyKates,

    randyKates randyKates Jan 16, 2014 6:15 PM in response to MarkElliott1010
    Level 1 (0 points)
    Jan 16, 2014 6:15 PM in response to MarkElliott1010

    For what its worth they are acknowleding the issue for me.  Here is an email I received today.

     

     

    ******************************************************************************** **************************

     

     

    Hello Randy,

     

    Thank you for your outreach.

     

    I communicated with my local Engineer here yesterday and I've requested that he speak to Corporate Engineering and obtain a updated response that I can provide you. I apologize the ticket is in a realm that I can not always obtain "Live" updates from, so I'm currently not able to provide you with a exact status update at this time.  Corporate Engineering I assure you is working on the issue, I cannot comment on a ETA to resolution as I'm not in the loop on what they've found at this time.

     

    The moment I have a updated response, which I'm hoping is this week, I will be happy to relay that to you.

     

     

     

    On Jan 15, 2014, at 6:38 AM, Randy Kates wrote:



    Please provide me some details of what is going on with my data and when we can expect a possible solution.

    Sent from my iPhone


    On Jan 2, 2014, at 4:45 PM, Michael  wrote:

     

    <Personal Information Edited by Host>

  • by randyKates,

    randyKates randyKates Jan 15, 2014 3:14 PM in response to randyKates
    Level 1 (0 points)
    Jan 15, 2014 3:14 PM in response to randyKates

    Good news.

     

    I just received a phone call from my liaison at Apple and I will be joining their SEED program and working with some Alpha and Beta batches for this fix. I agreed to do this so that I can be actively involved in getting this resolved.

     

    We also discussed about getting the level 1 technicians to notify callers that there is a known issue with Exchange and to then take the information and escalate to the engineers.  They said they would make this request and it should happen.  They did acknowledge to me that this is a real issue and that they have not gone public with it yet.

     

    By the end of the week I should be part of the Seed program and will begin to apply some of the alpha or beta batches they have been working on.

     

    By the way all these temp fixes you all are finding although not permanent may help them in resolving the issue faster.

     

    I will keep you all up to date as best as I can.


    Randy

  • by randyKates,

    randyKates randyKates Jan 15, 2014 3:14 PM in response to MarkElliott1010
    Level 1 (0 points)
    Jan 15, 2014 3:14 PM in response to MarkElliott1010

    Good news.

     

    I just received a phone call from my liaison at Apple and I will be joining their SEED program and working with some Alpha and Beta batches for this fix. I agreed to do this so that I can be actively involved in getting this resolved.

     

    We also discussed about getting the level 1 technicians to notify callers that there is a known issue with Exchange and to then take the information and escalate to the engineers.  They said they would make this request and it should happen.  They did acknowledge to me that this is a real issue and that they have not gone public with it yet.

     

    By the end of the week I should be part of the Seed program and will begin to apply some of the alpha or beta batches they have been working on.

     

    By the way all these temp fixes you all are finding although not permanent may help them in resolving the issue faster.

     

    I will keep you all up to date as best as I can.


    Randy

  • by bradhs,

    bradhs bradhs Jan 15, 2014 3:45 PM in response to randyKates
    Level 1 (0 points)
    Jan 15, 2014 3:45 PM in response to randyKates

    That's great randyKates! By chance, did you contact Apple via consumer or developer channels?  I'd like to join in on the seed and help.  I've got access to a bunch of Exchange servers and can help.

  • by bradhs,

    bradhs bradhs Jan 17, 2014 7:52 AM in response to pnoble
    Level 1 (0 points)
    Jan 17, 2014 7:52 AM in response to pnoble

    Hi pnoble, I was able to resolve the issue for John. 

     

    While I am still having issues, those issues are related to Mail and not Exchange server.  Most people on this thread seem to be having issues because their Exchange servers are not setup properly.  This is just my observations as I have already resolved the issue for a few others and each time it was Exchange not configured or patched properly.  And, while I have resolved the issue for some, they end up having the same issue some of us are still facing and what randyKates and others have gotten Apple to acknowldege.

     

    Also, as a side note, Exchange has many releases, each one requires different steps to configure propertly and also, as devlopers, to program/interface.  I'm sure Apple has invested a lot of time just to support Exchange 2003, 2007, 2010 and now 2013 and all the various Serive Packs in between.

     

    <Email Edited by Host>

  • by randyKates,

    randyKates randyKates Jan 17, 2014 7:53 AM in response to bradhs
    Level 1 (0 points)
    Jan 17, 2014 7:53 AM in response to bradhs

    I got into it by emailng and then heard back a few days later from a high level technican. 

     

    Randy

     

    <Edited By Host>

  • by pnoble,

    pnoble pnoble Jan 15, 2014 5:48 PM in response to bradhs
    Level 1 (0 points)
    Jan 15, 2014 5:48 PM in response to bradhs

    Thank you, Randy. I am copying our sys admin on your email. Much obliged. Meanwhile, as I think he will confirm, although Exchange + Mail has always been a struggle, updating to Mavericks is what caused this intractable problem. So, yes, it seems to be a Mail issue, and if there is a resolution or workaround, why in **** hasn't Apple published it? After 3-4 months?

  • by stevenzac,

    stevenzac stevenzac Jan 15, 2014 6:06 PM in response to pnoble
    Level 1 (4 points)
    Jan 15, 2014 6:06 PM in response to pnoble

    I had spoken to tech support for about three hours when Mavericks first came out about the problem of the sub folders not showing in the inbox.....the last time I called at least after half an hour they admitted there were known issues.  I just can't imagine how Apple didn't test this with Exchange before releasing Mavericks.  It's truly unbelievable to me.  Someone had said most beta testers aren't business people using Exchange, but that's just a load of an excuse.  Exchange is the defacto standard for office environments so Mail should be 100% compatible.

     

    The other thing that sort of aggravates me is everyone complaining about Outlook for Mac.  While I definitely admit that it's not nearly as advanced or nice looking as Outlook 2013 for Windows, it's a perfectly functionable program and it has email, calendar and contacts all in one program.  So what's the problem with it versus Mail, iCal and Contacts?

  • by peter_watt,

    peter_watt peter_watt Jan 16, 2014 2:29 AM in response to Ray-Monde
    Level 3 (910 points)
    Jan 16, 2014 2:29 AM in response to Ray-Monde

    Ray-monde, follow foil man's advice but  you will also find the passwords for the email servers in the icloud section of keychain.

  • by peter_watt,

    peter_watt peter_watt Jan 16, 2014 2:31 AM in response to stevenzac
    Level 3 (910 points)
    Jan 16, 2014 2:31 AM in response to stevenzac

    It was I who said typical beta testers are not business people. It was not intended as an excuse, rather a complaint that business activities are not tested enough - ie I agree with you.

  • by Edvard in Bromma,

    Edvard in Bromma Edvard in Bromma Jan 16, 2014 4:15 AM in response to MarkElliott1010
    Level 1 (0 points)
    Jan 16, 2014 4:15 AM in response to MarkElliott1010

    Hi

    I have the same problem. Users can't send mail from Apple mail. We have Exchange 2010 with latest updates.

     

    Sometimes it helps to restart the server.

     

    Does anyone have any workaround until Apple come with a permanent fix

     

    BR

    Edvard

first Previous Page 25 of 50 last Next